Searched refs:builds (Results 51 – 75 of 191) sorted by relevance
12345678
/Zephyr-latest/tests/arch/arm/arm_thread_swap/ |
D | README.txt | 61 ninja/make clean # discard results of previous builds 64 ninja/make pristine # discard results of previous builds
|
/Zephyr-latest/tests/drivers/build_all/w1/ |
D | app.overlay | 6 * Application overlay for testing driver builds
|
/Zephyr-latest/tests/ztest/fail/ |
D | README.rst | 10 There's a subdirectory to this test called 'core'. This project builds a sample as a
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | features.rst | 27 Controller builds: 49 * Support for Controller (HCI) builds over different physical transports
|
D | bluetooth-arch.rst | 93 Bluetooth-enabled builds that can be produced from the Zephyr project codebase: 129 used for Controller-only builds can be built as Host-only 142 used for Controller-only builds can be built as Combined 159 :alt: Bluetooth dual-chip configuration builds 161 Host-only and Controller-only builds on dual-chip configurations
|
/Zephyr-latest/tests/drivers/build_all/led_strip/ |
D | app.overlay | 7 * Application overlay for testing driver builds
|
/Zephyr-latest/tests/drivers/build_all/video/ |
D | app.overlay | 6 * Application overlay for testing driver builds
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | Kconfig.tfm | 200 secure + non-secure builds (TFM_MCUBOOT_IMAGE_NUMBER == 1). 268 non-secure builds (TFM_MCUBOOT_IMAGE_NUMBER == 1). 292 Path to MCUboot for TF-M builds. The default option 296 build time. The default option ensures that Zephyr builds 302 TF-M builds with BL2 will use the Zephyr's MCUboot version, 308 TF-M builds with BL2 will let the TF-M build to automatically 318 Path to a locally available Ethos-U driver to be used for TF-M builds or 330 Path to QCBOR for TF-M builds. Due to a license issue with this
|
/Zephyr-latest/tests/drivers/build_all/eeprom/ |
D | app.overlay | 6 * Application overlay for testing driver builds
|
/Zephyr-latest/doc/develop/optimizations/ |
D | footprint.rst | 50 This option can be enabled for debug builds.
|
/Zephyr-latest/tests/drivers/build_all/led/ |
D | app.overlay | 6 * Application overlay for testing driver builds
|
/Zephyr-latest/doc/kernel/object_cores/ |
D | index.rst | 123 code builds on the example above and initializes the object core. 141 :c:func:`k_obj_type_walk_unlocked`. The following code builds upon the example 174 The following code builds on the examples above and shows how an object
|
/Zephyr-latest/doc/kernel/services/synchronization/ |
D | semaphores.rst | 83 The following code builds on the example above, and gives the semaphore to 101 The following code builds on the example above, and waits up to 50 milliseconds
|
/Zephyr-latest/tests/kernel/context/ |
D | README.txt | 71 make clean # discard results of previous builds 74 make pristine # discard results of previous builds
|
/Zephyr-latest/share/sysbuild/cmake/modules/ |
D | native_simulator_sb_extensions.cmake | 15 # this final executable in the same place as for non-sysbuild builds.
|
D | sysbuild_root.cmake | 22 # correctly to image builds.
|
/Zephyr-latest/ |
D | .gitignore | 69 # Normal west builds will place the Rust target directory under the build directory. However,
|
/Zephyr-latest/cmake/compiler/armclang/ |
D | target.cmake | 9 # are unused during "real" builds of Zephyr source files linked into
|
/Zephyr-latest/doc/kernel/services/data_passing/ |
D | stacks.rst | 91 The following code builds on the example above, and shows how a thread 114 The following code builds on the example above, and shows how a thread
|
D | lifos.rst | 87 The following code builds on the example above, and uses the LIFO 122 The following code builds on the example above, and uses the LIFO
|
/Zephyr-latest/cmake/compiler/arcmwdt/ |
D | target.cmake | 8 # are unused during "real" builds of Zephyr source files linked into
|
/Zephyr-latest/soc/mediatek/mt8xxx/ |
D | CMakeLists.txt | 17 # available; generally it isn't except in SOF builds). Note that the
|
/Zephyr-latest/cmake/compiler/xcc/ |
D | target.cmake | 66 # are unused during "real" builds of Zephyr source files linked into
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | slabs.rst | 104 The following code builds on the example above, and waits up to 100 milliseconds 124 The following code builds on the example above, and allocates a memory block,
|
/Zephyr-latest/arch/arm/core/mpu/ |
D | Kconfig | 18 A minimum 4-byte alignment is enforced in ARM builds without
|
12345678