Hi all: I found this issue happen on NRF52 with SDK v11.0. Because I measured the current increased ~1mA after enable GPIOTE->IN, is there any solution can solve it?? Thanks...
Hi all: I found this issue happen on NRF52 with SDK v11.0. Because I measured the current increased ~1mA after enable GPIOTE->IN, is there any solution can solve it?? Thanks...
If you use IN event (high_acc = true) on nRF51 you will get around 800-900 uA. This is because the IN event on nRF51 request the HFCLK and 1V2 regulator as seen in the Product Specification part 8.3. If you use PORT event the current draw should be reduced to almost zero. This is done by setting it to false.
On nRF52 this is different. IN event on nRF52 should not result in higher current draw.
If you use IN event (high_acc = true) on nRF51 you will get around 800-900 uA. This is because the IN event on nRF51 request the HFCLK and 1V2 regulator as seen in the Product Specification part 8.3. If you use PORT event the current draw should be reduced to almost zero. This is done by setting it to false.
On nRF52 this is different. IN event on nRF52 should not result in higher current draw.
Then, how much current draw will nRF52 cause when using GPIOTE IN event (high precision)?
Hi
A GPIOTE IN event on the nRF52 should increase the sleep current by around 20uA.
In general though please open a new ticket if you are having issues with this, since this case is quite old.
Best regards
Torbjørn
Hi Torbjørn, thank you for reply.
One GPIO's GPIOTE IN event increases the current by 20uA...
Does it mean: two GPIO's GPIOTE IN events increase the current by 40uA? And three increasing by 60uA?
Hi
No, the difference between one and two GPIOTE IN events should be minimal.
Whether or not you add one or more GPIOTE IN events the current consumption will increase by approximately 20uA.
Best regards
Torbjørn
Thank you so much.