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

External battery supply issue to DK

Hi,

I'm supplying a DK with an external battery source plugged into J6 (Li-Po) and the nRF power source switch set to VDD. When I flash the chip with one of the Openthread client examples, the DK operates normally when the board is supplied by an external battery source rated at 4.2V fully charged.

Now, when I flash the board with the s140 SoftDevice (using the nRF5_SDK_14.0.0_3bcc1f7 file repository) and run the ble_app_uart_c example with the board also supplied by the 4.2V external battery source (with the USB cable now disconnected), the board does not function. I see the onboard led's flash and barely visible. Only when I use the USB cable as a power source, then does the board operate normally and the program runs as expected.

For an external battery source, does this have something to do with a setting in registries in one of the libraries?

  • Hi, That is pretty strange.

    1. Is your battery fully charged?
    2. Have you made sure that the Power Source Switch is set to Li-Po?
    3. What kind of battery is it?
  • Hi Martin,

    Yes, of course, I checked all those things. The battery is a NiMH battery rated at 3.6V and fully charged at 4.2V. I measured 3V over VDD and 5V over the 5v pin. As I mentioned earlier, the board works fine with an external battery source when I run the Thread client example. Irrespective whether I set the switch to VDD or Li-Po, the board still works with an external battery source. I'm thinking that the problem I'm encountering is perhaps something to do with software when I use the SoftDevice? Is it possible to emulate this test on one of your DK?

  • Which version of the PCA10056 board are you using? I encountered a similar issue with the same setup and UART example. My issue was that it got stuck in some UART function, possibly because it waited for some response from the onboard Segger chip that never came. Have you tried to connect a debugger (not through USB, but debug in interface) and see what happens? The solution for me was to use RTT instead of UART for debugging. To confirm that the issue was with UART, i disabled logging over UART and didn't run any UART functions in the application. It then started to advertise and function as it should. Another test for this might be to connect the UART pins on the DK to another DK or (some other UART enabled device) and see what data is output, if any.

  • Thank you jan Tore it was an issue with uart function only. i had disable uart now everything is working fine

  • hi jan i am working in ble_app_uart example and if comment out uart_init to avoid hanging in external supply it is consuming 2.5mA in advertisement and still hangs in coin cell. here battery is full and no issue with hardware i tried disabling RTT and UARTE, UART0, UART everything still issue remains same.

    i couldn't able to understand why current consumption is increasing if i comment out uart init() function and how to make my device run in external power supply

Related