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

Parents
  • After reading your comments, it is quite apparent that the software does not find the correct PPK firmware, and assumes you have an old version/ installed or is erased. To me, it seems like it is programming the DK. 
    OR, something is being messed up from soldering bridges on the DK. Being that you are using an external DUT, no bridges on the DK should be soldered. External supply is only connected to the PPK. The only preperation for the DK is the current measurement bridge that should be cut. 

    Have you ever had it working before? For instance, does it work in the standard configuration, i.e with the ppk connected to the dk, nothing external, USB connection to the DK? 

    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.

    Also, is it so that you are acquiring average (top chart) samples without any problem, and it fails after starting trigger? If so, there is something really wrong with the SEGGER interface. I have seen this before if trying to push more than we can out of the ppk, overflowing buffers on the on-board debugger. This can also occur on the PC-side if using an old version of the SEGGER software/libraries. 

    I might have more input, but it would be nice if you test these things first. And as a final note, do _not_ use trigger if you are after correct power profiling. It will make the measured average less accurate due to lost average data, as stated in the user guide.

  • Thank you for the response,

    I will be removing the solder bridge on SB12, to answer your question, I did test the most basic form of use (followed by the introduction video PPK youtube) And it worked. 

    At this point I have not yet flashed anything onto the DK or PPK, we started using this PPK purely for power consumption measurement purposes.

    I will get to testing all these suggestions, will get back to you with results as soon as I get them. But to answer your SEGGER question, As soon as the ppk is connected and the COM port selected, I do press start and it does acquire something. Not 100% sure the acquired data is from my DUT, but it gets something that repeats every 4 seconds. After a minute or two, the log displays the "corrupt data detected" message and stops the acquisition. Buffer doesn't buffer anything unless I select a window to view, and the trigger doesn't seem to properly adjust (please see image attached above, where external trigger is set to 15 uA and the log displays 1 uA.) However I am using the newest version of NRF Connect. 

    Thank you for the complete response, I will get back to you as soon as I get any results. 

    Sincerely, 

    Agustin

  • Just to point out, I shorted the SB12 jumper because it's explained here that I need to do it for NRF52DK preparation procedures for the PPK. 

    Thanks

  • Are you sure that you have uploaded the correct link? It sent me to nrf connect troubleshooting.

  • I see that now, thank you for noticing, I arrived at that page and it seems opening different links won't update the URL. Here Preparing the board for PPK

    Thank you!

Reply Children
Related