Hello,
Few days ago I bought sevral DK's(nrf52833 and nrf52840).
For the first shot I was not able to program them or event make a connection over jlink. I'm using WSL2 and Ubuntu22.04 and I'm forwarding ports using 'usbipd' tool.
I belive that there is not a problem with WSL2 because I have try with native Ubuntu22.04 as well.
I installed the newest version of nrfjprog from here:
https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download
Ubuntu is up-to-date as well.
After few tries nrf52833-dk started works. I have no idea why, it started and still works fine over WSL2 and native ubutnu.
But nrf52840-dk still don't want to cooperate. I'm not able to program using jlink...
The difference between those DK's is that nrf52840-dk jlink is based on Nordic chip.
Jlink firmware version is up-to-date. To verify, I utilized "J-Link Configuratio-v7.80c".
Output was always the same for nrf52833-dk and for nrf52840-dk. But, like I said, after few attemps nrf52833-dk started works, nrf52840-dk did not.
# nrfjprog -r
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 45272 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
# nrfjprog -r --log
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 45285 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
Under Windows 10 everything works perfectly.
