| /mcuboot-3.7.0/sim/src/ |
| D | lib.rs | 205 let images = run.clone().make_no_upgrade_image(&NO_DEPS, ImageManipulation::None); in run_single() localVariable
206 failed |= images.run_norevert_newimage(); in run_single()
208 let images = run.make_image(&NO_DEPS, true); in run_single() localVariable
210 failed |= images.run_basic_revert(); in run_single()
211 failed |= images.run_revert_with_fails(); in run_single()
212 failed |= images.run_perm_with_fails(); in run_single()
213 failed |= images.run_perm_with_random_fails(5); in run_single()
214 failed |= images.run_norevert(); in run_single()
216 failed |= images.run_with_status_fails_complete(); in run_single()
217 failed |= images.run_with_status_fails_with_reset(); in run_single()
|
| D | image.rs | 78 images: Vec<OneImage>, field
228 let images = self.slots.into_iter().enumerate().map(|(image_num, slots)| { in make_no_upgrade_image() localVariable
264 images, in make_no_upgrade_image()
271 let mut images = self.make_no_upgrade_image(deps, ImageManipulation::None); in make_image() localVariable
272 for image in &images.images { in make_image()
273 mark_upgrade(&mut images.flash, &image.slots[1]); in make_image()
278 return images; in make_image()
282 let total_count = match images.run_basic_upgrade(permanent) { in make_image()
292 images.total_count = Some(total_count); in make_image()
293 images in make_image()
[all …]
|
| /mcuboot-3.7.0/samples/zephyr/ |
| D | .gitignore | 2 test-images.zip
|
| /mcuboot-3.7.0/docs/ |
| D | readme-mynewt.md | 5 which at the same time requires to use `newtmgr` to manage images, MCUboot
35 different TLV structure, so images created by `newt` have to be generated
43 like listing images and uploading a new image to `slot0`. The serial bootloader
|
| D | ecdsa.md | 25 because images generated with newer tools will not
34 Without this argument, the images are padded with the
46 images. Without the argument, 3 out of 4 images generated will have
|
| D | readme-zephyr.md | 28 so your SoC runs it out of reset. If there are multiple updateable images
30 the rest of the images too (for example, `slot2_partition` and
104 `MCUBOOT_VALIDATE_PRIMARY_SLOT` is enabled), the images must be signed.
119 is usually not relevant for flash tools that use Intel Hex images (.hex) instead
120 of raw binary images (.bin) since the former include destination address
124 These images can also be marked for upgrade, and loaded into the secondary slot,
163 example) can be used to sign images.
208 and marked it as test/confirmed but MCUboot will not swap the images and
252 …ows fetching version and installation status (custom properties) for all images (enable with ``CON…
|
| D | index.md | 38 - [Encrypted images](encrypted_images.md)
59 The documentation page about [signed images](signed_images.md) is currently
80 …mcuboot/tree/main/scripts/imgtool.py) - A tool to securely sign firmware images for booting by MCU…
|
| D | imgtool.md | 4 operations that are necessary to manage keys and sign images. Using
23 This key file is what is used to sign images, this file should be
49 ## [Signing images](#signing-images)
|
| D | release-notes.md | 79 decrypted images.
173 - Increase coverage of large images in the simulator
269 X25519 encrypted images, rollback protection, hardware keys, and a
280 - Add support for X25519 encrypted images.
306 The 1.5.0 release of MCUboot adds support for encrypted images using
337 booting. With this release, MCUboot can manage two images that can be
342 of the images: specifically adding support for protected TLV entries.
343 If multiple images and dependencies are not used, the images will be
378 multi-images, and a new name for slot0/slot1 which are now called
387 In addition, support has been added for encrypted images. See [the
[all …]
|
| D | testplan-mynewt.md | 8 with wrong key images are not swapped to, and image signed with correct key
143 Confirm that both images are installed, request a permanent request to the
|
| D | readme-riot.md | 16 which should be able to boot any of the supported OS images.
|
| D | PORTING.md | 73 for MCUboot and images of applications are stored, in system-agnostic way.
126 /* Flash area IDs of the first image in case of multiple images */
131 /* Flash area IDs of the second image in case of multiple images */
|
| D | readme-espressif.md | 176 For Zephyr images, `--pad-header` is not needed as it already has the padding for MCUboot
197 Downgrade prevention (avoid updating of images to an older version) can be enabled using the
226 [MCUboot encrypted images](encrypted_images.md) do not provide full code confidentiality when only
360 be able to flash other images through UART.__*
417 3. Bootloader validates the application images and prepare the booting process (MCUboot phase).
508 be able to flash other images through UART.__*
660 The multi image feature (currently limited to 2 images) allows the images to be updated separately
695 In the multi boot approach the bootloader is responsible for booting two different images in two
697 CPU (current CPU), it is also responsible for update both images as well. Thus multi boot will be
736 MCUboot allows version dependency check between the images when updating them. As `imgtool.py`
|
| D | readme-nuttx.md | 23 ## Creating MCUboot-compatible application firmware images
|
| /mcuboot-3.7.0/samples/zephyr/bad-keys/ |
| D | README.md | 4 testing. Signing the images with either of these keys, but leaving
|
| /mcuboot-3.7.0/sim/mcuboot-sys/ |
| D | Cargo.toml | 74 # Support multiple images (currently 2 instead of 1).
89 # Support images with 32-byte maximum write alignment value.
|
| /mcuboot-3.7.0/boot/cypress/MCUBootApp/ |
| D | README.md | 89 In multi-image operation (two images are considered for simplicity) MCUboot Bootloader application …
91 * Verifies Primary_1 and Primary_2 images;
92 * Verifies Secondary_1 and Secondary_2 images;
93 * Upgrades Secondary to Primary if valid images found;
97 This ensures two dependent applications can be accepted by device only in case both images are vali…
164 After MCUBootApp is built with these settings unencrypted and encrypted images will be accepted in …
|
| /mcuboot-3.7.0/scripts/imgtool/ |
| D | main.py | 283 images = re.findall(r"\((\d+)", value)
284 if len(images) == 0:
288 if len(images) != len(raw_versions):
298 dependencies[image.DEP_IMAGES_KEY] = images
|
| /mcuboot-3.7.0/boot/zephyr/ |
| D | Kconfig | 248 images must be linked to be executed from the given image slot. Using this
296 attempt to boot the previous image. The images can also be made permanent
336 If y, images in the secondary slot can be encrypted and are decrypted
348 loading encrypted images via serial recovery which are then
389 memory usage; larger values allow it to support larger images.
611 int "Number of updateable images"
|
| D | Kconfig.serial_recovery | 19 MCUboot itself to load update images into flash over a UART.
|
| /mcuboot-3.7.0/ |
| D | README.md | 74 …mcuboot/tree/main/scripts/imgtool.py) - A tool to securely sign firmware images for booting by MCU…
|
| /mcuboot-3.7.0/boot/cypress/BlinkyApp/ |
| D | Readme.md | 82 *Note:* only 2 images are supported at the moment.
|
