Hi
I recently purchased olimex ARM-USB-OCD from sparkfun and having trouble.
Following is the log from gdb:
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
warning: Invalid remote reply: ?
I have latest openOCD (0.4.0) compiled on cygwin with ftd2xx driver. I have the latest driver from FTDI installed. My target is a custom ARM926EJ-s based board and it is detected properly by OpenOCD.
When I reset the target board I see following message in gdb:
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: ?
warning: Invalid remote reply: ?
warning: Invalid remote reply: Hc-1
warning: Invalid remote reply: qC
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: ?
warning: Invalid remote reply: ?
warning: Invalid remote reply: Hc-1
warning: Invalid remote reply: qC
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: ?
warning: Invalid remote reply: ?
warning: Invalid remote reply: Hc-1
warning: Invalid remote reply: qC
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: ?
warning: Invalid remote reply: ?
warning: Invalid remote reply: Hc-1
warning: Invalid remote reply: qC
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: qSupported
warning: Invalid remote reply: ?
warning: Invalid remote reply: ?
warning: Invalid remote reply: Hc-1
warning: Invalid remote reply: qC
I am pretty much out of options…please help to overcome this.
Thanks
Banks
edit: this was happening due to mismatch between telnet and gdb ports.
Thanks to freddiechopin.info for providing comprehensive distribution of OpenOCD and other drivers for windows platform.