External GPIO Interrupt

RE: External GPIO Interrupt

Vidar Berg — Wed, 28 Jun 2023 17:44:16 GMT

You are likely experiencing input 'bouncing'. To address this issue, one common approach is to disable the interrupt for a few milliseconds following the initial input event to give the input signal time to settle.

[quote user="Akhil Francis"]Also could you please explain me, why the dummy line added in NRF_SDK for the interrupt clearing for ARM cortex M4? [/quote]

Please refer to the 'the 'Interrupt event clearing' section in the Migrating from the nRF51 Series to the nRF52 Series guide. The dummy read may be needed when you have a very short execution time in the ISR.

RE: External GPIO Interrupt

Akhil Francis — Wed, 28 Jun 2023 14:49:29 GMT

Yes I did tried with ECTO_GPIOTE->EVENTS_IN[0] = 0; but still its making more than one for some time. But it wont happen if I am putting break point inside the handler function for each button press and executing again. It will only happen with continues execution. Is there any connection from time for the signal transition from low to high.

Also could you please explain me, why the dummy line added in NRF_SDK for the interrupt clearing for ARM cortex M4?

RE: External GPIO Interrupt

Vidar Berg — Wed, 28 Jun 2023 10:57:24 GMT

Hello,

Have you tried to just clear the event like this:

ECTO_GPIOTE->EVENTS_IN[0] = 0;

You can also use the register definitions from the MDK for the same.

e.g.

NRF_GPIOTE->EVENTS_IN[0] = 0;

Best regards,

Vidar