I am attempting to fix a problem with a system that, up until today, was working fine (not perfectly, but fine).
My system is configured as such:
I am developing for an ARM target using Linux build tools running under WSL. WSL has no ability to use or see USB devices. However, the Segger tools run fine under WSL.
I have my J-Link Ultra+ connected via USB to my machine. I launch J-Link Remote Server with the "Use LAN" option selected. The Remote Server indicates that it detects my J-Link.
Next, I attempt to launch a debug session. I have configured my launch to invoke JLinkGDBServer in WSL with the "-select ip=localhost" option (among the other, more standard options). When the GDB server is launched, I see that the Remote Server recognizes a connection. However, GDB is unable to connect to the J-Link itself. The exact output from the J-Link GDB Server is:
Display All
Note, that while this snippet shows V6.56a, I have tried this with the most up-to-date segger tools on both ends, and it doesn't fix the problem. This capture was from an attempt at downgrading to a version that used to work.
One last thing to note: it seems that when the GDB session fails, the connection does not detach properly from JLinkRemoteServer. This happens with all versions of the tools that I tried.
Can anyone provide suggestions on how to debug this problem?
My system is configured as such:
I am developing for an ARM target using Linux build tools running under WSL. WSL has no ability to use or see USB devices. However, the Segger tools run fine under WSL.
I have my J-Link Ultra+ connected via USB to my machine. I launch J-Link Remote Server with the "Use LAN" option selected. The Remote Server indicates that it detects my J-Link.
Next, I attempt to launch a debug session. I have configured my launch to invoke JLinkGDBServer in WSL with the "-select ip=localhost" option (among the other, more standard options). When the GDB server is launched, I see that the Remote Server recognizes a connection. However, GDB is unable to connect to the J-Link itself. The exact output from the J-Link GDB Server is:
Source Code
- SEGGER J-Link GDB Server V6.56a Command Line Version
- JLinkARM.dll V6.56a (DLL compiled Nov 25 2019 16:58:26)
- Command line: -if swd -port 50000 -swoport 50001 -telnetport 50002 -device STM32F756IG -select ip=localhost
- -----GDB Server start settings-----
- GDBInit file: none
- GDB Server Listening port: 50000
- SWO raw output listening port: 50001
- Terminal I/O port: 50002
- Accept remote connection: yes
- Generate logfile: off
- Verify download: off
- Init regs on start: off
- Silent mode: off
- Single run mode: off
- Target connection timeout: 0 ms
- ------J-Link related settings------
- J-Link Host interface: IP
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: STM32F756IG
- Target interface: SWD
- Target interface speed: 4000kHz
- Target endian: little
- Connecting to J-Link...
- Connecting to J-Link failed. Connected correctly?
- GDBServer will be closed...
- Shutting down...
- Could not connect to J-Link.
One last thing to note: it seems that when the GDB session fails, the connection does not detach properly from JLinkRemoteServer. This happens with all versions of the tools that I tried.
Can anyone provide suggestions on how to debug this problem?