From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17443 invoked by alias); 19 Feb 2003 17:59:45 -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 17421 invoked from network); 19 Feb 2003 17:59:44 -0000 Received: from unknown (HELO jifvik.dyndns.org) (62.253.130.87) by 172.16.49.205 with SMTP; 19 Feb 2003 17:59:44 -0000 Received: from eCosCentric.com (garibaldi.jifvik.org [172.31.1.2]) by jifvik.dyndns.org (Postfix) with ESMTP id 03117383DB; Wed, 19 Feb 2003 17:59:43 +0000 (GMT) Message-ID: <3E53C60E.6000305@eCosCentric.com> Date: Wed, 19 Feb 2003 17:59:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: "Gary D. Thomas" Cc: Mark Salter , qqi@theworld.com, Pierre.Habraken@imag.fr, gdb@sources.redhat.com, eCos Discussion Subject: Re: [ECOS] Can't connect to remote Evaluator 7T References: <20030219174138.A6E4578A6D@deneb.localdomain> <1045676870.18484.6026.camel@hermes.chez-thomas.org> In-Reply-To: <1045676870.18484.6026.camel@hermes.chez-thomas.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00364.txt.bz2 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. Here's how to do it in minicom: CTRL-A Z O select Serial port setup Make sure both hardware and software flow control are off, and the other serial settings are right (38400 8-N-1). Press return Choose Exit Ctrl-A Z q select yes You could also force Redboot into GDB mode by typing a $. You should lose the prompt then. Typing something like: +$k#6b should make it react and then return to the command prompt. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine