TF-M and MCUBoot (on the nrf9160)

[jeremyherbert]

Hi,

I am using the nrf9160 and attempting to enable MCUBoot and secure boot. Is it correct that you still cannot use any form of TF-M with MCUBoot on the nrf53 or nrf91 (as of NCS v2.0.2) ? Is it  still supported to use the SPM + MCUBoot combo for secure boot on these Cortex M33 devices? Just trying to understand what the state of things is right at this moment.

I am coming across a lot of assertion errors (to do with the SPU) when I try to mix flash partitions/MCUBoot and TF-M.

Thanks,

Jeremy

[Menon]

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

[jeremyherbert]

Hi Abhijith,

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

[Håkon Alseth]

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