| /Zephyr-latest/dts/common/nordic/ |
| D | nrf5340_cpuapp_partition.dtsi | 15 * 0x0001_0000 Primary image area (448 KB):
16 * 0x0001_0000 Secure image primary (256 KB)
17 * 0x0005_0000 Non-secure image primary (192 KB)
18 * 0x0008_0000 Secondary image area (448 KB):
19 * 0x0008_0000 Secure image secondary (256 KB)
20 * 0x000c_0000 Non-secure image secondary (192 KB)
37 label = "image-0";
41 label = "image-0-nonsecure";
45 label = "image-1";
49 label = "image-1-nonsecure";
[all …]
|
| D | nrf91xx_partition.dtsi | 15 * 0x0001_0000 Primary image area (448 KB):
16 * 0x0001_0000 Secure image primary (256 KB)
17 * 0x0005_0000 Non-secure image primary (192 KB)
18 * 0x0008_0000 Secondary image area (448 KB):
19 * 0x0008_0000 Secure image secondary (256 KB)
20 * 0x000c_0000 Non-secure image secondary (192 KB)
37 label = "image-0";
41 label = "image-0-nonsecure";
45 label = "image-1";
49 label = "image-1-nonsecure";
[all …]
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | CMakeLists.txt | 7 set(image mcuboot) variable
9 APPLICATION ${image}
14 sysbuild_add_dependencies(CONFIGURE ${DEFAULT_IMAGE} ${image})
15 sysbuild_add_dependencies(FLASH ${DEFAULT_IMAGE} ${image})
17 set_config_string(${image} CONFIG_BOOT_SIGNATURE_KEY_FILE "${SB_CONFIG_BOOT_SIGNATURE_KEY_FILE}")
18 set_config_bool(${image} CONFIG_BOOT_ENCRYPT_IMAGE "${SB_CONFIG_BOOT_ENCRYPTION}")
20 …set_config_string(${image} CONFIG_BOOT_ENCRYPTION_KEY_FILE "${SB_CONFIG_BOOT_ENCRYPTION_KEY_FILE}")
|
| /Zephyr-latest/tests/cmake/zephyr_get/ |
| D | sysbuild.cmake | 3 # Add a few copies of the same image, so that we can configure
7 set(image ${DEFAULT_IMAGE}_${suffix}) variable
8 if(NOT TARGET ${image})
10 APPLICATION ${image}
13 list(APPEND IMAGES ${image})
19 foreach(image ${IMAGES})
20 sysbuild_get(ASSERT_FAIL_COUNT IMAGE ${image} CACHE)
22 set(failures "${failures}\n - ${image}: ${ASSERT_FAIL_COUNT} assertion(s) failed")
28 message(FATAL_ERROR "Test failures per sysbuild image: ${failures}")
|
| /Zephyr-latest/share/sysbuild/cmake/ |
| D | domains.cmake | 10 foreach(image ${IMAGES})
11 set(domains_yaml "${domains_yaml}\n - name: ${image}")
12 set(domains_yaml "${domains_yaml}\n build_dir: $<TARGET_PROPERTY:${image},_EP_BINARY_DIR>")
15 foreach(image ${IMAGES_FLASHING_ORDER})
16 set(flash_cond "$<NOT:$<BOOL:$<TARGET_PROPERTY:${image},BUILD_ONLY>>>")
17 set(domains_yaml "${domains_yaml}$<${flash_cond}:\n - ${image}>")
|
| /Zephyr-latest/boards/st/nucleo_l552ze_q/ |
| D | nucleo_l552ze_q_stm32l552xx_ns.dts | 41 * multiple image boot, no tests.
50 /* Secure image primary slot */
52 label = "image-0";
55 /* Non-secure image primary slot */
57 label = "image-0-nonsecure";
60 /* Secure image secondary slot */
62 label = "image-1";
65 /* Non-secure image secondary slot */
67 label = "image-1-nonsecure";
|
| /Zephyr-latest/boards/st/b_u585i_iot02a/ |
| D | b_u585i_iot02a_stm32u585xx_ns.dts | 47 /* Secure image primary slot */
49 label = "image-0";
52 /* Non-secure image primary slot */
54 label = "image-0-nonsecure";
57 /* Secure image secondary slot */
59 label = "image-1";
62 /* Non-secure image secondary slot */
64 label = "image-1-nonsecure";
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 3 Application/software image management group
6 Application/software image management group defines following commands:
35 The "slot" and "image" definition comes from mcuboot where "image" would
43 to single application, but will name them as "image-0" and "image-1" respectively.
53 | 1 | "slot0_partition" | "image-0" |
54 | | "slot1_partition" | "image-1" |
56 | 2 | "slot2_partition" | "image-2" |
57 | | "slot3_partition" | "image-3" |
99 Below definition of the response contains "image" field that has been marked
101 does not support more than one image. The field is mandatory when application
[all …]
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/ |
| D | mcumgr.py | 22 image: int
56 def image_upload(self, image: Path | str, slot: int | None = None, timeout: int = 30):
78 image=int(m.group(1)),
93 for image in image_list:
94 if 'active' not in image.flags:
95 return image.hash
101 for image in image_list:
102 if 'confirmed' not in image.flags:
103 return image.hash
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 16 bool "Mcumgr handlers for image management"
24 Enables MCUmgr handlers for image management
31 bool "Use heap mem pool for flash image DFU context"
33 Use heap to allocate flash image upload context, otherwise a static variable will
34 be used. The context object is used by MCUMGR_GRP_IMG_MANAGER to buffer image writes
35 and has significant size, mainly affected by image write buffer of
59 bool "Verbose error responses when uploading application image"
66 bool "Allow to confirm secondary slot of non-active image"
69 Allows to confirm secondary (non-active) slot of non-active image.
71 image, via MCUmgr commands, to prevent confirming something that is
[all …]
|
| /Zephyr-latest/dts/common/espressif/ |
| D | partitions_0x0_amp_16M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x0_amp_2M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x0_amp_32M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x0_amp_4M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x0_amp_8M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x1000_amp_16M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x1000_amp_2M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x1000_amp_32M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x1000_amp_4M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| D | partitions_0x1000_amp_8M.dtsi | 20 label = "image-0";
25 label = "image-0-appcpu";
30 label = "image-1";
35 label = "image-1-appcpu";
45 label = "image-scratch";
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/ |
| D | bl5340_dvk_nrf5340_cpuapp_partition_conf.dtsi | 14 * Secure image will be placed, by default, in flash0
16 * Secure image will use sram0 for system memory.
18 * Non-Secure image will be placed in slot0_ns, and use
21 * Note that the Secure image only requires knowledge of
22 * the beginning of the Non-Secure image (not its size).
43 * - Lowest 256 kB SRAM allocated to Secure image (sram0_s)
44 * - Middle 192 kB allocated to Non-Secure image (sram0_ns)
|
| /Zephyr-latest/tests/subsys/dfu/mcuboot_multi/ |
| D | native_sim.overlay | 22 label = "image-0";
26 label = "image-1";
30 label = "image-2";
34 label = "image-3";
|
| D | nrf52840dk_nrf52840.overlay | 23 label = "image-0";
27 label = "image-1";
31 label = "image-2";
35 label = "image-3";
|
| /Zephyr-latest/tests/subsys/mgmt/mcumgr/img_mgmt_slot_info/boards/ |
| D | nrf52840dk_nrf52840_dual_slot.overlay | 22 label = "image-0";
26 label = "image-1";
30 label = "image-2";
34 label = "image-3";
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 8 receive the firmware image binary from the Distributor node.
20 started. Each firmware image in the image list must be independently updatable, and should have its
24 firmware update capabilities could have three entries in the firmware image list, each with their
31 the binary image. The interaction between the Firmware Update Server, BLOB Transfer Server and
44 firmware image metadata. The Firmware Update Server performs the transfer check by calling the
61 :ref:`bluetooth_mesh_models_rpr_srv` is supported, the Composition Data of the new firmware image
63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2,
65 firmware image until the device is reprovisioned with Node Provisioning Protocol Interface (NPPI)
73 and 130. The Models Metadata for the old image will be loaded into Models Metadata Page 0, and the
74 Models Metadata for the new image will be loaded into Models Metadata Page 128.
[all …]
|
