Home
last modified time | relevance | path

Searched refs:image (Results 576 – 600 of 966) sorted by relevance

1...<<21222324252627282930>>...39

/Zephyr-latest/boards/st/stm32u5a9j_dk/
Dstm32u5a9j_dk.dts270 label = "image-0";
274 label = "image-1";
/Zephyr-latest/boards/arduino/nano_33_iot/doc/
Dindex.rst12 .. image:: img/nano_33_iot.jpg
152 #. Flash the image:
/Zephyr-latest/boards/adi/max32690fthr/doc/
Dindex.rst99 ``west flash`` command to write a firmware image into flash. Here is an example
119 ``west debug`` command to write a firmware image into flash and start a debug
/Zephyr-latest/boards/nxp/frdm_mcxn947/
Dfrdm_mcxn947.dtsi149 label = "image-0";
153 label = "image-1";
/Zephyr-latest/boards/nxp/lpcxpresso11u68/doc/
Dindex.rst102 a J-Link interface. It depends on the embedded firmware image. The default
114 The firmware image of the LPC-Link2 can be updated using the
/Zephyr-latest/boards/arduino/zero/doc/
Dindex.rst13 .. image:: img/arduino_zero.jpg
147 #. To flash an image:
/Zephyr-latest/soc/st/stm32/
DKconfig.defconfig68 # Get flash configuration for NS image from dts flash partition
/Zephyr-latest/boards/qemu/riscv32e/doc/
Dindex.rst28 This will build an image with the synchronization sample app, boot it using
/Zephyr-latest/boards/sparkfun/red_v_things_plus/doc/
Dindex.rst12 .. image:: img/sparkfun_red_v_things_plus.jpg
/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst12 image to be used in a DFU operation.
/Zephyr-latest/boards/shields/x_nucleo_iks01a1/doc/
Dindex.rst16 .. image:: img/x-nucleo-iks01a1.jpg
/Zephyr-latest/boards/qemu/riscv32_xip/doc/
Dindex.rst28 This will build an image with the synchronization sample app, boot it using
/Zephyr-latest/boards/qemu/riscv64/doc/
Dindex.rst37 This will build an image with the synchronization sample app, boot it using
/Zephyr-latest/boards/arm/mps3/
Dmps3_corstone300_an552_ns.dts78 * project has defined for that board - a single image boot is
Dmps3_corstone300_fvp_ns.dts78 * project has defined for that board - a single image boot is
Dmps3_corstone310_an555_ns.dts78 * project has defined for that board - a single image boot is
Dmps3_corstone310_fvp_ns.dts78 * project has defined for that board - a single image boot is
Dmps3_corstone300_an547_ns.dts79 * project has defined for that board - a single image boot is
/Zephyr-latest/subsys/retention/
DKconfig.blinfo23 MCUboot and the running image. This can be used by applications so
/Zephyr-latest/soc/espressif/esp32c2/
DCMakeLists.txt21 # make ESP ROM loader compatible image
/Zephyr-latest/boards/renode/cortex_r8_virtual/doc/
Dindex.rst40 This will build an image with the synchronization sample app, boot it using
/Zephyr-latest/samples/net/ptp/
DREADME.rst66 When the Zephyr image is build, you can start it like this:
/Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/arm/mps2/
Dmps2_an521_cputest.dts34 * code and data memories to this secure firmware image.
/Zephyr-latest/boards/arm/mps2/
Dmps2_an521_cpu0.dts34 * code and data memories to this secure firmware image.
/Zephyr-latest/doc/services/tfm/
Dbuild.rst9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
60 (BL2) and firmware images must be signed with a private key. The firmware image
62 key, which is stored inside the secure bootloader firmware image.

1...<<21222324252627282930>>...39