This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: serial RDI
- To: Shaun Jackman <shaunj at gray-interfaces dot com>
- Subject: Re: serial RDI
- From: Grant Edwards <grante at visi dot com>
- Date: Tue, 22 Aug 2000 17:24:49 -0500
- Cc: gdb list <gdb at sources dot redhat dot com>
- References: <006c01c00c85$8454af60$6801a8c0@gray.internal>
On Tue, Aug 22, 2000 at 04:08:35PM -0600, Shaun Jackman wrote:
> I have an Atmel EB40, AT91M40807 processor (ARM7TDMI) which came with an
> Angel monitor in flash. I'm having difficulty connecting to it at any baud
> rate above 9600.
> I'm using Insight 5.0, but am running it no-windows (-nw) to try to sort out
> this remote debugging problem.
> set debug remote 1
> but the output was no different than above.
You're not using a "remote" target. The "remote" target uses
the gdb protocol. If you want to debug rdi stuff, there's an
rdilogfile command (it may be "maint rdilogfile" -- I forget).
If you set a log file name using that command, it will capture
all of the RDI frames to a file in a semi-readible format.
(You will probably need to look at the rdi header files to
figure out what's going on, but at least things are saved in
hex/ascii).
Someday I'm going to write a Python program to parse rdi log
files...
--
Grant Edwards
grante@visi.com