This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Can't talk to Angel debug monitor from arm-elf-gdb
- From: Dave Cleal <dave at cleal dot com>
- To: gdb at sources dot redhat dot com
- Date: Thu, 28 Oct 2004 11:56:50 +0100
- Subject: Re: Can't talk to Angel debug monitor from arm-elf-gdb
- References: <1979656656.20041022154729@cleal.com>
- Reply-to: Dave Cleal <dave at cleal dot 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