nRF54L15 with MCUBoot

[jeos]

Hi,

I've got an nRF54L15-DK, and I'm trying to get the sysbuild with mcuboot example working. https://docs.zephyrproject.org/latest/samples/sysbuild/with_mcuboot/README.html

I can successfully get my board to work if I set SB_CONFIG_BOOTLOADER_MCUBOOT=n, but if I set it to 'y', my board no longer works.

If I target 'nrf54l15dk/nrf54l15/cpuapp' my app works, but it doesn't work if I target 'nrf54l15dk/nrf54l15/cpuapp/ns'. However if I target 'cpuapp' only, VSCode has a warning of 'You are going to build without security by separation and Trusted Firmware-M (TF-M). Consider selecting the nrf54l15dk/nrf54l15/cpuapp/ns board target to better protect sensitive assets and code. In the /ns version of the board target, TF-M is automatically built as the secure firmware image.'

Is this the intended behaviour?

Using NCS 3.1.0. nRF54L15-DK 0.9.2 2024.49. 

[Hung Bui]

Hi James, 

Please give more info about the issue when you build for nrf54l15dk/nrf54l15/cpuapp/ns  

[jeos]

Hi Hung,

I get the following output when I build/run for nrf54l15dk/nrf54l15/cpuapp/ns:

*** Booting MCUboot v2.1.0-dev-2b69d93e75bc ***
*** Using nRF Connect SDK v3.1.0-6c6e5b32496e ***
*** Using Zephyr OS v4.1.99-1612683d4010 ***
E: Protect mcuboot flash failed, cancel startup.

[Hung Bui]

Hi James, 
That error comes from the issue that FPROTECT couldn't protect the MCUBoot partition for some reason. 
We are looking into this. 

For now you can test using the none ns board.

If you don't plan to use any TFM feature I don't see why you need to use the ns board. Note that ns stand for non secure. It's separated so that you can protect the secure part. 

[SimonV]

Has there been any update on this I am facing a similar issue?

[Hung Bui]

Hi Simon, 
These 2 PR are related: 
https://github.com/nrfconnect/sdk-nrf/pull/25655

https://github.com/nrfconnect/sdk-mcuboot/pull/576
They are under review.