<?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>Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/509/power-use-with-gpiote-is-too-high</link><description>I have just begun tests with the nRF51822 DK. 
 I have written a test program which uses the RTC and PPI to generate an event every 125 ms, and use a task to toggle a GPIO pin. I try to put the processor to sleep with __WFI(). 
 I was expecting a very</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Oct 2013 17:02:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/509/power-use-with-gpiote-is-too-high" /><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2662?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2013 17:02:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81834510-5f05-49a6-bf76-96d2e82b9c87</guid><dc:creator>Erland Lewin</dc:creator><description>&lt;p&gt;It&amp;#39;s the 1.2 volt voltage supply.&lt;/p&gt;
&lt;p&gt;According to the Product Specification, table 27, the system will draw 810 uA when the 16 MHz crystal and 1.2V regulator are enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2661?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2013 16:34:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:18a4fbf0-0137-4d5d-9ccb-b699407b371c</guid><dc:creator>Fred</dc:creator><description>&lt;p&gt;Hi Marc Nicholas,what&amp;#39;s mean with &amp;quot;1V2&amp;quot;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2660?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2013 15:50:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13ca09a8-2ac8-47a9-a3f6-3ffac4e86843</guid><dc:creator>Erland Lewin</dc:creator><description>&lt;p&gt;Credit to Marc Nicholas for pointing out that this is hardware bug #39 documented in the v2.0 Product Anomaly Notification released today, apparently present in all versions of the chip.&lt;/p&gt;
&lt;p&gt;I&amp;#39;d mark your comment as the correct reply, but as it&amp;#39;s a comment to a comment, it appears that I can&amp;#39;t.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2659?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2013 15:23:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fc3018d-4d10-43f4-90f9-16bae57a444b</guid><dc:creator>Marc Nicholas</dc:creator><description>&lt;p&gt;Have you read the PAN?&lt;/p&gt;
&lt;ol start="39"&gt;
&lt;li&gt;GPIOTE: 1V2 + HFCLK are requested always when the GPIOTE task is configured.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Symptoms:
Excess current consumption in system ON mode when CPU is sleeping.&lt;/p&gt;
&lt;p&gt;Conditions:
One or more GPIOTE channels are configured in task mode.&lt;/p&gt;
&lt;p&gt;Consequences:
Battery life time is degraded.&lt;/p&gt;
&lt;p&gt;Workaround:
None.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2658?ContentTypeID=1</link><pubDate>Sat, 28 Sep 2013 19:59:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:35ca24f0-7e31-43a2-9ca8-ad228b666768</guid><dc:creator>Christopher Mason</dc:creator><description>&lt;p&gt;FYI, I&amp;#39;m seeing similar behavior with GPIOTE causing about 1.2 mA current draw.  In my application I can relatively easily enable/disable the GPIOTE when needed by setting the GPIO config mode to DISABLE when not in use.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2657?ContentTypeID=1</link><pubDate>Tue, 24 Sep 2013 19:05:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:acf00169-1bdd-47bd-a548-db8380b9da69</guid><dc:creator>Erland Lewin</dc:creator><description>&lt;p&gt;Ok, I tracked this down further. I minimized the program, and the following line causes the program to draw about 950 uA:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;
	NRF_GPIOTE-&amp;gt;CONFIG[GPIOTE_CHANNEL_NUMBER] = 
(GPIOTE_CONFIG_MODE_Task *shiftleft* GPIOTE_CONFIG_MODE_Pos)     |
                                         ((uint32_t)outPin *shiftleft* GPIOTE_CONFIG_PSEL_Pos)     |
                                         ((uint32_t)NRF_GPIOTE_POLARITY_TOGGLE *shiftleft* GPIOTE_CONFIG_POLARITY_Pos) |
                                         ((uint32_t)NRF_GPIOTE_INITIAL_VALUE_HIGH *shiftleft* GPIOTE_CONFIG_OUTINIT_Pos);

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;(There&amp;#39;s apparently a bug in the forum, so I replaced two &amp;#39;less than&amp;#39; with &lt;em&gt;shiftleft&lt;/em&gt; above)&lt;/p&gt;
&lt;p&gt;In the product specification, section 8.10 says the GPIOTE should only draw 0.1 uA &amp;quot;in Output mode&amp;quot;. As far as I can understand, the above uses the GPIOTE in output mode (defines a task which toggles an output pin).&lt;/p&gt;
&lt;p&gt;Please help me understand why the above line causes the GPIOTE to draw more than 0.1 uA!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2656?ContentTypeID=1</link><pubDate>Tue, 24 Sep 2013 04:32:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f34cfad2-0d81-40e0-85be-3be2104decad</guid><dc:creator>Erland Lewin</dc:creator><description>&lt;p&gt;I added code to power down peripherals as below, but I am still measuring 87 mV (=870 uA).&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;
	// Disable unused peripherals
	// Radio:
	NRF_RADIO-&amp;gt;TASKS_DISABLE = 1;
	NRF_RADIO-&amp;gt;POWER = 0;
		
	NRF_POWER-&amp;gt;POFCON = 0; // Disable Power Fail Comparator
	NRF_GPIOTE-&amp;gt;INTENSET = 0; // Disable all GPIO interrupts
	NRF_TIMER0-&amp;gt;TASKS_STOP = 1;
	NRF_TIMER0-&amp;gt;POWER = 0;
	NRF_TIMER1-&amp;gt;TASKS_STOP = 1;
	NRF_TIMER1-&amp;gt;POWER = 0;
	NRF_TIMER2-&amp;gt;POWER = 0;
	// NRF_WDT-&amp;gt;CONFIG = 0;
	NRF_WDT-&amp;gt;POWER = 0;
	NRF_RNG-&amp;gt;POWER = 0;
	NRF_TEMP-&amp;gt;POWER = 0;
	NRF_ECB-&amp;gt;POWER = 0;
	NRF_CCM-&amp;gt;POWER = 0;
	NRF_AAR-&amp;gt;POWER = 0;
	NRF_SPI0-&amp;gt;POWER = 0;
	NRF_SPI1-&amp;gt;POWER = 0;
	NRF_SPIS1-&amp;gt;POWER = 0;
	NRF_TWI0-&amp;gt;POWER = 0;
	NRF_TWI1-&amp;gt;POWER = 0;
	NRF_UART0-&amp;gt;POWER = 0;
	NRF_QDEC-&amp;gt;POWER = 0;
	NRF_ADC-&amp;gt;POWER = 0;
	NRF_LPCOMP-&amp;gt;POWER = 0;

&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power use with GPIOTE is too high?</title><link>https://devzone.nordicsemi.com/thread/2655?ContentTypeID=1</link><pubDate>Mon, 23 Sep 2013 18:37:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db0d9728-7de2-4b7a-83a6-e4f44b410d24</guid><dc:creator>Erland Lewin</dc:creator><description>&lt;p&gt;I just found the discussion: &lt;a href="https://devzone.nordicsemi.com/index.php/why-does-my-nrf51822-consume-1-ma-in-sleep"&gt;&amp;quot;Why does my nrf51822 consume 1 ma in sleep&amp;quot;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I powercycled the circuit to disable the debug interface. This reduced the consumption from 1240 to 950 uA. Then I made sure the HF cystal was enabled, which reduced the power consumption ot 870 uA. Still a factor 100 too high, I think.&lt;/p&gt;
&lt;p&gt;As you see in the code, I have not explicitly enabled any other peripheral modules. But it does seem like something is using the 16 MHz crystal. Could it be the GPIOTE? If so, how can I make it release the 16 MHz crystal?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>