Searched full:build (Results 26 – 50 of 2206) sorted by relevance
12345678910>>...89
| /Zephyr-latest/samples/subsys/tracing/ |
| D | README.rst | 18 Build a UART-tracing image with:
24 :goals: build
33 :goals: build
45 Build a USB-tracing image with:
51 :goals: build
60 :goals: build
84 Build a POSIX-tracing image with:
89 :goals: build
98 :goals: build
106 Build a USER-tracing image with:
[all …]
|
| /Zephyr-latest/boards/seeed/xiao_esp32c3/doc/ |
| D | index.rst | 71 2. Manual build
85 The sysbuild makes possible to build and flash all necessary images needed to
88 To build the sample application using sysbuild use the command:
94 :goals: build
101 Build directory structure created by Sysbuild is different from traditional
102 Zephyr build. Output is structured by the domain subdirectories:
106 build/
119 With ``--sysbuild`` option the bootloader will be re-build and re-flash
120 every time the pristine build is used.
122 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/doc/build/snippets/ |
| D | using.rst | 11 Snippets have names. You use snippets by giving their names to the build
14 With west build
21 west build -S foo app
27 west build -S snippet1 -S snippet2 [...] app
32 If you are running CMake directly instead of using ``west build``, use the
39 cmake --build build
|
| /Zephyr-latest/boards/dptechnics/walter/doc/ |
| D | index.rst | 94 must be build (and flash) at least once.
99 2. Manual build
113 The sysbuild makes possible to build and flash all necessary images needed to
116 To build the sample application using sysbuild use the command:
122 :goals: build
129 Build directory structure created by sysbuild is different from traditional
130 Zephyr build. Output is structured by the domain subdirectories:
134 build/
147 With ``--sysbuild`` option the bootloader will be re-build and re-flash
148 every time the pristine build is used.
[all …]
|
| /Zephyr-latest/samples/tfm_integration/tfm_ipc/ |
| D | README.rst | 36 #. Build Zephyr with a non-secure configuration (``-DBOARD=mps2/an521/cpu0/ns``).
41 mkdir build
42 cd build
50 $ west build -p -b mps2/an521/cpu0/ns zephyr/samples/tfm_integration/tfm_ipc
89 As part of the normal build process above, a binary is also produced that can
94 qemu-system-arm -M mps2-an521 -device loader,file=build/zephyr/tfm_merged.hex -serial stdio
96 You can also run the binary as part of the ``west`` build process by appending
97 the ``-t run`` flag to the end of your build command, or in the case of
102 $ west build -b mps2/an521/cpu0/ns zephyr/samples/tfm_integration/tfm_ipc -t run
104 Or, post build:
[all …]
|
| /Zephyr-latest/tests/drivers/build_all/gpio/ |
| D | testcase.yaml | 7 drivers.gpio.build:
15 drivers.gpio.build.efinix_sapphire:
21 drivers.gpio.build.altera_pio:
29 drivers.gpio.build.adc_ads1x4s0x_gpio:
49 drivers.gpio.build.adc_lmp90xxx_gpio:
65 drivers.gpio.build.iproc:
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 11 - its **build directory** is :file:`<app>/build`
17 makes it easier to use ``west build`` and other commands with it. (You can
19 <important-build-vars>` is set appropriately, though.)
24 Zephyr's build system is based on `CMake`_.
26 The build system is application-centric, and requires Zephyr-based applications
27 to initiate building the Zephyr source code. The application build controls
28 the configuration and build process of both the application and Zephyr itself,
32 and build system. You also likely have installed various :ref:`modules`
54 * **CMakeLists.txt**: This file tells the build system where to find the other
56 build system. This link provides features supported by Zephyr's build system,
[all …]
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
38 during build time, which is not really practical. This sample is about the EDK
39 providing the ability to build extensions independently from the application.
40 One could build the extensions in different directories, not related to the
48 To build the EDK, use the ``llext-edk`` target. For example:
53 :goals: build llext-edk
62 cp build/zephyr/llext-edk.tar.xz /tmp/edk
84 To build the extensions, in the ``ext1``, ``ext2``, ``ext3`` and ``kext1``
89 cmake -B build
[all …]
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 33 bool "Build with TF-M as the Secure Execution Environment"
43 When enabled, this option instructs the Zephyr build process to
50 them, are generated during the normal Zephyr build process.
68 Build profile used to build tfm_s image. The available values are
73 prompt "TF-M build profile"
76 The TF-M build profile selection. Can be empty (not set),
82 bool "TF-M build profile: not set (base)"
85 bool "TF-M build profile: small"
88 bool "TF-M build profile: medium"
91 bool "TF-M build profile: ARoT-less"
[all …]
|
| /Zephyr-latest/samples/application_development/external_lib/ |
| D | README.rst | 4 Include an external static library into the Zephyr build system.
10 into the Zephyr build system.
11 The demonstrates both how to build the external library using a different build
29 Once installed, build the application as normal.
37 getting the ``Complete package`` setup. Once installed and in the path, build
|
| D | CMakeLists.txt | 10 # how to build for this platform so we export all the flags used in
11 # this zephyr build to the external build system.
13 # Other external build systems may be self-contained enough that they
14 # do not need any build information from zephyr. Or they may be
32 # Add an external project to be able download and build the third
52 BINARY_DIR ${mylib_src_dir} # This particular build system is invoked from the root
60 INSTALL_COMMAND "" # This particular build system has no install command
|
| /Zephyr-latest/tests/misc/llext-edk/pytest/ |
| D | test_edk.py | 30 # Can we build the edk?
33 "build",
38 "--build-dir",
66 file2hex = Path(os.environ["ZEPHYR_BASE"]) / "scripts/build/file2hex.py"
76 # Build the extension using the edk
78 command = ["cmake", "-B", "build"]
83 command = ["make", "-C", "build"]
88 assert os.path.exists(Path(tempdir_extension) / "build/extension.llext")
91 # build directory in the include path, so that the application can find the
93 logger.debug(f"Running application with extension in {tempdir_extension} - west build")
[all …]
|
| /Zephyr-latest/boards/seeed/xiao_esp32c6/doc/ |
| D | index.rst | 73 2. Manual build
87 The sysbuild makes possible to build and flash all necessary images needed to
90 To build the sample application using sysbuild use the command:
96 :goals: build
103 Build directory structure created by sysbuild is different from traditional
104 Zephyr build. Output is structured by the domain subdirectories:
108 build/
121 With ``--sysbuild`` option the bootloader will be re-build and re-flash
122 every time the pristine build is used.
124 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/others/esp32c3_supermini/doc/ |
| D | index.rst | 84 2. Manual build
98 The sysbuild makes possible to build and flash all necessary images needed to
101 To build the sample application using sysbuild use the command:
107 :goals: build
114 Build directory structure created by sysbuild is different from traditional
115 Zephyr build. Output is structured by the domain subdirectories:
119 build/
132 With ``--sysbuild`` option the bootloader will be re-build and re-flash
133 every time the pristine build is used.
135 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/samples/subsys/usb/dfu/ |
| D | README.rst | 36 The build system can do this for you by setting the :kconfig:option:`CONFIG_MCUBOOT_SIGNATURE_KEY_F…
42 west build -b nrf52840dk/nrf52840 zephyr/samples/subsys/usb/dfu -d build-dfu -- \
45 Build and flash MCUboot bootloader for Zephyr project as it is described in
46 the `Using MCUboot with Zephyr`_ documentation. Then build, sign and flash
49 Build and sign a second application image e.g. :zephyr:code-sample:`hello_world`,
56 west build -b nrf52840dk/nrf52840 zephyr/samples/hello_world -d build-hello_world -- \
75 dfu-util --alt 1 --download build-hello_world/zephyr/zephyr.signed.bin
82 *** Booting Zephyr OS build zephyr-v3.0.0-360-gc0dd594d4d3d ***
90 *** Booting Zephyr OS build zephyr-v3.0.0-361-gb987e6daa2f9 ***
99 *** Booting Zephyr OS build zephyr-v3.0.0-360-gc0dd594d4d3d ***
[all …]
|
| /Zephyr-latest/boards/lilygo/ttgo_t7v1_5/doc/ |
| D | index.rst | 83 must be build (and flash) at least once.
88 2. Manual build
102 The sysbuild makes possible to build and flash all necessary images needed to
105 To build the sample application using sysbuild use the command:
111 :goals: build
118 Build directory structure created by sysbuild is different from traditional
119 Zephyr build. Output is structured by the domain subdirectories:
123 build/
136 With ``--sysbuild`` option the bootloader will be re-build and re-flash
137 every time the pristine build is used.
[all …]
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 3 TF-M Build System
8 of TF-M's build system is required in most cases, and the following will
9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
14 … $ west build -p auto -b mps2/an521/cpu0/ns samples/tfm_integration/psa_protected_storage/ -t run
16 The outputs and certain key steps in this build process are described here,
20 Images Created by the TF-M Build
23 The TF-M build system creates the following executable files:
31 The TF-M build system also creates signed variants of tfm_s and tfm_ns, and a
43 The Zephyr build system usually signs both tfm_s and the Zephyr non-secure app itself.
102 the CMake arguments passed to the TF-M build.
[all …]
|
| /Zephyr-latest/samples/sysbuild/hello_world/ |
| D | README.rst | 9 The sample demonstrates how to build a Hello World application for two board
13 Zephyr Sysbuild, the build system adds additional images based on the options
14 selected in the project's additional configuration and build files.
32 Here's an example to build and flash the sample for the
40 :goals: build flash
50 :goals: build flash
61 *** Booting Zephyr OS build v3.6.0-274-g466084bd8c5d ***
68 *** Booting Zephyr OS build v3.6.0-274-g466084bd8c5d ***
|
| /Zephyr-latest/scripts/west_commands/ |
| D | spdx.py | 14 following the completion of a Zephyr build.
16 Prior to the build, an empty file must be created at
20 calling `west build`."""
38 parser.add_argument('-d', '--build-dir',
39 help="build directory")
55 self.dbg(f" --build-dir is", args.build_dir)
67 self.inf("initializing CMake file-based API prior to build")
70 self.die("Build directory not specified; call `west spdx --init --build-dir=BUILD_DIR`")
75 self.inf("initialized; run `west build` then run `west spdx`")
83 self.die("Build directory not specified; call `west spdx --build-dir=BUILD_DIR`")
|
| /Zephyr-latest/boards/heltec/heltec_wifi_lora32_v2/doc/ |
| D | index.rst | 61 2. Manual build
75 The sysbuild makes possible to build and flash all necessary images needed to
78 To build the sample application using sysbuild use the command:
84 :goals: build
91 Build directory structure created by sysbuild is different from traditional
92 Zephyr build. Output is structured by the domain subdirectories:
96 build/
109 With ``--sysbuild`` option the bootloader will be re-build and re-flash
110 every time the pristine build is used.
112 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/we/orthosie1ev/doc/ |
| D | index.rst | 86 2. Manual build
100 The sysbuild makes possible to build and flash all necessary images needed to
103 To build the sample application using sysbuild use the command:
109 :goals: build
116 Build directory structure created by sysbuild is different from traditional
117 Zephyr build. Output is structured by the domain subdirectories:
121 build/
134 With ``--sysbuild`` option the bootloader will be re-build and re-flash
135 every time the pristine build is used.
137 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/ |
| D | index.rst | 86 2. Manual build
100 The sysbuild makes possible to build and flash all necessary images needed to
103 To build the sample application using sysbuild use the command:
109 :goals: build
116 Build directory structure created by sysbuild is different from traditional
117 Zephyr build. Output is structured by the domain subdirectories:
121 build/
134 With ``--sysbuild`` option the bootloader will be re-build and re-flash
135 every time the pristine build is used.
137 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp8684_devkitm/doc/ |
| D | index.rst | 92 2. Manual build
106 The sysbuild makes possible to build and flash all necessary images needed to
109 To build the sample application using sysbuild use the command:
115 :goals: build
122 Build directory structure created by sysbuild is different from traditional
123 Zephyr build. Output is structured by the domain subdirectories:
127 build/
140 With ``--sysbuild`` option the bootloader will be re-build and re-flash
141 every time the pristine build is used.
143 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/olimex/olimex_esp32_evb/doc/ |
| D | index.rst | 85 2. Manual build
99 The sysbuild makes possible to build and flash all necessary images needed to
102 To build the sample application using sysbuild use the command:
108 :goals: build
115 Build directory structure created by sysbuild is different from traditional
116 Zephyr build. Output is structured by the domain subdirectories:
120 build/
133 With ``--sysbuild`` option the bootloader will be re-build and re-flash
134 every time the pristine build is used.
136 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitc/doc/ |
| D | index.rst | 86 2. Manual build
100 The sysbuild makes possible to build and flash all necessary images needed to
103 To build the sample application using sysbuild use the command:
109 :goals: build
116 Build directory structure created by sysbuild is different from traditional
117 Zephyr build. Output is structured by the domain subdirectories:
121 build/
134 With ``--sysbuild`` option the bootloader will be re-build and re-flash
135 every time the pristine build is used.
137 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
12345678910>>...89
