TF-M and MCUBoot (on the nrf9160)

RE: TF-M and MCUBoot (on the nrf9160)

Håkon Alseth — Wed, 14 Sep 2022 11:45:29 GMT

Hi,

You can change the static partition layout handled by partition manager (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/scripts/partition_manager/partition_manager.html) to change the size of the mcuboot region by defining a my_project/pm_static.yml file (which can be derived from my_project/build/partitions.yml file).

An easier choice is to set the size of mcuboot in my_project/child_image/mcuboot.conf file:

CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

This will then be picked up by the build system (partition manager) and adjusted accordingly.

Kind regards,

Håkon

RE: TF-M and MCUBoot (on the nrf9160)

jeremyherbert — Wed, 14 Sep 2022 01:11:06 GMT

Hi Abhijith,

OK, but what do I do then if I need debug optimisations?

RE: TF-M and MCUBoot (on the nrf9160)

Menon — Tue, 30 Aug 2022 11:52:44 GMT

Hello,

Sorry for the long response time

Could you try removing the debug configuration and run the code again. I tried this and now it does not hang.

And I can see there is CONFIG_FPROTECT=n in thigy91_nrf9160 mcuboot overlay file which disables flash protection. This might be the reason for: hangs with a failed assertion in nrf_spu_flashregion_set.

Kind Regards,

Abhijith

RE: TF-M and MCUBoot (on the nrf9160)

jeremyherbert — Sat, 27 Aug 2022 01:56:12 GMT

Seems like the culprit here is the flash. If you create a copy of the hello_world project, add this to the prj.conf:

CONFIG_FLASH=y
CONFIG_FLASH_MAP=y
CONFIG_FLASH_PAGE_LAYOUT=y

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_DEBUG=y

Then build and flash to the nrf9160dk_nrf9160_ns, it hangs with a failed assertion in nrf_spu_flashregion_set.

I can also reproduce a very similar problem without MCUBoot and just enabling littlefs:

CONFIG_FLASH=y
CONFIG_FLASH_MAP=y
CONFIG_FLASH_PAGE_LAYOUT=y

CONFIG_FILE_SYSTEM=y
CONFIG_FILE_SYSTEM_LITTLEFS=y

CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_DEBUG=y

If I then append the following to either of these:

CONFIG_BUILD_WITH_TFM=n
CONFIG_SPM=y

They build and run fine. So it indeed seems that TF-M and MCUBoot are currently mutually exclusive.