Hello, I have an issue to use GDB server in the J-Link Pro.
I'm using Atollic True Studio 9.0.1 to connect to J-Link Pro
I able to use debugger when use local GDB server and USB connection or using j-link GDB server APP on my PC and TCP connection in it.
But, when I try to use ETHERNET connection:
I able to connect to J-Link via Commander app:
J-Link>ipaddr
DHCP assigned network configuration
IP-Addr: 192.168.111.218
Subnetmask: 255.255.255.0
J-Link>conf
USB-Address: 0
Enum. type: Real-SN is used
KS-Power: Off (Default)
DHCP assigned network configuration
IP-Addr: 192.168.111.218
Subnetmask: 255.255.255.0
Gateway-Addr: 192.168.111.1
DNS-Addr: 192.168.111.16
MAC-Addr: 00:22:C7:07:10:AF (Default)
J-Link>f
Firmware: J-Link Pro V4 compiled Apr 20 2018 16:46:30
Hardware: V4.00
The Output inside IDE:
Failed to execute MI command:
target extended-remote 192.168.111.218:19020
Error message from debugger back end:
Bogus trace status reply from target: timeout
The output of arb-attolic-eabi-gdb.exe:
(gdb) target remote 192.168.111.218:19020
Remote debugging using 192.168.111.218:19020
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout
(gdb)
Should I add some additional initialization or it is same issue as described in:
J-Link GDB Server - Connection closed! ??
Or I just miss some page in user manual?
I'm using Atollic True Studio 9.0.1 to connect to J-Link Pro
I able to use debugger when use local GDB server and USB connection or using j-link GDB server APP on my PC and TCP connection in it.
But, when I try to use ETHERNET connection:
I able to connect to J-Link via Commander app:
J-Link>ipaddr
DHCP assigned network configuration
IP-Addr: 192.168.111.218
Subnetmask: 255.255.255.0
J-Link>conf
USB-Address: 0
Enum. type: Real-SN is used
KS-Power: Off (Default)
DHCP assigned network configuration
IP-Addr: 192.168.111.218
Subnetmask: 255.255.255.0
Gateway-Addr: 192.168.111.1
DNS-Addr: 192.168.111.16
MAC-Addr: 00:22:C7:07:10:AF (Default)
J-Link>f
Firmware: J-Link Pro V4 compiled Apr 20 2018 16:46:30
Hardware: V4.00
The Output inside IDE:
Failed to execute MI command:
target extended-remote 192.168.111.218:19020
Error message from debugger back end:
Bogus trace status reply from target: timeout
The output of arb-attolic-eabi-gdb.exe:
(gdb) target remote 192.168.111.218:19020
Remote debugging using 192.168.111.218:19020
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout
(gdb)
Should I add some additional initialization or it is same issue as described in:
J-Link GDB Server - Connection closed! ??
Or I just miss some page in user manual?
The post was edited 1 time, last by Aseris ().