Handling GPIO interrupt when pressed together

RE: Handling GPIO interrupt when pressed together

Kenneth — Tue, 28 May 2019 06:51:26 GMT

[quote user="beemavishnu"]Bit confused between high-accuracy (true) and port event (false) modes.[/quote]

Port event is low power (~uA) and "a bit slower", e.g. it may take a few additional us on wakeup. High-accuracy is high power (e.g. ~mA), but faster wakeup (within 1us).

RE: Handling GPIO interrupt when pressed together

beemavishnu — Mon, 27 May 2019 12:15:36 GMT

Hello Kenneth,

For me only button press state is good enough. When I kept GPIOTE_CONFIG_IN_SENSE_HITOLO(false) with 2 sec delay, it was working when I press one button at a time.

But if I press two buttons at a time (with in 2sec delay) never it worked.

In GPIOTE_CONFIG_IN_SENSE_TOGGLE(true) few interrupts are getting missed. So finally I reverted back to GPIOTE_CONFIG_IN_SENSE_TOGGLE(true). Now its working when I press two buttons at a time.

Bit confused between high-accuracy (true) and port event (false) modes.

Thanks & Regards

Vishnu Beema

RE: Handling GPIO interrupt when pressed together

Kenneth — Mon, 27 May 2019 11:18:00 GMT

Hello,

Using GPIOTE is typically the way to go:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/pin_change_int_example.html?cp=5_1_4_6_18

SDK example:
\nRF5_SDK_15.3.0_59ac345\examples\peripheral\pin_change_int

Devzone example:
https://devzone.nordicsemi.com/f/nordic-q-a/35945/nrf_drv_gpiote_in_event_enable

Best regards,
Kenneth