This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

how to recognize pin that caused GPIOTE PORT event (sense interrupt)?

Hi all,

we have an application in which low current consumption is important, therefore we cannot use the GPIOTE IN events due to their ~1mA current consumption (devzone.nordicsemi.com/.../ and have to use GPIOTE PORT events instead...

Is there any way to recognize which pin caused the event (we have to distinguish between multiple interrupt sources)? The problem is that the interrupt (from an analog front-end) is very short and can't be read from pin in time...

Otherwise we have to run SPI communication to 'ask' the analog front-end actively whether it has caused the event or not every single time...

Thanks in advance...

Related