https://devzone.nordicsemi.com/f/nordic-q-a/24411/wakeup-from-any-of-10-buttonshello, my custom hardware includes 10 buttons connected to 10 GPIOs of a nRF52832. The nRF52 is placed in low power or eventually system OFF all the time, waiting for a pin state change on any of the 10 buttons. GPIO are currently tied to grounden-USTelligent Community 13Thu, 17 Aug 2017 11:38:26 GMThttps://devzone.nordicsemi.com/thread/96144?ContentTypeID=1Thu, 17 Aug 2017 11:38:26 GMT137ad170-7792-4731-bb38-c0d22fbe4515:26c358bd-d87f-4fe9-b024-97fa2ecabe1ebloobird0<p>OK thanks for your help. I misunderstood the PORT event documentation (I was confused with the DETECT signal active high). I can now go on. Thanks again.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/96143?ContentTypeID=1Wed, 16 Aug 2017 17:41:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6274a8ad-110a-4019-a190-28febb8724cdJohn<p>I don&#39;t believe that is correct. You can get a port event on pin going low. We have buttons on our product that behave in just the way you describe and we detect the falling edge just fine. Section 20.1 of the PS says:</p> <p>&quot;Pins can be individually configured, through the SENSE field in the PIN_CNF[n] register, to detect either a high level or a low level on their input.</p> <p>When the correct level is detected on any such configured pin, the sense mechanism will set the DETECT signal high. Each pin has a separate DETECT signal, and the default behaviour, as defined by the DETECTMODE register, is that the DETECT signal from all pins in the GPIO Port are combined into a common DETECT signal that is routed throughout the system&quot;</p> <p>The detect signal itself is active high which may be what is confusing?</p><div style="clear:both;"></div>