Production config in nRF Connect SDK

RE: Production config in nRF Connect SDK

Edvin — Tue, 27 Feb 2024 15:00:09 GMT

Hello,

I see. In that case, I think that the UICR would be an appropriate place. Please see the UICR documentation. As you can see, you have 32 register, each 4 bytes available.

The address of these registers on the nRF52840 is 0x10001080 + n*0x4, where n = 0 .. 31.

We don't have any Nordic tools to generate hex files for this, but you can either read on ARM's website what the format of these .hex files are (and then write some python scripts that generate these files), or you can program the data directly using nrfjprog:

nrfjprog --program 0x10001080 --val 0xCAFEFOOD

To fetch the values of the UICR in your application, you can use:

uint32_t uicr_cust_00 = NRF_UICR->CUSTOMER[0];

I am not aware of any, but I would assume that there exists some "intel hex file generator", either online or as python scripts if you look around. In case you manage to create .hex files with only the UICR->CUSTOMER[n] values that you want, you can use:

mergehex -m file1.hex file2.hex -o merged.hex

to combine file1.hex and file2.hex into merged.hex, as long as they are not overlapping. The mergehex tool is part of the nrfutil tool.

Best regards,

Edvin

RE: Production config in nRF Connect SDK

Alexey_B — Tue, 27 Feb 2024 14:03:03 GMT

Hello Edvin,

I'd like to store data like: channel mask, hardware version, serial number, modification number. This information can be fitted in install codes easily. Rougly I need about ~40 bytes.

Best regards.

RE: Production config in nRF Connect SDK

Edvin — Wed, 21 Feb 2024 12:44:38 GMT

Hello,

What sort of data do you want to store? Is it only a serial number, or is it more? And does this data ever change, or will it remain the same for the lifetime of the product?

And finally, how much data do you intend to store? (number of bytes)

Best regards,

Edvin