mcuboot can't find bootable image when multi-image configuration is used

RE: mcuboot can't find bootable image when multi-image configuration is used

dejans — Mon, 07 Nov 2022 18:47:47 GMT

Hi Jason,

Described way of having main and recovery images as well as update support for the application is not supported at the moment. However, you might still be able to achieve your goal. As this is design decision, you would need to be aware of its potential implications. You can find some suggestions on similar topic in this discussion.

Best regards,
Dejan

RE: mcuboot can't find bootable image when multi-image configuration is used

Jason Wright — Tue, 01 Nov 2022 23:36:14 GMT

Thank you Dejan, I'll wait for your update.

RE: mcuboot can't find bootable image when multi-image configuration is used

dejans — Tue, 01 Nov 2022 15:16:38 GMT

Hi,

It seems that your use case might be supported. However, additional discussion with developers would be needed to consider potential options and approaches. I'll get back to you when I get new information, hopefully till the end of this week.

Best regards,
Dejan

RE: mcuboot can't find bootable image when multi-image configuration is used

Jason Wright — Mon, 31 Oct 2022 14:48:35 GMT

Do you think Partition Manager is the issue here? I understand the downsides, but it would be worth it for our use case (bricked or non-upgradable device is unacceptable).

I would like to understand what's going wrong as this looks to be a supported use case of mcuboot, any suggestions for how to troubleshoot further?

RE: mcuboot can't find bootable image when multi-image configuration is used

dejans — Fri, 28 Oct 2022 09:32:42 GMT

Hi Jason,

I would suggest that you use regular MCUBoot functionality with SMP server as part of the application. In this case it would not be necessary to use pm_static.yml, as partition manager can do partitioning for you. The disadvantages of your idea would be the need for additional flash space and issues with static partitioning.

Best regards,
Dejan

RE: mcuboot can't find bootable image when multi-image configuration is used

Jason Wright — Tue, 25 Oct 2022 12:53:53 GMT

Hi Dejan,

For my use case, I want to support an updateable application with signing and BLE-only transport (SMP server). In the field, there is no possibility of hardware access to the device, so the concern is that having only a single image containing SMP server as part of the application could lead to a bricked device if the application fails to boot properly.

So the idea is to have a "recovery" image and a "main" image, where the recovery image is essentially just SMP sever, but will jump to the "main" image (mcuboot's image 1 slot 0 -- mcuboot_primary_1 partition) after a command is sent or timeout occurs. This way we do not depend on the application itself to provide the upgrade transport.

Let me know if that helps.

Jason

RE: mcuboot can't find bootable image when multi-image configuration is used

dejans — Tue, 25 Oct 2022 11:47:59 GMT

Hi Jason,

Could you provide more information about your use case?

Best regards,
Dejan