Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dave Cleal <dave@cleal.com>
To: gdb@sources.redhat.com
Subject: Re: Can't talk to Angel debug monitor from arm-elf-gdb
Date: Fri, 29 Oct 2004 15:23:00 -0000	[thread overview]
Message-ID: <1596379650.20041028115650@cleal.com> (raw)
In-Reply-To: <1979656656.20041022154729@cleal.com>

(talking to myself)

Eventually got around this by re-flashing to replace Angel with
the Redboot monitor. arm-elf-gdb talks to that just fine as a remote
target.

I do have a remaining problem with my toolchain, which is that
ideally, I'd like to develop in Eclipse. Eclipse won't interact nicely
with arm-elf-gdb running a remote target. I'm not sure whether this is
Eclipse sending the wrong commands, or arm-elf-gdb responding weirdly.
Just before I start messing with Eclipse, has anyone got experience of
this kind of set up (eclipse -> arm-elf-gdb -> remote target)?

- Dave

> Hi,

> I've got an ATMEL EB40A ARM evaluation board that has ARM Angel 1.04
> running in the flash, and I can talk to this fine from the
> ARM-supplied AXD debugger. But I can't talk to it from arm-elf-gdb (I
> have v.6.1, compiled by macgraigor.com) which is running under cygwin
> on Windows 2000. arm-elf-gdb works just fine with the simulator
> target.

> I start up arm-elf-gdb, then do

> set remotebaud 9600
> target rdi com1

> The second command just hangs, I can see LEDs flashing to indicate
> that data is passing back and forth, but no response in gdb.

> Any ideas?

> - Dave


  parent reply	other threads:[~2004-10-28 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 15:01 Dave Cleal
2004-10-23 15:04 ` Dave Korn
2004-10-29 15:23 ` Dave Cleal [this message]
2004-11-12  2:16   ` Re[2]: " Dave Cleal
2004-11-12 13:28     ` Alain Magloire
2004-11-12 16:25       ` Re[4]: " Dave Cleal
2004-11-12 18:47         ` Alain Magloire

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=1596379650.20041028115650@cleal.com \
    --to=dave@cleal.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