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

Failed to start PPK

Hi, 

I have nrF52840 DK rev 2.0.1

switch to VDD, Default, SB40 is cut (confirmed by multimeter)

I have the PPK rev 1.1.1

switch DUT to DK

switch Power to DK

I can run the program with segger IDE (and only with PPK as i cut SB40)

nrfConnect is 3.6.1

OS : Windows 10

When i run Power Profiler (3.1.0) i can't connect the device.

Here is the log file : 

2021-02-16T15:43:10.666Z INFO Application data folder: C:\Users\XXXXXX\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2021-02-16T15:43:10.756Z DEBUG App pc-nrfconnect-ppk v3.1.0 official
2021-02-16T15:43:10.756Z DEBUG App path: C:\Users\XXXXXX\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2021-02-16T15:43:10.756Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.1)
2021-02-16T15:43:10.756Z DEBUG nRFConnect path: C:\Users\XXXXXX\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-02-16T15:43:10.756Z DEBUG HomeDir: C:\Users\XXXXXX
2021-02-16T15:43:10.756Z DEBUG TmpDir: C:\Users\XXXXXX\AppData\Local\Temp
2021-02-16T15:43:11.669Z VERBOSE Could not fetch serial number for serial port at COM1
2021-02-16T15:43:13.929Z INFO Validating firmware for device with s/n 000683XXXXXX
2021-02-16T15:43:14.472Z INFO Opening device with s/n 000683XXXXXX
2021-02-16T15:43:14.565Z INFO Initializing the PPK
2021-02-16T15:43:14.979Z INFO SEGGER serial number: 683XXXXXX
2021-02-16T15:43:14.979Z INFO SEGGER speed: 2000 kHz
2021-02-16T15:43:14.979Z INFO SEGGER version: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00
2021-02-16T15:43:20.982Z ERROR Failed to start PPK
2021-02-16T15:43:20.983Z DEBUG Timed out in 6000 ms.
2021-02-16T15:43:21.065Z INFO PPK opened
2021-02-16T15:43:25.476Z ERROR Error while probing devices: Error occured when get serial numbers. Errorcode: Could not execute the function due to too many calls in line (0xe)

Parents Reply
  • Hi there,

    I have some additional questions, and would appreciate if you answer them:

    Did the Power Profiler App ask to update the FW on the PPK when you first started? Our suspicion is that it might have flashed the DK instead of the PPK, as our earlier discussion indicate that the SW has some issues detecting the PPK. 

    Do you have an external J-link Debugger? Could you try to connect the debugger to the PPK as shown here? That way, we could ensure that the SW doesn't flash the wrong board. Note that the SW3 should be set to EXT and that the USB should be connected directly to the PPK. 

    Thank you

    regards

    Jared 

Children
Related