<?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>NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/110765/nrf52832-proper-way-to-configure-gpio-interrupts-in-nrf-connect</link><description>Hi all, 
 NRF52832 NRF Connect 2.6.0 
 
 We need to configure interrupts on a GPIO on both edges. T here are several topics recommending to use GPIO_INT_TRIG_BOTH instead of GPIO_INT_EDGE_BOTH for power savings. 
 As discussed in the following topic this</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 22 May 2024 11:41:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/110765/nrf52832-proper-way-to-configure-gpio-interrupts-in-nrf-connect" /><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/485384?ContentTypeID=1</link><pubDate>Wed, 22 May 2024 11:41:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97890b2a-3dc7-4aa9-b911-6bdd73347256</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Good job&lt;/p&gt;
[quote user="Rait"]&lt;p&gt;Figured it out.&lt;/p&gt;
&lt;p&gt;The problem with the assert was caused by&amp;nbsp;incorrect suggestion in the other topic (GPIO_INT_EDGE_FALLING -&amp;gt;&amp;nbsp;&lt;span&gt;GPIO_INT_TRIG_BOTH). Should have been&amp;nbsp;GPIO_INT_EDGE_BOTH.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/90532/reducing-current-consumption-of-nrf5340-gpio-interrupts-configured-for-edge-triggering/379777"&gt;RE: reducing current consumption of nrf5340 GPIO interrupts configured for edge triggering&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Reason why the extra current consumption did not show up was because I still had the &amp;quot;sense-edge-mask&amp;quot; set in devicetree as it overrides the configuration. Seeing +4uA without it.&lt;/span&gt;&lt;/p&gt;[/quote]
&lt;p&gt;Good job!&lt;br /&gt;And thanks for explaining what you found!&lt;/p&gt;
[quote user="Rait"]The extra documentation/example would still be very useful. Google gives 7 results total for&amp;nbsp;&amp;quot;sense-edge-mask&amp;quot;.&amp;nbsp;Maybe in&amp;nbsp;the &amp;quot;nrf\samples&amp;quot; folder.[/quote]
&lt;p&gt;I will mention such a sample to my colleagues and see what we can do&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/484689?ContentTypeID=1</link><pubDate>Thu, 16 May 2024 12:34:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7619a90a-b4fd-4d2e-932f-3016075fa64b</guid><dc:creator>Rait</dc:creator><description>&lt;p&gt;You are correct about &lt;span&gt;Zephyr&amp;nbsp;being a complex system. Unfortunately,&amp;nbsp;mandating Zephyr is a decision&amp;nbsp;&lt;/span&gt;Nordic made..&lt;/p&gt;
&lt;p&gt;Figured it out.&lt;/p&gt;
&lt;p&gt;The problem with the assert was caused by&amp;nbsp;incorrect suggestion in the other topic (GPIO_INT_EDGE_FALLING -&amp;gt;&amp;nbsp;&lt;span&gt;GPIO_INT_TRIG_BOTH). Should have been&amp;nbsp;GPIO_INT_EDGE_BOTH.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/90532/reducing-current-consumption-of-nrf5340-gpio-interrupts-configured-for-edge-triggering/379777"&gt;RE: reducing current consumption of nrf5340 GPIO interrupts configured for edge triggering&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Reason why the extra current consumption did not show up was because I still had the &amp;quot;sense-edge-mask&amp;quot; set in devicetree as it overrides the configuration. Seeing +4uA without it.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The extra documentation/example would still be very useful. Google gives 7 results total for&amp;nbsp;&amp;quot;sense-edge-mask&amp;quot;.&amp;nbsp;Maybe in&amp;nbsp;the &amp;quot;nrf\samples&amp;quot; folder.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/482195?ContentTypeID=1</link><pubDate>Tue, 07 May 2024 08:06:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f32d874a-a8c0-42ee-91bd-ce278f93cefb</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>[quote user="Rait"]In case&amp;nbsp;the current consumption difference is actually ~10uA, any chance Nordic could come up with an application example for your boards/chips together with proper documentation? Or even changing the defaults in Zephyr with a clear notice about the tradeoff.[/quote]
&lt;p&gt;Zephyr is a complex system, so for general debugging I like to check my assumptions just to cover all bases. I would expect them to be set correctly, but want to make sure 100%.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;...&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately we can not have samples for everything that causes extra current draw.&lt;br /&gt;We can not document nRF current draw on the generic Zephyr API for GPIO.&lt;br /&gt;The current solution we have to this is indirect, but I would say effective, as it covers most current consumption issues and not only this one.&lt;br /&gt;Firstly, we assume that users perform current consumption analysis on their products.&lt;br /&gt;And then users can check the Product Specification or search/ask here on DevZone if they need to figure out anything about their current consumption.&lt;br /&gt;We also provide some guides and docs for power optimization, but they can not cover everything.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/481868?ContentTypeID=1</link><pubDate>Sat, 04 May 2024 09:31:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e5732a4-999d-4be2-b18e-770b6da39664</guid><dc:creator>Rait</dc:creator><description>&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;But why wouldn&amp;#39;t the configuration be applied correctly? AFAIK, Nordic maintains the relevant part of Zephyr and we are using your SDK without any modifications.&lt;/p&gt;
&lt;p&gt;In case&amp;nbsp;the current consumption difference is actually ~10uA, any chance Nordic could come up with an application example for your boards/chips together with proper documentation? Or even changing the defaults in Zephyr with a clear notice about the tradeoff.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/481512?ContentTypeID=1</link><pubDate>Thu, 02 May 2024 11:25:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec036059-172d-4916-adcf-b51275828fca</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;In this case, it is a good idea to first check if the configuration was applied correctly or not.&lt;/p&gt;
&lt;p&gt;Could you debug your code for both cases and check what &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/gpiote.html?cp=5_2_0_20_3_0#register.INTENSET"&gt;INTENSET&lt;/a&gt; is set to?&lt;br /&gt;If I remember correctly, the configuration you refer to selects wether this is configured to PORT or not.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/481500?ContentTypeID=1</link><pubDate>Thu, 02 May 2024 10:58:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b46812f5-b4b0-4821-9af4-66e9838e946d</guid><dc:creator>Rait</dc:creator><description>&lt;p&gt;I&amp;#39;m measuring the current consumption for a custom board using Power Profiler Kit 2.&amp;nbsp;During CPU idle getting ~2uA for both options.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 Proper way to configure GPIO interrupts in NRF Connect</title><link>https://devzone.nordicsemi.com/thread/481473?ContentTypeID=1</link><pubDate>Thu, 02 May 2024 09:15:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:243f6ca3-76dc-446d-be37-affad4c106b3</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Which currents are you measuring and what do you use for the measurements?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>