Re: insight/262: couldnt establish connection to remote taret reply contains invalid hex digit 59

Re: insight/262: couldnt establish connection to remote taret reply contains invalid hex digit 59

[kseitz]

Synopsis: couldnt establish connection to remote taret reply contains invalid hex digit 59

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Wed Oct 13 20:04:25 2004
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Wed Oct 13 20:04:25 2004
State-Changed-Why:
    What is your target triple ("insight -v" or "gdb -v")?
    Any reason you are using 5.2? That's well over two years old now...
    
    Anyway, the error says "cannot connect to target board using :3333" Looks funny. Should be a hostname in there (if running on the same host, use "localhost").
    
    Of course, I didn't even know that there was a gdbserver for cygwin...

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=262

insight/262: couldnt establish connection to remote taret reply contains invalid hex digit 59

[davidgkatz]

>Number:         262
>Category:       insight
>Synopsis:       couldnt establish connection to remote taret reply contains invalid hex digit 59
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 13 19:53:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     davidgkatz@yahoo.com
>Release:        5.2
>Organization:
>Environment:
Windows -> Cygwin
>Description:
Went through special Cygwin user installation process.  opens .elf file but cannot establish connection.  msp430-gdbproxy connects connected to mpu but insight generates error: 

Couldn't establish connection to remote target Reply contains invalid hex digit 59.  GDB cannot connect to the target board using :3333 Verify that the board is securely connected and, if necesssary, modify the port settings with the debugger preferences.

I verified the port as 3333 and that it was set to Remote/TCP.  

msp430-gdbproxy output:

info:    msp430: Target device is a 'MSP430F149' (type 7)
notice:  msp430-gdbproxy.exe: waiting on TCP port 3333
notice:  msp430-gdbproxy.exe: connected
info:    msp430-gdbproxy.exe: debugger has terminated    connection
info:    msp430-gdbproxy.exe: will reopen the connection

The strangest thing is that the Run menu only contains the "Run R" option and a "Kill" option... what happened to my connect / disconnect options? 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: