NRF 52832 Chip ID or unique serial number?

[TimW]

Hello,

I need to read the unique serial number from a nordic NRF 52832 device. This number is necessary for our production testing.

I have the latest SDK.

Thanks!

[wpaul]

Someone asked a related question which I answered previously:

https://devzone.nordicsemi.com/f/nordic-q-a/42671/how-to-find-out-nrf52-chip-revision

The FICR register region also contains DEVICEID and DEVICEADDR registers. These indicate the unique per-chip device identification (which I think is as close to a serial number as you can get) and the per-chip BLE station address. You can also determine the part (52832 vs 52840), variant, package code, and the amount of RAM and flash present. Refer to the FICR section in the nRF52832 reference manual (product specification). As my example shows, you should be able to write some simple code to read the values of these registers.

-Bill

[awneil]

Note that the DeviceID is guaranteed unique, but the DEVICEADDR is "random" - so may not be unique.

CORRECTION: Despite what the documentation says, The DeviceID is not guaranteed unique - it is also random!

See: https://devzone.nordicsemi.com/f/nordic-q-a/49664/title-corrected-deviceid-is-not-unique---it-is-random/198038#198038

See: https://devzone.nordicsemi.com/f/nordic-q-a/22089/specific-unique-id-for-device-detection/86800#86800

Which leads to: https://devzone.nordicsemi.com/f/nordic-q-a/2112/how-to-get-6-byte-mac-address-at-nrf51822/9000#9000

"The BLE address we provide is a random static address, which means that it is random generated .... The high order of randomness (46 bits are random) in this type of address does not provide 100 % security wrt. two devices having the same address, but the probability is quite low."

(my emphasis)

[awneil]

wpaul said:

you should be able to write some simple code to read the values of these registers

Indeed; eg,

    NRF_LOG_INFO("SAADC Low Power Example; built on " __DATE__ " at " __TIME__ " for " BOARD_STR );	
    NRF_LOG_INFO("DevAddr %08X %08X", NRF_FICR->DEVICEADDR[1], NRF_FICR->DEVICEADDR[0] );	

I always do that in development so that, when looking back through old recorded logs, I can tell what software was used, and what it was running on.

[TimW]

Thank you for this information. That is what I needed!

[toni95]

Is there way to do similar approach in nrf Connect SDK 2.8.0?