PPK: Failed to write input to target

[crides]

I bought a PPK (not the PPK2) a while ago, and it's been working fine. However, recently it stopped working. I'm using a JLink EDU mini, and the power profiler app in nrfconnect can flash the firmware to the PPK, but shows that it can't start the PPK. Digging in a bit, and it turns out that the PPK can't be written to. The same thing happens with JLinkRTTViewer, but this doesn't occur when using Zephyr projects with RTT console enabled. Using nrfconnect 3.11.0 on Arch Linux, with JLink software version being 7.64b

Edit: With JLinkRTTViewer, the board displays:

VERSION ppk-fw-2.1.0 CAL:1 R1:508.196 R2:30.202 R3:1.793 Board ID 1A96253E
Refs VDD: 3296 HI: 20000 LO: 44270

[Simonr]

Hi

Can you try using the nRF command line tools to do a recovery or a full erase of the PPK. Then you should get prompted to flash the Power Profiler firmware the next time you open the device in the Pwoer Profiler app.

nrfjprog --recover or nrfjprog --eraseall should do the trick. If you have issues, try doing the nrfjprog commands with a --log at the end and upload the log here, and I'll take a look.

Best regards,

Simon

[crides]

I tried to erase and let the power profiler reflash, same result. I don't think I can use `nrfjprog` for writing to the RTT console. When I modified the app to print out the error, I get:

```

13:22:36.980

Initializing the PPK

13:22:36.981

SEGGER serial number: 000801030890

13:22:36.981

SEGGER version: J-Link EDU Mini V1 compiled Mar 3 2022 10:17:12

13:22:38.693

Failed to start PPK

13:22:38.693

Unhandled error. ('PPK command failed: {"error_code":9,"message":"JLINKARM_DLL_ERROR","origin":"Error when running nrfdl_rtt_write"}')

13:22:38.834

PPK opened

```

[Simonr]

Hi

What version of the SEGGER software are you running exactly? We're looking into this, but are not able to find the correct version to make sense of this error message.

Best regards,

Simon