Hi,
I've originally asked on connecting to the Segger J-Link Pro over TCP/IP on this thread
-timeout parameter to JLinkGDBServer seems not working
but the subject just dealt with my misunderstanding on GDBServer -timeout parameter. Now may be I have bigger misunderstanding on remote debugging with Segger J-Link Pro.
So we got this Segger J-Link Pro, with Ethernet connection. It is connected to target, and it is connected to network, and configured with IP 10.69.4.251. It's up and running, as seems
verified with local connection
Now I'm connecting (trying to) remotely to it, and I'm having issues that JLinkGDBServer, or JLinkExe, refuse to connect to it, even though I seems can access it using other tools.
I can connect to it using my browser - port 80 - and I can check it settings, network status, etc.. power on, off target voltage, etc.
When I try with JLinkGDBServer:
/opt/SEGGER/JLink/JLinkGDBServer -device VF6xx_M4 -IF JTAG -select ip=10.69.4.251, that just exists saying failed to connect. It's not even waiting much, seems tries way too fast (I thought -timeout would help ...wrong).
Same with JLinkExe:
J-Link>ip 10.69.4.251
Connecting to 10.69.4.251
Connecting to J-Link via IP...FAILED: Can not connect to J-Link via TCP/IP (10.69.4.251, port 19020)
But, I can connect to that IP & port using other tools just fine, e.g. netcat:
nc -v 10.69.4.251 19020
Ncat: Version 7.40 ( nmap.org/ncat )
Ncat: Connected to 10.69.4.251:19020.
�)�/J-Link Pro V4 compiled 15:44:26 on Jul 10 2017
As you can see connection is established and I get the J-Link Pro trace.
So what is the story with the JLinkGDBServer and JLinExe ? Why do they refuse to connect here? ......
They both only seems like when I'm connecting to localhost, with JLinkRemoteServer running locally and accessing my local USB JLink. Which is of course totally useless for me in this case ..
Please help? ?(
I've originally asked on connecting to the Segger J-Link Pro over TCP/IP on this thread
-timeout parameter to JLinkGDBServer seems not working
but the subject just dealt with my misunderstanding on GDBServer -timeout parameter. Now may be I have bigger misunderstanding on remote debugging with Segger J-Link Pro.
So we got this Segger J-Link Pro, with Ethernet connection. It is connected to target, and it is connected to network, and configured with IP 10.69.4.251. It's up and running, as seems
verified with local connection
Now I'm connecting (trying to) remotely to it, and I'm having issues that JLinkGDBServer, or JLinkExe, refuse to connect to it, even though I seems can access it using other tools.
I can connect to it using my browser - port 80 - and I can check it settings, network status, etc.. power on, off target voltage, etc.
When I try with JLinkGDBServer:
/opt/SEGGER/JLink/JLinkGDBServer -device VF6xx_M4 -IF JTAG -select ip=10.69.4.251, that just exists saying failed to connect. It's not even waiting much, seems tries way too fast (I thought -timeout would help ...wrong).
Same with JLinkExe:
J-Link>ip 10.69.4.251
Connecting to 10.69.4.251
Connecting to J-Link via IP...FAILED: Can not connect to J-Link via TCP/IP (10.69.4.251, port 19020)
But, I can connect to that IP & port using other tools just fine, e.g. netcat:
nc -v 10.69.4.251 19020
Ncat: Version 7.40 ( nmap.org/ncat )
Ncat: Connected to 10.69.4.251:19020.
�)�/J-Link Pro V4 compiled 15:44:26 on Jul 10 2017
As you can see connection is established and I get the J-Link Pro trace.
So what is the story with the JLinkGDBServer and JLinExe ? Why do they refuse to connect here? ......
They both only seems like when I'm connecting to localhost, with JLinkRemoteServer running locally and accessing my local USB JLink. Which is of course totally useless for me in this case ..
Please help? ?(