Searched full:build (Results 176 – 200 of 2206) sorted by relevance
12345678910>>...89
/Zephyr-latest/tests/net/wifi/wifi_nm/ |
D | testcase.yaml | 13 - rd_rw612_bga/rw612/ethernet # Requires binary blobs to build 14 - frdm_rw612 # Requires binary blobs to build
|
/Zephyr-latest/doc/develop/sca/ |
D | sparse.rst | 21 To run a sparse verification build :ref:`west build <west-building>` should be 26 … west build -d hello -b intel_adsp/cavs25 zephyr/samples/hello_world -- -DZEPHYR_SCA_VARIANT=sparse
|
/Zephyr-latest/samples/basic/sys_heap/ |
D | README.rst | 21 :goals: build 24 To build for another board, change "native_sim" above to that board's name. 29 Run build/zephyr/zephyr.exe
|
/Zephyr-latest/samples/subsys/fs/fatfs_fstab/ |
D | README.rst | 17 To run this sample, build it for the ``native_sim`` board 18 and afterwards run the generated executable file within the build folder. 27 :goals: build
|
/Zephyr-latest/tests/drivers/build_all/bbram/ |
D | testcase.yaml | 11 drivers.bbram.build: 15 drivers.bbram.emul.build:
|
/Zephyr-latest/tests/drivers/build_all/display/ |
D | testcase.yaml | 9 drivers.display.build.default: 14 drivers.display.build.rk055hdmipi4ma0:
|
/Zephyr-latest/tests/drivers/build_all/flash/ |
D | testcase.yaml | 10 drivers.flash.build: 13 drivers.flash.emul.build:
|
/Zephyr-latest/tests/net/all/ |
D | testcase.yaml | 10 net.build: 13 net.build.preempt:
|
/Zephyr-latest/boards/infineon/cy8cproto_063_ble/doc/ |
D | index.rst | 48 Build blinking led sample 56 :goals: build 81 west config build.cmake-args -- -DOPENOCD=path/to/infineon/openocd/bin/openocd.exe 83 # Do a pristine build once after setting CMake argument 84 west build -b cy8cproto_063_ble -p always samples/basic/blinky 94 west config build.cmake-args -- -DOPENOCD=path/to/infineon/openocd/bin/openocd 96 # Do a pristine build once after setting CMake argument 97 west build -b cy8cproto_063_ble -p always samples/basic/blinky
|
/Zephyr-latest/tests/drivers/build_all/counter/ |
D | testcase.yaml | 7 drivers.counter.build.xlnx: 11 drivers.counter.build.i2c:
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.6.rst | 12 Additionally, this release adds many improvements for documentation, build 99 * Added raw HCI API to enable physical HCI transport for a Controller-only build. 106 Build Infrastructure 109 * Makefile: Changed outdir into board-specific directory to avoid build collisions. 111 * Makefile: Added support for third party build systems. 115 * Sanity: Added extra arguments to be passed to the build. 118 * Modified build infrastructure to support unified kernel. 175 * ``ZEP-308`` - Build System cleanup and Kernel / Application build separation 282 * ``ZEP-517`` - build on windows failed "zephyr/Makefile:869: \*\*\* multiple target patterns" 289 …n "Application Development Primer" and "Developing an Application and the Build System" is largely… [all …]
|
/Zephyr-latest/soc/nuvoton/npcx/ |
D | Kconfig | 18 bool "Build npcx binary in BIN format" 21 Build a "raw" binary zephyr/zephyr.npcx.bin in the build directory. 25 bool "Build npcx binary in HEX format" 28 Build an HEX binary zephyr/zephyr.npcx.hex in the build directory.
|
/Zephyr-latest/boards/innblue/innblue21/doc/ |
D | index.rst | 61 1. Build the Secure Zephyr application using ``-DBOARD=innblue21`` and 63 2. Build the Non-Secure Zephyr application using ``-DBOARD=innblue21/nrf9160/ns``. 74 Build the Zephyr app in the usual way (see :ref:`build_an_application` 82 found in :ref:`nordic_segger_flashing`. Then build and flash 97 Then build and flash the application in the usual way. 102 :goals: build flash
|
/Zephyr-latest/boards/innblue/innblue22/doc/ |
D | index.rst | 61 1. Build the Secure Zephyr application using ``-DBOARD=innblue22`` and 63 2. Build the Non-Secure Zephyr application using ``-DBOARD=innblue22/nrf9160/ns``. 74 Build the Zephyr app in the usual way (see :ref:`build_an_application` 82 found in :ref:`nordic_segger_flashing`. Then build and flash 97 Then build and flash the application in the usual way. 102 :goals: build flash
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-dev.rst | 53 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported 54 but you might need to build Zephyr more than once if you are using a dual-chip 56 build type (e.g., one running the Host, the other the Controller). 78 #. A :ref:`Host-only <bluetooth-build-types>` application running in the 84 * A :ref:`Controller-only <bluetooth-build-types>` build of Zephyr 109 Refer to :ref:`bluetooth_qemu_native` for full instructions on how to build and 149 Just like with the :ref:`native_sim <native_sim>` target, the build result is a normal Linux 155 <bluetooth-build-types>`, but it is also possible to build the controller with one of the 159 With the :ref:`nrf5340bsim <nrf5340bsim>`, you can build with either, both controller and host
|
/Zephyr-latest/doc/ |
D | glossary.rst | 16 The set of user-supplied files that the Zephyr build system uses 17 to build an application image for a specified board configuration. 20 The application's kernel configuration settings direct the build system 51 The Zephyr build system defines one or more board configurations 53 specified by the build system can be over-ridden by the application, 59 information that may be required to actually build a Zephyr image for it. 77 The full string that can be provided to any of the Zephyr build tools to 153 particular type or configuration of a build for a combination of :term:`SoC` 157 build. 197 Zephyr build system to integrate the source code and configuration files [all …]
|
/Zephyr-latest/tests/drivers/build_all/fuel_gauge/ |
D | testcase.yaml | 5 drivers.fuel_gauge.build: 13 drivers.fuel_gauge.emul.build:
|
/Zephyr-latest/.github/workflows/ |
D | twister.yaml | 23 twister-build-prep: 26 twister-build: 29 needs: twister-build-prep 30 if: needs.twister-build-prep.outputs.size != 0 37 subset: ${{fromJSON(needs.twister-build-prep.outputs.subset)}} 48 WEEKLY_OPTIONS: ' -M --build-only --all --show-footprint --report-filtered' 155 … if [ "${{matrix.subset}}" = "1" -a ${{needs.twister-build-prep.outputs.fullrun}} = 'True' ]; then 214 - twister-build 216 # the build-and-test job might be skipped, we don't need to run this job then 221 if: needs.twister-build.result == 'failure' [all …]
|
/Zephyr-latest/doc/_extensions/zephyr/ |
D | doxyrunner.py | 11 This Sphinx plugin can be used to run Doxygen build as part of the Sphinx build 16 - Doxygen build is run before Sphinx reads input files 18 - Changes in the Doxygen input files are tracked so that Doxygen build is only 37 - ``outdir``: Doxygen build output directory (inserted to ``OUTPUT_DIRECTORY``) 38 - ``outdir_var``: Variable representing the Doxygen build output directory, 149 outdir: Output directory of the Doxygen build. 202 env: Sphinx build environment instance. 218 # build a set with input files hash 269 """Run Doxygen build. 296 """Synchronize Doxygen output with a previous build. [all …]
|
/Zephyr-latest/boards/m5stack/m5stickc_plus/doc/ |
D | index.rst | 106 2. Manual build 120 The sysbuild makes possible to build and flash all necessary images needed to 123 To build the sample application using sysbuild use the command: 129 :goals: build 136 Build directory structure created by sysbuild is different from traditional 137 Zephyr build. Output is structured by the domain subdirectories: 141 build/ 154 With ``--sysbuild`` option the bootloader will be re-build and re-flash 155 every time the pristine build is used. 157 For more information about the system build please read the :ref:`sysbuild` documentation. [all …]
|
/Zephyr-latest/boards/lilygo/ttgo_t8s3/doc/ |
D | index.rst | 109 2. Manual build 123 The sysbuild makes possible to build and flash all necessary images needed to 126 To build the sample application using sysbuild use the command: 132 :goals: build 139 Build directory structure created by sysbuild is different from traditional 140 Zephyr build. Output is structured by the domain subdirectories: 144 build/ 157 With ``--sysbuild`` option the bootloader will be re-build and re-flash 158 every time the pristine build is used. 160 For more information about the system build please read the :ref:`sysbuild` documentation. [all …]
|
/Zephyr-latest/cmake/sca/eclair/ECL/ |
D | adopted_code.ecl | 2 -file_tag+={adopted,"^zephyr/build/zephyr/include/generated/autoconf\\.h$"} 6 -file_tag+={adopted,"^zephyr/build/zephyr/kobject_.*\\.c$"}
|
/Zephyr-latest/tests/drivers/build_all/charger/ |
D | testcase.yaml | 5 drivers.charger.build: 13 drivers.charger.emul.build:
|
/Zephyr-latest/tests/drivers/build_all/eeprom/ |
D | testcase.yaml | 7 drivers.eeprom.build: 16 drivers.eeprom.emul.build:
|
/Zephyr-latest/tests/drivers/build_all/rtc/ |
D | testcase.yaml | 7 drivers.rtc.build.pcf8523: 14 drivers.rtc.build.i2c:
|
12345678910>>...89