nRF54L15 - unable to provision key

[Igor]

I get error provisioning key on nRF54L15 and NCS 3.0.1. I tried using "Erase all" in nRF connect SDK Programmer, but it doesn't help. Please check also the attached log.
nrf54l15dk/nrf54l15/cpuapp/ns is used.

PS H:\cup> python H:/ncs/v3.0.1/bootloader/mcuboot/scripts/imgtool.py keygen -t ed25519 -k private_key.pem
PS H:\cup> west ncs-provision upload -s nrf54l15 -k private_key.pem                                                                                                                    
nrfutil device x-provision-keys --key-file C:\Users\IgorGorjanc\AppData\Local\Temp\nrfutil_j8mc7y15\keyfile.json --traits jlink
Error: One or more key provisioning tasks failed:
 * 1057746146: [Probe] Device error: Tried to provision 1 keys, 1 keyslot(s) failed to be provisioned (Generic)


Uploading failed!
PS H:\cup> nrfutil device x-provision-keys --key-file C:\Users\IgorGorjanc\AppData\Local\Temp\nrfutil_j8mc7y15\keyfile.json --traits jlink --log-level trace --log-output stdout --json > log.txt                              
Error: One or more key provisioning tasks failed:
 * 1057746146: [Probe] Device error: Tried to provision 1 keys, 1 keyslot(s) failed to be provisioned (Generic)

sysbuild.conf:

SB_CONFIG_BOOTLOADER_MCUBOOT=y
SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="\${APP_DIR}/private_key.pem"
SB_CONFIG_MCUBOOT_SIGNATURE_USING_KMU=y
SB_CONFIG_BOOT_SIGNATURE_TYPE_ED25519=y

prj.conf:

CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="nRF54L15-PDK"

# Enable the LBS service
CONFIG_BT_LBS=y
CONFIG_BT_LBS_POLL_BUTTON=y
CONFIG_DK_LIBRARY=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# Enable FOTA over Bluetooth LE
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

Output on a virtual COM port:

*** Booting MCUboot v2.1.0-dev-ae1ee57f3906 ***
*** Using nRF Connect SDK v3.0.1-9eb5615da66b ***
*** Using Zephyr OS v4.0.99-77f865b8f8d0 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
E: ED25519 signature verification failed -136
E: Image in the primary slot is not valid!
E: Unable to find bootable image

4628.log.txt

[AHaug]

Hello,

Looks like you're missing a command in https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf54l/kmu_provision.html, i.e the erase command in between generating the key and uploading the key

Let me know if this changes anything.

Kind regards,
Andreas

[Igor]

Erase does not help.

PS H:\cup> python H:\ncs\v3.0.1\bootloader/mcuboot/scripts/imgtool.py keygen -t ed25519 -k private_key.pem
PS H:\cup> nrfutil device erase --all
v Erased 1057746146
PS H:\cup> west ncs-provision upload -s nrf54l15 -k private_key.pem
nrfutil device x-provision-keys --key-file C:\Users\IgorGorjanc\AppData\Local\Temp\nrfutil_2twnst4d\keyfile.json --traits jlink
Error: One or more key provisioning tasks failed:
 * 1057746146: [Probe] Device error: Tried to provision 1 keys, 1 keyslot(s) failed to be provisioned (Generic)


Uploading failed!

[sbarnowski]

I am having the same issue. Could it be related to silicon version?

[AHaug]

Hi,

That's a good suggestion. Could both you and Igor verify if the SoC you're using matches the support matrices for NCS v3.0.1? 

https://docs.nordicsemi.com/bundle/comp_matrix_nrf54l15/page/COMP/nrf54l15/nrf54l15_ic_revision_overview.html for SoC revisions and variants and https://docs.nordicsemi.com/bundle/comp_matrix_nrf54l15/page/COMP/nrf54l15/nrf54l15_nrf_connect_sdk.html for which version of the SDK that requires what version of the SoC

Kind regards,
Andreas

[Igor]

I downgraded to NCS 2.9.1 and it works. So it seems to be something related to NCS 3.0
SoC is N54L15 QFAABB 2433AA. According to your link, this seems to be Engineering B and NOT supported in NCS 3.
This SoC is part of PCA10156 0.8.1 2024.41. I would like to point out that some other person from Nordic assured me it is compatible, but obviously isn't....

[sbarnowski]

I am also on ENGB silicon. Trying to do this on NCS v3.0.2.

[AHaug]

Hi,

Igor said:

According to your link, this seems to be Engineering B and NOT supported in NCS 3.

This is correct, Engineering B is not supported. Apologies for not suggesting this before and simply assuming you were using Rev 1... Again thank you Sebastian for bringing this up.

Igor said:

This SoC is part of PCA10156 0.8.1 2024.41. I would like to point out that some other person from Nordic assured me it is compatible, but obviously isn't....

Ah, I see where the fault has happened. There's a mismatch in https://docs.nordicsemi.com/bundle/ncs-3.0.0/page/nrf/app_dev/device_guides/nrf54l/index.html w.r.t the supported device.

1. This link comp matrix for DK and SDK states that 0.8.1 DK/PDK uses engineering B, i.e it's a PDK
2. This link Comp matrix for SoC version and SDK says that 0.8.1 is not usable after NCS v2.8.0
3. The documentation/guide for getting started with 54L15, i.e https://docs.nordicsemi.com/bundle/ncs-3.0.0/page/nrf/app_dev/device_guides/nrf54l/index.html states that you can use nRF54L15 PDK, which is a fault in the documentation. I believe you (as well as potentially other including myself) have been mislead by this..

Igor said:

I downgraded to NCS 2.9.1 and it works. So it seems to be something related to NCS 3.0
SoC is N54L15 QFAABB 2433AA.

The fact that it works for NCS v2.9.1 is interesting though... My best hypothesis is that rev 0.8.1 was not tested/tagged to be supported in NCS v2.9.1 (hence the lack of mentioning this device in the support matrix), but that the silicon on 0.8.1 and 0.9.1 are similar enough that it's still compatible (for atleast some things) in NSC v2.9.1

I will create a Tech doc ticket to review and update this immediately and verify if my reasoning based on the Datasheet docs (1. and 2.) overrules the development guide doc (3.)

Kind regards,
Andreas

[Igor]

According to Developing with nRF54L Series there is also a nRF54L15 DK v0.9.3 but it is not even mentioned in compatibility matrix. Please fix also that.

[AHaug]

I've added that to the tech doc ticket now,

Kind regards,
andreas