<?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>Is  TEMP anomaly 31 applicable to nRF52832-QFAA-0B?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42170/is-temp-anomaly-31-applicable-to-nrf52832-qfaa-0b</link><description>Dear Colleagues, 
 I am not sure whether TEMP anomaly 31 is applicable to nRF52832-QFAA-0B (NRF_FICR-&amp;gt;INFO.VARIANT == 0x41414230) 
 nrf_temp.h @ 65 says: 
 static __INLINE void nrf_temp_init(void) { /**@note Workaround for PAN_028 rev2.0A anomaly 31 </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 16 Jan 2019 13:50:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42170/is-temp-anomaly-31-applicable-to-nrf52832-qfaa-0b" /><item><title>RE: Is  TEMP anomaly 31 applicable to nRF52832-QFAA-0B?</title><link>https://devzone.nordicsemi.com/thread/165999?ContentTypeID=1</link><pubDate>Wed, 16 Jan 2019 13:50:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce77b48c-7c73-4d6e-bda1-aa80df621a59</guid><dc:creator>Andreas</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This anomaly is not relevant for nRF52 series, it seems to have carried over from earlier versions of the SDK.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>