/Zephyr-latest/subsys/bindesc/ |
D | Kconfig.version | 14 The kernel version string, such as "3.4.0" 19 The major version number, such as 3 in 3.4.0 24 The minor version number, such as 4 in 3.4.0 29 The patchlevel version number, such as 0 in 3.4.0 34 The kernel version as binary coded decimal, computed as 36 3.4.0 would be represented as 0x30400 41 The kernel git reference, such as "v3.3.0-18-g2c85d9224fca", 47 The app version string, such as "1.0.0" 52 The app major version number, such as 1 in 1.0.0 57 The app minor version number, such as 0 in 1.0.0 [all …]
|
D | Kconfig.build_time | 28 The year the image was compiled, such as 2023 33 The month the image was compiled, such as 5 (May) 38 The day of the month the image was compiled, such as 9 43 The hour of the day the image was compiled, such as 13 in 13:34:52 48 The minute the image was compiled, such as 34 in 13:34:52 53 The second the image was compiled, such as 52 in 13:34:52 56 bool "Build time as UNIX time" 62 bool "Build date and time as string" 64 The date and time of compilation as a string, such as "2023-09-29T17:43:14+0000" 67 bool "Build date as string" [all …]
|
D | Kconfig.host_info | 19 The C compiler name, such as "GNU" 24 The C compiler version, such as "12.3.0" 29 The C++ compiler name, such as "GNU" 34 The C++ compiler version, such as "12.3.0"
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/figures/ |
D | integration_diagram_detailed.drawio | 8 <mxGeometry x="516" y="-192" width="465" height="407" as="geometry" /> 11 <mxGeometry x="544" y="260" width="310" height="177" as="geometry" /> 14 <mxGeometry x="646" y="-68" width="164" height="30" as="geometry" /> 17 <mxGeometry x="285" y="-122" width="116" height="559" as="geometry" /> 20 <mxGeometry x="634" y="273" width="208" height="75" as="geometry" /> 23 <mxGeometry x="641" y="289" width="60" height="30" as="geometry" /> 26 <mxGeometry x="775" y="289" width="60" height="30" as="geometry" /> 29 <mxGeometry x="708" y="289" width="60" height="30" as="geometry" /> 32 <mxGeometry x="634" y="361" width="208" height="70" as="geometry" /> 35 <mxGeometry x="641" y="389" width="60" height="30" as="geometry" /> [all …]
|
D | integration_diagram_simplified.drawio | 8 <mxGeometry x="527" y="-207" width="195" height="261" as="geometry" /> 11 <mxGeometry x="574" y="-81" width="164" height="30" as="geometry" /> 14 <mxGeometry x="271" y="-122" width="116" height="348" as="geometry" /> 17 <mxGeometry x="714" y="173" width="108" height="51" as="geometry" /> 20 <mxGeometry x="584" y="22" width="164" height="30" as="geometry" /> 23 <mxGeometry x="596" y="128" width="164" height="30" as="geometry" /> 26 <mxGeometry x="397" y="208" width="164" height="30" as="geometry" /> 29 <mxGeometry relative="1" as="geometry" /> 32 <mxGeometry x="552" y="-35" width="147" height="50" as="geometry" /> 35 <mxGeometry relative="1" as="geometry" /> [all …]
|
/Zephyr-latest/arch/xtensa/include/ |
D | xtensa_mpu_priv.h | 115 .as.p.enable = en, \ 116 .as.p.lock = 0, \ 117 .as.p.mbz = 0, \ 118 .as.p.start_addr = (saddr >> XTENSA_MPU_ENTRY_START_ADDR_SHIFT), \ 201 return (entry->as.p.start_addr << XTENSA_MPU_ENTRY_REG_START_ADDR_SHIFT); in xtensa_mpu_entry_start_address_get() 213 entry->as.p.start_addr = addr >> XTENSA_MPU_ENTRY_REG_START_ADDR_SHIFT; in xtensa_mpu_entry_start_address_set() 227 return entry->as.p.lock != 0; in xtensa_mpu_entry_lock_get() 239 entry->as.p.lock = lock ? 1 : 0; in xtensa_mpu_entry_lock_set() 253 return entry->as.p.enable != 0; in xtensa_mpu_entry_enable_get() 265 entry->as.p.enable = en ? 1 : 0; in xtensa_mpu_entry_enable_set() [all …]
|
/Zephyr-latest/samples/net/lwm2m_client/ |
D | Kconfig | 12 This is used as client endpoint name as well as PSK ID. 20 PSK key as a hex string. 38 LwM2M server address. Write as a full URI including optional port number. 40 When DNS resolver is enabled, DNS domain names could be used as well.
|
/Zephyr-latest/samples/drivers/dac/ |
D | README.rst | 24 :zephyr:board:`nucleo_l073rz` as follows: 35 :zephyr:board:`nucleo_l152re` as follows: 46 :zephyr:board:`nucleo_f767zi` as follows: 57 :zephyr:board:`stm32f3_disco` as follows: 68 :zephyr:board:`nucleo_f429zi` as follows: 79 :zephyr:board:`stm32l562e_dk` as follows: 90 :zephyr:board:`nucleo_l552ze_q` as follows: 100 The sample can be built and executed for the :zephyr:board:`twr_ke18f` as 114 The sample can be built and executed for the :zephyr:board:`frdm_k64f` as 127 The BL652 DVK PCB contains a footprint for a MCP4725 to use as an external [all …]
|
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
D | README.rst | 2 :name: GPIO as a wake-up pin source 5 Use a GPIO as a wake-up pin source. 10 This sample is a minimum application to demonstrate using a wake-up pin with a GPIO as 14 Press the user button designated in boards's devicetree overlay as "wkup-src" to power it on again. 16 .. _gpio-as-a-wkup-pin-src-sample-requirements: 29 Build and flash wkup_pins as follows, changing ``nucleo_u5a5zj_q`` for your board:
|
/Zephyr-latest/doc/hardware/peripherals/audio/ |
D | i2s.rst | 10 as well as common non-standard extensions such as PCM Short/Long Frame Sync
|
/Zephyr-latest/share/sysbuild/template/ |
D | CMakeLists.txt | 5 # Generic sysbuild CMakeLists.txt file used as sysbuild entry point for multi-image builds. 8 # file to the folder `<app-dir>/sysbuild` and use as a template and extend as needed.
|
/Zephyr-latest/lib/posix/options/ |
D | Kconfig.device_io | 15 Group such as FD_CLR(), FD_ISSET(), FD_SET(), FD_ZERO(), close(), fdopen(), fileno(), open(), 24 # implementations such as those in Newlib or Picolibc. 29 When selected via Kconfig, Zephyr will provide an alias for close() as _close(). 34 When selected via Kconfig, Zephyr will provide an alias for open() as _open(). 39 When selected via Kconfig, Zephyr will provide an alias for read() as _read(). 44 When selected via Kconfig, Zephyr will provide an alias for write() as _write().
|
D | Kconfig.fd_mgmt | 18 # implementations such as those in Newlib or Picolibc. 23 When selected via Kconfig, Zephyr will provide an alias for fcntl() as _fcntl(). 28 When selected via Kconfig, Zephyr will provide an alias for ftruncate() as _ftruncate(). 33 When selected via Kconfig, Zephyr will provide an alias for lseek() as _lseek().
|
/Zephyr-latest/tests/kernel/context/ |
D | README.txt | 5 This test verifies that the kernel CPU and context APIs operate as expected. 53 be tested in the same way as irq_lock() and irq_unlock(). 60 on QEMU as follows: 101 got thread (q order: 2, t/o: 500) as expected 103 got thread (q order: 3, t/o: 750) as expected 105 got thread (q order: 0, t/o: 1000) as expected 107 got thread (q order: 6, t/o: 1250) as expected 109 got thread (q order: 1, t/o: 1500) as expected 111 got thread (q order: 4, t/o: 1750) as expected 113 got thread (q order: 5, t/o: 2000) as expected [all …]
|
/Zephyr-latest/doc/hardware/arch/ |
D | risc-v.rst | 8 Currently, there's support for some boards, as well as Qemu support 9 and support for some FPGA implementations such as neorv32 and 13 ISA extensions as well as :ref:`semihosting<semihost_guide>`.
|
/Zephyr-latest/cmake/ |
D | verify-toolchain.cmake | 5 # other tools, such as twister / python scripts. 7 # When invoked as a script with -P: 11 # FORMAT=json: Print the output as a json formatted string, useful for Python 17 "as:\n 'cmake ... -P verify-toolchain.cmake'\n" 23 # all other messages as only the specified output should be printed.
|
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/philosophers/ |
D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping 18 are shown as well, such as STARVING when the philosopher is hungry but the 29 on QEMU as follows: 56 priorities, as well as semaphores and thread sleeping.
|
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping 18 are shown as well, such as STARVING when the philosopher is hungry but the 29 on QEMU as follows: 56 priorities, as well as semaphores and thread sleeping.
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | charger.rst | 9 system as an input and provide power as an output downstream to the battery pack(s) and system. 10 The charger device can exist as a module, an integrated circuit, or as a functional block in a power 13 The action of charging a battery pack is referred to as a charge cycle. When the charge cycle is 34 Chargers typically support multiple properties, such as temperature readings of the battery-pack
|
/Zephyr-latest/tests/posix/eventfd/ |
D | Kconfig | 31 In order to get a true benchmark, there should be as few branches 32 as possible on the hot path. Say 'y' here to add extra assertions 33 on the hot path as well to verify functionality. 38 In order to get a true benchmark, there should be as few branches 39 as possible on the hot path. Say 'y' here to skip reporting.
|
/Zephyr-latest/boards/nxp/rd_rw612_bga/ |
D | pre_dt_board.cmake | 4 # Suppress "spi_bus_bridge" as flexcomm node can be used as a SPI device.
|
/Zephyr-latest/boards/nxp/frdm_rw612/ |
D | pre_dt_board.cmake | 4 # Suppress "spi_bus_bridge" as flexcomm node can be used as a SPI device.
|
/Zephyr-latest/share/sysbuild/build/ |
D | Kconfig | 6 bool "Treat warnings as errors" 8 Turn on "warning as error" toolchain flags for all images if set.
|
/Zephyr-latest/tests/kernel/smp/ |
D | Kconfig | 9 int "Run factor for stressing tests, such as 'switch torture', \ 10 as a percentage"
|
/Zephyr-latest/samples/sysbuild/with_mcuboot/ |
D | README.rst | 9 automatically include MCUboot as the bootloader. 16 This sample automatically includes MCUboot as bootloader when built using 25 The :file:`sysbuild/mcuboot.conf` file will be used as an extra fragment that 28 :file:`sysbuild/mcuboot.conf` adjusts the log level in MCUboot, as well as
|