serial RDI

serial RDI

[Shaun Jackman]

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.

This is the problem I run into...

This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf".
(gdb) file main.elf
Reading symbols from main.elf...done.
(gdb) set remotebaud 19200
(gdb) target rdi /dev/ttyS1
Angel Debug Monitor (serial) 1.04 (Advanced RISC Machines SDT 2.5) for
AT91EB40
(2.00)
Angel Debug Monitor rebuilt on Apr 07 2000 at 12:40:31
Serial Rate:  19200
[dies here and never comes back]
It silently ignores ctrl-c and makes no response to a SIGINT
I have to send a SIGKILL to get my console back.

But it works at 9600...
This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf".
(gdb) set remotebaud 9600
(gdb) file main.elf
Reading symbols from main.elf...done.
(gdb) target rdi /dev/ttyS1
Angel Debug Monitor (serial) 1.04 (Advanced RISC Machines SDT 2.5) for
AT91EB40
(2.00)
Angel Debug Monitor rebuilt on Apr 07 2000 at 12:40:31
Serial Rate:   9600
Connected to ARM RDI target.
(gdb)
[works]

I can run it up to 38400 with the ARM Ltd. debugger, but have been
unsuccessful running it any faster than 9600 with gdb.
I would really like to get this working at a faster baudrate, and gdb's lack
of comunication when it fails is disconcerting.
Any suggestions on where I could start trouble shooting?
I tried
set debug remote 1
but the output was no different than above.

Thanks,
Shaun

Re: serial RDI

[Grant Edwards]

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

Re: serial RDI

[Grant Edwards]

> 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.

Oh, I forgot -- you've also got to enable the log with the 
"maint rdilogenable" command.

-- 
Grant Edwards
grante@visi.com