Newer versions of nrfjprog crash when communication fails

[jm_laird]

Testing on windows 7 SP1 64-bit with 32-bit nrfjprog 10.5.0 JLinkARM.dll version 6.54c. I do not know the version I had previously but with the old version if you ran an nrfjprog command with no device connected, you would get an error output whereas now the nrfjprog utility crashes. The same thing happens if you have a device connected but for whatever reason it isn't responding to the JLink.

[bjorn-spockeli]

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

[jm_laird]

Hi Bjørn,

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

Thanks,
Jamie

[bjorn-spockeli]

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

[jm_laird]

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

[bjorn-spockeli]

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?