<?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>clarification of PAN#73 (v3 TIMER PPI sleep issues) workaround</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8481/clarification-of-pan-73-v3-timer-ppi-sleep-issues-workaround</link><description>The workaround for nRF51822 PAN#73 specifies setting an undocumented register at offset 0x0C0C of the timer peripheral to 1 prior to TASKS_START , and clearing it after TASKS_STOP . 
 Two questions: 
 
 
 The description says &amp;quot;Routing TASKs...using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Aug 2015 06:59:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8481/clarification-of-pan-73-v3-timer-ppi-sleep-issues-workaround" /><item><title>RE: clarification of PAN#73 (v3 TIMER PPI sleep issues) workaround</title><link>https://devzone.nordicsemi.com/thread/30947?ContentTypeID=1</link><pubDate>Wed, 05 Aug 2015 06:59:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:21d84948-d1a0-4ba8-ac28-13d2314c94b3</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;My description 2) explains this behavior. The workaround will also force to switch a voltage regulator on , that is why it was required to set this register to zero when not sleeping or not using timer events to trigger GPIOTE or RTC tasks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: clarification of PAN#73 (v3 TIMER PPI sleep issues) workaround</title><link>https://devzone.nordicsemi.com/thread/30946?ContentTypeID=1</link><pubDate>Tue, 04 Aug 2015 17:44:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d32de41-e491-4bd2-b7f9-0228409faee2</guid><dc:creator>Paolo D</dc:creator><description>&lt;p&gt;I measured the current consumption on the PCA10028 development board with a rev 3 chip. When in sleep mode, setting the timer register for the workaround to 1, without enabling the timer or doing anything else with it, increases the current consumption by 290uA.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: clarification of PAN#73 (v3 TIMER PPI sleep issues) workaround</title><link>https://devzone.nordicsemi.com/thread/30945?ContentTypeID=1</link><pubDate>Mon, 03 Aug 2015 06:56:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2bea58c-0e47-4e94-947d-a54f493b1fd9</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;The Anomaly apply only when in sleep mode and if TIMER events are channeled to gpiote or RTC through PPI (not necessarily configured just before the sleep)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If the chip is in normal (or system on) mode then no difference in power consumption. But if in sleep mode and not using Timer events to trigger GPIOTE or RTC tasks, then there will be unnecessary increase in power consumption.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The registers are undocumented for a good reason. And hence not available in header files.
It is always good to explain this in comments giving links to PAN in your code if possible irrespective of if the register is documented or not(or available in header or not)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>