Attachments (2) Download All
Nordic Case Info
  • Case ID: 241173
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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.

Parents
  • 0

    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

  • 0 in reply to bjorn-spockeli

    Hi Bjørn,

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

    Thanks,
    Jamie

  • 0 in reply to bjorn-spockeli

    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

  • 0 in reply to jm_laird

    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?

  • 0 in reply to bjorn-spockeli

    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.

    Fullscreen 3286.log.log Download
    "

    Thanks,
    Jamie

  • 0 in reply to jm_laird

    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 

  • +1 in reply to bjorn-spockeli

    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?

Reply
  • +1 in reply to bjorn-spockeli

    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?

Children
Terms of service