Searched full:build (Results 126 – 150 of 2206) sorted by relevance
12345678910>>...89
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 23 In this tutorial, we will show you how to build a minimal running instance of Zephyr
29 Build your Zephyr App
32 First, build the Zephyr application you want to run in ACRN as you
37 west build -b acrn_ehl_crb samples/hello_world
43 Note the kconfig output in ``build/zephyr/.config``, you will need to
46 The Zephyr build artifact you will need is ``build/zephyr/zephyr.bin``,
50 Configure and build ACRN
62 Like Zephyr, ACRN favors build-time configuration management instead
111 $ objdump -f build/zephyr/zephyr.elf
113 build/zephyr/zephyr.elf: file format elf64-x86-64
[all …]
|
| /Zephyr-latest/samples/drivers/spi_flash_at45/ |
| D | sample.yaml | 12 sample.drivers.spi.flash.at45.build:
14 sample.drivers.spi.flash.at45.build.page_layout:
17 sample.drivers.spi.flash.at45.build.pm:
20 sample.drivers.spi.flash.at45.build.page_layout_pm:
|
| /Zephyr-latest/tests/bluetooth/shell/ |
| D | run-bsim.sh | 20 # Build it with e.g.
22 # west build -d build -b nrf52_bsim -S xterm-native-shell $ZEPHYR_BASE/tests/bluetooth/shell
23 default_image=${ZEPHYR_BASE}/tests/bluetooth/shell/build/zephyr/zephyr.exe
|
| /Zephyr-latest/samples/bluetooth/ |
| D | bluetooth.rst | 6 To build any of the Bluetooth samples, follow the same steps as building
13 Several of the bluetooth samples will build a Zephyr-based Controller that can
19 If you want to run any bluetooth sample on the nRF5340 device (build using
21 ``-DBOARD=nrf5340dk/nrf5340/cpuapp/ns``) you must also build
|
| /Zephyr-latest/samples/boards/bbc/microbit/line_follower_robot/ |
| D | README.rst | 15 To build and run this sample you'll need a `DFRobot Maqueen robot
18 for the robot to follow. Build and flash the program to the BBC
25 Build and flash this sample project using these commands:
30 :goals: build flash
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 174 "build" "compile a Zephyr application" \
429 # build
430 …_zephyr_west_use_subcommand; and __zephyr_west_check_if_in_workspace" -ra build -d "compile a Zeph…
431 complete -c west -n "__zephyr_west_seen_subcommand_from build" -ra "(__zephyr_west_complete_directo…
432 complete -c west -n "__zephyr_west_seen_subcommand_from build" -o b -l board -xa "(__zephyr_west_co…
433 …n "__zephyr_west_seen_subcommand_from build" -o d -l build-dir -xa "(__zephyr_west_complete_direct…
434 complete -c west -n "__zephyr_west_seen_subcommand_from build" -o f -l force -d "ignore errors and …
435 …lete -c west -n "__zephyr_west_seen_subcommand_from build" -l sysbuild -d "create multi-domain bui…
436 …-c west -n "__zephyr_west_seen_subcommand_from build" -l no-sysbuild -d "do not create multi-domai…
437 complete -c west -n "__zephyr_west_seen_subcommand_from build" -o c -l cmake -d "force a cmake run"
[all …]
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 19 and build project documentation.
72 You can configure the Zephyr build system to use a specific toolchain by
89 at build time. Zephyr SDK is identified by the value ``zephyr``.
178 Build and Run an Application
181 You can build, flash, and run Zephyr applications on real
188 Build Blinky
191 Let's build the :zephyr:code-sample:`blinky` sample application.
195 <reel_board>` here, but you can change the ``reel_board`` build target
206 #. Build the blinky sample for the ``reel_board``:
211 :goals: build
[all …]
|
| D | modules.rst | 8 mature code as possible when it makes sense. In the context of Zephyr's build
10 Zephyr build system, as described in more detail in other sections on
49 <modules_using_west>`, then the build system uses west in order to find modules.
54 the Zephyr build system can pull in the source code from the repository.
60 Modules are found by the Zephyr build system either via :ref:`west itself
400 deprecated and the build system shall issue a warning
401 when trying to build Zephyr using a deprecated module.
412 Integrate modules in Zephyr build system
415 The build system variable :makevar:`ZEPHYR_MODULES` is a `CMake list`_ of
418 build and configure them, respectively. Module :file:`CMakeLists.txt` files are
[all …]
|
| /Zephyr-latest/tests/arch/x86/info/src/ |
| D | main.c | 11 printk("MULTIBOOT: Not supported in this build.\n\n"); in multiboot()
16 printk("MEMMAP: Not supported in this build.\n\n"); in memmap()
21 printk("ACPI: Not supported in this build.\n\n"); in acpi()
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 31 Follow these steps to build the PTP sample application:
36 :goals: build
63 :goals: build
66 When the Zephyr image is build, you can start it like this:
70 build/zephyr/zephyr.exe -attach_uart
|
| /Zephyr-latest/cmake/modules/ |
| D | basic_settings.cmake | 12 # Sysbuild is a higher level build system used by Zephyr.
13 # Sysbuild allows users to build multiple samples for a given system.
15 # For this to work, sysbuild manages other Zephyr CMake build systems by setting
16 # dedicated build variables.
|
| /Zephyr-latest/subsys/fb/ |
| D | README_fonts.txt | 8 ${ZEPHYR_BASE}/scripts/build/gen_cfb_font_header.py \
12 ${ZEPHYR_BASE}/scripts/build/gen_cfb_font_header.py \
16 ${ZEPHYR_BASE}/scripts/build/gen_cfb_font_header.py \
|
| /Zephyr-latest/samples/subsys/display/cfb/ |
| D | README.rst | 22 Build this sample application with the following commands:
27 :goals: build
30 See :ref:`reel_board` on how to flash the build.
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 78 from source files to the corresponding generated build files.
84 #. Pre-populate a build directory :file:`BUILD_DIR` like this:
90 This step ensures the build directory contains CMake metadata required for
95 #. Build your application using this pre-created build directory, like so:
99 west build -d BUILD_DIR [...]
101 #. Generate SPDX documents using this build directory:
110 - :file:`app.spdx`: BOM for the application source files used for the build
111 - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for the build
112 - :file:`build.spdx`: BOM for the built output files
121 CMake build targets, build targets that are linked together, and
[all …]
|
| /Zephyr-latest/boards/arduino/portenta_h7/doc/ |
| D | index.rst | 34 hardware revision at build time (see :ref:`application_board_version` for
35 information on how to build for specific revisions of the board).
37 Applications that intend to use BLE must specify hardware revision at build time.
84 have to build dfu-util from source.
91 into the Arduino Bootloader mode. Then build and flash your application.
98 :goals: build flash
112 Similarly, you can build and flash samples on the M4 target. For this, please
120 :goals: build flash
135 http://dfu-util.sourceforge.net/build.html
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 25 the nrf5340bsim/nrf5340/cpuapp build target provides support for the application core,
26 and the nrf5340bsim/nrf5340/cpunet build target provides support for the network
89 By default, when you build targeting either nrf5340bsim/nrf5340/cpuapp or
95 built with either Zephyr's build system or another native simulator compatible build system,
96 you can provide that image to the Zephyr build of the second image using
99 You can also use :ref:`System build (sysbuild) <sysbuild>` to build your dual MCU executable.
118 * There is no nrf5340bsim/nrf5340/cpuapp/ns board/build target, or posibility of mixing secure
|
| /Zephyr-latest/include/zephyr/llext/ |
| D | symbol.h | 40 * 'scripts/build/llext_prepare_exptab.py' build script.
43 /** At build time, we always write to 'name'.
92 /* Extension build: add exported symbols to llext table */
132 /* Extension build: EXPORT_SYMBOL maps to LL_EXTENSION_SYMBOL */
153 /* No extension support in this build */
159 * @brief Export a constant symbol from the current build with a custom name
173 * @brief Export a constant symbol from the current build
177 * by extensions or by the base image, depending on the current build type.
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/ |
| D | pyproject.toml | 1 [build-system]
2 build-backend = "setuptools.build_meta"
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 12 Try again with a pristine build directory
17 See :ref:`west-building-pristine` for examples, or just delete the build
57 That is, the Kconfig option which makes the build system compile the driver
63 Below, ``<build>`` means your build directory.
69 :file:`<build>/zephyr/include/generated/zephyr/devicetree_generated.h`. For example, if
79 * <build>/zephyr/zephyr.dts.pre
91 Now look for this node in :file:`<build>/zephyr/zephyr.dts`, which is the final
92 devicetree for your application build. (See :ref:`get-devicetree-outputs` for
188 :file:`<build>/zephyr/.config` file.
263 :kconfig:option:`CONFIG_COMPILER_SAVE_TEMPS` option. For example, to build
[all …]
|
| /Zephyr-latest/scripts/dts/python-devicetree/ |
| D | .gitignore | 3 build/
7 doc/build/
|
| /Zephyr-latest/samples/psa/its/ |
| D | README.rst | 18 An implementation of the PSA ITS API must be present for this sample to build.
30 You can use them to build the sample, depending on the PSA ITS provider, as follows:
41 :goals: build
54 :goals: build
63 :goals: build
|
| /Zephyr-latest/samples/posix/gettimeofday/ |
| D | Makefile.host | 4 mkdir -p build
5 $(CC) $^ -o build/$@
|
| /Zephyr-latest/samples/posix/eventfd/ |
| D | Makefile.host | 4 mkdir -p build
5 $(CC) $^ -o build/$@
|
| /Zephyr-latest/samples/posix/uname/ |
| D | Makefile.host | 4 mkdir -p build
5 $(CC) $^ -o build/$@
|
| /Zephyr-latest/boards/lilygo/ttgo_lora32/doc/ |
| D | index.rst | 97 2. Manual build
111 The sysbuild makes possible to build and flash all necessary images needed to
114 To build the sample application using sysbuild use the command:
120 :goals: build
127 Build directory structure created by sysbuild is different from traditional
128 Zephyr build. Output is structured by the domain subdirectories:
132 build/
145 With ``--sysbuild`` option the bootloader will be re-build and re-flash
146 every time the pristine build is used.
148 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
12345678910>>...89
