RE: MCUBoot build issue CMake Error "NOT" "EXISTS" when adding mcuboot.conf

Elfving — Mon, 23 May 2022 10:45:08 GMT

Hello Mark,

Sorry about the wait, though I guess you solved it on your own. Great!

Regards,

Elfving

RE: MCUBoot build issue CMake Error "NOT" "EXISTS" when adding mcuboot.conf

markuckermann — Fri, 20 May 2022 16:58:42 GMT

Ok, I've managed to do it using command line arguments, adding -Dmcuboot_CONF_FILE=<full_path_to>/mcuboot.conf

RE: MCUBoot build issue CMake Error "NOT" "EXISTS" when adding mcuboot.conf

markuckermann — Fri, 20 May 2022 11:17:48 GMT

Ok, I've gotten a bit further.

1. I think the flash overflow was due to the application image being too big, not the MCUboot bootloader. It would have been useful if the build logs told you that though! Reducing the things included in the application makes it work

2. mcuboot.conf would not be merged with the default config because of the parent build being proj_a.conf. So the file would have to be called mcuboot_a.conf.

However, I'd like to reduce the size of MCUboot now, to gain extra space for the application. If I just want a single .conf file for MCUboot to always replace the default .prj, how do I do that?

I've currently added a child_image/mcuboot/prj_a.conf with the contents of the default prj_minimal +

CONFIG_PM_PARTITION_SIZE_MCUBOOT=9000 but it's not being picked up.

Also, I don't want the same prj_a, prj_b, prj_c .conf files with the same content for multiple builds but I don't know how to avoid that!