RE: Some Questions regarding the usage of MCUboot as bootloader

Torsten Robitzki — Thu, 28 Mar 2024 14:13:18 GMT

Hi Amanda Hsieh ,

that answers my questions already.

Have nice Easter holidays!

Torsten

RE: Some Questions regarding the usage of MCUboot as bootloader

Amanda Hsieh — Thu, 28 Mar 2024 14:10:29 GMT

Hi,

Due to the Easter holidays in Norway, we are less staffed than usual. You can expect a delayed answer.

You could enable the mcoboot by adding "CONFIG_BOOTLOADER_MCUBOOT=y" in the prj.conf, CONFIG_SECURE_BOOT is for nRF Secure Immutable Bootloader as an immutable bootloader. See Secure bootloader chain and Adding a bootloader chain for more information.

[quote user=""]what are the exact names of the partitions that I have to define, to have a partition for MCUboot, the application and a firmware update?[/quote]

It's unnecessary to define those partitions manually. The partition manager would generate partitions.yml automatically without pm_static.yml. You could duplicate the partitions.yml under the build folder, rename it to pm_static.yml, and put it under the app for the next build.

[quote user=""]There are some options to configure MCUBoot itself. For example `MCUBOOT_VALIDATE_PRIMARY_SLOT`, which is also mentioned in the Nordic-Zephry documentation. Where does this configurations have to be applied? Are they CMake cache variables or are they KKonfig options?[/quote]

You could create child_image/mcuboot.conf to set the mcuboot configs.

Regards,
Amanda