<?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 disable workaround for NRF52 errata 102 and 106?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29563/how-to-disable-workaround-for-nrf52-errata-102-and-106</link><description>I am using a nRF52 to communicate using both BLE and proprietary protocols. When using BLE, I apply the workarounnd for errata 102 and 106. However, when I switch to my proprietary protocol, how do I disable the workaround, so I don&amp;#39;t lose the 3 dB in</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 19 Jan 2018 14:10:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29563/how-to-disable-workaround-for-nrf52-errata-102-and-106" /><item><title>RE: How to disable workaround for NRF52 errata 102 and 106?</title><link>https://devzone.nordicsemi.com/thread/117519?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2018 14:10:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25da7796-2995-47ca-a537-4d1c310c1642</guid><dc:creator>abkirchhoff</dc:creator><description>&lt;p&gt;Thanks for the quick response!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to disable workaround for NRF52 errata 102 and 106?</title><link>https://devzone.nordicsemi.com/thread/117518?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2018 13:10:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b49fe357-c72e-4eeb-bb54-3342216b3693</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;To apply the workaround:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;if ((NRF_FICR-&amp;gt;INFO.VARIANT &amp;amp; 0x0000FF00u) &amp;lt; (((uint32_t) &amp;#39;E&amp;#39;) &amp;lt;&amp;lt; 8))
{
    *((volatile uint32_t*) 0x40001774u) = (*((volatile uint32_t*) 0x40001774u) &amp;amp; 0xFFFFFFFEu) | 0x01000000u;
} 
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To reverse the workaround:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;if ((NRF_FICR-&amp;gt;INFO.VARIANT &amp;amp; 0x0000FF00u) &amp;lt; (((uint32_t) &amp;#39;E&amp;#39;) &amp;lt;&amp;lt; 8))
{
    *((volatile uint32_t*) 0x40001774u) = (*((volatile uint32_t*) 0x40001774u) &amp;amp; 0xFEFFFFFFu) | 0x00000001u;
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The fix required for PAN182 will only be applied to Rev 2 silicon and only needs to be done every time the radio power is enabled.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;if ((*((uint32_t*) 0x10000130ul) == 0x6ul) &amp;amp;&amp;amp; (*((uint32_t*) 0x10000134ul) == 0x6ul))
{
    *(volatile uint32_t *) 0x4000173C |= (1u &amp;lt;&amp;lt; 10);
}
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>