Closed 0Grit closed 5 years ago
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1400
cc @evedon @alzix
@maclobdell
cc @SeppoTakalo
For added incentive, MCU boot supports SUIT manifest.
@maclobdell @SeppoTakalo
FYI @AGlass0fMilk has a POC working.
mcuboot Mbed port is working. It's not optimized for size at this point. I can write up a guide on how to use it if there's interest.
Mainly, the user just needs to provide a BlockDevice
pointer to the secondary mcuboot partition where the update candidates are stored.
Thanks for sharing the links. might come handy for someone.
cc @ARMmbed/mbed-os-storage
@AGlass0fMilk Yes, I'm definitely interested if you can write some kind of guide that describes how you did the integration.
In theory, it should be possible to convert our Pelion Update client to use MCUBOOT, but no study, or no proof of concept exist yet. But it is definitely something that we are interested to study further.
Purpose of Mbed bootloader is to be easiest to port to any platform that Mbed OS supports. It has never intended to be the most optimal for any specific platform.
For example Pelion Client porting guides don't directly name Mbed bootloader as the choice.
We are beginning to work on improving documentation, and perhaps publish the internal design documents so that it is evident what interactions is happening between update client and the bootloader. That would allow anyone to switch the bootloader, or write from scratch something that is most optimal for their target board.
We are beginning to work on improving documentation, and perhaps publish the internal design documents so that it is evident what interactions is happening between update client and the bootloader. That would allow anyone to switch the bootloader, or write from scratch something that is most optimal for their target board.
Please do!
We are willing to build upon anything that is well documented and logically designed.
I'm closing this ticket for backlog clean up purposes. This is more of a useful discussion than an issue.
Since it fit with discussions internally at ARM and is resulting in design docs being released, the issue has accomoplished its original intent.
Im fine with closing.
Description
mcuboot is quickly gaining traction. If I'm not mistaken even TFM uses it? The mbed bootloader from @ARMmbed/team-embeddedplanet's experience is not well documented, confusing and less featured.
Not a trivial task I know, since Pelion client needs to be considered as well but, Any plans to make the switch?
Issue request type