MCUBoot fails to load if using CMake Overlay Config

RE: MCUBoot fails to load if using CMake Overlay Config

Alexey Papkovskiy — Wed, 22 Mar 2023 09:06:57 GMT

So, I run into the same issue, the solution is pretty easy, you have to change how you set mcuboot_OVERLAY_CONFIG, it has to be CACHE variable

if(MYCONDITION_FOR_USING_OVERLAY)
set(mcuboot_OVERLAY_CONFIG ${CMAKE_CURRENT_LIST_DIR}/child_image/mcuboot_my_overlay.conf CACHE STRING "MCUBOOT configuration")

endif()

If it is not CACHE the build system doesn't add ${NRF_DIR}/subsys/partition_manager/partition_manager_enabled.conf to config overlays, and Partition Manager will be not enabled on MCUboot

RE: MCUBoot fails to load if using CMake Overlay Config

vcbz — Tue, 25 Oct 2022 13:59:12 GMT

yes thats one way, but I need the overlay as I only want to enable certain debug options on the bootloader when I build a debug release. I could also try the approach

<ACI_NAME>_<buildtype>.conf

specfied in the docs for child images and check if that helps

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrf/ug_multi_image.html

RE: MCUBoot fails to load if using CMake Overlay Config

Susheel Nuguru — Tue, 18 Oct 2022 07:36:02 GMT

From Multi-Image builds, Image Specific Variables:

The build system grabs the Kconfig fragment or configuration file
specified in a CMake argument relative to that image’s application
directory.
For example, the build system uses nrf/samples/bootloader/my-fragment.conf when building with the -Db0_OVERLAY_CONFIG=my-fragment.conf option, whereas -DOVERLAY_CONFIG=my-fragment.conf grabs the fragment from the main application’s directory, such as zephyr/samples/hello_world/my-fragment.conf.

So the fix would be to use mcuboot_CONF_FILE instead. Keep in mind that with mcuboot_CONF_FILE, you need to re-specify the whole config file and not just overlay, so the easier way is just to use child_image/mcuboot.conf

RE: MCUBoot fails to load if using CMake Overlay Config

Susheel Nuguru — Mon, 17 Oct 2022 17:51:44 GMT

I need to ask my colleague to help me with this. Please wait until I get some more insights from him.

RE: MCUBoot fails to load if using CMake Overlay Config

vcbz — Thu, 13 Oct 2022 18:15:56 GMT

Well escaping the characters did not help, Zephyr interpreted it as

file not found:
C:/ncs/v2.0.0/bootloader/mcuboot/boot/zephyr/"C:/MY_PROJECT_PATH/child_image/mcuboot_Debug.conf"

The variable is set correctly here is the outpt

message(SEND_ERROR "overlay config is ${mcuboot_OVERLAY_CONFIG}" )

overlay config is
C:/MY_PROJECT_PATH/child_image/mcuboot_Debug.conf

What I dont understand is why zephyr ignores my partition_static.yml when using the overlay config... The problem is not related to the MCuboot config not being passed or merged in the build process but rather that when using the mcuboot overlay as discussed above those two specifc defines for partition configuration are not set anymore. Note that these configurations are not set by me but I guess they are selected with the partition manager script.

I also checked the partition manager script output and seems correct

-- Found partition manager static configuration: C:/MY_PROJECT_PATH/pm_static.yml
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined.
Partition 'nvs_storage' is not included in the dynamic resolving since it is statically defined.

RE: MCUBoot fails to load if using CMake Overlay Config

vcbz — Thu, 13 Oct 2022 12:04:40 GMT

I will try to check by printing the mcuboot_OVERLAY_CONFIG variable in cmake after setting it. The way I know that specifcally the config CONFIG_PARTITION_MANAGER_ENABLED and CONFIG_FLASH_MAP_CUSTOM are different is because I compared the .config and autonf.h files of the childimage (mcuboot) with winmerge.

About escaping characters I will have a look about this, because I am also using a private key and know about this issue. Actually I had to escape characters three times when I was using a private key 😅, anyhow that is not my problem but will see if escaping characters as well for the MCUBoot overlay config solves this.

set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE \\\"${CMAKE_CURRENT_LIST_DIR}/keys/mcuboot_sign.pem\\\")

RE: MCUBoot fails to load if using CMake Overlay Config

Susheel Nuguru — Thu, 13 Oct 2022 10:51:43 GMT

Can you please verify that his configurations are actually set by checking the build/mcuboot/zephyr/include/generated/autoconf.h or by running "menuconfig" inside build/mcuboot.

My colleague says he had some issues with paths inside CMakeLists.txt. Can you do "message(mcuboot_OVERLAY_CONFIG)" after setting it, to double check inside CMakeList.txt also.

See this for how to escape the paths:

set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE \\"${CMAKE_CURRENT_SOURCE_DIR}/custom_key_dir/custom_priv.pem\\")