Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Thomas TESTASECCA" <thomas.testasecca@etictelecom.com>
To: "gdb list" <gdb@sources.redhat.com>
Subject: Remote debugging ( target : ARM7/linux ) (host x86/linux ) with JTAG emulator : how to choose ???????
Date: Thu, 13 Dec 2001 08:38:00 -0000	[thread overview]
Message-ID: <AEEFILJDOOHJLBCFOBJDGEJNCAAA.thomas.testasecca@etictelecom.com> (raw)


Hi everybody,

I need help to understand and choose the right product.

I develop for an embedded target : a cyrrus logic CDB89712 card, it is
composed of an ARM720 ( cs89712 ), the OS on the board is linux BlueCat from
LynuxWorks.
I want to develop from a Linux Host.
I need a good debugging tool, to debug the kernel, and user applications,
with source code support.
For that i have chosen to use the JTAG bus of the ARM processor, but there
is a lot of emulators :

    - Macgraigor OCDemon
    - Lauterbach products
    - Abatron BDI2000
    - EPI JEENI
    - ...

I want to use GNU utils like GDB under linux.
Does someone know what are the difference between these components, the ones
which works well with GDB/Insight ?
This processor/OS use MMU, does it make a difference ?
What is the difference between the diffrerent protocols (Angel, ICE, RDI
...) ?
What is the difference between the diffrerent file format ( ELF, AIF, COFF
...) ?
Does remote debug really works the same way than  local mode ?
Can i debug the kernel easily, with the source files view ?

I know that's a lot of questions but i must decide and i'm in trouble ...

Thanks a lot by advance.

Thomas TESTASECCA
ETIC telecom
FRANCE

my e-mail : thomas.testasecca@etictelecom.com

I'm new, in the mailing, i don't really know how it works ;)






             reply	other threads:[~2001-12-13 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13  8:38 Thomas TESTASECCA [this message]
2001-12-13  9:30 ` Shaun Jackman
2001-12-13  9:30 ` William A. Gatliff
2001-12-13  9:39   ` William A. Gatliff

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=AEEFILJDOOHJLBCFOBJDGEJNCAAA.thomas.testasecca@etictelecom.com \
    --to=thomas.testasecca@etictelecom.com \
    --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