From: Torsten Mohr <tmohr@s.netic.de>
To: insight <insight@sources.redhat.com>
Subject: Re: ARM debugging via JTAG?
Date: Wed, 26 Jun 2002 12:42:00 -0000 [thread overview]
Message-ID: <200206261947.g5QJlRo04409@schleim.qwe.de> (raw)
In-Reply-To: <20020626111149.A6611@visi.com>
Hi,
thanks for that hint, but it must be possible somehow to debug
an ARM chip with a parallel port (/dev/parport*).
Has anybody got some info about what's necessary to debug
an ARM? I took a look into gdb/rdi-share/ardi.c, hostchan.c
and devsw.c .
I still don't know exactly what's necessary to debug an ARM,
has anybody got a hint or some documentation for me what's
necessary to debug that chip?
I once wrote some very basic code to send some commands to
my ARMs JTAG state machine and could stop the core, but
couldn't yet send commands to the core.
http://www.s.netic.de/tmohr/linux.html
Best regards,
Torsten.
> On Tue, Jun 25, 2002 at 10:28:02PM +0200, Torsten Mohr wrote:
> > Does anybody know of patches for GDB that enable ARM debugging
> > via JTAG over the parallel port?
>
> I don't know of any that do JTAG directly on the parallel port.
>
> There are several ARM JTAG interfaces that are supported by gdb:
>
> ARM EmbeddedICE (uses rdi target via serial/parallel)
> EPI Jeeni (uses rdi target via serial or Ethernet)
> ARM MultiIce (via some server program run on Windows)
> Macraigor/OCDemon (via remote target)
> Abatron BDIxxx (via remote target)
next prev parent reply other threads:[~2002-06-26 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 13:51 Torsten Mohr
2002-06-26 9:09 ` Grant Edwards
2002-06-26 12:42 ` Torsten Mohr [this message]
2002-08-14 6:58 ` Tim Chick
2002-08-14 8:15 ` Fernando Nasser
2002-08-12 22:49 Rafael Vuijk (aka Dark Fader)
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=200206261947.g5QJlRo04409@schleim.qwe.de \
--to=tmohr@s.netic.de \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).