How to seperate building/flashing of MCUBoot and the Application?

[Kuno.]

Hi,

Currently when building an application for mcuboot the bootloader will also be build and when flashing the application the bootloader will also be flashed using the merged image.

I would like to get more in control and be able to build and flash the bootloader separately and the same for the application. I have not been able to find any documentation regarding this.

Can anyone tell me how to archive this?

Br,

Kuno

[AHaug]

Hi,

Could you expand a bit on your motivation for why you want to build the bootloader and application separately? Is it because you want to save time, flash only either the bootloader or the application or other?

I would recommend that you keep building the bootloader and application simultaneously as that ensures that signing of the images to proceed properly.

Kind regards,
Andreas

[Kuno.]

Thank you for your reply, Andreas.

I would like to control the version of the image for both the bootloader and application. When a product goes to production it will be flashed with a version of the bootloader and a version of the application.
But when a product is shipped, only the application should be needed to be upgraded and still work with the old bootloader.

Br,

Kuno

[AHaug]

Hi Kuno,

 By following the suggestions in this case you should be able to separate the building and flashing of the bootloader and application How to use a prebuilt (MCUBOOT)HEX file of the child image and include it with the parent image?  

Let me know if the info in this case is enough to get you going, and if not I'll keep looking into it!

Kind regards,
Andreas