Serial Connectivity and Serial DFU - High Current Draw - nRF51822

[jpreston]

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?

[jpreston]

Upon further inspection, adding a hci_slip_close() fixes the issue as well. However, the character doesn't get transmitted out the UART like it did before. I'm guessing that because the UART is trying to transmit something while the chip is changing context is causing the issue? What would be the best way to accomplish what I'm trying to do here (i.e. transmit character from the bootloader)?