<?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>Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14712/run-current-resources-with-gpiote-event-nrf52</link><description>What system resources are required when using GPIOTE channels (not the PORT event, the other channels)? 
 I remember on the nrf51822 there was a long-running PAN, fixed in the last release, that HFCLK and 1v2 were always required when any GPIOTE event</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 07 Sep 2016 01:02:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14712/run-current-resources-with-gpiote-event-nrf52" /><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56130?ContentTypeID=1</link><pubDate>Wed, 07 Sep 2016 01:02:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54dc42dd-2f14-4355-8684-3479b970e5ae</guid><dc:creator>nrf52</dc:creator><description>&lt;p&gt;Thanks Stefan.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56132?ContentTypeID=1</link><pubDate>Tue, 06 Sep 2016 15:02:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90a5adb0-016c-48e8-b772-f2384ce809dc</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;GPIOTE handles GPIO interrupts. If your application is very current sensitive, then it is better to use GPIOTE PORT event. When you configure low power button in the nrf_drv_gpiote driver you are using GPIOTE PORT event in the background. It has the same functionality as the GPIOTE IN, but the limitation is if two pins are asserted within the same ~10us, then only the first pin is detected. Similarly, if the same pin is asserted twice within the same ~10us, then only one assert is detected. When using softdevice, the ~10us may increase to ~500us. So if you do not need to detect two or more GPIO interrupts within the same ~10us/~500ms, then it is fine to configure low power GPIO interrupt.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56128?ContentTypeID=1</link><pubDate>Mon, 05 Sep 2016 12:08:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d153dd0-4f49-46b6-b3e6-a38194a2c027</guid><dc:creator>nrf52</dc:creator><description>&lt;p&gt;Hi Stefan , is it possible to disable GPIOE when using GPIO interrupt? If  yes ,where is the example link , if not , it is bad for nrf52 ,it will eat 8uA when GPIO interrupt open&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56129?ContentTypeID=1</link><pubDate>Mon, 05 Sep 2016 11:25:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b0f3153-65f4-4e07-b0c6-cf22a3acfff2</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;I dont think there is a workaround. We cant make GPIOTE IN consume less than ~8uA. GPIOTE PORT event still consumes &amp;lt;&amp;lt;1uA. I suspect that the PS data will be updated to reflect this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56131?ContentTypeID=1</link><pubDate>Sat, 03 Sep 2016 09:29:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1833377-8e11-49cb-8265-ad936a2a382b</guid><dc:creator>nrf52</dc:creator><description>&lt;p&gt;Stefan, is there any update for the 8uA current, how to work around the issue&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Run current/resources with GPIOTE Event nRF52</title><link>https://devzone.nordicsemi.com/thread/56127?ContentTypeID=1</link><pubDate>Mon, 04 Jul 2016 15:37:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc605934-8c4f-4dec-bd5e-0441f59cfd77</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi RK&lt;/p&gt;
&lt;p&gt;From my measurement, it seems that GPIOTE IN adds ~8uA to the current consumption when enabled. That is a whole lot better than the nRF51, but still not as specified in the nRF52832 PS. Ill update this thread when I have more information on what internal resources are used when GPIOTE IN is enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>