Newer versions of nrfjprog crash when communication fails

RE: Newer versions of nrfjprog crash when communication fails

jm_laird — Thu, 20 Feb 2020 07:30:30 GMT

Hi Bjørn,

Sorry, I should have closed the ticket earlier, I can confirm 10.6.0 fixes the issue.

Thanks,
Jamie

RE: Newer versions of nrfjprog crash when communication fails

bjorn-spockeli — Wed, 19 Feb 2020 13:17:57 GMT

Reply from PC tools team:

This is a known issue with 10.5.0, a failure to read an access port register triggers a series of recursive dp aborts. The user should get a better error message in 10.6.0. Could you have him retry with 10.6.0 and send us the new log?

RE: Newer versions of nrfjprog crash when communication fails

bjorn-spockeli — Tue, 17 Dec 2019 10:35:37 GMT

Hi Jami, thanks for the logs. I have created an issue in our internal bug tracking database and the logs have been passed on to the PC tools team. Will let you know when they have looked into it.

Best regards

Bjørn

RE: Newer versions of nrfjprog crash when communication fails

jm_laird — Mon, 16 Dec 2019 13:56:16 GMT

Hi Bjørn,

Correct, here I have attached a log from a previous version of nrfjprog whereby it emits this error and does not crash: "ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.devzone.nordicsemi.com/.../3286.log.log"

Thanks,
Jamie

RE: Newer versions of nrfjprog crash when communication fails

bjorn-spockeli — Mon, 16 Dec 2019 13:53:52 GMT

Thank you. So this issue happens when you issue a nrfjprog command and there is no device connected to the jlink probe or if the device connected to the Jlink probe is not responding?

RE: Newer versions of nrfjprog crash when communication fails

jm_laird — Mon, 16 Dec 2019 13:24:33 GMT

devzone.nordicsemi.com/.../5460.log.log

Hi Bjørn,

Captured and uploaded, I think this shows clearly what the error is, I had to stop the first try as it didn't crash and the log filesize kept growing over 60MB... So I tried again for a much shorter time and ended up with a 3MB log file which I've manually truncated.

Thanks,
Jamie

RE: Newer versions of nrfjprog crash when communication fails

bjorn-spockeli — Mon, 16 Dec 2019 13:17:57 GMT

Hi Jamie,

Sorry, I mixed up nrfutil and nrfjprog. There is no verbosity option for nrfjprog so you only need to capture a log, this is done by appending the --log option without passing a log file name. The log file will be log.log and will be placed in the same folder where you called nrfjprog from.

Best regards

Bjørn

RE: Newer versions of nrfjprog crash when communication fails

jm_laird — Mon, 16 Dec 2019 12:28:19 GMT

Hi Bjørn,

Have tried adding -v, -vvvv and -log out.log separately and all of them give invalid argument errors.

Thanks,
Jamie

RE: Newer versions of nrfjprog crash when communication fails

bjorn-spockeli — Mon, 16 Dec 2019 09:55:35 GMT

Hi Jamie,

can you use the -vvvv and -log option to capture a log file when this issue occurs? Then I can pass this on to the PC tools team.

Best regards

Bjørn