This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB using Angel error on an OKI board
- From: Grant Edwards <grante at visi dot com>
- To: Charles-Henri Balet <charles-henri at bluewin dot ch>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 25 Feb 2002 10:27:24 -0600
- Subject: Re: GDB using Angel error on an OKI board
- References: <005801c1bd6a$b6545e10$0401a8c0@CHARLESHENRI>
On Sun, Feb 24, 2002 at 08:37:36PM +0100, Charles-Henri Balet wrote:
> Hello,
>
> I'm using an OKI developpement board with the OKI ML671000
> processor, this is provide with an ARM SDT 2.50 software and an
> ARM Angel 1.20 in the flash memory on the board, when I use the
> ARM Debugger with an angel link, all work fine in 9600 or
> 19200, the message in the console box at the start is the next:
> (gdb) target rdi com1
> RDI_open: undefined error message, should reset target
> RDI_open failed
At this point things are probably already broken, so I don't
know if the messages below mean much. ADP (the protocol used
by Angel) has a _lot_ of state to it, and restting the target
without restarting GDB never works (at least not for me).
Restarting GDB without resetting the target usually works, but
not always.
1) Reset the board.
2) Start GDB.
3) Do the command "maint rdilogen on"
4) Do the command "target rdi com1"
5) Exit GDB
That should create a file named "rdi.log" with the initial ADP
packets logged to it. Post that file and we'll see what we can
see.
--
Grant Edwards
grante@visi.com