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...
I implemented the function to vibrate when system is reset , and wake up system by Gsensor interrupt. After I call the function of power off after broadcast timeout, there is no vibration happens and it only vibrate after I shake device to trigger G-Sensor interrupt . According this symptom, it's seems system had enter power off mode already and waked up by interrupt. it it true? However, the power consumption still keep 1.9mA.. Why ???
You are sure the 1.9mA is not caused by other parts (e.g. chips) in the system? The nRF52 should not be able to draw 1.9mA in system OFF.
Just adding to the discussion here, even I am facing similar issues of high sleep current. I am using nrf51882 S110 with SDK 8. On using the GPIOTE_CONFIG_IN_SENSE_TOGGLE(high) function i am getting a sleep current of 860 micro amperes. Is it because this function doesn't use the PORT event and if i set to false will it reduce the sleep current?
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.
After check my codes, it seems follow design requirements. So, I am asking HW engineer to breakdown power consumption of each component..