Searched full:build (Results 76 – 100 of 2206) sorted by relevance
12345678910>>...89
| /Zephyr-latest/doc/services/llext/ |
| D | debug.rst | 25 2. Build the Zephyr application and the extensions.
27 For each target ``name`` included in the current build, two files will be
28 generated into the ``llext`` subdirectory of the build root:
40 build configuration.
128 The following command will build the project and start the emulator in
132 :caption: Terminal 1 (build, QEMU emulator, GDB server)
134 zephyr$ west build -p -b mps2/an385 tests/subsys/llext/ -T llext.writable -t debugserver_qemu
135 -- west build: generating a build system
137 -- west build: running target debugserver_qemu
148 zephyr$ ${LLEXT_SDK_INSTALL_DIR}/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb build/zephyr/zephyr.elf
[all …]
|
| /Zephyr-latest/boards/khadas/edgev/doc/ |
| D | index.rst | 33 :goals: build
35 This will build an image with the synchronization sample app.
37 Build the zephyr image:
41 …mkimage -C none -A arm64 -O linux -a 0x10000000 -e 0x10000000 -d build/zephyr/zephyr.bin build/zep…
53 *** Booting Zephyr OS build XXXXXXXXXXXX ***
|
| /Zephyr-latest/lib/libc/newlib/ |
| D | Kconfig | 7 bool "Build with newlib-nano C library"
10 Build with newlib-nano library, for small embedded apps.
49 bool "Build with newlib float printf"
51 Build with floating point printf enabled. This will increase the size of
55 bool "Build with newlib float scanf"
57 Build with floating point scanf enabled. This will increase the size of
|
| /Zephyr-latest/samples/boards/st/h7_dual_core/ |
| D | README.rst | 14 Build for stm32h747i_disco/stm32h747xx/m7:
19 :goals: build
21 Build for stm32h747i_disco/stm32h747xx/m4:
26 :goals: build
|
| /Zephyr-latest/samples/sensor/bme280/ |
| D | README.rst | 40 sure this node has ``status = "okay";``, then build and run with:
44 :goals: build flash
50 If you wired the sensor to a SPI peripheral on an Arduino header, build and
55 :goals: build flash
65 If you wired the sensor to an I2C peripheral on an Arduino header, build and
70 :goals: build flash
81 to GPIO16 through GPIO19. With the sensor wired to those lines, build and
86 :goals: build flash
92 Build and flash with:
96 :goals: build flash
[all …]
|
| /Zephyr-latest/tests/drivers/build_all/video/ |
| D | testcase.yaml | 7 drivers.video.build:
14 drivers.video.mcux_csi.build:
18 drivers.video.mcux_mipi_csi2rx.build:
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 34 application should build and run for other platforms with same connectivity.
58 The below steps describe how to build and run the ``UpdateHub`` sample in
68 Step 1: Build/Flash MCUboot
78 :build-dir: mcuboot-frdm_k64f
79 :goals: build flash
158 Step 4: Build UpdateHub App
161 In order to correctly build UpdateHub the overlay files must be use correctly.
162 More information about overlay files in :ref:`important-build-vars`.
169 Step 4.1: Build for Ethernet
177 :build-dir: app
[all …]
|
| /Zephyr-latest/snippets/xen_dom0/ |
| D | README.rst | 9 This snippet allows user to build Zephyr as a Xen initial domain (Dom0). The feature
22 be entered when you invoke ``west build``.
27 west build -b qemu_cortex_a53 -S xen_dom0 samples/synchronization
37 * fetch and build Xen (e.g. RELEASE-4.17.0) for arm64 platform
39 * build your Zephyr sample/application with ``xen_dom0`` snippet and start it as Xen control domain
48 -device loader,file=<path to Zephyr app build>/zephyr.bin,addr=0x40600000 \
49 -dtb <path to DTB>/xen.dtb -kernel <path to Xen build>/xen
|
| /Zephyr-latest/samples/net/openthread/coprocessor/ |
| D | README.rst | 5 Build a Thread border-router using OpenThread's co-processor designs.
15 Additional required host-side tools (e.g. otbr-agent) to build a Thread Border
17 https://openthread.io/guides/border-router/build#set-up-the-border-router.
27 Build the OpenThread NCP sample application like this:
33 :goals: build
36 Build the OpenThread NCP sample application which uses CDC ACM UART device:
41 :goals: build flash
|
| /Zephyr-latest/samples/bluetooth/cap_acceptor/ |
| D | README.rst | 34 You can build both the application core image and an appropriate controller image for the network
40 :goals: build
43 If you prefer to only build the application core image, you can do so by doing instead:
48 :goals: build
62 :goals: build
65 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
74 :goals: build
|
| /Zephyr-latest/samples/bluetooth/cap_initiator/ |
| D | README.rst | 34 You can build both the application core image and an appropriate controller image for the network
40 :goals: build
43 If you prefer to only build the application core image, you can do so by doing instead:
48 :goals: build
62 :goals: build
65 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
74 :goals: build
|
| /Zephyr-latest/samples/bluetooth/pbp_public_broadcast_sink/ |
| D | README.rst | 36 You can build both the application core image and an appropriate controller image for the network
42 :goals: build
45 If you prefer to only build the application core image, you can do so by doing instead:
50 :goals: build
64 :goals: build
67 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
76 :goals: build
|
| /Zephyr-latest/samples/bluetooth/pbp_public_broadcast_source/ |
| D | README.rst | 36 You can build both the application core image and an appropriate controller image for the network
42 :goals: build
45 If you prefer to only build the application core image, you can do so by doing instead:
50 :goals: build
64 :goals: build
67 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
76 :goals: build
|
| /Zephyr-latest/boards/vcc-gnd/yd_esp32/doc/ |
| D | index.rst | 94 2. Manual build
108 The sysbuild makes possible to build and flash all necessary images needed to
111 To build the sample application using sysbuild use the command:
117 :goals: build
124 Build directory structure created by sysbuild is different from traditional
125 Zephyr build. Output is structured by the domain subdirectories:
129 build/
142 With ``--sysbuild`` option the bootloader will be re-build and re-flash
143 every time the pristine build is used.
145 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wroom/doc/ |
| D | index.rst | 94 2. Manual build
108 The sysbuild makes possible to build and flash all necessary images needed to
111 To build the sample application using sysbuild use the command:
117 :goals: build
124 Build directory structure created by sysbuild is different from traditional
125 Zephyr build. Output is structured by the domain subdirectories:
129 build/
142 With ``--sysbuild`` option the bootloader will be re-build and re-flash
143 every time the pristine build is used.
145 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wrover/doc/ |
| D | index.rst | 94 2. Manual build
108 The sysbuild makes possible to build and flash all necessary images needed to
111 To build the sample application using sysbuild use the command:
117 :goals: build
124 Build directory structure created by sysbuild is different from traditional
125 Zephyr build. Output is structured by the domain subdirectories:
129 build/
142 With ``--sysbuild`` option the bootloader will be re-build and re-flash
143 every time the pristine build is used.
145 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32c6_devkitc/doc/ |
| D | index.rst | 128 2. Manual build
142 The sysbuild makes possible to build and flash all necessary images needed to
145 To build the sample application using sysbuild use the command:
151 :goals: build
158 Build directory structure created by sysbuild is different from traditional
159 Zephyr build. Output is structured by the domain subdirectories:
163 build/
176 With ``--sysbuild`` option the bootloader will be re-build and re-flash
177 every time the pristine build is used.
179 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 15 When we build Zephyr targeting a :ref:`bsim board<bsim boards>` we produce a Linux
23 `build <https://babblesim.github.io/building.html>`_ the simulator.
26 you can find more information about how to build Zephyr targeting these particular boards,
44 running, and most, more than 1 simulated device. Due to this, these tests are not build and run
48 scripts contained in that folder are used by the CI system to build the needed images and execute
51 See sections below for more information about how to build and run them, as well as the conventions
59 failure, and in many cases to build several tests into the same binary.
96 # Build all the tests
104 Or to build and run only a specific subset, e.g. host advertising tests:
108 # Build the Bluetooth host advertising tests
[all …]
|
| /Zephyr-latest/samples/subsys/bindesc/hello_bindesc/ |
| D | README.rst | 15 Follow these steps to build the ``hello_bindesc`` sample application:
20 :goals: build
27 west bindesc dump build/zephyr/zephyr.bin
29 (Note: you can also dump the contents of ``zephyr.elf``, if your build system
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/support/ |
| D | appli_debug_cmd.gdb | 5 # works if the .elf is located in "build" directory
11 restore ./build/zephyr/zephyr.elf
12 symbol-file -readnow ./build/zephyr/zephyr.elf
|
| /Zephyr-latest/subsys/bluetooth/common/ |
| D | hci_common_internal.h | 9 /* Following build configurations use configurable CONFIG_BT_BUF_CMD_TX_COUNT:
10 * 1. Host + Controller build with and without Controller to Host data flow control, or
15 /* Host + Controller build, and Host-only build */
24 /* Controller-only build need no additional HCI command buffers */
29 /* Controller-only build do not enqueue auto initiated HCI commands */
36 /* When Controller to Host data flow control is supported in Host plus Controller build, or
37 * Host-only build, then we need additional BT_BUF_ACL_RX_COUNT number of HCI command buffers for
85 /* When Controller to Host data flow control is supported in the Controller-only build, ensure
|
| /Zephyr-latest/tests/drivers/build_all/ethernet/ |
| D | testcase.yaml | 9 net.ethernet.build.default: {}
11 net.ethernet.build.spi:
20 net.ethernet.build.stm32_ethernet:
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | application.py | 21 of the shell commands needed to manage (build, flash, etc.) an application.
38 'build-args': directives.unchanged,
40 'build-dir': directives.unchanged,
41 'build-dir-fmt': directives.unchanged,
70 build_args = self.options.get('build-args', None)
72 build_dir_append = self.options.get('build-dir', '').strip('/')
73 build_dir_fmt = self.options.get('build-dir-fmt', None)
87 raise self.error('Both build-dir and build-dir-fmt options were given.')
90 raise self.error('build-dir-fmt is only supported for the west build tool.')
112 # Allow build directories which are nested.
[all …]
|
| /Zephyr-latest/doc/build/snippets/ |
| D | writing.rst | 13 additional build system settings, like this:
18 # ... build system settings go here ...
20 Build system settings go in other keys in the file as described later on in
66 The build system looks for snippets in these places:
78 For each directory in the list, the build system looks for
82 For example, if :makevar:`SNIPPET_ROOT` is set to ``/foo;/bar``, the build
104 automatically be discovered by the build system, just as if
118 cmake --build build
124 west build -S foo -S bar [...] app
141 This :file:`snippet.yml` adds :file:`foo.overlay` to the build:
[all …]
|
| /Zephyr-latest/tests/drivers/build_all/watchdog/ |
| D | testcase.yaml | 7 drivers.watchdog.build:
11 drivers.watchdog.build.i2c:
18 drivers.watchdog.build.spi:
|
12345678910>>...89
