nrf54l15-dk + NSIB

RE: nrf54l15-dk + NSIB

Hung Bui — Fri, 19 Sep 2025 10:33:09 GMT

Hi Dede,

I would suggest to have MCUBoot in addition to NSIB. NSIB can only do image verification and jump between two image. It doesn't do any image swapping.

Regarding the issue you have, please make sure you updated to latest toolchain.
I would suggest to open the toolchain here:

First you need to recover the chip. After that call this:

After that you click flash (not erase and flash) then Hello World should work.

RE: nrf54l15-dk + NSIB

dede — Fri, 19 Sep 2025 03:44:32 GMT

Hi,

Actually, my real intention is:
The device communicates with a hub via BLE-Pawr mode. Before updating the firmware, the hub and the device establish a BLE connection first. Then, using a custom app, the firmware is sent to the hub, and the hub then sends the firmware to the device. The device has two areas to store the firmware. The device writes the firmware to area 2 by itself, and then proceeds to boot to verify and update it to area 1. Here is my question: Can either b0 or mcuboot achieve the step of boot verification and firmware update?

Thanks.

RE: nrf54l15-dk + NSIB

dede — Fri, 19 Sep 2025 03:12:38 GMT

Hi,

I tried the command you mentioned, but it gave an error.

The path for configuring the key in sysbuild.conf - isn't this supposed to pre-set the key? I was following the instructions for setting up the link: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-2-dfu-over-usb-adding-external-flash/

The prj.conf is configured as follows:

CONFIG_IS_SECURE_BOOTLOADER=y
CONFIG_FPROTECT=y
CONFIG_FW_INFO=y
CONFIG_SECURE_BOOT_CRYPTO=y
CONFIG_SECURE_BOOT_STORAGE=y
CONFIG_SECURE_BOOT_VALIDATION=y
CONFIG_FLASH=y
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

After I compiled, VSCode reported an error:

Can you check if there are any problems with the project I uploaded?

devzone.nordicsemi.com/.../0284.hello_5F00_world.rar

Thanks.

RE: nrf54l15-dk + NSIB

Hung Bui — Thu, 18 Sep 2025 12:30:49 GMT

Hi Dede,

Since the nRF54L has a KMU unit to store the key. The private key for the B0 need to be stored (provisioned) in the KMU for security reason. (CPU can only request KMU to use the key to sign or validate firmware for example, but CPU can't read the key).
So you need to provision the key. You can take a look here:
https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf54l/dfu_config.html

This is needed:

Please try doing this before you flash the application. I did a quick test here and it seems to work for me.