Searched full:build (Results 226 – 250 of 2206) sorted by relevance
12345678910>>...89
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 25 # its own at build time. And likewise the signing key isn't provided
26 # by Zephyr and needs tob e found by a SOF build by passing it in
30 # exercised from a SOF build and it doesn't belong here in Zephyr;
42 --if-tool-available --tool rimage --build-dir ${CMAKE_BINARY_DIR}
|
| /Zephyr-latest/.github/workflows/ |
| D | scripts_tests.yml | 12 - 'scripts/build/**'
19 - 'scripts/build/**'
67 pip install -r scripts/requirements-base.txt -r scripts/requirements-build-test.txt
74 pytest ./scripts/build
|
| /Zephyr-latest/doc/develop/west/ |
| D | alias.rst | 44 call ``west build`` with the corresponding CMake targets:
48 west config --global alias.run "build --pristine=never --target run"
49 west config --global alias.menuconfig "build --pristine=never --target menuconfig"
55 west config alias.sample "build -b native_sim samples/hello_world -t run -- -DCONFIG_ASSERT=y"
|
| /Zephyr-latest/doc/develop/sca/ |
| D | index.rst | 8 The build setting :makevar:`ZEPHYR_SCA_VARIANT` can be used to specify the SCA
22 Zephyr itself is always added as an :makevar:`SCA_ROOT` but the build system offers the
52 file, see :ref:`Zephyr Modules - Build settings <modules_build_settings>`
59 The following is a list of SCA tools natively supported by Zephyr build system.
|
| /Zephyr-latest/samples/sensor/thermometer/ |
| D | README.rst | 29 To build for the nrf52840dk/nrf52840 board use:
34 :goals: build flash
38 To build for other boards and ambient temperature sensors, enable the sensor
59 *** Booting Zephyr OS build zephyr-v3.3.0-2354-gb4f4bd1f1c22 ***
|
| /Zephyr-latest/scripts/native_simulator/ |
| D | Makefile | 8 # By default all the build output is placed under the _build folder, but the user can override it
15 # to also build the components in native/src/
19 #If the file does not exist, we don't use it as a build dependency
25 # Folder where the build output will be placed
60 # Build debug switch (by default enabled)
62 # Build optimization level (by default disabled to ease debugging)
80 @echo "There is no default rule, please specify what you want to build,\
110 #Extra sources build:
115 #Extra C++ sources build:
174 @echo " clean : clean all build output"
[all …]
|
| /Zephyr-latest/scripts/ |
| D | requirements-build-test.txt | 1 # BUILD-TEST: required to do build tests of zephyr
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.11.rst | 17 * Native build target on POSIX platforms.
51 * New POSIX architecture for native GNU/Linux and macOS build targets:
130 Build and Infrastructure
137 * Build time now comparable to Linux and macOS using Ninja
189 * :github:`1082` - build all tests have issues for devices that don't exist on a given board
198 * :github:`1868` - Build System cleanup and Kernel / Application build separation
205 * :github:`1926` - build system does not re-link if linker script changed
227 * :github:`2994` - The build system crashes when GCCARMEMB_TOOLCHAIN_PATH has a space in it
242 * :github:`3329` - Build warnings [-Wpointer-sign] with LLVM/icx (bluetooth_ipsp)
252 * :github:`3597` - Build warnings [-Wpointer-sign] with LLVM/icx (tests/net/ieee802154/crypto)
[all …]
|
| /Zephyr-latest/samples/subsys/shell/fs/ |
| D | README.rst | 23 You can build this sample for :ref:`native_sim <native_sim>` with:
28 :goals: build
48 Before starting a build, make sure that the i386 pkgconfig directory is in your
61 :goals: build
70 :goals: build
82 :goals: build
88 If you want to use the 'flash load' command then build the sample with the
230 relative to the directory where the build is started.
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/support/ |
| D | appli_dl_cmd.gdb | 10 restore ./build/zephyr/zephyr.elf
11 symbol-file -readnow ./build/zephyr/zephyr.elf
|
| /Zephyr-latest/cmake/modules/ |
| D | doc.cmake | 6 # documentation build.
16 # The Zephyr package required for documentation build setup.
|
| /Zephyr-latest/boards/sifive/hifive_unleashed/doc/ |
| D | index.rst | 25 :goals: build
32 :goals: build
46 riscv64-zephyr-elf-gdb build/zephyr/zephyr.elf
|
| /Zephyr-latest/boards/sifive/hifive_unmatched/doc/ |
| D | index.rst | 25 :goals: build
32 :goals: build
46 riscv64-zephyr-elf-gdb build/zephyr/zephyr.elf
|
| /Zephyr-latest/samples/drivers/mspi/mspi_flash/ |
| D | README.rst | 18 The application will build only for a target that has a :ref:`devicetree <dt-guide>`
26 :goals: build flash
34 *** Booting Zephyr OS build zephyr-v2.3.0-2142-gca01d2e1d748 ***
|
| /Zephyr-latest/samples/basic/hash_map/ |
| D | README.rst | 25 :goals: build
28 To build for another board, change "native_sim" above to that board's name.
41 Run ``build/zephyr/zephyr.exe``
|
| /Zephyr-latest/samples/drivers/led/lp5569/ |
| D | README.rst | 19 Build the application for the :ref:`nrf52840dk_nrf52840` board, and connect
25 :goals: build
33 *** Booting Zephyr OS build zephyr-v3.3.0 ***
|
| /Zephyr-latest/samples/sensor/proximity_polling/ |
| D | README.rst | 29 After creating the devicetree overlay you can build the sample with:
34 :goals: build flash
42 *** Booting Zephyr OS build zephyr-v3.2.0-210-gd95295f08646 ***
|
| /Zephyr-latest/boards/nordic/nrf9131ek/doc/ |
| D | index.rst | 133 1. Build the Secure Zephyr application using ``-DBOARD=nrf9131ek/nrf9131`` and
135 2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9131ek/nrf9131/ns``.
141 The process to build the Secure firmware image using TF-M and the Non-Secure
144 1. Build the Non-Secure Zephyr application
146 To invoke the building of TF-M the Zephyr build system requires the
149 The Zephyr build system will perform the following steps automatically:
151 * Build the Non-Secure firmware image as a regular Zephyr application
152 * Build a TF-M (secure) firmware image
154 * Optionally build a bootloader image (MCUboot)
170 Build the Zephyr app in the usual way (see :ref:`build_an_application`
[all …]
|
| /Zephyr-latest/boards/intel/ehl/doc/ |
| D | index.rst | 39 Build Zephyr application
42 #. Build a Zephyr application; for instance, to build the ``hello_world``
48 :goals: build
53 created in the build directory after the application is built.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | wifi.rst | 28 Wi-Fi PSA crypto supported build
31 To enable PSA crypto API supported Wi-Fi build, the :kconfig:option:`CONFIG_WIFI_NM_WPA_SUPPLICANT_…
38 build process the certificates are converted to a C header file that is included by the Wi-Fi shell
49 $ west build -p -b <board> samples/net/wifi -- -DEXTRA_CONF_FILE=overlay-enterprise.conf
55 …$ west build -p -b <board> samples/net/wifi -- -DEXTRA_CONF_FILE=overlay-enterprise-variable-bufs.…
|
| /Zephyr-latest/samples/sensor/ds18b20/ |
| D | README.rst | 38 Make sure this node has ``status = "okay";``, then build and run with:
42 :goals: build flash
51 to the 1-Wire bus, build and flash with:
55 :goals: build flash
74 *** Booting Zephyr OS build zephyr-v2.6.0-1929-gf7abe4a6689e ***
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 43 to build the binary locally on their development machine and flash remotely,
50 Note that if you plan to use SOF on your board, you will need to build and
52 recommended you follow the `SOF instructions`_ to build and run SOF on Zephyr.
70 Follow the instructions in the rimage :file:`README.md` to build the tool on
72 use ``west config rimage.path /path/to/rimage-build/rimage``; see more details
73 in the output of ``west sign -h``. Running directly from the build directory
78 ``west config build.cmake-args -- -DRIMAGE_CONFIG_PATH=/path/to/my/rimage/config``.
84 The Zephyr SDK provides GCC-based toolchains necessary to build Zephyr for
86 may desire to build with the proprietary Xtensa toolchain distributed by
112 Build as usual.
[all …]
|
| /Zephyr-latest/boards/arm/fvp_base_revc_2xaemv8a/doc/ |
| D | index.rst | 74 Use this configuration to build basic Zephyr applications and kernel tests in the
81 :goals: build
83 This will build an image with the synchronization sample app.
84 Then you can run it with ``west build -t run``.
94 Checkout and Build the TF-A:
106 export ARMFVP_BL1_FILE=<path/to/tfa-a/build/fvp/release/bl1.bin>
107 export ARMFVP_FIP_FILE=<path/to/tfa-a/build/fvp/release/fip.bin>
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 87 The following examples build the test suite for the ``native_sim``
88 board. To build the test suite for a different board, replace the
91 To build the test application with the default configuration, testing
100 :goals: build
102 To build the test with additional RTC features enabled, use menuconfig
113 Then build the test application using the following command:
121 :goals: build
|
| /Zephyr-latest/boards/others/neorv32/doc/ |
| D | index.rst | 31 which results in a small run-time overhead. If the clock frequency is known at build time, this
87 Next, build and flash applications as usual (see :ref:`build_an_application` and
133 *** Booting Zephyr OS build zephyr-vn.n.nn ***
143 the NEORV32 ``image_gen`` binary is available, the build system will
147 In order for the build system to automatically detect the ``image_gen`` binary
149 can be passed at build time:
154 :goals: build
161 ``image_gen`` binary is available, the build system will automatically generate
180 *** Booting Zephyr OS build zephyr-vn.n.nn ***
|
12345678910>>...89
