Searched refs:image (Results 626 – 650 of 966) sorted by relevance
1...<<21222324252627282930>>...39
| /Zephyr-latest/samples/subsys/nvs/ |
| D | README.rst | 34 After flashing the image to the board the output on the console shows the
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/train/ |
| D | README.md | 62 *This image was derived from visualizing the 'model.tflite' file in [Netron](https://github.com/lut…
|
| /Zephyr-latest/boards/shields/link_board_eth/doc/ |
| D | index.rst | 15 .. image:: img/link_board_eth.jpg
|
| /Zephyr-latest/boards/qemu/arc/doc/ |
| D | index.rst | 77 This will build an image with the synchronization sample app, boot it using
|
| /Zephyr-latest/lib/libc/minimal/ |
| D | Kconfig | 21 the image.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr.rst | 140 limiting the maximum packet size (most likely to occur when using image
149 bootloader, providing the ability to send and upgrade a Zephyr image to a
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 196 to support MCUboot and a signed image is generated, the version information will be automatically
197 included in the image data.
|
| /Zephyr-latest/boards/phytec/phyboard_electra/doc/ |
| D | index.rst | 139 …-AM64x-PD23.2.1/images/ampliphy/phyboard-electra-am64xx-2/phytec-headless-image-phyboard-electra-a…
142 …-AM64x-PD23.2.1/images/ampliphy/phyboard-electra-am64xx-2/phytec-headless-image-phyboard-electra-a…
|
| /Zephyr-latest/boards/phytec/phyboard_nash/doc/ |
| D | index.rst | 44 .. image:: img/phyboard_nash.webp
156 This will build an image with the synchronization sample app, boot it and
|
| /Zephyr-latest/boards/adafruit/grand_central_m4_express/doc/ |
| D | index.rst | 135 #. Flash the image:
153 #. Flash the image:
|
| /Zephyr-latest/boards/arduino/mkrzero/doc/ |
| D | index.rst | 12 .. image:: img/arduino_mkrzero.jpg
164 #. Flash the image:
|
| /Zephyr-latest/boards/nxp/mimxrt1064_evk/ |
| D | mimxrt1064_evk.dts | 197 label = "image-0";
201 label = "image-1";
|
| /Zephyr-latest/boards/atmel/sam0/samr34_xpro/doc/ |
| D | index.rst | 98 .. image:: img/atsamr34-xpro-pinout.jpg
183 #. To flash an image:
|
| /Zephyr-latest/soc/infineon/cat1b/cyw20829/ |
| D | linker.ld | 202 * On non-XIP images this may enlarge image size up to 3 bytes. This
244 /* Align the start of image RAM with the
476 /* To provide the image size as a const expression,
|
| /Zephyr-latest/cmake/ |
| D | mcuboot.cmake | 87 # If single slot mode, or if in firmware updater mode and this is the firmware updater image,
96 # Basic 'imgtool sign' command with known image information.
121 # RAM load requires setting the location of where to load the image to
|
| /Zephyr-latest/boards/luatos/esp32s3_luatos_core/doc/ |
| D | index.rst | 13 .. image:: img/esp32s3_luatos_core.jpg
81 .. image:: img/esp32s3_luatos_core_pinout.jpg
142 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
| D | index.rst | 237 I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
238 I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
242 I: Jumping to the first image slot
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 147 same firmware image that is programmed onto the chip):
164 When using a Zephyr Host (left side of image), two instances of Zephyr OS
166 must be programmed into each of the chips respectively. The Host build image
174 of the image shows. One can indeed take one of the many existing GNU/Linux
|
| /Zephyr-latest/boards/nxp/imx95_evk/doc/ |
| D | index.rst | 149 This will build an image (zephyr.bin) with the synchronization sample app.
188 This will build an image (zephyr.bin) with the synchronization sample app.
232 To program M7, an i.MX container image ``flash.bin`` must be made, which contains
234 image and so on.
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | CMakeLists.txt | 403 # the image manifest
455 # Use the TF-M NS binary as the Non-Secure application firmware image
458 # Use the Zephyr binary as the Non-Secure application firmware image
463 # Merge tfm_s and zephyr (NS) image to a single binary.
507 #Create and sign for concatenated binary image, should align with the TF-M BL2
|
| /Zephyr-latest/boards/espressif/esp_wrover_kit/doc/ |
| D | index.rst | 33 .. image:: img/esp-wrover-kit-block-diagram.jpg
162 .. |jmpextpwr| image:: img/esp-wrover-kit-v4.1-jp7-ext_5v.jpg
164 .. |jmpusbpwr| image:: img/esp-wrover-kit-v4.1-jp7-usb_5v.jpg
166 .. |jmpjtag| image:: img/esp-wrover-kit-v4.1-jp2-jtag.jpg
168 .. |jmpuart| image:: img/esp-wrover-kit-v4.1-jp2-tx-rx.jpg
170 .. |jmpctrl| image:: img/esp-wrover-kit-v4.1-jp14.jpg
507 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_root.cmake | 22 # correctly to image builds.
|
| /Zephyr-latest/samples/sensor/lps22hh_i3c/ |
| D | README.rst | 36 bus. Therefore, when flashing a new image, a power cycle is needed
|
| /Zephyr-latest/samples/subsys/settings/ |
| D | README.rst | 38 After running the image to the board the output on the console shows the
|
| /Zephyr-latest/boards/shields/x_nucleo_wb05kn1/doc/ |
| D | index.rst | 15 .. image:: img/x-nucleo-wb05kn1.webp
|
1...<<21222324252627282930>>...39
