Re: MCUboot - Signing image for slot 1 #mcuboot
Adam Podogrocki
Hi Brenton, The only images you should flash are MCUboot and an image that goes to Slot#0. Any further operations should be conducted with the mcumgr tool. At least I used to do that. This tool gives you options to upload the new image (the first uploaded image should obviously be the one dedicated to slot#1), list already uploaded images, to check which slot is the current one, to boot from specified slot in test mode and finally to confirm, that the currently run image should become the active one. This tool performs swapping of images, so this is why you should also have a scratch_partition in your layout, e.g. partitions { boot_partition {}; slot0_partition {}; slot1_partition {}; scratch_partition {}; data_partition{}; // remaining space for application data purposes, optional }; When the image is confirmed, then swapping takes place and always the image from slot#0 is booted. At the time I used that tool UART and Bluetooth protocol were available. Cheers, Adam
On Thu, 28 Oct 2021 at 08:57, Brenton Chetty <brent7984@...> wrote:
|
|