From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17326 invoked by alias); 19 Feb 2003 19:22:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 17301 invoked from network); 19 Feb 2003 19:22:57 -0000 Received: from unknown (HELO mx1.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 19 Feb 2003 19:22:57 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h1JJMvK06139; Wed, 19 Feb 2003 14:22:57 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h1JJMva03940; Wed, 19 Feb 2003 14:22:57 -0500 Received: from deneb.localdomain (msalter.cipe.redhat.com [10.0.0.36]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h1JJMuO00367; Wed, 19 Feb 2003 14:22:56 -0500 Received: by deneb.localdomain (Postfix, from userid 500) id 962AE78A6D; Wed, 19 Feb 2003 14:22:55 -0500 (EST) From: Mark Salter To: jifl@eCosCentric.com Cc: gary.thomas@mind.be, qqi@theworld.com, Pierre.Habraken@imag.fr, gdb@sources.redhat.com, ecos-discuss@sources.redhat.com In-reply-to: <3E53C60E.6000305@eCosCentric.com> (message from Jonathan Larmour on Wed, 19 Feb 2003 17:59:42 +0000) Subject: Re: [ECOS] Can't connect to remote Evaluator 7T References: <20030219174138.A6E4578A6D@deneb.localdomain> <1045676870.18484.6026.camel@hermes.chez-thomas.org> <3E53C60E.6000305@eCosCentric.com> Message-Id: <20030219192255.962AE78A6D@deneb.localdomain> Date: Wed, 19 Feb 2003 19:22:00 -0000 X-SW-Source: 2003-02/txt/msg00370.txt.bz2 >>>>> Jonathan Larmour writes: > Gary D. Thomas wrote: >> On Wed, 2003-02-19 at 10:41, Mark Salter wrote: >> >>>>>>>> Quality Quorum writes: >>> >>>> On Wed, 19 Feb 2003, Mark Salter wrote: >>> >>>>> Not only that, from my experiments with a cable tap, nothing is going out >>>>> of the PC to the target. The write(2) succeeds, but nothing is sent on >>>>> the wire. Closing and reopening the serial device usually clears up the >>>>> problem. >>> >>>> Connect through minicom and make sure that target responds with gdb packet >>>> when you send enter. My $0.02. >>> >>> The target is sitting at the RedBoot prompt. I physically tapped the >>> serial line and watched from another host. The packet from GDB never >>> makes it to the wire. If I startup minicom on the host with GDB still >>> trying to connect, then data starts flowing on the wire again although >>> GDB and minicom are fighting over the read data. >>> >> >> >> Maybe it's a handshake issue? Perhaps GDB is leaving or setting >> the port into a handshake mode (that may not work) and minicom does >> not. Or some such combination. Checking with "stty > from another window while both applications are running might >> give some useful insights. > As I said earlier :-). I think making sure it's off using minicom would be > more reliable (from user error) though. % stty -a ; eol2 = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5; -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke Starting minicom does not reliably get it going again. If I wait for GDB to timeout and retry a target command, it usually works. The act of closing/ opening the tty device seems to get it unclogged. --Mark