<?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>GPIOTE consumption too high</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7646/gpiote-consumption-too-high</link><description>Hi,
My application uses the softdevice 110.
Everytime, there is an event on my sensor. The sensor sends the event to my pin, which generates a gpiote interrupt . But, the consumption is too high. We have about 4mA/300&amp;#181;s. Is it normal?
If not, how to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 18 Jun 2015 09:45:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7646/gpiote-consumption-too-high" /><item><title>RE: GPIOTE consumption too high</title><link>https://devzone.nordicsemi.com/thread/27253?ContentTypeID=1</link><pubDate>Thu, 18 Jun 2015 09:45:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a27cb147-1374-4a4c-b5d7-b4110d4fa7df</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;You can use both PORT event and configure gpiote for EVENTS/TASK, nrf_drv_gpiote.c uses both.
if you are only using app_gpiote.c then it should be just the PORT mode,hence it should be less power. Can you readout the config registers of GPIOTE and see if they are having reset values?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GPIOTE consumption too high</title><link>https://devzone.nordicsemi.com/thread/27254?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 15:26:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:72655faf-e56d-4186-8645-54bcbdd2fbc2</guid><dc:creator>ting&amp;#178;</dc:creator><description>&lt;p&gt;Thank you for your answer. Indeed ,setting the GPIOTE  into PORT MODE , the consumption is reduced. But, I also need EVENT/TASK event for another pin. Is it possible to have the both modes ?
I used app_gpiote.c to create my gpiote interrupt. I understood that in &amp;quot;app_gpiote&amp;#39; , the port mode is used. So why the consumption is so high? Or did I misunderstand something?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GPIOTE consumption too high</title><link>https://devzone.nordicsemi.com/thread/27252?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 09:29:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f6b3b19-af9e-4ef2-957d-fd89bbcfb95e</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Try this below thread.
&lt;a href="https://devzone.nordicsemi.com/question/2471/gpio-wakeup-low-power-workarounds/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you search this forum for gpiote current you will find much needed info
&lt;a href="https://devzone.nordicsemi.com/questions/sort:relevance-desc/query:gpiote%20current/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>