public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Yanbing Yu <yanbingyu@netzero.net>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ARM debugger with ICE for ARM target
Date: Thu, 11 Nov 1999 06:27:00 -0000	[thread overview]
Message-ID: <19991111082730.A20472@visi.com> (raw)
In-Reply-To: <004601bf2c05$a49a56a0$1f26f1cd@mercury>

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

  reply	other threads:[~1999-11-11  6: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 [this message]
1999-11-12  3:27   ` Nacho de los Ríos Tormo

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=19991111082730.A20472@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=yanbingyu@netzero.net \
    /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).