commit | 48deccaaee6f66316077cf082c0cf39767ff711c | [log] [tgz] |
---|---|---|
author | Dominik Ermel <dominik.ermel@nordicsemi.no> | Fri Jul 09 10:23:58 2021 +0000 |
committer | David Brown <davidb@davidb.org> | Fri Jul 16 13:24:26 2021 -0600 |
tree | d5a7c6c13baea3166c2e5383105cd7b548f1ccda | |
parent | 8c5ec5a6cfa9596e88b884a3a63b3f0bca299841 [diff] |
boot_serial: Allow direct image upload The commit provides support for "image" parameter in mcumgr image update frame, that is used to select image number to be updated; for the purpose, the option MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD that enables the feature. Platform that enables the feature needs, to provide an implementation of the flash_area_id_from_direct_image function that will match the image number to flash area to upload to. Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
This is mcuboot version 1.8.0-dev
MCUboot is a secure bootloader for 32-bit MCUs. The goal of MCUboot is to define a common infrastructure for the bootloader, system flash layout on microcontroller systems, and to provide a secure bootloader that enables simple software upgrades.
MCUboot is operating system and hardware independent and relies on hardware porting layers from the operating. Currently, mcuboot works with both the Apache Mynewt and Zephyr operating systems, but more ports are planned in the future. RIOT is currently supported as a boot target with a complete port planned.
Instructions for different operating systems can be found here:
The issues being planned and worked on are tracked using GitHub issues. To participate please visit:
Issues were previously tracked on MCUboot JIRA , but it is now deprecated.
Information and documentation on the bootloader are stored within the source.
It was previously also documented on confluence: MCUBoot Confluence however, it is now deprecated and not currently maintained
For more information in the source, here are some pointers:
Developers welcome!