Trouble using nrfjprog

RE: Trouble using nrfjprog

wade smith — Thu, 09 Nov 2023 17:16:56 GMT

Sorry I did not close the tread; Vidar answered the question.

RE: Trouble using nrfjprog

wade smith — Thu, 09 Nov 2023 17:16:23 GMT

It turns out that the SEGGER probe was counterfeit; bought it on Amazon. Annoying that there are people out there stealing IP from companies.

RE: Trouble using nrfjprog

wade smith — Mon, 31 Jul 2023 21:33:41 GMT

Thank you Vidar for figuring this out. I will check with SEGGER- I bought the probe from them.

RE: Trouble using nrfjprog

Vidar Berg — Mon, 31 Jul 2023 08:53:18 GMT

[2023-Jul-28 09:53:46] [trace] [ JLink] - JLINK_GetSN()
[2023-Jul-28 09:53:46] [trace] [ JLink] - - 0.007ms returns -1

Thank you for providing the log file. The issue arises because the debugger's serial number is set to 4294967295, which equals 0xFFFFFFFF. This corresponds to "-1" when it is interpreted as a two's complement value by the J-Link library, and negative values are treated as errors. I guess SES must be ignoring this error.

Please contact Segger support if this is a genuine debug probe. The serial number is supposed to be set during production.

RE: Trouble using nrfjprog

wade smith — Fri, 28 Jul 2023 16:55:20 GMT

Same trouble. Attached is the log file. Thanksdevzone.nordicsemi.com/.../0458.log.log

RE: Trouble using nrfjprog

Vidar Berg — Mon, 17 Jul 2023 11:54:05 GMT

Hello,

Could you please try to re-install the command line tools package at https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download with the bundled Jlink drivers (v7.80c)? I don't see any reason why it shouldn't work with 7.88l, but v7.80c is the version nrfjprog has been tested and verified with.

If you still encounter the same error with this version, please run "$ nrfjprog --recover --log" and post the log file here.

Thanks,

Vidar