Searched full:build (Results 1976 – 2000 of 2206) sorted by relevance
1...<<71727374757677787980>>...89
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | handlers.py | 169 # Load domain yaml to get default domain build directory
1050 # QEMU fifo will use main build dir
1052 # PID file will be created in the main sysbuild app's build dir
1233 # PID file will be created in the main sysbuild app's build dir
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.7.rst | 18 Build System
25 * The following build-time generated headers:
280 binding to indicate invalid devicetree values at build time. (:github:`69910`)
822 interface. It is now being enforced through a build-time assertion.
|
| /Zephyr-latest/boards/u-blox/ubx_bmd345eval/doc/ |
| D | index.rst | 420 found in :ref:`nordic_segger_flashing`. Then build and flash
435 Then build and flash the application in the usual way.
440 :goals: build flash
460 You can build and flash the examples to make sure Zephyr is running
|
| /Zephyr-latest/scripts/build/ |
| D | gen_kobject_list.py | 24 The zephyr build generates an intermediate ELF binary, zephyr_prebuilt.elf,
27 kernel objects. For device drivers, the API struct pointer populated at build
843 # either completely initialized at build time, or done automatically
|
| /Zephyr-latest/doc/develop/west/ |
| D | release-notes.rst | 178 - the deprecated ``west.build`` module used for Zephyr v1.14 LTS compatibility was
214 itself usually appeared when running an extension command like ``west build``
634 - west.build and west.cmake: deprecated; this is Zephyr-specific functionality
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 146 | | | 4 B: Build number |
281 build the Distributor's receivers list, and a Firmware Distribution Receivers Delete All message to
|
| /Zephyr-latest/include/zephyr/toolchain/ |
| D | gcc.h | 365 * So that the build tool could mark them as an entry point to be linked
506 * GEN_ABSOLUTE_SYM_KCONFIG() is outputted by the build system
|
| /Zephyr-latest/soc/espressif/esp32c2/ |
| D | mcuboot.ld | 21 /* Global symbols required for espressif hal build */
|
| /Zephyr-latest/soc/espressif/esp32c3/ |
| D | mcuboot.ld | 21 /* Global symbols required for espressif hal build */
|
| /Zephyr-latest/soc/espressif/esp32c6/ |
| D | mcuboot.ld | 21 /* Global symbols required for espressif hal build */
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/ |
| D | hardware_adapter.py | 47 '--build-dir', str(self.device_config.build_dir),
|
| /Zephyr-latest/include/zephyr/arch/riscv/ |
| D | arch.h | 81 * generated at build time by gen_kobject_list.py
|
| /Zephyr-latest/boards/96boards/neonkey/doc/ |
| D | index.rst | 143 :goals: build
|
| /Zephyr-latest/arch/x86/ |
| D | gen_idt.py | 14 which is a link of the Zephyr kernel without various build-time
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/doc/ |
| D | index.rst | 167 …west flash -r trace32 --startup-args elfFile=build/zephyr/zephyr.elf loadTo=flash eraseFlash=yes v…
|
| /Zephyr-latest/include/zephyr/kernel/ |
| D | mm.h | 169 * at build time.
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | nordic_segger.rst | 232 file that you can find in your build folder.
|
| /Zephyr-latest/samples/kernel/condition_variables/simple/ |
| D | README.rst | 33 To build for another board, change ``native_sim`` above to that board's name.
|
| /Zephyr-latest/boards/snps/hsdk/doc/ |
| D | index.rst | 11 Development System SoC. This allows developers to build and debug complex
404 You can build an application in the usual way. Refer to
412 :goals: build
444 One option is to build and debug the application using the usual
445 Zephyr build system commands.
463 console, from the build directory containing the output :file:`zephyr.elf`.
|
| /Zephyr-latest/boards/olimex/stm32_h407/doc/ |
| D | index.rst | 314 of the OLIMEX-STM32-H407 board. Then build and flash an application.
321 :goals: build flash
333 ***** BOOTING ZEPHYR OS v1.11.0 - BUILD: Mar 12 2018 03:12:40 *****
|
| /Zephyr-latest/boards/olimex/olimexino_stm32/doc/ |
| D | index.rst | 360 To build the stm32flash tool, follow the steps below:
369 #. Build the stm32flash tool.
391 #. To build the application and flash it, enter:
|
| /Zephyr-latest/boards/olimex/stm32_e407/doc/ |
| D | index.rst | 308 the OLIMEX-STM32-E407 board. Then build and flash an application.
315 :goals: build flash
327 ***** BOOTING ZEPHYR OS v1.8.99 - BUILD: May 29 2017 22:31:53 *****
|
| /Zephyr-latest/soc/espressif/common/ |
| D | loader.c | 112 /* Traverse segments to fix flash offset changes due to post-build processing */ in map_rom_segments()
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_mdb.py | 138 # replacing its build directory with 'tmpdir' after writing
|
| /Zephyr-latest/drivers/sensor/st/stm32_temp/ |
| D | stm32_temp.c | 288 * fail build with an explicit error message.
|
1...<<71727374757677787980>>...89
