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

Power Profiler kit disconnects and the NRF52DK

Hello, 

First time posting, Here are the details of my setup, I would greatly appreciate any help from anyone at this point.
I have purchased 2 nrf52 development kits with 2 power profiler kits to go with them. I am trying to measure the current / power consumption of a lithium ion battery CR2477 in a small test circuit.

1 NRF52DK with 1 PPK plugged together / stacked.

1 external circuit / hardware in breadboard.

1 CR2477 coin cell lithium ion battery (3.0 V).

1 Computer with NRF Connect wand power consumption app installed. (V. 2.3.2 for NRF connect, and 2.0 for the power) 

The NRF52DK has jumper SB9 cut, and SB12 joined (as SB12 is for external source)

I have 2 jumper cables running from the battery holder, to the PPK External supply. 

I also have 2 jumpers running from External DUT to power the breadboarded circuit.

After I've connected the DK to the computer (PC) it asks for a firmware update, I agree and continue. I select the COM port to use and select start.

It seems to work from here, and we'll get to that in a bit. But after pressing start, the system disconnects or drops into an error for no apparent reason. Please see image below:

I'm not sure if the quality is good enough, however the text under the red highlight it says: "Corrupt data detected, please check connection to PPK"

At this point nothing has changed, no cable has moved, and I checked various micro usb cables connected to the DK. 

The issue persists. 

Another screenshot of the logged info can be found below: 

I'm not sure if this is a known issue, but we're in a tight deadline to test our circuits for power consumption / battery life and it's a bit troublesome that it doesn't work as expected. 

I would greatly appreciate anyone's help. I have this setup up and ready to run if anyone has any suggestions or need more information from the device / me.

Thank you in advance

  • I have removed the jumper on SB12, and also removed the battery as external supply. I am now testing my DUT using the DK.

    Connections are as follows:

    USB cable connected to DK

    Connections from External DUT (P16 of PPK) to DUT

    PPK Switch SW2 on DUT Select External

    PPK Switch SW4 on Power select DK

    My DUT is powered properly and works as expected, but when I run NRFConnect, and start the acquisition, I still do not see the right consumption and it still crashes. My device draws around 300 uA for 3.5 seconds when activated, and 14 uA at rest. I do not see this reflected on the screen. 

    I would like to ask you for help regarding the other points:

    You should also try to do an erase before launching the application,
    which will ask you to flash. Verify that it is the PPK that is erased,
    by observing your DK acting normal
    (just flash it with e.g. a blinky example and watch LED's still flashing after erase).
    
    If you do an erase, then flash the firmware yourself
    (find the firmware at C:\Users\<user>\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk\firmware\)
    and the PPK app still reports the need for flashing a new firmware,
    then we know for sure something is wrong with the connection/flashing/reading.

    I do not know how to do the "quoted" text above, I'm not sure how to erase the board, nor re-flash the DK or PPK. I would greatly appreciate your assistance with this if possible.

    Thank you Kindly for your help!

  • You can use nrfjprog (our cli tool) or download our programming app through nrf connect (install apps) and do both erase and program from there.

    The fact that it crashes worries me, as I have never seen it semi-working like this before. Does it run fine without you starting triggering? Also, did you try and flash the DK with a Blinky to verify it is not running the PPK firmware? Just drag and drop an example from the SDK to do that :) 

  • Thanks for the follow up information. I have used the NRFConnect v2.3.2 (programmer - v1.0.0) and uploaded the firmware located at the folder you mentioned previously. 

    I still get the same problems, the PPK disconnects with the following error

    I found a similar issue or what seems to be a similar issue that pertained the version of the command line tools, so I downgraded to a previous version. But no dice. I still get the same error. 

    Another thing to note, when the DK is used as DUT I should be getting a graph (according to your youtube channel) similar to the following: 

    So I'm wondering if the Hex in the main folder may also be corrupted? 

    Thank you again for your continued support.

  • No problem. So you're saying you don't get data using the DK as DUT either?? Again, are you absolutely certain that the DK is running it's firmware, e.g a blinky example when measuring with the PPK? 

    Also, do you have cables/external debugger available?

  • Hi,

    I thought my response was posted yesterday, I apologize for that. Yes I do get data using the DK as a DUT. I have deleted the hex image in the DK using NRF Connect's programmer app, as well as flashed the ble_blinky program in the DK successfully. And I do get what the video I referred to previously got as a result. 

    However after a few minutes (between 1 - 5) the program crashes with error:

    Corrupt data detected, please check connection to PPK. 

    PPK closed

    PPK closed

    I have used 4 different USB cables and do not touch the board while the acquisition is on. 

    I don't have any external debugger available... If you have a product number or link to it I may be able to get it depending on the cost and lead time.

    Thank you

Related