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

Failed to start the PPK.

Hello,

I use PPK to measure the power consumption.

but I always get :  Failed to start the PPK.

I have measured it last week and it is work.

and this is nrf connect log:

2018-07-23T08:27:09.150Z INFO Application data folder: C:\Users\Lin\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2018-07-23T08:27:09.274Z INFO App initialized
2018-07-23T08:27:09.300Z DEBUG App pc-nrfconnect-ppk v2.0.0 official
2018-07-23T08:27:09.300Z DEBUG App path: C:\Users\Lin\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2018-07-23T08:27:09.300Z DEBUG nRFConnect 2.4.0 is supported by the app (^2.3.0)
2018-07-23T08:27:09.300Z DEBUG nRFConnect path: C:\Users\Lin\AppData\Local\Programs\nrfconnect\resources\app.asar
2018-07-23T08:27:09.300Z DEBUG HomeDir: C:\Users\Lin
2018-07-23T08:27:09.300Z DEBUG TmpDir: C:\Users\Lin\AppData\Local\Temp
2018-07-23T08:27:13.470Z INFO PPK opened
2018-07-23T08:27:13.471Z INFO Initializing the PPK
2018-07-23T08:27:14.176Z INFO Segger serial:  682116104
2018-07-23T08:27:14.176Z INFO Segger speed:  2000  kHz
2018-07-23T08:27:14.176Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Jul  4 2018 16:22:02
2018-07-23T08:27:20.178Z ERROR Failed to open RTT channel
2018-07-23T08:27:20.179Z DEBUG RTT open timed out
2018-07-23T08:27:20.185Z INFO PPK closed
2018-07-23T08:27:25.182Z ERROR Failed to start the PPK.
2018-07-23T08:27:25.182Z DEBUG 

  • Since you have used it before, but it's not working now, it seems to be a power issue. Please check the points below, and we can take it from there.


    * If the PPK doesn't light it's LED(s), then it might be due to erased firmware, or no power supplied. Check to see that the Power Select switch is set in DK-position.

    * Failed to open RTT channel means that there are no debug connection. If the PPK doesn't power up, then that makes sense. Try setting the DUT Select to External, and verify you have ~3V on the output pins. If so, the PPK should be powered, and the issue is related to the Segger J-Link connection.

    * Next to check is the COM switch (the small one in the middle of the board), and verify it's in DK position. 

    Edit: Also, try and plug a USB directly in to the PPK, and see if that changes anything with regards to power. If that works, you should also try an external debugger (can be a DK with a 10pin jtag cable)

  • Hi ,all

    I also encountered this fail .

    What I had to do is to born PPK firmware once again.

    Steps to reproduce :

        1. Try to open DK com port ( PPK shield should be disconnected from DK) using Power Profiler application.

        2. Pop up window with the notification will appear on the PP screen:

             Would you like to program development kit with the required firmware ?

        3. Connect PPK shield to the DK and confirm YES.

        4. After that procedure PPK shield will be reanimated (Led will be on) and ready

    for use. Just press START in power profiler application.

    Note : Try not forget to disconnect PPK from the DK during DK's firmware update via

    debugger.

  • It seems to be a bug with the software, i am using it on ubuntu18.04 and this occurs frequently. it may connect sometimes and give the readings properly but in most cases it gives the error "Failed to read PPK metadata".

    so in every session, i am forced to erase the ppk and start again (even this method doesn't guarantee above 70% success ).i am using v2.6.1

  • Does this happen on the Power Profiler software on windows? Seems to run fine over here.

Related