<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46428/nrf-52832-chip-id-or-unique-serial-number</link><description>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!</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 Nov 2024 12:41:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46428/nrf-52832-chip-id-or-unique-serial-number" /><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/512747?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2024 12:41:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00c8cbab-cee7-4820-a9d8-dbc2e67863a0</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;The name of the registers, which comes from the MDK, is equal in the nRF5 SDK and in NCS. So apart from that you can&amp;#39;t use &amp;quot;NRF_LOG_INFO()&amp;quot;, the approach is the same.&lt;/p&gt;
&lt;p&gt;Try something like:&lt;/p&gt;
&lt;p&gt;LOG_INF(&amp;quot;DevAddr %08x %08x&amp;quot;, NRF_FICR-&amp;gt;DEVICEADDR[1], NRF_FICR-&amp;gt;DEVICEADDR[0]);&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;printk(&lt;span&gt;&amp;quot;DevAddr %08x %08x\r\n&amp;quot;, NRF_FICR-&amp;gt;DEVICEADDR[1], NRF_FICR-&amp;gt;DEVICEADDR[0]);&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Edvin&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/512702?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2024 09:47:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88a936e8-be4e-4287-aef2-3e054111cc44</guid><dc:creator>toni95</dc:creator><description>&lt;p&gt;Is there way to do similar approach in nrf Connect SDK 2.8.0?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/183099?ContentTypeID=1</link><pubDate>Tue, 23 Apr 2019 11:47:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e13f1ae9-0647-4b5f-b121-4df333111c56</guid><dc:creator>TimW</dc:creator><description>&lt;p&gt;Thank you for this information. That is what I needed!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/182852?ContentTypeID=1</link><pubDate>Sat, 20 Apr 2019 08:33:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3fa708dd-d145-4cb2-89e7-f53af5ce6025</guid><dc:creator>awneil</dc:creator><description>[quote userid="75667" url="~/f/nordic-q-a/46428/nrf-52832-chip-id-or-unique-serial-number/182840"]you should be able to write some simple code to read the values of these registers[/quote]
&lt;p&gt;Indeed; eg,&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    NRF_LOG_INFO(&amp;quot;SAADC Low Power Example; built on &amp;quot; __DATE__ &amp;quot; at &amp;quot; __TIME__ &amp;quot; for &amp;quot; BOARD_STR );	
    NRF_LOG_INFO(&amp;quot;DevAddr %08X %08X&amp;quot;, NRF_FICR-&amp;gt;DEVICEADDR[1], NRF_FICR-&amp;gt;DEVICEADDR[0] );	
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/182851?ContentTypeID=1</link><pubDate>Sat, 20 Apr 2019 08:28:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43bb319a-e982-4f04-9a14-1014b8c94b78</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;&lt;del&gt;Note that the DeviceID is guaranteed unique,&lt;/del&gt; but the&amp;nbsp;&lt;span&gt;DEVICEADDR&amp;nbsp;is &amp;quot;random&amp;quot; - so may not be unique.&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;strong&gt;CORRECTION: Despite what the documentation says, The DeviceID is &lt;span style="text-decoration:underline;"&gt;&lt;em&gt;not&lt;/em&gt;&lt;/span&gt; guaranteed unique - it is also random!&lt;/strong&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;strong&gt;See:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/49664/title-corrected-deviceid-is-not-unique---it-is-random/198038#198038"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/49664/title-corrected-deviceid-is-not-unique---it-is-random/198038#198038&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;See:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/22089/specific-unique-id-for-device-detection/86800#86800"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/22089/specific-unique-id-for-device-detection/86800#86800&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Which leads to:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/2112/how-to-get-6-byte-mac-address-at-nrf51822/9000#9000"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/2112/how-to-get-6-byte-mac-address-at-nrf51822/9000#9000&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;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 &lt;strong&gt;does not provide 100 % security&lt;/strong&gt; wrt. two devices having the same address, &lt;strong&gt;but the probability is quite low&lt;/strong&gt;.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;(my emphasis)&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF 52832 Chip ID or unique serial number?</title><link>https://devzone.nordicsemi.com/thread/182840?ContentTypeID=1</link><pubDate>Fri, 19 Apr 2019 21:49:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f8e42733-d62b-4d8c-9d3a-48fcbf4f84d5</guid><dc:creator>wpaul</dc:creator><description>&lt;p&gt;Someone asked a related question which I answered previously:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/42671/how-to-find-out-nrf52-chip-revision"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/42671/how-to-find-out-nrf52-chip-revision&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;-Bill&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>