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

Not possible to use PPK while debugging

I am trying to measure the power consumption of a PCA10040 board while debugging, using the PPK. I am using the setup shown here: "Measuring current on nRF5 DK while debugging" with the slight change that I am using another PCA10040 board as JLink probe (as the nRF Connect v2.4.0 does not yet support a "real" JLink probe).

In detail, my setup is as follows. One PCA10040 board (naming this “DK A”) is connected with USB. The PPK is piggyback on DK A.

Another PCA10040 (“DK B”) is connected to the PPK with a 10 pin cable (Debug out on DK B is connected to Debug in on the PPK).

The COM SW3 is set to EXT.

SEGGER JLink version is V632i.

 

Steps to reproduce this problem

  1. Start a debugging session with IAR to DK A
  2. Start nRF Connect v2.4.0 Power Profiler and try to connect to DK B. This error message is given ("JLINKARM_DLL_ERROR (ffffff9a)"):

 

Another way to reproduce this

  1. Start nRF Connect v2.4.0 Power Profiler and to connect to DK B
  2. Start a debugging session with IAR to DK A
  3. This will kick the Power Profiler app out (the measurement stops). After this, it is impossible to connect to DK A with the app, showing the error message of step 2 above
  • This was working in the beginning, but SEGGER has done some changes, breaking this feature for us. This means that the state of the debug lines to/from the PPK is wrong. The issue has been reported to SEGGER, and as soon as they'll update per our request this will not longer be a problem. 

    For now, the only viable thing to do is to not use the PPK at all if you need to do J-Link requests like flash, debug, RTT etc to the application board. And as a side note, CTRL+R will refresh the PPK app, making it faster to start it over :) 

Related