Not possible to use PPK while debugging

RE: Not possible to use PPK while debugging

wlgrd — Wed, 29 Aug 2018 08:37:05 GMT

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 :)

RE: Not possible to use PPK while debugging

gnf — Thu, 23 Aug 2018 13:37:14 GMT

Yes, I know that the measurements will be wrong when measuring at the same time as debugging. What I want to solve is this workflow:

- Activate the measurement in the app RF Connect Power Profiler

- Run the debugger (yes, the current consumption is wrong here but I can still do my usual cycle of compile/debug/recompile/debug/... before finding a state where my code actually seems to work)

- When the code seems to be working, stop the debugger (or even remove the SWD 9 pin cable) to run the device in a "release" state, with realistic current measurements

- When I need to reflash the device or start a compile/debug cycle again, I just reattach the SWD cable (although I have seen that it is enough to just stop the debugger in EWARM and keep the SWD cable connected. Most of the time this gives me somewhat useful measurements)

But... My workflow right now looks like this, because of the above issue:

- Activate the measurement

- Run the debugger... But this crashes the Power Profiler app!

- Stop the debugger

- Close the Power Profiler app and open it again. Find the correct serial port. Start the measurement.... .... You see where this is going?

Edit: So my point is, I am not looking for a solution to get good measurements while debugging. I just want to avoid having to close and reopen the Power Profiler app all the time just because the JLink crashes.

RE: Not possible to use PPK while debugging

Bjørn Kvaale — Thu, 23 Aug 2018 08:43:10 GMT

It seems that this is an issue with a segger update. According to another colleague, it is not such a great idea to debug & measure the current consumption at the same time, as you will receive around 4 mA no matter what. This is because the debugger will turn on all regulators & clocks on the chip.

RE: Not possible to use PPK while debugging

Bjørn Kvaale — Thu, 09 Aug 2018 13:42:21 GMT

Hi gnf,

I just tested this with the setup you provided & I also received the same error code:

I will mention this internally to the developer.

RE: Not possible to use PPK while debugging with IAR

gnf — Tue, 07 Aug 2018 11:28:27 GMT

I think I found another issue reported 6 months ago regarding the same thing:

devzone.nordicsemi.com/.../power-profiler-kit-ppk-with-dk-rtt-debug-out-not-working

RE: Not possible to use PPK while debugging with IAR

gnf — Tue, 07 Aug 2018 10:51:28 GMT

A third way of reproducing the problem (which suggests that IAR has nothing to do with this):

6. Start nRF Connect v2.4.0 Power Profiler and to connect to DK B

7. Connect Segger RTTViewer to DK A

8. 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