Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Gary D. Thomas" <gary.thomas@mind.be>
To: Mark Salter <msalter@redhat.com>
Cc: qqi@theworld.com, jifl@eCosCentric.com, Pierre.Habraken@imag.fr,
	gdb@sources.redhat.com,
	eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Can't connect to remote Evaluator 7T
Date: Wed, 19 Feb 2003 17:47:00 -0000	[thread overview]
Message-ID: <1045676870.18484.6026.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20030219174138.A6E4578A6D@deneb.localdomain>

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 </dev/XXX"
from another window while both applications are running might
give some useful insights.

-- 
.--------------------------------------------------------.
|       Mind: Embedded Linux and eCos Development        |
|--------------------------------------------------------|
| Gary Thomas              email:  gary.thomas@mind.be   |
| Mind ( http://mind.be )  tel:    +1 (970) 229-1963     |
| gpg: http://www.chez-thomas.org/gary/gpg_key.asc       |
'--------------------------------------------------------'


  reply	other threads:[~2003-02-19 17:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 14:59 Pierre Habraken
2003-02-19 15:30 ` [ECOS] " Jonathan Larmour
2003-02-19 15:59   ` Pierre Habraken
2003-02-19 16:32     ` Jonathan Larmour
2003-02-19 17:14       ` Mark Salter
2003-02-19 17:35         ` Quality Quorum
2003-02-19 17:41           ` Mark Salter
2003-02-19 17:47             ` Gary D. Thomas [this message]
2003-02-19 17:59               ` Jonathan Larmour
2003-02-19 19:22                 ` Mark Salter
2003-02-20 14:27                   ` Pierre Habraken
2003-02-20 14:33                     ` Gary D. Thomas
2003-02-20 14:59                       ` Pierre Habraken
2003-02-21  8:06                         ` Pierre Habraken
2003-02-21 15:14                           ` Gary D. Thomas
2003-02-20 14:35                     ` Mark Salter
2003-02-20 14:38                     ` Andrew Lunn
2003-02-19 16:44     ` Mark Salter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1045676870.18484.6026.camel@hermes.chez-thomas.org \
    --to=gary.thomas@mind.be \
    --cc=Pierre.Habraken@imag.fr \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jifl@eCosCentric.com \
    --cc=msalter@redhat.com \
    --cc=qqi@theworld.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox