Searched refs:builds (Results 76 – 100 of 191) sorted by relevance
12345678
| /Zephyr-latest/tests/drivers/build_all/ethernet/ |
| D | spi_devices.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/tests/arch/arm/arm_interrupt/ |
| D | README.txt | 46 ninja/make clean # discard results of previous builds
49 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/cmake/modules/ |
| D | FindGnuLd.cmake | 28 # GNULD_LINKER exists on repeated builds or defined manually...
|
| D | user_cache.cmake | 8 # across builds to speed up CMake configure / build system generation and/or
|
| D | zephyr_default.cmake | 55 # It seems only pip-installed builds are affected so we test to see if we are affected
|
| /Zephyr-latest/samples/subsys/testsuite/pytest/shell/ |
| D | README.rst | 12 A simple application provides basic Zephyr shell interface. Twister builds it
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | fifos.rst | 96 The following code builds on the example above, and uses the FIFO
134 The following code builds on the example above, and uses the FIFO
|
| D | message_queues.rst | 107 The following code builds on the example above, and uses the message queue
138 The following code builds on the example above, and uses the message queue
|
| /Zephyr-latest/tests/drivers/build_all/sensor/ |
| D | app.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 67 For new builds, the ``--board`` option, :envvar:`BOARD` environment variable,
70 .. _west-multi-domain-builds:
72 Sysbuild (multi-domain builds)
168 byproducts from previous builds have been removed.
216 generated. This will make incremental builds slower (but still much faster
220 <build-dir>`` on subsequent runs to do incremental builds.
223 section; it will not slow down incremental builds.
540 When a :ref:`west-multi-domain-builds` folder is detected, then ``west flash``
658 :ref:`west-multi-domain-builds` folder is detected, ``west debug``
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | mutexes.rst | 122 The following code builds on the example above, and waits indefinitely
145 The following code builds on the example above,
|
| D | condvar.rst | 99 The following code builds on the example above.
|
| /Zephyr-latest/arch/common/ |
| D | Kconfig | 65 execute code from SRAM in XIP builds.
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/doc/ |
| D | index.rst | 249 sample currently enabled for dual core builds is the ``openamp`` sample.
254 The secondary core can be debugged normally in single core builds
255 (where the target is ``mimxrt1160_evk/mimxrt1166/cm4``). For dual core builds, the
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 88 .. [#f2] Stack limit checking only in Secure builds in Cortex-M23
105 builds with user mode support.
115 In Arm Cortex-M builds a single interrupt stack memory is shared among exceptions and interrupts. T…
124 In Arm Cortex-M builds, the PendSV exception is used in order to trigger a context switch to a diff…
253 HW interrupts in Mainline Cortex-M builds are allocated a priority level lower than the SVC.
257 interrupt. If the ZLI feature is enabled in Mainline Cortex-M builds (see
281 Cortex-M builds select :kconfig:option:`CONFIG_CPU_CORTEX_M_HAS_BASEPRI` to signify that BASEPRI re…
306 Cortex-M builds support the installation of direct interrupt service routines during
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 120 The :ref:`native_sim <native_sim>` target builds your Zephyr application
154 With the :ref:`nrf52_bsim <nrf52_bsim>`, typically you do :ref:`Combined builds
|
| /Zephyr-latest/cmake/compiler/gcc/ |
| D | target.cmake | 128 # are unused during "real" builds of Zephyr source files linked into
|
| /Zephyr-latest/boards/st/stm32h735g_disco/doc/ |
| D | index.rst | 73 See :ref:`build_an_application` for more information about application builds.
|
| /Zephyr-latest/tests/drivers/build_all/dac/ |
| D | app.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 67 Then build the sample as follows, don't forget, two builds are necessary
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/doc/ |
| D | index.rst | 325 sample currently enabled for dual core builds is the ``openamp`` sample.
330 The secondary core can be debugged normally in single core builds
331 (where the target is ``mimxrt1170_evk/mimxrt1176/cm4``). For dual core builds, the
|
| /Zephyr-latest/boards/arduino/portenta_h7/doc/ |
| D | index.rst | 73 See :ref:`build_an_application` for more information about application builds.
|
| /Zephyr-latest/boards/arduino/nicla_vision/doc/ |
| D | index.rst | 73 See :ref:`build_an_application` for more information about application builds.
|
| /Zephyr-latest/soc/sensry/ganymed/sy1xx/common/ |
| D | linker.ld | 26 * jumping distance of the vector table in non-XIP builds, so avoid them.
|
| /Zephyr-latest/boards/st/stm32h750b_dk/doc/ |
| D | index.rst | 73 See :ref:`build_an_application` for more information about application builds.
|
12345678
