<?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>How to find out nRF52 chip revision</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42671/how-to-find-out-nrf52-chip-revision</link><description>Hello, 
 I am using multiple custom boards with ISP1507-AX modules from InsightSIP, based on the nRF52 chip. I want to verify the revision numbers of the nrf52 chips inside them. Is there a way to do this? I have tried nRFGo Studio, but the revision is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 21 Jan 2019 12:38:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42671/how-to-find-out-nrf52-chip-revision" /><item><title>RE: How to find out nRF52 chip revision</title><link>https://devzone.nordicsemi.com/thread/166836?ContentTypeID=1</link><pubDate>Mon, 21 Jan 2019 12:38:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53c9f4ba-6098-4185-91dc-d9899ca86d83</guid><dc:creator>OJ</dc:creator><description>&lt;p&gt;Yes, thank you very much &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to find out nRF52 chip revision</title><link>https://devzone.nordicsemi.com/thread/166349?ContentTypeID=1</link><pubDate>Thu, 17 Jan 2019 17:37:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd19ddbd-f47e-4d92-8d4b-27be696c2120</guid><dc:creator>wpaul</dc:creator><description>&lt;p&gt;There is a set of FICR registers which indicate the manufacturing info for the device, which you can print out in your application. I use code like this:&lt;/p&gt;
&lt;p&gt;info = NRF_FICR-&amp;gt;INFO.VARIANT;&lt;br /&gt; p = (uint8_t *)&amp;amp;info;&lt;br /&gt; printf (&amp;quot;Nordic Semiconductor nRF%x Variant: %c%c%c%c &amp;quot;,&lt;br /&gt; NRF_FICR-&amp;gt;INFO.PART, p[3], p[2], p[1], p[0]);&lt;br /&gt; printf (&amp;quot;RAM: %dKB Flash: %dKB\r\n&amp;quot;, NRF_FICR-&amp;gt;INFO.RAM,&lt;br /&gt; NRF_FICR-&amp;gt;INFO.FLASH);&lt;br /&gt; printf (&amp;quot;Device ID: %x%x\r\n&amp;quot;, NRF_FICR-&amp;gt;DEVICEID[0],&lt;br /&gt; NRF_FICR-&amp;gt;DEVICEID[1]);&lt;/p&gt;
&lt;p&gt;The NRF_FICR.INFO registers are defined in the SDK headers like this:&lt;/p&gt;
&lt;p&gt;/**&lt;br /&gt; * @brief FICR_INFO [INFO] (Device info)&lt;br /&gt; */&lt;br /&gt;typedef struct {&lt;br /&gt; __IM uint32_t PART; /*!&amp;lt; (@ 0x00000000) Part code */&lt;br /&gt; __IM uint32_t VARIANT; /*!&amp;lt; (@ 0x00000004) Build code (hardware version and production configuration) */&lt;br /&gt; __IM uint32_t PACKAGE; /*!&amp;lt; (@ 0x00000008) Package option */&lt;br /&gt; __IM uint32_t RAM; /*!&amp;lt; (@ 0x0000000C) RAM variant */&lt;br /&gt; __IM uint32_t FLASH; /*!&amp;lt; (@ 0x00000010) Flash variant */&lt;br /&gt; __IOM uint32_t UNUSED8[3]; /*!&amp;lt; (@ 0x00000014) Unspecified */&lt;br /&gt;} FICR_INFO_Type; /*&lt;/p&gt;
&lt;p&gt;They should also be documented in the various nRF52 product specification documents.&lt;/p&gt;
&lt;p&gt;Does that help?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>