Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

pcspets — Wed, 04 Dec 2024 12:01:18 GMT

I see that that dependency to 'slot0_partition' and 'slot1_partition' comes from this MCUBoot change. CMake fails if they are not defined. Seems like they are used only for build time flash size check. Not absolutely sure though.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

pcspets — Wed, 04 Dec 2024 09:25:33 GMT

Do these Devicetree definitins have to match exactly the ones in Partition Manager or are they ignored and needed only to compile successfully?

For example, if slot1 is actually on the external flash?

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Fri, 26 Jul 2024 12:28:48 GMT

You probably need to add this just for the compilation to pass.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

PuffinEgg — Thu, 25 Jul 2024 19:43:07 GMT

Thanks for the heads up! Yes, I have fixed partitions in the custom board dts. However, I don't have the slot0_partition and slot1_partition labels (only boot_partition). I am guessing these are probably needed in this case then since the definition you give me uses it?

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Thu, 25 Jul 2024 18:10:55 GMT

Hi,

The team said the Audio Application hasn't been ported to sysbuild yet. Sorry for the mislead.

Since you are mentioning a custom board, I guess you forgot to add fixed-partitions to your custom boards:

Ref: https://github.com/nrfconnect/sdk-nrf/blob/63b0986ccbfd6d3c44b48b2c6139764cb384d1c7/boards/nordic/nrf52kbd/nrf52kbd_nrf52832.dts#L65 we do have these for all the boards in Zephyr.

-Amanda H.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

PuffinEgg — Wed, 24 Jul 2024 23:01:47 GMT

No worries! I am currently trying to build the Audio Application that you mentioned. However, I can't seem to get it build with mcuboot when I build using the NRF Connect extension using prj_fota.conf and with sysbuild enabled. Is there a guide perhaps to build the audio application with mcuboot? Thanks!

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Wed, 24 Jul 2024 19:02:41 GMT

We are currently understaffed due to the summer vacation period, so delayed replies must be expected. I am sorry about any inconvenience this might cause.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

PuffinEgg — Fri, 19 Jul 2024 23:24:04 GMT

Hi, unfortunately this is a custom board so I can't really build it using the nRF52DK board file.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Fri, 19 Jul 2024 21:08:25 GMT

Do you build for nRF52DK board or custom board? Is it possible to reproduce with the nRF52DK board file? If so, please share the project to help reproduce the issue. Thanks.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

PuffinEgg — Fri, 19 Jul 2024 19:17:00 GMT

I understand and MCUBoot is enabled, but I don't know why the partition manager is not enabled for MCUBoot. Here is the building output for my main application showing that it is building with partition manager AFTER adding the partition dummy label to the dts file

slot0_partition: partition@8000 {

label = "image-0";

reg = <0x00008000 0x1>;

};

slot1_partition: partition@8001 {

label = "image-1";

reg = <0x00008001 0x1>;

};

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/....../build/....
-- Found partition manager static configuration : /Users/......./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 'settings_storage' is not included in the dynamic resolving since it is statically defined.
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/......./build
-- west build: building application

The issue I am facing right now is this step happens AFTER the mcuboot CMake, so mcuboot is only reading the dts file. If I remove the dummy label, I get the following error when rebuilding.

-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/f8037e9b83/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Using ccache: /opt/nordic/ncs/toolchains/f8037e9b83/bin/ccache
MCUBoot bootloader key file: /Users/......./bootloader/mcuboot/root-rsa-2048.pem
ERRORUnable to get parent of node: 
ERRORUnable to get parent of node: 
ERRORUnable to get parent of node: 
ERRORUnable to get parent of node: 
CMake Error at /Users/......./zephyr/cmake/modules/extensions.cmake:3805 (message):
  dt_prop(erase_size ...) missing required argument: PATH

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Fri, 19 Jul 2024 19:04:50 GMT

You can enable mcuboot by SB_CONFIG_BOOTLOADER_MCUBOOT=y for sysbuild. See Adding MCUboot as an immutable bootloader

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

PuffinEgg — Fri, 19 Jul 2024 15:44:00 GMT

Hi, changing the content of the pm_static.yml does not impact the build error message and I still get the same complain of missing dts label. I know partition manager is enabled for child image, but how can I tell it is enabled for mcuboot using sysbuild?

Update: when building the audio application, it seems that sysbuild actually builds the main application first before mcuboot, whereas in my case mcuboot is always builded first. Does that mean the partition manager needs to be activated first in building the main application to generate the necessary dts file that mcuboot can utilize? If so, how can i make sure that my main app will always get build before mcuboot.

RE: Unable to compile MCUBoot without specifying flash slot0_partition and slot1_partition using sysbuild

Amanda Hsieh — Fri, 19 Jul 2024 13:07:53 GMT

Hi,

Could you share your pm_static.yml?

The usage of pm_static.yml is the same. The sysbuild will source pm_static.yml to build. The Audio application also uses pm_static.yml to build.

Regards,
Amanda H.