Home
last modified time | relevance | path

Searched refs:image (Results 1 – 25 of 47) sorted by relevance

12

/mcuboot-3.7.0/docs/
Dtestplan-mynewt.md8 with wrong key images are not swapped to, and image signed with correct key
20 Build and load good image in slot 0:
22 * `newt create-image k64f_blinky 1.0.1 key_<sign-algo>.pem`
28 *If testing RSA/PSS `newt create-image` needs to be passed in the extra*
31 `newt create-image k64f_blinky 1.0.1 key_rsa.pem --rsa-pss`
35 Build and load image in slot 1 with no signing, signed with
37 test image and check that swap only happens for image signed with
40 * `newt create-image k64f_blinky2 1.0.2 <one-of-the-sign-keys-or-none>`
41 * `newtmgr image upload k64f_blinky2`
42 * `newtmgr image list`
[all …]
Dreadme-nuttx.md6 - `CONFIG_MCUBOOT_PRIMARY_SLOT_PATH`: MTD partition for the application firmware image PRIMARY slot;
7 - `CONFIG_MCUBOOT_SECONDARY_SLOT_PATH`: MTD partition for the application firmware image SECONDARY …
15 …_map_backend.h>`, for enabling MCUboot to manage the application firmware image slots in the devic…
25image and, once this application firmware image is assured to be valid, the application may confir…
27image from a webserver, installing it and triggering the firmware update process for the next boot…
31image, it delegates the loading and execution of the application firmware image to a platform-spec…
39 …map_backend/flash_map_backend.h>` expects that the MTD driver for a given image partition handles …
Dimgtool.md51 Image signing takes an image in binary or Intel Hex format intended for the
56 Create a signed or unsigned image
68 it from the image version.
74 beginning of the image
75 -S, --slot-size INTEGER Size of the slot where the image will be
77 --pad Pad image to --slot-size bytes, adding
79 --confirm When padding the image, mark it as confirmed
88 -E, --encrypt filename Encrypt image using the provided public key
92 -L, --load-addr INTEGER Load address for image when it should run
106 already prepended a zeroed header to the image. If another build system is
[all …]
Dreadme-espressif.md184 For signing with a crypto key and guarantee the authenticity of the image being booted, see the
185 section [MCUboot image signature verification](#mcuboot-image-signature-verification) below.*
204 MCUboot will then verify and compare the new image version number with the current one before
207 Version number is added to the image when signing it with `imgtool` (`-v` parameter, e.g.
212 It is also possible to rely on a security counter, also added to the image when signing with
213 `imgtool` (`-s` parameter), apart from version number. This allows image downgrade at some extent,
221 E.g.: if the current image was signed using `-s 1` parameter, an eventual update image must have
228 MCUboot design the image in Primary Slot, from where the image is executed, is stored plaintext.
229 Espressif chips have off-chip flash memory, so to ensure a security chain along with MCUboot image
233 ## [MCUboot image signature verification](#mcuboot-image-signature-verification)
[all …]
Dtestplan-zephyr.md27 messages, and lastly: "main: Unable to find bootable image".
33 This should print "main: Jumping to the first image slot", and you
34 should get an image "hello1".
53 Repeat this, to make sure we can mark the image as OK, and that a
64 And make sure this stays in the "hello2" image.
Dreadme-mynewt.md34 Also, MCUboot uses a different image header struct as well as slightly
38 `newt create-image <target> <version> <pubkey> -2`
43 like listing images and uploading a new image to `slot0`. The serial bootloader
49 newtmgr --conntype serial --connstring "dev=/dev/ttyUSB0,mtu=256" image upload -e blinky.img
Drelease-notes.md12 - Added support for using builtin keys for image validation
36 recovery and encryption whereby an encrypted image is loaded
38 - Zephyr: Add estimated image footer size to cache in sysbuild.
40 allows for a single application slot and firmware loader image in
41 the secondary slot which is used to update the primary image
78 - Fixed issue with serial recovery not showing image details for
81 iterating over 2 image slots.
91 - Serial recovery image state and image set state optional commands added
92 - imgtool: add 'dumpinfo' command for signed image parsing.
112 - Reworked image encryption support for Zephyr, static dummy key files
[all …]
Dreadme-mbed.md15 * `"mcuboot.slot-size"`: size of an image slot (only one image, two slots are currently supported)
39 … application needs to confirm the current image with `boot_set_confirmed()` after an update, or se…
41 …ot.header-size"`, and some space must be left for the image trailer too (see [this](design.md#imag…
Dreadme-zephyr.md26 Currently, the two image slots must be contiguous. If you are running
78 programming the bootloader image itself.
96 provides additional details regarding the changes it makes to the image
103 In order to upgrade to an image (or even boot it, if
126 the image to mark the primary slot as "image ok" before the next reboot,
185 label = "image-0";
189 label = "image-1";
202 times per image upgrade/revert). To configure MCUboot to work in
234 ### Direct image upload
237 To change it, invoke the `image upload` MCUmgr command with a selected image number, and make sure …
[all …]
/mcuboot-3.7.0/sim/mcuboot-sys/
DCargo.toml44 # Encrypt image in the secondary slot using RSA-OAEP-2048
47 # Encrypt image in the secondary slot using AES-256-CTR and RSA-OAEP-2048
50 # Encrypt image in the secondary slot using AES-KW-128
53 # Encrypt image in the secondary slot using AES-256-CTR and AES-KW-256
56 # Encrypt image in the secondary slot using ECIES-P256
59 # Encrypt image in the secondary slot using AES-256-CTR and ECIES-P256
62 # Encrypt image in the secondary slot using ECIES-P256 using Mbed TLS
65 # Encrypt image in the secondary slot using ECIES-X25519
68 # Encrypt image in the secondary slot using AES-256-CTR and ECIES-X25519
78 # image is copied to RAM before loading it.
[all …]
/mcuboot-3.7.0/scripts/imgtool/
Ddumpinfo.py27 from imgtool import image
31 TLV_TYPES = dict((value, key) for key, value in image.TLV_VALUES.items())
160 b[tlv_off:(tlv_off + image.TLV_INFO_SIZE)])
164 tlv_off += image.TLV_INFO_SIZE
170 b[tlv_off:(tlv_off + image.TLV_INFO_SIZE)])
171 tlv_off += image.TLV_INFO_SIZE
177 _tlv_head = struct.unpack('HH', b[tlv_off:(tlv_off + image.TLV_INFO_SIZE)])
182 tlv_off += image.TLV_INFO_SIZE
188 b[tlv_off:(tlv_off + image.TLV_INFO_SIZE)])
189 tlv_off += image.TLV_INFO_SIZE
[all …]
Dmain.py26 from imgtool import image, imgtool_version
217 ret, version, digest = image.Image.verify(imgfile, key)
218 if ret == image.VerifyResult.OK:
223 elif ret == image.VerifyResult.INVALID_MAGIC:
225 elif ret == image.VerifyResult.INVALID_TLV_INFO_MAGIC:
227 elif ret == image.VerifyResult.INVALID_HASH:
229 elif ret == image.VerifyResult.INVALID_SIGNATURE:
231 elif ret == image.VerifyResult.KEY_MISMATCH:
273 min_hdr_size = image.IMAGE_HEADER_SIZE
298 dependencies[image.DEP_IMAGES_KEY] = images
[all …]
/mcuboot-3.7.0/boot/zephyr/boards/
Dnrf52840dk_ram_multi.overlay18 label = "image-0";
22 label = "image-1";
26 label = "image-3";
55 label = "image-2";
Dnrf52840dk_qspi_nor_secondary.overlay18 label = "image-0";
31 label = "image-1";
Dnrf52840_big.overlay22 label = "image-0";
26 label = "image-1";
Dnrf52840dk_ram.overlay18 label = "image-0";
47 label = "image-1";
/mcuboot-3.7.0/ci/fih_test_docker/docker-build/
Dbuild.sh28 image=mcuboot/fih-test
29 docker build --pull --tag=$image .
/mcuboot-3.7.0/boot/cypress/BlinkyApp/
DReadme.md11 * Blinks RED led with 2 different rates, depending on type of image - BOOT or UPGRADE.
54 To build UPGRADE image use following command:
60 Example command-line for single-image:
66 `BlinkyApp` can be built to use in multi-image bootloader configuration.
68 To get appropriate artifacts to use with multi image MCUBootApp, makefile flag `HEADER_OFFSET=` can…
74 * first image BOOT (PRIMARY) slot start `0x10018000`
76 * second image BOOT (PRIMARY) slot start `0x10038000`
78 To get appropriate artifact for second image PRIMARY slot run this command:
84 **How to build upgrade image for external memory:**
88 For build BlinkyApp upgrade image for external memory use command:
[all …]
/mcuboot-3.7.0/boot/zephyr/sysbuild/
DCMakeLists.txt28 foreach(image ${IMAGES})
30 get_property(app_type TARGET ${image} PROPERTY APP_TYPE)
38 …set_property(TARGET ${image} APPEND_STRING PROPERTY CONFIG "CONFIG_ROM_END_OFFSET=${mcuboot_image_…
39 …set_property(TARGET ${image} APPEND_STRING PROPERTY CONFIG "CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE=${mc…
/mcuboot-3.7.0/sim/tests/
Dcore.rs44 let image = r.$maker($($margs),*); localVariable
45 dump_image(&image, stringify!($name));
46 assert!(!image.$test($($targs),*));
92 let image = r.clone().make_image(&dep, true); localVariable
93 dump_image(&image, "dependency_combos");
94 assert!(!image.run_check_deps(&dep));
190 fn dump_image(image: &Images, name: &str) { in dump_image()
198 image.debug_dump(&full_name); in dump_image()
/mcuboot-3.7.0/boot/zephyr/
DKconfig.serial_recovery51 bool "Allow to select image number for DFU"
55 respect the "image" field in mcumgr image update frame
57 The mapping of image number to partition is as follows:
59 1 -> image-0 (primary slot of the first image);
60 2 -> image-1 (secondary slot of the first image);
61 3 -> image-2;
62 4 -> image-3.
104 instead of erasing the whole image slot at once. This is necessary
194 If y, image list responses will include the image hash (adds ~100
202 If y, image states will be included with image lists and the set
[all …]
DKconfig66 Single image area is used for application which means that
171 bool "Use HW key for image verification"
174 Use HW key for image verification, otherwise the public key is embedded
175 in MCUBoot. If enabled the public key is appended to the signed image
180 bool "Validate image in the primary slot on every boot"
186 able to modify the flash image itself.
189 bool "Validate image in the primary slot just once after after upgrade"
224 bool "Overwrite image updates instead of swapping"
226 If y, overwrite the primary slot with the upgrade image instead
243 bool "Run the latest image directly from its slot"
[all …]
/mcuboot-3.7.0/boot/bootutil/include/bootutil/
Dbootutil_public.h133 #define BOOT_SET_SWAP_INFO(swap_info, image, type) { \ argument
134 assert((image) < 0xF); \
136 (swap_info) = (image) << 4 \
/mcuboot-3.7.0/boot/cypress/MCUBootApp/
DREADME.md17 Single-image mode.
29 MCUBootApp checks image integrity with SHA256, image authenticity with EC256 digital signature veri…
83 Multi-image operation considers upgrading and verification of more then one image on the device.
85 …enable multi-image operation define `MCUBOOT_IMAGE_NUMBER` in `MCUBootApp/config/mcuboot_config.h`…
87 Default value of `MCUBOOT_IMAGE_NUMBER` is 1, which corresponds to single image configuratios.
89 In multi-image operation (two images are considered for simplicity) MCUboot Bootloader application …
94 * Boots image from Primary_1 slot only;
115 …to place secondary (upgrade) slots in external memory module so resulting image size can be double…
144 * Build MCUBootApp in `Debug` for signle image use case.
148 * Build MCUBootApp in `Release` for multi image use case.
[all …]
DExternalMemory.md27 Single-image mode.
37 Multi(dual)-image mode.
59 After that MCUBootApp is ready to accept upgrade image from external memory module.
61 Once valid upgrade image was accepted the image in external memory will be erased.
72 **How to build upgrade image for external memory:**
76 `HEADER_OFFSET` defines the offset from original boot image address. This one in line above suggest…
97 2. Once DAP Link removable disk appeared drop (copy) the upgrade image HEX file to it.

12