nRF9160 GPIO consume higher current when configure as input

RE: nRF9160 GPIO consume higher current when configure as input

phipi — Mon, 09 Dec 2019 17:18:55 GMT

For anyone encountering the same situation I ended up disabling the interrupt callback while servicing the interrupt. I believe that in LEVEL mode the interrupt will be fired constantly while the line is held.

RE: nRF9160 GPIO consume higher current when configure as input

phipi — Fri, 29 Nov 2019 18:30:18 GMT

Sigurd When I configure the button in this mode my current drops as expected, however now I have 3mA of current while the button is held. Is this expected or am I doing something wrong? In edge mode the increase while holding the button was 50uA

RE: nRF9160 GPIO consume higher current when configure as input

khodidas — Thu, 22 Aug 2019 06:25:35 GMT

Hi,

Thanks using "GPIO_INT_LEVEL" reduced the current.

Regards,

Nirav Patel

RE: nRF9160 GPIO consume higher current when configure as input

Sigurd — Mon, 19 Aug 2019 14:39:03 GMT

Hi,

The GPIOTE peripheral can either use the IN event or the PORT event(sense mechanism) to trigger an interrupt. When you set the flag GPIO_INT_EDGE, the zephyr gpio driver will use a GPIOTE IN channel(IN EVENT) for the pin, this will consume some additional current (10 - 20 uA range).

The low-power option is to use PORT event instead. Looking at the zephyr driver, you then need to set GPIO_INT_LEVEL. You can read about the Pin sense mechanism here. Note that PORT DETECT signal is shared by multiple pins, so if you are using multiple input pins that changes level at about the same time, and at a high frequency, it might be better to use IN event.