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

Serial Connectivity and Serial DFU - High Current Draw - nRF51822

I have combined Nordic's serial connectivity code and Nordic's serial DFU example.

Upon initial powerup, the nRF51822 draws an expected amount of current (~600uA). When issuing the system off command via serial, the current draw drops to about 0.5uA, which is to be expected.

The issue occurs when waking the nRF51822 via external interrupt. When I do that, the chip wakes up but starts drawing about 1800uA. Issuing the system off command drops it to about 1200uA. This current draw corresponds to what I see when the debug interface is active (i.e. just after programming the chip without a power cycle).

I have verified that the nRF51 is resetting because I have the DFU code send a string out the UART so the main processor can know it started. I've also verified that the application starts running after waking up from an external interrupt.

I'll also add that I don't see this issue unless I program the bootloader. The Softdevice and connectivity code show expected current draw all the time when the bootloader is not programmed.

Any advice?

Parents
  • I think you're right about the bootloader using peripherals before jumping to the application is the problem. I had modified it to send a character out the UART to give our main processor notification that the nRF51 is booting. I'm not positive that this completely solves the issue yet, but I removed that part of the bootloader and it seems to be working properly now. Why do you think this would still cause high current draw when in SystemOFF?

Reply
  • I think you're right about the bootloader using peripherals before jumping to the application is the problem. I had modified it to send a character out the UART to give our main processor notification that the nRF51 is booting. I'm not positive that this completely solves the issue yet, but I removed that part of the bootloader and it seems to be working properly now. Why do you think this would still cause high current draw when in SystemOFF?

Children
No Data
Related