Searched refs:image (Results 451 – 475 of 966) sorted by relevance
1...<<11121314151617181920>>...39
| /Zephyr-latest/boards/nxp/hexiwear/ |
| D | hexiwear_mk64f12.dts | 199 label = "image-0";
203 label = "image-1";
|
| /Zephyr-latest/boards/nxp/vmu_rt1170/ |
| D | vmu_rt1170.dtsi | 223 label = "image-0";
227 label = "image-1";
|
| /Zephyr-latest/boards/nxp/mimxrt1015_evk/ |
| D | mimxrt1015_evk.dts | 113 label = "image-0";
117 label = "image-1";
|
| /Zephyr-latest/boards/st/nucleo_f446re/doc/ |
| D | index.rst | 101 .. image:: img/nucleo_f446re_arduino_top_left.jpg
104 .. image:: img/nucleo_f446re_arduino_top_right.jpg
107 .. image:: img/nucleo_f446re_morpho_top_left.jpg
110 .. image:: img/nucleo_f446re_morpho_top_right.jpg
|
| /Zephyr-latest/boards/adi/max32655fthr/doc/ |
| D | index.rst | 19 .. image:: img/max32655fthr_img1.jpg
23 .. image:: img/max32655fthr_img2.jpg
27 .. image:: img/max32655fthr_img3.jpg
194 ``west flash`` command to write a firmware image into flash.
|
| /Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
| D | index.rst | 18 .. image:: img/v2m_musca_s1.jpg
327 be prepended to the image.
330 alias is ``0x0``. The image offset is calculated by adding the flash offset to the
334 the Intel formatted hex image.
345 .. image:: img/v2m_musca_s1_powered.jpg
364 Building a secure/non-secure image with Trusted Firmware-M
373 5. Concatenate the bootloader with the signed image blob.
405 Zephyr binaries with the MCUboot image, and converting it to Intel's hex format.
|
| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | README | 18 .pof file which will then put the image onto the device using quartus_pgm tool.
|
| /Zephyr-latest/arch/arm/core/cortex_m/tz/ |
| D | CMakeLists.txt | 12 # when building a Non-Secure image which shall have access to Secure
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 110 affect the Zephyr image's link, and will decrease the total amount of
122 area that the Zephyr image will be allowed to occupy. If zero, the
123 image will be able to occupy from the FLASH_LOAD_OFFSET to the end of
138 space between the beginning of the image and the start of the first
139 section to store an image header or any other metadata.
141 space to store the image header, which should also meet vector table
149 If non-zero, this option reduces the maximum size that the Zephyr image is allowed to
150 occupy, this is to allow for additional image storage which can be created and used by
151 other systems such as bootloaders (for MCUboot, this would include the image swap
152 fields and TLV storage at the end of the image).
[all …]
|
| /Zephyr-latest/boards/nordic/nrf9160dk/doc/ |
| D | index.rst | 154 image. The Secure image can be built using either Zephyr or
160 By default the Secure image for nRF9160 is built using TF-M.
175 The process to build the Secure firmware image using TF-M and the Non-Secure
176 firmware image using Zephyr requires the following action:
185 * Build the Non-Secure firmware image as a regular Zephyr application
186 * Build a TF-M (secure) firmware image
188 * Optionally build a bootloader image (MCUboot)
193 required, to adjust the Non-Secure image Flash and SRAM starting address
|
| /Zephyr-latest/boards/microchip/mec172xmodular_assy6930/doc/ |
| D | mec172xmodular_assy6930.rst | 176 #. Make the image generation available for Zephyr, by making the tool
187 SPI flash can be found in the same folder. If needed, a custom SPI image
194 #. Example command to generate 128MBit spi image for hello_world:
237 can find the image generation tool. This binary image can be used
|
| /Zephyr-latest/boards/st/disco_l475_iot1/ |
| D | disco_l475_iot1.dts | 232 label = "image-0";
337 label = "image-1";
342 label = "image-3";
|
| /Zephyr-latest/boards/gd/gd32f403z_eval/doc/ |
| D | index.rst | 131 #. To flash an image:
141 #. To debug an image:
170 #. To flash an image:
|
| /Zephyr-latest/boards/adi/eval_adin1110ebz/ |
| D | adi_eval_adin1110ebz.dts | 123 label = "image-0";
127 label = "image-1";
131 label = "image-scratch";
|
| /Zephyr-latest/boards/gd/gd32a503v_eval/doc/ |
| D | index.rst | 136 #. To flash an image:
146 #. To debug an image:
175 #. To flash an image:
|
| /Zephyr-latest/boards/gd/gd32e103v_eval/doc/ |
| D | index.rst | 128 #. To flash an image:
138 #. To debug an image:
167 #. To flash an image:
|
| /Zephyr-latest/share/sysbuild/image_configurations/ |
| D | BOOTLOADER_image_default.cmake | 6 # on Zephyr MCUboot / bootloader image.
|
| /Zephyr-latest/samples/subsys/display/cfb_custom_font/ |
| D | README.rst | 13 a PNG image, and then uses the generated header (``cfb_font_dice.h``)
|
| /Zephyr-latest/boards/microchip/mec1501modular_assy6885/ |
| D | CMakeLists.txt | 17 message(NOTICE "There is no SPI image generation tool for MacOS.")
|
| /Zephyr-latest/boards/microchip/mec15xxevb_assy6853/ |
| D | CMakeLists.txt | 17 message(NOTICE "There is no SPI image generation tool for MacOS.")
|
| /Zephyr-latest/boards/microchip/mec172xevb_assy6906/ |
| D | CMakeLists.txt | 17 message(NOTICE "There is no SPI image generation tool for MacOS.")
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | board.cmake | 23 …# Note: Please use JLINK above V7.50 (Only support run cm4 image when debugging due to default boo…
|
| /Zephyr-latest/boards/renesas/da14695_dk_usb/ |
| D | da14695_dk_usb.dts | 117 label = "image-0";
121 label = "image-1";
|
| /Zephyr-latest/boards/sparkfun/micromod/ |
| D | micromod_nrf52840.dts | 172 label = "image-0";
177 label = "image-1";
|
| /Zephyr-latest/boards/st/nucleo_g0b1re/ |
| D | nucleo_g0b1re.dts | 209 label = "image-0";
213 label = "image-1";
|
1...<<11121314151617181920>>...39
