<?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 consumption of NRF52 GPIOTE-&amp;gt;IN</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14514/power-consumption-of-nrf52-gpiote--in</link><description>Hi all:
I found this issue happen on NRF52 with SDK v11.0. Because I measured the current increased ~1mA after enable GPIOTE-&amp;gt;IN, is there any solution can solve it?? Thanks...</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Jun 2021 09:07:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14514/power-consumption-of-nrf52-gpiote--in" /><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/314131?ContentTypeID=1</link><pubDate>Tue, 08 Jun 2021 09:07:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06733878-79f1-413b-ae4a-9636f57f3bc0</guid><dc:creator>gilbertjuly</dc:creator><description>&lt;p&gt;Thank you so much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/313867?ContentTypeID=1</link><pubDate>Mon, 07 Jun 2021 09:49:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d20041cb-b751-43ab-9d78-eef477682421</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;No, the difference between one and two GPIOTE IN events should be minimal.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Whether or not you add one or more GPIOTE IN events the current consumption will increase by approximately 20uA.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/313732?ContentTypeID=1</link><pubDate>Fri, 04 Jun 2021 15:52:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32d7e8ce-c2d7-4036-8192-f6a83b55e082</guid><dc:creator>gilbertjuly</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Torbj&amp;oslash;rn, t&lt;/span&gt;hank you for reply.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;One GPIO&amp;#39;s GPIOTE IN event increases the current by 20uA...&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Does it mean: two&amp;nbsp;&lt;span&gt;GPIO&amp;#39;s GPIOTE IN events increase the current by 40uA? And three increasing by 60uA?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/313644?ContentTypeID=1</link><pubDate>Fri, 04 Jun 2021 11:55:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efcf2687-1e8f-404b-8e84-f9cc40788ad6</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;A GPIOTE IN event on the nRF52 should increase the sleep current by around 20uA.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In general though please open a new ticket if you are having issues with this, since this case is quite old.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/313239?ContentTypeID=1</link><pubDate>Thu, 03 Jun 2021 03:19:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a4fce66-55d9-4424-98eb-7ad24ce609a7</guid><dc:creator>gilbertjuly</dc:creator><description>&lt;p&gt;Then, how much current draw will nRF52 cause when using GPIOTE IN event (high precision)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55411?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2016 08:57:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2f5af0d-2ddc-4c95-af28-5c9447055410</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;See &lt;a href="https://devzone.nordicsemi.com/question/87822/spi-consumption-problem/"&gt;this&lt;/a&gt; post. If you are using SPIM or TWIM in combination with GPIOTE-&amp;gt;IN you may experience an increase in current of about 450uA. This is related to &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.Rev1.errata/anomaly_832_89.html?cp=2_2_1_0_1_26"&gt;this&lt;/a&gt; errata (it does not mention SPIM since we are working on figuring out what the underlying cause is).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55410?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2016 06:25:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f71a7425-2587-486b-b643-4bf1a0cb1377</guid><dc:creator>nrf52</dc:creator><description>&lt;p&gt;Hi Ole,
As you said &amp;quot;With GPIOTE_CONFIG_IN_SENSE_HITOLO(true), which uses GPIOTE-&amp;gt;IN you may see an increase in current consumption of ~450uA&amp;quot; ,
I meet the same issue, when enable GPIOTE-&amp;gt;IN interrupt , increased &amp;quot;~450uA&amp;quot; on nRF52 board, how to fix it ,thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55409?ContentTypeID=1</link><pubDate>Wed, 22 Jun 2016 06:51:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:892a35f4-b472-4744-a639-760381544f91</guid><dc:creator>Jorgewu</dc:creator><description>&lt;p&gt;After check my codes, it seems follow design requirements.
So, I am asking HW engineer to breakdown power consumption of each component..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55408?ContentTypeID=1</link><pubDate>Tue, 21 Jun 2016 10:13:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ad00cdf-59a7-4030-8692-9f1e6203be3d</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;If you use IN event (high_acc = true) on nRF51 you will get around 800-900 uA. This is because the IN event on nRF51 request the HFCLK and 1V2 regulator as seen in the Product Specification part 8.3. If you use PORT event the current draw should be reduced to almost zero. This is done by setting it to false.&lt;/p&gt;
&lt;p&gt;On nRF52 this is different. IN event on nRF52 should not result in higher current draw.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55407?ContentTypeID=1</link><pubDate>Tue, 21 Jun 2016 06:23:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1fe81cd-e3ab-4f14-bba1-7ab3f30301ff</guid><dc:creator>soumil</dc:creator><description>&lt;p&gt;Just adding to the discussion here, even I am facing similar issues of high sleep current. I am using nrf51882 S110 with SDK 8. On using the GPIOTE_CONFIG_IN_SENSE_TOGGLE(high) function i am getting a sleep current of 860 micro amperes. Is it because this function doesn&amp;#39;t use the PORT event and if i set to false will it reduce the sleep current?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55406?ContentTypeID=1</link><pubDate>Mon, 20 Jun 2016 11:43:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a56b64fc-a88b-4159-a755-7b271af08c25</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;You are sure the 1.9mA is not caused by other parts (e.g. chips) in the system? The nRF52 should not be able to draw 1.9mA in system OFF.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55405?ContentTypeID=1</link><pubDate>Sat, 18 Jun 2016 12:18:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63ced9c6-cdc3-4fdf-b475-dc26d336114d</guid><dc:creator>Jorgewu</dc:creator><description>&lt;p&gt;I implemented the function to vibrate when system is reset , and wake up system by Gsensor interrupt.
After I call the function of power off after broadcast timeout, there is no vibration happens and it only vibrate after I shake device to trigger G-Sensor interrupt . According this symptom, it&amp;#39;s seems system had enter power off mode already and waked up by interrupt. it it true?
However, the power consumption still keep 1.9mA.. Why ???&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55404?ContentTypeID=1</link><pubDate>Fri, 17 Jun 2016 14:24:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:751904cb-5f14-4702-9fe2-9f2da993d227</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;Try to turn off UART and see if the current consumption is less. You are sure that the sensors are not drawing current? The reset reason have to be cleared manually, it is not cleared unless the reset is power on or brown out reset, see &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.0/power.html?cp=2_2_0_16_6#unique_1090177824"&gt;here&lt;/a&gt;. Your reset reason shows many things (pin reset, soft reset and wake up from system off reset).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55403?ContentTypeID=1</link><pubDate>Fri, 17 Jun 2016 02:15:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:006e6a8e-5bfa-498b-82d9-470a63e10a64</guid><dc:creator>Jorgewu</dc:creator><description>&lt;p&gt;After fine tuning my codes the power is down to 1.97 mA  in the conditions(The current is Same as the conditions of  just execute the loop of __WFI(), in the main())
1.Enable softdevice.
2. without advertising..
3. My HW just connect G-sensors via I2C
However it still cannot enter power off mode...
My Sense pin is pin27 , here is the pin status before enter power_off and reset reason(UART is enabled to print message(pin30, 31 for CTS/RTS, and pin 29 for DTM enable ))
NRF_GPIO-&amp;gt;IN:0x80200000
Reset Reason:0x50005
Is any item needed be checked again?&lt;/p&gt;
&lt;p&gt;Thanks..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55402?ContentTypeID=1</link><pubDate>Thu, 16 Jun 2016 15:09:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0be15caa-5952-4f7f-91c5-8562db71380b</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;If you use GPIOTE_CONFIG_IN_SENSE_HITOLO(false) you should not see any increase in current, this uses GPIOTE-&amp;gt;PORT not GPIOTE-&amp;gt;IN. With GPIOTE_CONFIG_IN_SENSE_HITOLO(true), which uses GPIOTE-&amp;gt;IN you may see an increase in current consumption of ~450uA.&lt;/p&gt;
&lt;p&gt;1.9mA when not doing anything is very high. Are you advertising or scanning often or doing other power hungry stuff?&lt;/p&gt;
&lt;p&gt;If you enter system OFF the current consumption should be less than 1uA. If you see the same current consumption after going to System OFF the device probably have woken up from system OFF mode. If the pin configured for GPIOTE_CONFIG_IN_SENSE_HITOLO(false) is low when you enter system OFF the chip will immidiately wake up (GPIOTE-&amp;gt;PORT can wake the chip up from system OFF sleep).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55401?ContentTypeID=1</link><pubDate>Thu, 16 Jun 2016 14:09:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9338ff93-2608-4f39-bc93-378b6fef0492</guid><dc:creator>Jorgewu</dc:creator><description>&lt;p&gt;If I enabled the GPIOTE-&amp;gt;IN the current is ~3.1mA(2.8V) by
const nrf_drv_gpiote_in_config_t in_config1 = GPIOTE_CONFIG_IN_SENSE_HITOLO(true).
And the current decreased to ~2.6mA after set the config by GPIOTE_CONFIG_IN_SENSE_HITOLO(false).
If I have not enable GPIOTE-&amp;gt;IN the current is ~1.9mA..&lt;/p&gt;
&lt;p&gt;BTW,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Is the current consumption of GPIOTE-&amp;gt;IN still keep 500uA while enter  power off  after enable it?
if I just execute for loop to call power_manage() in the main(), the current is 1.9mA, is it reasonable?
3.To reduce power cinsumption, I tried to enter power off mode by call the function of sd_power_system_off(). However, the power consumption always same as before execute the function..
Is any item needed be prepared before enter power off mode?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Thanks..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power consumption of NRF52 GPIOTE-&gt;IN</title><link>https://devzone.nordicsemi.com/thread/55400?ContentTypeID=1</link><pubDate>Thu, 16 Jun 2016 11:01:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41c46a3b-2d70-4146-bb94-462f57607523</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;We have seen problems when using GPIOTE-&amp;gt;IN combined with other peripherals that resulted in a current increase of about 450uA due to the high frequency clock being requested, but not 1mA. Can you give us some more information about your application?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>