High power consumption with interrupt enabled

[Dane du Plooy]

I would like to wake my app from sleep (k_msleep) on a GPIO interrupt. I'm finding that enabling the interrupt draws an additional 6uA however (8uA vs 2uA without it) - am I missing something, or is this normal? This is on an nRF52-DK dev board, using BUTTON1 for the interrupt GPIO. The main thread does k_msleep whilst the interrupt calls k_wakeup.

Thank-you.

[nordicator_prim3]

Hi,

I saw saw current in that ballpark recently. If you're using GPIOTE, then the current consumption can be higher than you would think. If the interrupt pin you need isn't high frequency (sounds like it isn't) then you can use the "sense-edge-mask" dts property on your GPIO node to tell it which pins on that port to not use gpiote on.

I found that originally at this github issue which was made before that dts property was added. Later in that thread, they point to where the fix was implemented here.

[Dane du Plooy]

Thanks nordicator_prim3 ! That worked. I also found an alternative solution (not "better", but FYI); use GPIO_INT_LEVEL_ACTIVE and just disable the interrupt again immediately in the interrupt routine (otherwise it keeps firing).