<?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>NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122849/nrf52840-gpio-41-drawing-140-ua-when-configured-as-input-with-pullup</link><description>Setup: - We have a custom board using the BL654 (Laird Connectivity) module with the NRF52840 core using SDK 17.1 
 Issue: 
 - On power up we configure the GPIO 41 as an input with internal pullup (NRF_GPIO_PIN_PULLUP) 
 . The input in this test is disconnected</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Jul 2025 00:17:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122849/nrf52840-gpio-41-drawing-140-ua-when-configured-as-input-with-pullup" /><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/542162?ContentTypeID=1</link><pubDate>Fri, 11 Jul 2025 00:17:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0094594-3350-4c5c-b3da-d8fb614e8787</guid><dc:creator>jthmp</dc:creator><description>&lt;p&gt;So, it looks like this was a HW issue on our end and has since been resolved.&lt;/p&gt;
&lt;p&gt;Thank you for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/542145?ContentTypeID=1</link><pubDate>Thu, 10 Jul 2025 18:25:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e15a4ff4-90b4-4834-8403-e629fbe1060a</guid><dc:creator>jthmp</dc:creator><description>&lt;p&gt;Hi, also based on my example code it looks like we are using the PORT EVENT code&lt;br /&gt;nrfx_gpiote_in_config_t in_config = NRFX_GPIOTE_CONFIG_IN_SENSE_TOGGLE(false);&lt;br /&gt;&lt;br /&gt;So, HFINT isn&amp;#39;t enabled. Unless I got this backwards?&lt;/p&gt;
&lt;p&gt;Can you clarify?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/542144?ContentTypeID=1</link><pubDate>Thu, 10 Jul 2025 18:02:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8899e7e1-3c31-4fbc-a3f4-dd1c00b92205</guid><dc:creator>jthmp</dc:creator><description>&lt;p&gt;From the BL654 data sheet&lt;/p&gt;
&lt;p&gt;SIO_41 (BL654) = R1 (NRF52840 QFN Pin) = P1.09 (NRF52480 QFN Name)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/542106?ContentTypeID=1</link><pubDate>Thu, 10 Jul 2025 12:01:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ac4a6272-a3c8-4783-a57a-91516eeb456c</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Can you confirm that GPIO 41 here is referring to P0.28 on the nRF52840 QFN48 package, or does the&amp;nbsp;&lt;span&gt;BL654&amp;nbsp;have a different GPIO naming convention? Regarding the port event, the GPIOTE documentation describes how to change this &lt;a href="https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/hardware_driver_gpiote.html#gpiote_in"&gt;here&lt;/a&gt;, and we have multiple other&lt;a href="https://devzone.nordicsemi.com/search?q=port%20event"&gt; tickets on the DevZone &lt;/a&gt;where this has been discussed in the past.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Simon&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/541987?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2025 18:17:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:157c0ceb-2302-4f3b-b581-83d05ded962c</guid><dc:creator>jthmp</dc:creator><description>&lt;p&gt;Hi, ok but it looks like even when I do this (not using events or triggers) I still get the issue&lt;/p&gt;
&lt;p&gt;Also, some tests show that even using NOPULLUP results in 140 uA current draw&lt;/p&gt;
&lt;p&gt;Can you provide an example of using the &amp;quot;port event&amp;quot; option?&amp;nbsp;&lt;br /&gt;Thank you!&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;if (!nrfx_gpiote_is_init())
{
ASSERT(0 == nrfx_gpiote_init());
}
nrf_gpio_cfg_input(41u, NRF_GPIO_PIN_PULLUP);&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 GPIO 41 Drawing 140 uA when configured as input with PULLUP</title><link>https://devzone.nordicsemi.com/thread/541985?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2025 17:55:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:207cea18-5205-42b3-b296-2a4f22b280ab</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;GPIOTE IN event (edge triggers) require HFINT running in order to work. That is where the additional current goes into.&lt;/p&gt;
&lt;p&gt;Consider using a level trigger (&amp;quot;port event&amp;quot;) if you wanted lowest consumtion.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>