From: Nacho de los RÃÂos Tormo <irios@proin.es>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] ARM debugger with ICE for ARM target
Date: Fri, 12 Nov 1999 03:27:00 -0000 [thread overview]
Message-ID: <000901bf2d00$b74eade0$2100000a@irios> (raw)
In-Reply-To: <19991111082730.A20472@visi.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
On the subjectof JTAG debuggers, does anybody have information on what
exactly does ARM's embedded ICE have inside?
A parallel to JTAG converter is not really a big deal; in fact, Altera sells
one for programming its CPLD devices at a cost below $100, which makes the
$1500 that ARM charges seem a tad expensive.
Intel has an application note detailing how to program standard Flash memory
chips that reside in the bus of a microprocessor that has a JTAG interface
describes how to build one with just a couple of standard logic ICs, and
includes some simple code to dump the programming commands and data to the
processor's bus via JTAG. I've seen this done with a 386EX and 4 Mbit flash
devices, and though the speed won't ruin your hairdo, it was still pretty
good.
Anybody knows where to start looking to develop a DIY Embedded ICE for ARM?
It would make for a nice Open Hardware project ...
Nacho de los RÃos
irios@proin.es
----- Original Message -----
From: Grant Edwards <grante@visi.com>
To: Yanbing Yu <yanbingyu@netzero.net>
Cc: <ecos-discuss@sourceware.cygnus.com>
Sent: Thursday, November 11, 1999 3:27 PM
Subject: Re: [ECOS] ARM debugger with ICE for ARM target
> On Wed, Nov 10, 1999 at 11:27:39PM -0600, Yanbing Yu wrote:
>
> > I am new to eCos, and am evaluating eCos for our new ARM based
> > platform. I downloaded all the necessary tools, compiled the
> > libraries and test programs, and ran successfully on my AEB-1
> > board through gdb.
> >
> > Now I am wondering if I can use the ARM debugger with an ICE
> > to download and debug eCos programs to the target through
> > JTAG port?
>
> I don't know. You can also build coff format executables using the
> Gnu toolchain if that helps.
>
> Gdb does support the RDI protocol used to talk to JTAG interface boxes
> for the ARM. I've used gdb with the ARM Embedded ICE and the EPI
> Jeeni. The latter has an ethernet port, so downloading is way faster.
>
> I've submitted several patches to improve RDI support, so you should
> either get GDB 4.18 sources and apply the patches, or you should get
> the CVS snapshot of gdb (which I think has my patches merged into it
> at this point)..
>
> > Since the executables are ELF files, which ARM
> > debugger supports, I should be able to use it instead of GDB.
> > But the ARM debugger crashed when I did that. Why?
>
> Don't know -- I use gdb.
>
> --
> Grant Edwards
> Principal Engineer
> Comtrol Corporation
>
prev parent reply other threads:[~1999-11-12 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-10 21:34 Yanbing Yu
1999-11-11 6:27 ` Grant Edwards
1999-11-12 3:27 ` Nacho de los RÃos Tormo [this message]
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='000901bf2d00$b74eade0$2100000a@irios' \
--to=irios@proin.es \
--cc=ecos-discuss@sourceware.cygnus.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).