Searched full:builds (Results 176 – 200 of 262) sorted by relevance
1234567891011
208 # to ASM builds (which may use 'stdbool.h').
6 * Application overlay for testing driver builds
484 * Builds a list of all known Subnet indexes in the @c net_idxs array.592 * Builds a list of all Application indexes for the given network index in the
33 - CI sees the tag, builds and runs tests; Test teams analyse the report from the212 automated builds and CI tools.
7 # It builds signed binaries using imgtool as a post-processing step
88 /* Vectors according to builds/RF-2015.2-win32/esp108_v1_2_s5_512int_2/config.html */
82 /* Vectors according to builds/RF-2015.2-win32/esp108_v1_2_s5_512int_2/config.html */
91 /* Vectors according to builds/RF-2015.2-win32/esp108_v1_2_s5_512int_2/config.html */
108 "The script needs Zephyr repository there to read SHA and commit time of builds. "
194 * the associated object that builds up the record. in bt_ots_dir_list_search()
163 See :ref:`build_an_application` for more information about application builds.
583 your project's :file:`CMakeLists.txt` to let Zephyr find your header file during builds.602 tests. For native simulator builds you can provide the seed as an argument to
65 provided in the ``testcase.yaml`` file, Twister builds the application from ``src`` and then, if the
214 * :github:`1332` - sanitycheck builds too many duplicates in CI, make it smarter321 * :github:`3682` - incremental builds do not work properly in Windows503 * :github:`5008` - system call headers are not properly regenerated in CMake on incremental builds
257 * ``ZEP-689`` - Builds on em_starterkit fail
222 project's CI infrastructure that builds and optionally executes tests and samples
138 * lead to system crash in TrustZone enabled Non-Secure builds. in ZTEST_USER()
43 * href="https://openthread.io">OpenThread</a> stack into Zephyr. It builds upon
232 * builds; Zephyr running in Non-Secure mode will generate SecureFault in ZTEST_USER()
23 * For builds using XIP, there is a different load memory address (LMA) and
6 Sysbuild can be used to add additional images to builds, these can be added by projects or boards
80 method scans format string and based on detected format specifiers builds the
325 sample currently enabled for dual core builds is the ``openamp`` sample.330 The secondary core can be debugged normally in single core builds331 (where the target is ``mimxrt1170_evk/mimxrt1176/cm4``). For dual core builds, the
