From: Grant Edwards <grante@visi.com>
To: Charles-Henri Balet <charles-henri@bluewin.ch>
Cc: gdb@sources.redhat.com
Subject: Re: GDB using Angel error on an OKI board
Date: Mon, 25 Feb 2002 08:20:00 -0000 [thread overview]
Message-ID: <20020225102723.A11481@visi.com> (raw)
In-Reply-To: <005801c1bd6a$b6545e10$0401a8c0@CHARLESHENRI>; from charles-henri@bluewin.ch on Sun, Feb 24, 2002 at 08:37:36PM +0100
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
next prev parent reply other threads:[~2002-02-25 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 11:39 Charles-Henri Balet
2002-02-25 8:20 ` Grant Edwards [this message]
[not found] ` <000f01c1ebb8$84dbc630$0401a8c0@CHARLESHENRI>
2002-02-25 11:10 ` Grant Edwards
[not found] ` <000501c1be32$8ea031f0$0401a8c0@CHARLESHENRI>
2002-02-25 12:04 ` Grant Edwards
[not found] ` <003001c1be39$fc62ef00$0401a8c0@CHARLESHENRI>
2002-02-25 14:10 ` Grant Edwards
2002-02-25 14:02 Charles-Henri Balet
2002-02-25 14:13 ` Grant Edwards
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=20020225102723.A11481@visi.com \
--to=grante@visi.com \
--cc=charles-henri@bluewin.ch \
--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