<?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 IN event silently drops a rising edge when preceded by a sub-microsecond glitch</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127822/gpiote-in-event-silently-drops-a-rising-edge-when-preceded-by-a-sub-microsecond-glitch</link><description>Symptoms 
 A GPIOTE event channel is configured to detect a rising edge on a GPIO input. Via PPI, the event drives a GPIO output low within a few hundred nanoseconds. The setup works correctly in isolation, but intermittently randomly, sometimes several</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 17 Apr 2026 09:18:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127822/gpiote-in-event-silently-drops-a-rising-edge-when-preceded-by-a-sub-microsecond-glitch" /><item><title>RE: GPIOTE IN event silently drops a rising edge when preceded by a sub-microsecond glitch</title><link>https://devzone.nordicsemi.com/thread/565092?ContentTypeID=1</link><pubDate>Fri, 17 Apr 2026 09:18:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5dffdf8c-30ba-4329-9af8-ad3e909c191a</guid><dc:creator>PolyTrackk</dc:creator><description>&lt;div&gt;
&lt;div dir="ltr"&gt;
&lt;p&gt;That sounds like a classic case of the &amp;quot;GPIOTE glitch filter&amp;quot; or a clock-domain synchronization issue, which can be incredibly maddening since the hardware registers look perfectly fine. I’ve seen similar behavior when the input signal has a slow slew rate or high-frequency noise right at the threshold, causing the internal edge detector to misfire or fail to latch. Have you checked the signal integrity with a high-bandwidth scope to see if there&amp;#39;s any ringing or &amp;quot;flat-spotting&amp;quot; during the transition.&lt;span style="color:rgba(255, 255, 255, 1);"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>