From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18224 invoked by alias); 13 Oct 2004 19:53:01 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 18203 invoked by uid 71); 13 Oct 2004 19:53:01 -0000 Resent-Date: 13 Oct 2004 19:53:01 -0000 Resent-Message-ID: <20041013195301.18201.qmail@sourceware.org> Resent-From: insight-gnats@sources.redhat.com (GNATS Filer) Resent-To: nobody@sources.redhat.com Resent-Cc: insight-prs@sources.redhat.com Resent-Reply-To: insight-gnats@sources.redhat.com, davidgkatz@yahoo.com Received: (qmail 15435 invoked by uid 48); 13 Oct 2004 19:47:47 -0000 Message-Id: <20041013194747.15434.qmail@sourceware.org> Date: Wed, 13 Oct 2004 19:53:00 -0000 From: davidgkatz@yahoo.com Reply-To: davidgkatz@yahoo.com To: insight-gnats@sources.redhat.com X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: insight/262: couldnt establish connection to remote taret reply contains invalid hex digit 59 X-SW-Source: 2004-q4/txt/msg00000.txt.bz2 List-Id: >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: