GPIOTE missing interrupts

RE: GPIOTE missing interrupts

ubrindis — Wed, 18 Mar 2020 18:34:21 GMT

Thanks, this clear things up for me.

RE: GPIOTE missing interrupts

Susheel Nuguru — Wed, 18 Mar 2020 12:45:28 GMT

I stand corrected.
GPIOTE_IN events (high_accuracy) will use HFCLK but only for the sprint of times and not always. So

GPIOTE IN will use in the order of ~10-25 uA, depending on which nRF52 device is used.

The GPIOTE IN will enable the HFCLK source to run when an edge is triggered, then start sampling using the HFCLK. Before this, the HFCLK is not used.

This is all handled and requested by the GPIOTE module,

RE: GPIOTE missing interrupts

ubrindis — Tue, 17 Mar 2020 15:58:29 GMT

Hi Susheel,

That is not the case as I am only measuring a few uA. For the GPIOTE in_event, is the clock source selectable?

Thanks

RE: GPIOTE missing interrupts

Susheel Nuguru — Tue, 17 Mar 2020 13:23:36 GMT

The high accuracy mode will need to use the HFCLK, which is listed to use at least 250uA when it is on, which means that running in high accuracy mode likely will consume somewhat more current than this. If you do not notice increase in power compared to low accuracy/ high accuracy, then the HFCLK seems to be on in both cases. Can happen if any other peripheral is keeping HFCLK on when using low accuracy on GPIOTE