From: "William A. Gatliff" <bgat@saturn.billgatliff.com>
To: Thomas TESTASECCA <thomas.testasecca@etictelecom.com>
Cc: gdb list <gdb@sources.redhat.com>
Subject: Re: Remote debugging ( target : ARM7/linux ) (host x86/linux ) with JTAG emulator : how to choose ???????
Date: Thu, 13 Dec 2001 09:30:00 -0000 [thread overview]
Message-ID: <20011213112950.B32120@saturn.billgatliff.com> (raw)
In-Reply-To: <AEEFILJDOOHJLBCFOBJDGEJNCAAA.thomas.testasecca@etictelecom.com>; from thomas.testasecca@etictelecom.com on Thu, Dec 13, 2001 at 05:35:08PM +0100
Thomas:
> - Abatron BDI2000
I have one of these, for CPU32, and I recommend it highly.
It's an ethernet-to-BDM/JTAG bridge, and it speaks gdb's native remote
protocol on the ethernet side. It's easy to set up, and the best part
is that since it speaks the native protocol, the *standard* gdb runs
fine with it. No patches, no b.s.. That would also include Insight
and DDD.
The bdi2000 has been great for me. It's fast, sets up easily, and is
stable and reliable. I use it to test debugging stubs, RTOS code and
interrupt handlers, and it just keeps coming back for more. Abatron's
support has been excellent, too.
The OCDemon is similar, except I've heard from several places that it
is slower to download, and the information at http://www.ocdemon.com
makes it sound like you need a (binary) proxy to talk to it (see the
text "modified GDB and Insight" in the FAQ). That's just one more
thing to break in the process, in my opinion. I wouldn't go there.
In fact, I didn't. :^)
> This processor/OS use MMU, does it make a difference ?
It may.
If you are debugging applications running under Linux (i.e. in an mmu
environment) on the target, then you'll probably use gdbserver, not
one of the widgets you mentioned above. The BDI2000 et all will be
for KERNEL debugging, not APPLICATION debugging.
> What is the difference between the diffrerent protocols (Angel, ICE, RDI
> ...) ?
Basically the same differences as french vs. english vs. Klingon, in
no particular order. It's just the name for the protocol spoken
between the debugger and the target. It's always best if the two use
the same protocol. :^)
> What is the difference between the diffrerent file format ( ELF, AIF, COFF
> ...) ?
The key difference is in how the symbol information in the image is
encoded. If you debugger can't understand an ELF format, then you
can't do anything with that file.
> Does remote debug really works the same way than local mode ?
No.
> Can i debug the kernel easily, with the source files view ?
Yes.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2001-12-13 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 8:38 Thomas TESTASECCA
2001-12-13 9:30 ` William A. Gatliff [this message]
2001-12-13 9:39 ` William A. Gatliff
2001-12-13 9:30 ` Shaun Jackman
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=20011213112950.B32120@saturn.billgatliff.com \
--to=bgat@saturn.billgatliff.com \
--cc=bgat@billgatliff.com \
--cc=gdb@sources.redhat.com \
--cc=thomas.testasecca@etictelecom.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