How program serialnumber on nRF54L15 in factory setup

[Tommy F Kristensen]

Hi Nordic support

We have ealier used your legasy SDK16.0 on nRF52840 where we where programming our device serial number in the UIRC area. 

NRF_UICR->CUSTOMER[0-4] where NRF_UIRC is at adress    0x10001000UL

It was done by generating a small hex file that contains the UIRC data and then flashed with NRJPROG 

I can see that the new way on NRF Connect SDK 2.9.0 and nRF54L15 the UIRC register is not present and it is advised to use the  NVC 

Im expect I should use the zephyr settings API to get the production parameters like serialnumber manufactor model etc.

I have added below in my prj.conf, to support settings api

# Below is setup to let DIS information be read from settings

CONFIG_BT_SETTINGS=y

CONFIG_SETTINGS_RUNTIME=y

CONFIG_SETTINGS=y

CONFIG_SETTINGS_NONE=y

CONFIG_BT_DIS_SETTINGS=y

CONFIG_BT_DIS_STR_MAX=21

Is there a tool to set the serialnumber, hw_rev, model_number in flash, so it can be done in production ? 

Can i use nrfjprog with a specific address ?

Do you have an example on how this can be done ? 

Best Regards

Tommy F Kristensen

PS. I have hardcoded it in the prj.conf as below, to do testing, but need to be able to generate the serial dynamically

# Bluetooth Device Settings config

CONFIG_BT_DIS=y

CONFIG_BT_DIS_PNP=n

CONFIG_BT_DIS_MODEL="0007-00-000-001"

CONFIG_BT_DIS_MANUF="MyFirm"

CONFIG_BT_DIS_SERIAL_NUMBER=y

CONFIG_BT_DIS_FW_REV=y

CONFIG_BT_DIS_HW_REV=n

CONFIG_BT_DIS_SW_REV=y

CONFIG_BT_DIS_SERIAL_NUMBER_STR="65533-255-311540"

CONFIG_BT_DIS_FW_REV_STR="0.0.0"

#CONFIG_BT_DIS_HW_REV_STR="Zephyr Hardware"

CONFIG_BT_DIS_SW_REV_STR="0.0.0"

[Hung Bui]

Hi Tommy, 
Thanks for your patience, regarding the OTP reserved for customer use, there is now a PR: 
https://github.com/nrfconnect/sdk-nrf/pull/24686

You can find the draft documentation here: https://ncsdoc.z6.web.core.windows.net/PR-24686/nrf/app_dev/device_guides/nrf54l/otp_map_nrf54l.html

There are 32x4 bytes available at the bottom of the OTP area. 

[Emil Lenngren]

I have a request that you make it clear in the documentation that even though it's called OTP, it can actually be rewritten if you perform an erase all operation. The text "it is possible only once after an erase all operation" doesn't logically imply that an erase all would also reset OTP. Your AI bot believed that OTP actually was one-time-programmable and that erase all wouldn't reset it.

[Hung Bui]

Hi Emil, 
Thanks for your feedback. I agree that it is a bit confusing. But if you have a look at section 4.2.9 UICR you can find that it's mentioned that the OTP is an "emulated one-time programmable (OTP)". So it's not real OTP but emulated meaning it can be erased when doing an "erase all" operation.