Using a configuration file with mcuboot

RE: Using a configuration file with mcuboot

dwalton65 — Tue, 18 Jan 2022 01:29:57 GMT

Thanks Hung Bui

"peripheral_hr_SMP.zip" builds ok for me.

I went back to see what the difference between your example and mine was. Previously when "mcuboot.conf" was in the folder "child_image", I had to add the contents of "\ncs\v1.8.0\bootloader\mcuboot\boot\zephyr\prj.conf" into the start of "mcuboot.conf" to get it to build. Now for some reason I don't have to. Simply moving "mcuboot.conf" into the folder "child_image" is now working. I have no idea what has changed apart from my computer being restarted.

I have attached the updated version of hello-world

devzone.nordicsemi.com/.../hello_2D00_world2.zip

RE: Using a configuration file with mcuboot

Hung Bui — Mon, 17 Jan 2022 11:53:10 GMT

Hi David,
Could you tried again with my example here.
Please edit mcuboot.conf to point to the absolute folder you copied the project to.

I tested with nrf52dk_nrf52832 board and it worked both in VS Code and when compile from command line.

devzone.nordicsemi.com/.../peripheral_5F00_hr_5F00_SMP.zip

RE: Using a configuration file with mcuboot

dwalton65 — Sun, 16 Jan 2022 22:05:29 GMT

[quote userid="2121" url="~/f/nordic-q-a/83657/using-a-configuration-file-with-mcuboot/347770#347770"]Hi David,
I found what worked for me the smoothest is putting a mcu_boot.conf into the child_image folder in the project root folder to have an overlay over the original proj.conf
Doing that I don't need to define the path to the file. [/quote]

I removed the code set(mcuboot_CONF_FILE ... from "CMakeLists.txt"

Created the folder "child_image" and moved "mcuboot.conf" into it.

The project now does not build. It appears that "mcuboot.conf" in the folder "child_image" has replaced "\ncs\v1.8.0\bootloader\mcuboot\boot\zephyr\prj.conf" instead of adding to it.

For a test, I added the contents of "\ncs\v1.8.0\bootloader\mcuboot\boot\zephyr\prj.conf" into the start of "mcuboot.conf". The problem now is that it is trying to find "test-key.pem" at 'C:/ncs/v1.8.0/bootloader/mcuboot/test-key.pem' instead of in the project directory. Changing CONFIG_BOOT_SIGNATURE_KEY_FILE in "mcuboot.conf" to an absolute path fixed that CONFIG_BOOT_SIGNATURE_KEY_FILE="/ncs/myapps/bootloader/key/test-key.pem". The project now builds.

Is there a way using this method for "mcuboot.conf" in the folder "child_image" to be in addition to "\ncs\v1.8.0\bootloader\mcuboot\boot\zephyr\prj.conf" instead of replacing it?

RE: Using a configuration file with mcuboot

Hung Bui — Fri, 14 Jan 2022 13:11:16 GMT

Hi David,
I found what worked for me the smoothest is putting a mcu_boot.conf into the child_image folder in the project root folder to have an overlay over the original proj.conf
Doing that I don't need to define the path to the file.