Searched full:builds (Results 151 – 175 of 262) sorted by relevance
1234567891011
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | pipes.rst | 130 The following example builds on the producer thread example above. It shows
|
| /Zephyr-latest/drivers/cache/ |
| D | cache_nrf.c | 135 * Trustzone secure builds. in _cache_range()
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 17 or other types of builds you want to run.
93 Here is an example. For details, see :ref:`west-multi-domain-builds` in
113 Since sysbuild supports both single- and multi-image builds, this lets you
355 This builds ``hello_world`` and ``mcuboot`` for the ``reel_board``, and then
|
| /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/boards/phytec/phyboard_electra/doc/ |
| D | index.rst | 114 This builds the program and the binary is present in the :file:`build/zephyr` directory as
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 96 The MT8195 toolchain is already part of the Zephyr SDK, so builds for
|
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | linker.ld | 23 * jumping distance of the vector table in non-XIP builds, so avoid them.
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 21 By default the controller builds use the following settings:
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | README.rst | 21 By default the controller builds use the following settings:
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 161 builds. To change the Zephyr package, for example to test the application using Zephyr base
252 This can be useful to avoid accidental builds when only part of a workspace has been
|
| /Zephyr-latest/scripts/ |
| D | twister | 37 builds.
|
| /Zephyr-latest/boards/arduino/opta/doc/ |
| D | index.rst | 102 See :ref:`build_an_application` for more information about application builds.
|
| /Zephyr-latest/boards/phytec/phyboard_lyra/doc/ |
| D | phyboard_lyra_am62xx_m4.rst | 108 This builds the program and the binary is present in the :file:`build/zephyr` directory as
|
| /Zephyr-latest/doc/services/retention/ |
| D | index.rst | 15 The retention system builds on top of the retained data driver, and adds
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 155 introducing both secure and non-secure builds for platforms with Trusted
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 25 There are a few reasons why twister only builds a test and doesn't run it:
369 are only run under certain circumstances, like daily builds. These test
429 actually builds. A ``build_only`` test is not designed to be run in any
431 that the code builds.
434 enabled in Zephyr and that the code builds, for example sensor drivers. Such
1083 the scope of builds and tests if applicable to platforms defined under the
|
| /Zephyr-latest/scripts/native_simulator/ |
| D | Makefile | 5 # It builds the simulator runner itself, and produces the final
|
| /Zephyr-latest/tests/subsys/logging/dictionary/pytest/ |
| D | test_logging_dictionary.py | 121 the decoded log lines for FPU 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/ |
| D | Kconfig.zephyr | 693 control over this can be useful for reproducible builds
716 from the build process. Note this breaks incremental builds, west spdx
967 failure logs more deterministic and most importantly makes builds more
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 569 following code builds on the examples above and publishes to channel ``acc_chan``. The code is
611 For example, the following code builds on the examples above and forces a notification for the
630 channel or observer on the same call. The following code builds on the examples above and displays
811 The following code builds on the examples above and claims the ``acc_chan`` to set the ``user_data``
|
| /Zephyr-latest/samples/subsys/usb_c/sink/src/ |
| D | main.c | 50 * @brief Builds a Request Data Object (RDO) with the following properties:
|
| /Zephyr-latest/include/zephyr/drivers/firmware/scmi/ |
| D | util.h | 21 * Given a protocol ID, this macro builds the protocol
|
| /Zephyr-latest/arch/arm/core/ |
| D | Kconfig | 83 Thumb-2 technology builds on the success of Thumb, the innovative
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 105 In-source builds are not supported.\
|
1234567891011
