Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Pierre Habraken <Pierre.Habraken@imag.fr>
Cc: gdb@sources.redhat.com, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Can't connect to remote Evaluator 7T
Date: Wed, 19 Feb 2003 15:30:00 -0000	[thread overview]
Message-ID: <3E53A321.1060907@eCosCentric.com> (raw)
In-Reply-To: <3E539BFB.6B81024F@imag.fr>

Pierre Habraken wrote:
> 
> Now I want to use RedBoot instead of Angel.
> I uploaded redboot.UU onto the board and then verified (using a
> communication program) that redboot was properly installed (see redboot
> banner below).
> But when I launch arm-elf-gdb and type the command 'target remote
> /dev/ttyS0' then gdb fails to talk to redboot :
> =================================================================
> $ arm-elf-gdb
> GNU gdb 5.2
> ...
> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Couldn't establish connection to remote target
> Malformed response to offset query, timeout
> =================================================================
> Could it be that the serial line is not configured as required on the
> gdb side ? (using ckermit I had to force parity to none...)

Possible, but unlikely since you're receiving stuff at all (packet errors, 
not just timeout) and I assume you have the baud rate right :-).

Before target remote you could do:

set debug remote 1

to see what that says. If that doesn't reveal anything interesting then 
(if I'm remembering right) you can also do:

set remotelogfile gdblog.txt

before the target remote, which should give a slightly more accurate 
version of what was sent/received, into the file gdblog.txt.

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


  reply	other threads:[~2003-02-19 15:30 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 ` Jonathan Larmour [this message]
2003-02-19 15:59   ` [ECOS] " 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
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=3E53A321.1060907@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=Pierre.Habraken@imag.fr \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gdb@sources.redhat.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