<?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>NRF52832 Anomaly 89 - When should the workaround be applied?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75571/nrf52832-anomaly-89---when-should-the-workaround-be-applied</link><description>Dear support, 
 Anomaly 89 of the NRF52832 states that a high static current consumption is observed when the SPIM/TWIM uses EasyDMA and the GPIOTE is configured in event mode. The workaround, copied below, consist on &amp;quot;power cycling&amp;quot; the peripheral, by</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 May 2021 15:39:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75571/nrf52832-anomaly-89---when-should-the-workaround-be-applied" /><item><title>RE: NRF52832 Anomaly 89 - When should the workaround be applied?</title><link>https://devzone.nordicsemi.com/thread/311884?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 15:39:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5902a4eb-8ddf-4fe2-8081-29764a24064b</guid><dc:creator>p.martins</dc:creator><description>&lt;p&gt;Hi Jared,&lt;/p&gt;
&lt;p&gt;Thank you for such a clear answer. I have understood and have no further questions.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Pedro&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Anomaly 89 - When should the workaround be applied?</title><link>https://devzone.nordicsemi.com/thread/311818?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 13:04:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:927d7ace-7c1b-4bf0-aa5e-0548bf32ef8f</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;It depends a bit on your application. More specially how much time it goes between transactions. In most cases it should be good enough to run the workaround when you are done using the peripheral. Typical usecase would be before going to sleep, as this is usually where a low current draw is most important.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Yes, you should run the workaround, Uninitializing the peripheral does not ensure that the HFCLK is released properly. It needs a complete power cycle.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>