<?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>extra current in idle ~450 uA NRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25956/extra-current-in-idle-450-ua-nrf52832</link><description>Hi all 
 I&amp;#39;m trying to build a generator based on NRF52832. Outpit signals are: 8MHz clock and two latches signals highly sinchronized with clock - RGB_LAT and TXT_LAT. For this task I used TIMER1, PPI and GPIOTE. Actually my approach is working as expected</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Oct 2017 13:19:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25956/extra-current-in-idle-450-ua-nrf52832" /><item><title>RE: extra current in idle ~450 uA NRF52832</title><link>https://devzone.nordicsemi.com/thread/102258?ContentTypeID=1</link><pubDate>Mon, 16 Oct 2017 13:19:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc49fba9-f167-4b68-acf9-9a18cbd50332</guid><dc:creator>Konstantin</dc:creator><description>&lt;p&gt;Thanks! It is working now!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: extra current in idle ~450 uA NRF52832</title><link>https://devzone.nordicsemi.com/thread/102257?ContentTypeID=1</link><pubDate>Mon, 16 Oct 2017 11:47:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23e91509-ca6e-4a7c-a4ff-e4358412e210</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This seems to be related to this recently published erratum: &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.Rev1.errata/anomaly_832_156.html?cp=2_1_1_0_1_45"&gt;GPIOTE: Some CLR tasks give unintentional behavior&lt;/a&gt;. I tested your code and using channels 1, 3, and 5 for example, seemed to solve the problem.&lt;/p&gt;
&lt;p&gt;The easiest workaround seems to be to only use the odd numbered GPIOTE channels to keep the GPIOTE in low power mode all the time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>