Searched refs:image (Results 351 – 375 of 966) sorted by relevance
1...<<11121314151617181920>>...39
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 002_enhancement.md | 27 Add any other context or graphics (drag-and-drop an image) about the feature request here.
|
| D | 004_feature_request.md | 27 Add any other context or graphics (drag-and-drop an image) about the feature request here.
|
| /Zephyr-latest/soc/nuvoton/npcx/ |
| D | Kconfig | 11 On NPCX series chip, the NPCX ROM code loads firmware image from flash
29 This is generated from the npcx BIN image.
131 bool "Firmware image crc check"
133 When enabled, the firmware image will be verified at boot using a
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 38 means that the command will be ran once with the first image flashing process per set of board
39 targets, or to ``last`` which will be ran once for the final image flash per set of board targets.
90 include MCUboot as a secondary image:
99 first image:
|
| /Zephyr-latest/boards/st/nucleo_f412zg/doc/ |
| D | index.rst | 100 .. image:: img/nucleo_f412zg_zio_left.jpg
103 .. image:: img/nucleo_f412zg_zio_right.jpg
106 .. image:: img/nucleo_f412zg_morpho_left.jpg
109 .. image:: img/nucleo_f412zg_morpho_right.jpg
|
| /Zephyr-latest/boards/nxp/frdm_rw612/doc/ |
| D | index.rst | 158 with the application image directly, forming one single monolithic image.
168 with the application image directly, forming one single monolithic image.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 32 has certain implications about what the Zephyr application image can and can
36 * Resource allocation for Zephyr relies on choices made in the secure image.
43 order (secure boot > secure image > ns image).
63 the (TF-M) Secure Processing Environment image happens based on a set of PSA
90 secure boot image, which verifies that the secure and non-secure images are
94 this image is **immutable**.
112 Zephyr application image in this case.
158 * Client software is responsible for writing a new image to the secondary slot
168 * The ``AES-CTR`` key is included in the image and can be encrypted using:
184 Once the secure bootloader has finished executing, a TF-M based secure image
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/doc/ |
| D | index.rst | 169 incorporated for application image storage and large datasets.
277 firmware image for the application core. The Secure image can be built
284 By default the Secure image for BL5340's application core is
290 The process to build the Secure firmware image using TF-M and the
291 Non-Secure firmware image using Zephyr requires the following steps:
300 * Build the Non-Secure firmware image as a regular Zephyr application
301 * Build a TF-M (secure) firmware image
302 * Merge the output image binaries together
303 * Optionally build a bootloader image (MCUboot)
308 be required, to adjust the Non-Secure image Flash and SRAM starting
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/include/mgmt/mcumgr/grp/img_mgmt/ |
| D | img_mgmt_priv.h | 142 int img_mgmt_get_next_boot_slot(int image, enum img_mgmt_next_boot_type *type);
|
| /Zephyr-latest/samples/subsys/ipc/ipc_service/static_vrings/ |
| D | sysbuild.cmake | 21 # remote core's build, such as the output image's LMA
|
| /Zephyr-latest/soc/raspberrypi/rpi_pico/rp2350/ |
| D | Kconfig | 29 RP23XX devices to consider this a valid image in flash.
|
| /Zephyr-latest/boards/arduino/opta/ |
| D | arduino_opta_stm32h747xx_m4.dts | 37 label = "image-0";
|
| /Zephyr-latest/boards/arm/mps2/ |
| D | CMakeLists.txt | 7 # Building a firmware image for CPU1: this requires a binary
|
| /Zephyr-latest/boards/seco/stm32f3_seco_d23/ |
| D | stm32f3_seco_d23.dts | 200 label = "image-0";
204 label = "image-1";
212 label = "image-scratch";
|
| /Zephyr-latest/boards/u-blox/ubx_bmd330eval/ |
| D | ubx_bmd330eval_nrf52810.dts | 201 label = "image-0";
205 label = "image-1";
209 label = "image-scratch";
|
| /Zephyr-latest/boards/u-blox/ubx_bmd360eval/ |
| D | ubx_bmd360eval_nrf52811.dts | 202 label = "image-0";
206 label = "image-1";
210 label = "image-scratch";
|
| /Zephyr-latest/boards/st/nucleo_wb55rg/ |
| D | nucleo_wb55rg.dts | 231 label = "image-0";
235 label = "image-1";
239 label = "image-scratch";
|
| /Zephyr-latest/boards/st/sensortile_box/ |
| D | sensortile_box.dts | 229 label = "image-0";
233 label = "image-1";
237 label = "image-scratch";
|
| /Zephyr-latest/boards/ezurio/mg100/ |
| D | mg100.dts | 199 label = "image-0";
227 label = "image-1";
232 label = "image-scratch";
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 66 MCUboot will take contents of secondary slot of an image and will overwrite primary slot
77 can boot from either partition and will select one with higher application image version,
101 will select the image with the higher version number, copy it to RAM and begin execution
102 from there. The image must be linked to execute from RAM, the address that it is copied
157 bool "Encrypted image support"
|
| /Zephyr-latest/subsys/bindesc/ |
| D | Kconfig.host_info | 14 The name of the host that the image was compiled on
|
| /Zephyr-latest/samples/subsys/llext/modules/ |
| D | Kconfig | 18 linked in the Zephyr image.
|
| /Zephyr-latest/arch/arm/core/cortex_m/ |
| D | vector_table_pad.ld | 9 * Zephyr image does not attempt to use the area which we reserve to
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/ |
| D | Kconfig.defconfig | 22 # Adjust the offset of the output image if building for RT11xx SOC
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | Kconfig.defconfig | 22 # Adjust the offset of the output image if building for RT11xx SOC
|
1...<<11121314151617181920>>...39
