Radio Activity Causes GPIOTE Interrupt Missing

RE: Radio Activity Causes GPIOTE Interrupt Missing

Rick.Soza — Thu, 06 Nov 2014 00:44:00 GMT

Hi Bruce,

Would you be willing to share your GPIOTE driver solution. Seems we're having the same issue. Or walk us through the solution?

Thanks, Rick S

RE: Radio Activity Causes GPIOTE Interrupt Missing

Martin — Fri, 09 May 2014 06:19:08 GMT

Hi, old thread maybee, have a look in the nrf51822-PAN document, think I read something about missing interrupts.

RE: Radio Activity Causes GPIOTE Interrupt Missing

Bruce — Fri, 28 Mar 2014 23:02:16 GMT

Hi Tomoyuki,

I had to write our own GPIOTE driver that utilizes the hardware capture (GPIOTE PIN Event) as opposed to the PORT Events that requires timely CPU intervention. When you use GPIOTE PIN event, there's hardware register that saves the pin status if I'm not mistaken.

Bruce

RE: Radio Activity Causes GPIOTE Interrupt Missing

Tomoyuki — Fri, 28 Mar 2014 11:43:45 GMT

Hi Bruce,

I'm facing same issue. Did you find any workarounds for this issue?

Thank you.

Tomoyuki

RE: Radio Activity Causes GPIOTE Interrupt Missing

Bruce — Sun, 15 Dec 2013 02:39:03 GMT

update on this issue, hopefully this can help someone hitting the same issue.

caused by app_gpiote.c GPIOTE_IRQHandler implementation. The interrupt is trigger by HW, however, the state of the pins are read when CPU enters GPIOTE_IRQHandler. If CPU is servicing higher priority interrupt such as Lower Stack ISR when GPIOTE interrupt happens, then GPIOTE_IRQHandler is deferred until Lower Stack ISR finishes. By the time GPIOTE_IRQHandler is serviced, the pin state might have changed causing GPIOTE_IRQHandler to react based on the erroneous pin state.