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

Sleep Mode Current

I know there have been a ton of topics about this but I've tried pretty much every solution I can think of and I cannot seem to figure out why my sleep current is consistently ~90 uA on my custom board. Here's my configuration:

  • SD 8.0.0 + SDK 8
  • Custom board with nRF51822 (rev 2)

I tried the system_power_on and system_power_off examples and I get 2.6 uA and 0.6 uA, respectively, so I know it's not the rest of my hardware that's causing the issue. I use sd_app_evt_wait and after that the device stays consistently at ~90uA. I also tried the ble_app_pwr_profiling_s110 example where I increased the advertising interval significantly and I see the same 90 uA in between advertisements.

I tested my application on the nRF51-DK and I get ~4-5 uA between advertisements which leads me to believe that it might be caused by me using a second revision chip on SDK 8. Can it be this or could it be something else?

My application was built using the ble_app_template_s110 as a template if that helps.

  • I tried using SDK 7.1.0 + SD110 7.1.0 and I still get the same issue. I used the ble_app_proximity app as an example.

  • Hi Ash

    Since you tried your application on a nRF51DK and get a normal current consumption, the problem has something to do with the hardware on your custom board. But since you get normal current consumption for the most basic examples on your custom board, gpio is not leaking current.

    I have the same suspicion as you, that this is due to using SDK 8 with second revision chip. There were a lot more anomalies for second revision chip, that SDK 8 might now support anymore, since it is made for and tested with third revision only. I would then advise you to upgrade to third revision chip if you intend to use SDK 8. Another option would be to look at the PAN document and try to identify any anomalies in the second revision that might cause the issue. What if you use an example from SDK 6.1 instead which is compatible with the second revision hardware according to the nRF51 compatibility matrix.

Related