<?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_IRQHandler does not execute</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21948/gpiote_irqhandler-does-not-execute</link><description>Hi all, 
 I have some problems with GPIO Interrupts. 
 I&amp;#39;m using nrf52832, s132 and sdk 12.2 
 The error is totally random so I don&amp;#39;t know why is generated. The case is I have 3 pins that I configure with app_button_init and 2 pins that I configure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 May 2017 12:55:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21948/gpiote_irqhandler-does-not-execute" /><item><title>RE: GPIOTE_IRQHandler does not execute</title><link>https://devzone.nordicsemi.com/thread/86130?ContentTypeID=1</link><pubDate>Thu, 11 May 2017 12:55:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c2b9b18-d929-481e-8627-54dfefce9e4c</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;The &amp;quot;low accuracy&amp;quot; in the GPIOTE driver refers to using the PORT event instead of the IN event. The PORT event is generated for all GPIOs which is configured with the DETECT signal, which means that several pins can potentially generate the same event. So the driver then checks which pin triggered the signal afterwards. This will take a few CPU cycles and any changes on other pins will not be detected until it is finished.&lt;/p&gt;
&lt;p&gt;The DETECT signal will trigger on either high level or low level but not on rising/falling edge. So if it is configured to trigger on high level, and the signal goes high, the DETECT signal will continue to generate a PORT event until the line goes low again. In practice this means that you can not trigger on two GPIOs simultaneously. Like two button presses at the same time.&lt;/p&gt;
&lt;p&gt;Using low accuracy mode is reliable if the frequency is not very high, like user input, and the user presses one button at a time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GPIOTE_IRQHandler does not execute</title><link>https://devzone.nordicsemi.com/thread/86129?ContentTypeID=1</link><pubDate>Wed, 10 May 2017 13:16:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9eafb0f5-749c-4c43-8b06-2c0c5b428262</guid><dc:creator>abosch</dc:creator><description>&lt;p&gt;I&amp;#39;ve tried setting .hi_accuracy = true to all pins and the error has not reappeared but the consumption is higher. I search information about why hi_accuracy solves the problem and I find a question with the same situation as me: &lt;a href="https://devzone.nordicsemi.com/question/106123/gpiote-interrupt-nrf51822-freezing/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;. The solution that is given here in order to have low consumption and avoid this error is to config all pins with GPIOTE_CONFIG_IN_SENSE_TOGGLE. At the moment, this solve my problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>