I'm having trouble with the J-Link GDB Server. The problem is that the connection to the GDB client closes immediately after the connection is established with the server.
I'm running J-Link GDB Server on a Windows 7 64-bit PC. I have a SAM-ICE (J-Link ARM) v8.00, connected via JTAG to our board that has an AT91SAM9G10. The J-Link is using firmware "J-Link ARM V8 compiled Jan 31 2011 18:34:52". The GDB client version is 7.0.1.
J-Link GDB Server V4.24b Log Window:
SEGGER J-Link GDB Server V4.24b
JLinkARM.dll V4.24b (DLL compiled Feb 22 2011 20:47:17)
Listening on TCP/IP port 2331
J-Link connected
Firmware: J-Link ARM V8 compiled Jan 31 2011 18:34:52
Hardware: V8.00
S/N: 28004705
OEM: SAM-ICE
Feature(s): RDI
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x0792603F (ARM9)
SAM-ICE found !
Connected to 10.128.0.248
SAM-ICE found !
Connection closed!
GDB client console output:
target remote 10.128.1.92:2331
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
I actually had everything working when I was evaluating GDB Server about two weeks ago. At this time I was using GDB Server v4.20h and the firmware of the J-Link was an older revision. My settings on the client side haven't changed since then, but now it doesn't work. I'm wondering if updating J-Link's firmware caused the problem.
I've also tried different combinations of GDB Server and ARM toolchains without success:
Our Timesys toolchain (gcc v4.4.3, gdb v7.0.1).
yagarto-bu-2.21_gcc-4.5.2-c-c++_nl-1.19.0_gdb-7.2_eabi_20101223 (connected to j-link gdb-server locally)
yagarto-bu-2.20.1_gcc-4.5.1-c-c++_nl-1.18.0_gdb-7.1_eabi_20100813 (connected to j-link gdb-server locally)
GDB Server 4.20h
GDB Server 4.22f
GDB Server 4.24b
According to the following thread, arm-none-eabi-gdb.exe and j-link gdb-server 4.22f is working:
JLinkGDBServer and gdb (arm-none-eabi-gdb): Remote 'g' packet reply is too long:
But not for me.
I've also tried different JTAG speeds without success.
Suggestions are greatly appreciated! Thanks!
I'm running J-Link GDB Server on a Windows 7 64-bit PC. I have a SAM-ICE (J-Link ARM) v8.00, connected via JTAG to our board that has an AT91SAM9G10. The J-Link is using firmware "J-Link ARM V8 compiled Jan 31 2011 18:34:52". The GDB client version is 7.0.1.
J-Link GDB Server V4.24b Log Window:
SEGGER J-Link GDB Server V4.24b
JLinkARM.dll V4.24b (DLL compiled Feb 22 2011 20:47:17)
Listening on TCP/IP port 2331
J-Link connected
Firmware: J-Link ARM V8 compiled Jan 31 2011 18:34:52
Hardware: V8.00
S/N: 28004705
OEM: SAM-ICE
Feature(s): RDI
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x0792603F (ARM9)
SAM-ICE found !
Connected to 10.128.0.248
SAM-ICE found !
Connection closed!
GDB client console output:
target remote 10.128.1.92:2331
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
I actually had everything working when I was evaluating GDB Server about two weeks ago. At this time I was using GDB Server v4.20h and the firmware of the J-Link was an older revision. My settings on the client side haven't changed since then, but now it doesn't work. I'm wondering if updating J-Link's firmware caused the problem.
I've also tried different combinations of GDB Server and ARM toolchains without success:
Our Timesys toolchain (gcc v4.4.3, gdb v7.0.1).
yagarto-bu-2.21_gcc-4.5.2-c-c++_nl-1.19.0_gdb-7.2_eabi_20101223 (connected to j-link gdb-server locally)
yagarto-bu-2.20.1_gcc-4.5.1-c-c++_nl-1.18.0_gdb-7.1_eabi_20100813 (connected to j-link gdb-server locally)
GDB Server 4.20h
GDB Server 4.22f
GDB Server 4.24b
According to the following thread, arm-none-eabi-gdb.exe and j-link gdb-server 4.22f is working:
JLinkGDBServer and gdb (arm-none-eabi-gdb): Remote 'g' packet reply is too long:
But not for me.
I've also tried different JTAG speeds without success.
Suggestions are greatly appreciated! Thanks!