Searched full:build (Results 51 – 75 of 2206) sorted by relevance
12345678910>>...89
| /Zephyr-latest/modules/trusted-firmware-a/ |
| D | Kconfig | 8 bool "Build with TF-A as the Secure Execution Environment"
10 When enabled, this option instructs the Zephyr build process to
18 bool "Debug build"
20 When enabled, the build type of TF-A would be debug.
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 6 Binaries can be optionally signed as part of a build automatically using CMake code, there is
13 The Zephyr build system has special support for signing binaries for use with the `MCUboot`_
14 bootloader using the `imgtool`_ program provided by its developers. You can both build and sign
24 west build -b YOUR_BOARD zephyr/samples/hello_world --sysbuild -d build-hello-signed -- \
27 west flash -d build-hello-signed
39 - ``SB_CONFIG_BOOTLOADER_MCUBOOT``: build the application for loading by MCUboot
47 ``pip3 install imgtool``, then retry with a pristine build directory.
51 ``west flash -d build-hello-signed``:
55 *** Booting Zephyr OS build zephyr-v2.3.0-2310-gcebac69c8ae1 ***
62 *** Booting Zephyr OS build zephyr-v2.3.0-2310-gcebac69c8ae1 ***
[all …]
|
| /Zephyr-latest/samples/kernel/bootargs/ |
| D | README.rst | 30 :goals: build run
37 *** Booting Zephyr OS build v3.7.0-514-gd4490bc739d1 ***
51 :goals: build run
58 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
59 argv[0] = /home/user/zephyr/samples/kernel/bootargs/build/zephyr/zephyr.elf
65 …qemu-system-x86_64 -kernel ./build/zephyr/zephyr.elf -nographic -append "This is 'a list of' argum…
71 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
72 argv[0] = ./build/zephyr/zephyr.elf
85 :goals: build run
100 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
[all …]
|
| /Zephyr-latest/boards/m5stack/m5stack_cores3/doc/ |
| D | index.rst | 74 2. Manual build
88 The sysbuild makes possible to build and flash all necessary images needed to
91 To build the sample application using sysbuild use the command:
101 :goals: build
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/boards/lilygo/ttgo_t8c3/doc/ |
| D | index.rst | 96 2. Manual build
110 The sysbuild makes possible to build and flash all necessary images needed to
113 To build the sample application using sysbuild use the command:
119 :goals: build
126 Build directory structure created by sysbuild is different from traditional
127 Zephyr build. Output is structured by the domain subdirectories:
131 build/
144 With ``--sysbuild`` option the bootloader will be re-build and re-flash
145 every time the pristine build is used.
147 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/others/icev_wireless/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/seeed/xiao_esp32s3/doc/ |
| D | index.rst | 90 2. Manual build
104 The sysbuild makes possible to build and flash all necessary images needed to
107 To build the sample application using sysbuild use the command:
113 :goals: build
120 Build directory structure created by sysbuild is different from traditional
121 Zephyr build. Output is structured by the domain subdirectories:
125 build/
138 With ``--sysbuild`` option the bootloader will be re-build and re-flash
139 every time the pristine build is used.
141 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32s2_devkitc/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/esp32s2_saola/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/adafruit/qt_py_esp32s3/doc/ |
| D | index.rst | 74 2. Manual build
88 The sysbuild makes possible to build and flash all necessary images needed to
91 To build the sample application using sysbuild use the command:
97 :goals: build
104 Build directory structure created by sysbuild is different from traditional
105 Zephyr build. Output is structured by the domain subdirectories:
109 build/
122 With ``--sysbuild`` option the bootloader will be re-build and re-flash
123 every time the pristine build is used.
125 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/samples/sysbuild/with_mcuboot/ |
| D | README.rst | 4 Build a Zephyr application + MCUboot using sysbuild.
31 To build both the sample and MCUboot with ``west`` for the ``reel_board``, run:
37 :goals: build
45 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 ***
46 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 ***
50 The first ``Booting Zephyr OS build`` is printed by MCUboot itself and the
|
| /Zephyr-latest/cmake/ |
| D | pristine.cmake | 7 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.")
|
| D | package_helper.cmake | 9 # build tool that is executed during CMake configure time without creating a
10 # complete build system.
19 # The build directory will default to current working directory but can be
20 # controlled with: '-B <path-to-build>'
23 # $ cmake -DBOARD=<board> -B build -S samples/hello_world
26 # $ cmake -DBOARD=<board> -B build -S samples/hello_world \
29 # It is also possible to pass additional build settings.
32 # $ cmake -DBOARD=<board> -B build -S samples/hello_world -DEXTRA_CONF_FILE=foo.conf
35 # $ cmake -DBOARD=<board> -B build -S samples/hello_world -DEXTRA_CONF_FILE=foo.conf \
|
| /Zephyr-latest/tests/drivers/build_all/interrupt_controller/intc_plic/ |
| D | testcase.yaml | 17 drivers.interrupt_controller.intc_plic.build: {}
18 drivers.interrupt_controller.intc_plic.plic_shell.build:
24 drivers.interrupt_controller.intc_plic.multi_instance.build:
35 drivers.interrupt_controller.intc_plic.irq_affinity.build:
|
| /Zephyr-latest/samples/subsys/mgmt/hawkbit/ |
| D | README.rst | 30 build and run for other platforms with support internet connection. Some
43 The below steps describe how to build and run the hawkBit sample in
44 Zephyr. Where examples are given, it is assumed the sample is being build for
47 Step 1: Build MCUboot
50 Build MCUboot by following the instructions in the :ref:`mcuboot` documentation
78 Step 4: Build hawkBit
87 :goals: build
89 If you want to build it with the ability to set the hawkBit server address
96 :goals: build
100 The firmware will be signed automatically by the build system with the
[all …]
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.zsh | 28 'build[compile a Zephyr application]'
233 '(-b --board)'{-b,--board}'[board to build for]:board:_get_west_boards'
234 '(-d --build-dir)'{-d,--build-dir}'[build directory to create or use]:build dir:_directories'
236 '--sysbuild[create multi-domain build system]'
237 '--no-sysbuild[do not create multi-domain build system]'
240 '--domain[execute build tool (make or ninja) for a given domain]:domain:'
241 '(-t --target)'{-t,--target}'[run build system target]:target:'
242 '(-T --test-item)'{-T,--test-item}'[Build based on test data in .yml]:test item:'
243 {-o,--build-opt}'[options to pass to build tool (make or ninja)]:tool opt:'
244 …'(-n --just-print --dry-run --recon)'{-n,--just-print,--dry-run,--recon}"[just print build command…
[all …]
|
| /Zephyr-latest/doc/develop/sca/ |
| D | cpptest.rst | 13 Generating Build Data Files
17 :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=cpptest``
22 west build -b qemu_cortex_m3 zephyr/samples/hello_world -- -DZEPHYR_SCA_VARIANT=cpptest
25 A ``.bdf`` file will be generated as :file:`build/sca/cpptest/cpptestscan.bdf`.
36 …cpptestcli -data out -localsettings local.conf -bdf build/sca/cpptest/cpptestscan.bdf -config "bui…
40 ``bdf.import.linker.exec`` to the toolchain :ref:`west build <west-building>` used.
|
| /Zephyr-latest/.github/workflows/ |
| D | doc-build.yml | 4 name: Documentation Build
24 doc-build-html:
25 name: "Documentation Build (HTML)"
31 group: doc-build-html-${{ github.ref }}
38 sudo apt-get install -y wget python3-pip git ninja-build graphviz lcov
79 - name: build-docs
113 - name: upload-build
146 doc-build-pdf:
147 name: "Documentation Build (PDF)"
155 group: doc-build-pdf-${{ github.ref }}
[all …]
|
| /Zephyr-latest/samples/bluetooth/bap_unicast_client/ |
| D | README.rst | 37 :goals: build
43 You can build both the application core image and an appropriate controller image for the network
49 :goals: build
52 If you prefer to only build the application core image, you can do so by doing instead:
57 :goals: build
71 :goals: build
74 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
83 :goals: build
|
| /Zephyr-latest/samples/bluetooth/bap_unicast_server/ |
| D | README.rst | 37 :goals: build
43 You can build both the application core image and an appropriate controller image for the network
49 :goals: build
52 If you prefer to only build the application core image, you can do so by doing instead:
57 :goals: build
71 :goals: build
74 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
83 :goals: build
|
| /Zephyr-latest/tests/net/lib/mqtt/v3_1_1/mqtt_packet/ |
| D | README | 9 Build and Run
14 Build & run:
15 mkdir build; cd build
21 Build:
22 mkdir build; cd build
28 Build: Aug 24 2015 17:06:30
|
| /Zephyr-latest/boards/espressif/esp32s3_devkitm/doc/ |
| D | index.rst | 122 2. Manual build
136 The sysbuild makes possible to build and flash all necessary images needed to
139 To build the sample application using sysbuild use the command:
145 :goals: build
152 Build directory structure created by sysbuild is different from traditional
153 Zephyr build. Output is structured by the domain subdirectories:
157 build/
170 With ``--sysbuild`` option the bootloader will be re-build and re-flash
171 every time the pristine build is used.
173 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32s3_devkitc/doc/ |
| D | index.rst | 122 2. Manual build
136 The sysbuild makes possible to build and flash all necessary images needed to
139 To build the sample application using sysbuild use the command:
145 :goals: build
152 Build directory structure created by sysbuild is different from traditional
153 Zephyr build. Output is structured by the domain subdirectories:
157 build/
170 With ``--sysbuild`` option the bootloader will be re-build and re-flash
171 every time the pristine build is used.
173 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 13 During the :ref:`build_configuration_phase`, the build system tries to match
14 each node in the devicetree to a binding file. When this succeeds, the build
46 The build system matches the ``bar-device`` node to its YAML binding because
49 What the build system does with bindings
52 The build system uses bindings both to validate devicetree nodes and to convert
56 For example, the build system would use the above binding to check that the
60 The build system will then generate a macro for the ``bar-device`` node's
65 For another example, the following node would cause a build error, because it
78 If a node has more than one string in its ``compatible`` property, the build
91 "generic-baz-device"`` line if the build system can't find a binding with a
[all …]
|
| /Zephyr-latest/samples/boards/arc_secure_services/ |
| D | README.rst | 58 First, you should build the secure application.
63 :goals: build
71 file to the specific board dir to build normal application.
79 :goals: build
100 $ cd samples/boards/arc_secure_services/build
103 $ monitor load_image ../../../philosophers/build/zephyr/zephyr.elf
114 $ cd samples/boards/arc_secure_services/build
122 $ cd samples/boards/arc_secure_services/build
126 $ load ../../../philosophers/build/zephyr/zephyr.elf
|
12345678910>>...89
