Home
last modified time | relevance | path

Searched refs:image (Results 601 – 625 of 966) sorted by relevance

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

/Zephyr-latest/boards/adi/max32666fthr/doc/
Dindex.rst17 .. image:: img/max32666fthr_img1.jpg
21 .. image:: img/max32666fthr_img2.jpg
219 ``west flash`` command to write a firmware image into flash.
/Zephyr-latest/boards/arduino/nano_33_ble/doc/
Dindex.rst14 .. image:: img/arduino_nano_33_ble_sense.jpg
127 Then, you can flash the image using the above script.
142 .. image:: img/nano_33_ble_swd.jpg
/Zephyr-latest/arch/
DKconfig258 bool "Trusted Execution: Secure firmware image"
261 image for a platform that supports Trusted Execution. A
262 Secure firmware image will execute in Secure state. It may
264 Therefore, a Secure firmware image shall be able to
273 bool "Trusted Execution: Non-Secure firmware image"
276 firmware image for a platform that supports Trusted
277 Execution. A Non-Secure firmware image will execute
476 caution as enabling this will increase the image size by a
635 firmware image is chain-loaded, for example, by a debugger
843 that all RAM is mapped at boot, and not just the bounds of the Zephyr image.
[all …]
/Zephyr-latest/soc/nxp/imxrt/
DKconfig122 by booting an image targeting the Cortex-M4 from the Cortex-M7 CPU.
123 The M4 image will be loaded from flash into RAM based off a
/Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/
Dindex.rst104 This will load the image into flash.
117 To debug a previously flashed image, after resetting the board, use the 'debug'
/Zephyr-latest/boards/fanke/fk750m1_vbt6/doc/
Dindex.rst10 and image processing technologies.
14 Its wide range of hardware features, including advanced display and image processing capabilities,
/Zephyr-latest/boards/nxp/twr_ke18f/
Dtwr_ke18f.dts350 label = "image-0";
354 label = "image-1";
/Zephyr-latest/boards/atmel/sam0/saml21_xpro/doc/
Dindex.rst80 .. image:: img/atsaml21-xpro-pinout.jpg
169 #. To flash an image:
/Zephyr-latest/boards/nordic/nrf21540dk/
Dnrf21540dk_nrf52840.dts273 label = "image-0";
277 label = "image-1";
/Zephyr-latest/boards/nxp/mimxrt1040_evk/
Dmimxrt1040_evk.dts143 label = "image-0";
147 label = "image-1";
/Zephyr-latest/boards/atmel/sam0/samd21_xpro/doc/
Dindex.rst83 .. image:: img/ATSAMD21-XPRO-pinout.jpg
170 #. To flash an image:
/Zephyr-latest/boards/nxp/rd_rw612_bga/
Drd_rw612_bga.dtsi160 label = "image-0";
164 label = "image-1";
/Zephyr-latest/boards/cypress/cy8ckit_062_ble/doc/
Dindex.rst33 .. image:: img/cy8ckit-062-ble.jpg
180 #. To flash an image:
218 #. To flash an image:
228 The last step flash the M4 image on the flash. However, Cortex-M0 by default
/Zephyr-latest/boards/nxp/mimxrt1160_evk/doc/
Dindex.rst247 Dual core samples load the M4 core image from flash into the shared ``ocram``
250 To flash a dual core sample, the M4 image must be flashed first, so that it is
251 written to flash. Then, the M7 image must be flashed. The openamp sysbuild
252 sample will do this automatically by setting the image order.
/Zephyr-latest/boards/shields/frdm_cr20a/doc/
Dindex.rst15 .. image:: frdm_cr20a.jpg
/Zephyr-latest/doc/connectivity/canbus/
Disotp.rst39 .. image:: isotp_sequence.svg
/Zephyr-latest/boards/shields/st_b_lcd40_dsi1_mb1166/doc/
Dindex.rst19 .. figure:: image.jpg
/Zephyr-latest/boards/arm/mps3/
Dboard.cmake48 # TF-M (Secure) & Zephyr (Non Secure) image (when running
/Zephyr-latest/doc/develop/west/
Dzephyr-cmds.rst203 You can search for a specific descriptor in an image, for example::
211 You can dump all of the descriptors in an image using::
219 You can print the offset of the descriptors inside the image using::
/Zephyr-latest/include/zephyr/arch/arm/cortex_a_r/scripts/
Dlinker.ld226 * On non-XIP images this may enlarge image size up to 3 bytes. This
261 /* Align the start of image RAM with the
412 /* To provide the image size as a const expression,
/Zephyr-latest/boards/adi/max32690evkit/doc/
Dindex.rst14 .. image:: img/max32690evkit.jpg
18 .. image:: img/max32690evkit_img2.jpg
287 ``west flash`` command to write a firmware image into flash.
/Zephyr-latest/subsys/bluetooth/host/
DCMakeLists.txt98 A hardcoded OOB data set will be stored in the image, do not use in
/Zephyr-latest/subsys/
DKconfig63 that can either be built as a part of the system image or as a
/Zephyr-latest/samples/tfm_integration/
Dtfm_integration.rst19 images to be verified and either accepted or rejected during the image
/Zephyr-latest/soc/espressif/common/
DKconfig23 Output is a single image that should be flashed at an offset defined by used SOC.

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