Home
last modified time | relevance | path

Searched refs:build (Results 1 – 25 of 783) sorted by relevance

12345678910>>...32

/Zephyr-Core-2.7.6/doc/guides/west/
Dbuild-flash-debug.rst1 .. _west-build-flash-debug:
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
23 Building: ``west build``
26 .. tip:: Run ``west build -h`` for a quick overview.
28 The ``build`` command helps you build Zephyr applications from source. You can
33 - If there is a Zephyr build directory named :file:`build` in your current
35 run ``west build`` from a Zephyr build directory.
37 - Otherwise, if you run ``west build`` from a Zephyr application's source
38 directory and no build directory is found, a new one is created and the
44 The easiest way to use ``west build`` is to go to an application's root
[all …]
Dwithout-west.rst13 - specifying the locations of these repositories to the Zephyr build
27 Otherwise, Zephyr's build system will find it and may try to use
52 You can build a Zephyr application using CMake and Ninja (or make) directly
58 :goals: build
62 When building with west installed, the Zephyr build system will use it to set
63 :ref:`ZEPHYR_MODULES <important-build-vars>`.
66 these repositories, the build will still work.
77 Running build system targets like ``ninja flash``, ``ninja debug``,
79 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
85 If you want to use these build system targets but do not want to
[all …]
Dsign.rst13 The Zephyr build system has special support for signing binaries for use with
15 developers. You can both build and sign this type of application binary in one
20 build system will do it for you.
29 west build -b YOUR_BOARD -s bootloader/mcuboot/boot/zephyr -d build-mcuboot
30 west build -b YOUR_BOARD -s zephyr/samples/hello_world -d build-hello-signed -- \
34 west flash -d build-mcuboot
35 west flash -d build-hello-signed
47 - :kconfig:`CONFIG_BOOTLOADER_MCUBOOT`: build the application for loading by
57 to run ``pip3 install imgtool``, then retry with a pristine build directory.
61 serial console when you run ``west flash -d build-mcuboot``:
[all …]
Dzephyr-cmds.rst60 from source files to the corresponding generated build files.
66 #. Pre-populate a build directory :file:`BUILD_DIR` like this:
72 This step ensures the build directory contains CMake metadata required for
75 #. Build your application using this pre-created build directory, like so:
79 west build -d BUILD_DIR [...]
81 #. Generate SPDX documents using this build directory:
90 - :file:`app.spdx`: BOM for the application source files used for the build
92 the build
93 - :file:`build.spdx`: BOM for the built output files
100 CMake build targets, build targets that are linked together, and
[all …]
/Zephyr-Core-2.7.6/tests/subsys/jwt/src/
Dmain.c40 struct jwt_builder build; in test_jwt() local
43 res = jwt_init_builder(&build, buf, sizeof(buf)); in test_jwt()
47 res = jwt_add_payload(&build, 1530312026, 1530308426, in test_jwt()
51 res = jwt_sign(&build, jwt_test_private_der, jwt_test_private_der_len); in test_jwt()
54 zassert_equal(build.overflowed, false, "Not overflow"); in test_jwt()
57 printk("len: %zd\n", jwt_payload_len(&build)); in test_jwt()
/Zephyr-Core-2.7.6/modules/trusted-firmware-m/
DKconfig.tfm.partitions13 to be passed to the TF-M build system. Look at 'config_default.cmake'
16 options are handled by the build system in the trusted-firmware-m
24 to be passed to the TF-M build system. Look at 'config_default.cmake'
27 options are handled by the build system in the trusted-firmware-m
35 to be passed to the TF-M build system. Look at 'config_default.cmake'
38 options are handled by the build system in the trusted-firmware-m
46 to be passed to the TF-M build system. Look at 'config_default.cmake'
49 options are handled by the build system in the trusted-firmware-m
57 to be passed to the TF-M build system. Look at 'config_default.cmake'
60 options are handled by the build system in the trusted-firmware-m
[all …]
DKconfig.tfm35 When enabled, this option instructs the Zephyr build process to
42 them, are generated during the normal Zephyr build process.
78 Build profile used to build tfm_s image. The available values are
83 prompt "TF-M build profile"
87 The TF-M build profile selection. Can be empty (not set),
93 bool "TF-M build profile is not set"
96 bool "TF-M build profile: small"
99 bool "TF-M build profile: medium"
102 bool "TF-M build profile: large"
107 prompt "The build type for TFM"
[all …]
/Zephyr-Core-2.7.6/doc/guides/build/
Dindex.rst13 CMake is used to build your application together with the Zephyr kernel. A
14 CMake build is done in two stages. The first stage is called
15 **configuration**. During configuration, the CMakeLists.txt build scripts are
17 Zephyr build, and can generate build scripts that are native to the host
20 CMake supports generating scripts for several build systems, but only Ninja and
22 **build** stage by executing the generated build scripts. These build scripts
25 be executed again before building. The build scripts can detect some of these
29 Zephyr uses CMake's concept of a 'target' to organize the build. A
32 understand. All source code that goes into a Zephyr build does so by
36 build scripts like this:
[all …]
/Zephyr-Core-2.7.6/cmake/
Dpristine.cmake7 usage: cmake -DBINARY_DIR=<build-path> -DSOURCE_DIR=<source-path>
11 -DBINARY_DIR=<build-path>: Absolute path to the build directory to pristine
13 creating <build-path>
32 message(FATAL_ERROR "Refusing to run pristine in in-source build folder.")
/Zephyr-Core-2.7.6/samples/application_development/external_lib/
DCMakeLists.txt10 # 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
28 # Add an external project to be able download and build the third
48 BINARY_DIR ${mylib_src_dir} # This particular build system is invoked from the root
56 INSTALL_COMMAND "" # This particular build system has no install command
DREADME.rst9 into the Zephyr build system.
10 The demonstrates both how to build the external library using a different build
/Zephyr-Core-2.7.6/samples/tfm_integration/tfm_ipc/
DREADME.rst41 mkdir build
42 cd build
50 $ west build -p -b mps2_an521_ns zephyr/samples/tfm_integration/tfm_ipc
89 As part of the normal build process above, a binary is also produced that can
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_ns zephyr/samples/tfm_integration/tfm_ipc -t run
104 Or, post build:
121 $ west build -b nucleo_l552ze_q_ns samples/tfm_integration/tfm_ipc/
127 $ west build -b stm32l562e_dk_ns samples/tfm_integration/tfm_ipc/
[all …]
/Zephyr-Core-2.7.6/doc/application/
Dindex.rst9 :file:`<home>/app`, and that its **build directory** is
10 :file:`<home>/app/build`.
18 Zephyr's build system is based on `CMake`_.
20 The build system is application-centric, and requires Zephyr-based applications
21 to initiate building the kernel source tree. The application build controls
22 the configuration and build process of both the application and Zephyr itself,
26 configuration options, and its build definitions.
44 * **CMakeLists.txt**: This file tells the build system where to find the other
46 build system. This link provides features supported by Zephyr's build system,
64 known as the **build directory**. Application build artifacts are always
[all …]
/Zephyr-Core-2.7.6/samples/boards/arc_secure_services/
DREADME.rst56 First, you should build the secure application.
61 :goals: build
69 file to the specific board dir to build normal application.
77 :goals: build
98 $ cd samples/boards/arc_secure_services/build
101 $ monitor load_image ../../../philosophers/build/zepher/zephyr.elf
112 $ cd samples/boards/arc_secure_services/build
120 $ cd samples/boards/arc_secure_services/build
124 $ load ../../../philosophers/build/zepher/zephyr.elf
/Zephyr-Core-2.7.6/samples/drivers/dac/
DREADME.rst28 :goals: build flash
39 :goals: build flash
50 :goals: build flash
61 :goals: build flash
72 :goals: build flash
83 :goals: build flash
94 :goals: build flash
105 :goals: build flash
119 :goals: build flash
133 :goals: build flash
[all …]
/Zephyr-Core-2.7.6/doc/guides/tfm/
Dbuild.rst6 of TF-M's build system is required in most cases, and the following will
7 build a TF-M and Zephyr image pair, and run it in qemu with no additional
12 $ west build -p auto -t mps2_an521_ns samples/tfm_integration/psa_crypto/ -t run
14 The outputs and certain key steps in this build process are described here,
21 The TF-M build system creates the following executable files:
29 The TF-M build system also creates signed variants of tfm_s and tfm_ns, and a
38 The Zephyr build system usually signs both tfm_s and the Zephyr ns app itself.
97 the CMake arguments passed to the TF-M build.
99 Zephyr TF-M build offers several Kconfig options for controlling the build, but
100 doesn't cover every CMake argument supported by the TF-M build system.
[all …]
/Zephyr-Core-2.7.6/scripts/dts/python-devicetree/
D.gitignore3 build/
7 doc/build/
/Zephyr-Core-2.7.6/samples/sensor/bme280/
DREADME.rst39 sure this node has ``status = "okay";``, then build and run with:
43 :goals: build flash
49 If you wired the sensor to a SPI peripheral on an Arduino header, build and
54 :goals: build flash
64 If you wired the sensor to an I2C peripheral on an Arduino header, build and
69 :goals: build flash
83 The build system uses these overlays by default when targeting those boards, so
86 For example, to build for the :ref:`adafruit_feather_m0_basic_proto` using the
92 :goals: build flash
112 *** Booting Zephyr OS build zephyr-v2.4.0-2940-gbb732ada394f ***
[all …]
/Zephyr-Core-2.7.6/samples/sensor/fxos8700/
DREADME.rst31 :goals: build flash
40 :goals: build flash
51 :goals: build flash
60 :goals: build flash
74 :goals: build flash
86 :goals: build flash
98 :goals: build flash
110 :goals: build flash
121 :goals: build flash
/Zephyr-Core-2.7.6/samples/tfm_integration/psa_crypto/
DREADME.rst54 This sample will only build on a Linux or macOS development system
80 west build -p -b mps2_an521_ns samples/tfm_integration/psa_crypto
87 rm -rf build
88 mkdir build && cd build
97 rm -rf build
98 mkdir build && cd build
134 west build -p -b mps2_an521_ns samples/tfm_integration/psa_crypto -t run
141 rm -rf build
142 mkdir build && cd build
151 rm -rf build
[all …]
/Zephyr-Core-2.7.6/samples/subsys/mgmt/updatehub/
DREADME.rst33 application should build and run for other platforms with same connectivity.
57 The below steps describe how to build and run the ``UpdateHub`` sample in
70 The MCUboot can be build following the instructions in the :ref:`mcuboot`
77 :build-dir: mcuboot-frdm_k64f
78 :goals: build flash
160 In order to correctly build UpdateHub the overlay files must be use correctly.
161 More information about overlay files in :ref:`important-build-vars`.
176 :build-dir: app
178 :goals: build
191 :build-dir: app
[all …]
/Zephyr-Core-2.7.6/doc/security/
Dhardening-tool.rst13 preferences defined by the **Security Group**. The tool can identify the build
20 After configure of your application, change directory to the build folder and:
24 # ninja build system:
26 # make build system:
/Zephyr-Core-2.7.6/samples/drivers/spi_flash_at45/
DREADME.rst41 To build and flash the application:
46 :goals: build flash
49 To build and flash with device power management enabled:
55 :goals: build flash
58 To build and flash with flash page layout enabled:
64 :goals: build flash
67 Finally, to build and flash with both device power management and flash page
74 :goals: build flash
/Zephyr-Core-2.7.6/samples/sensor/dht/
DREADME.rst23 build this sample app using:
28 :goals: build flash
35 *** Booting Zephyr OS build zephyr-v2.1.0-329-g38418b26c4cc ***
/Zephyr-Core-2.7.6/doc/guides/dts/
Dtroubleshooting.rst10 Try again with a pristine build directory
15 See :ref:`west-building-pristine` for examples, or just delete the build
87 build :ref:`hello_world` with west with this option set, use:
91 west build -b BOARD samples/hello_world -- -DEXTRA_CFLAGS=-save-temps=obj
93 This will create a preprocessor output file named :file:`foo.c.i` in the build
96 You can then search for the file in the build directory to see what your
102 $ find build -name main.c.i
103 build/CMakeFiles/app.dir/src/main.c.i
110 clang-format -i build/CMakeFiles/app.dir/src/main.c.i
119 identifier and property. For example, if you get a build error on a line that
[all …]

12345678910>>...32