From: Shaun Jackman <sjackman@pathwayconnect.com>
To: gdb@sources.redhat.com
Cc: "Thomas TESTASECCA" <thomas.testasecca@etictelecom.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: <E16EZek-0002HJ-00@dazed> (raw)
In-Reply-To: <AEEFILJDOOHJLBCFOBJDGEJNCAAA.thomas.testasecca@etictelecom.com>
> 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 ?
Both the BDI2000 and the Jeeni work well with GDB/Insight.
> This processor/OS use MMU, does it make a difference ?
I'm only familiar with the ARM7TDMI, but it works fabulously!
> What is the difference between the different protocols (Angel, ICE, RDI
> ...) ?
In my experience Angel (and RDI, same thing) aren't as well supported under
GDB as the GDB remote protocol is. The Jeeni speaks RDI, the BDI2000 speaks
GDB. The BDI2000 also has a handy telnet terminal, for when you're having
trouble with GDB.
> What is the difference between the different file format ( ELF, AIF, COFF
> ...) ?
I'm only familiar with elf. It seems to be the most common format for ARM
targets. Works well.
> Does remote debug really works the same way than local mode ?
> Can i debug the kernel easily, with the source files view ?
If by "kernel" you mean Linux kernel, I have no idea as I'm not running Linux
on my target. I am able to debug our in-house RTOS quite well though. I'd
even be willing to say it works *better* than local mode because you can step
through interrupt handlers much easier.
Cheers,
Shaun
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
2001-12-13 9:39 ` William A. Gatliff
2001-12-13 9:30 ` Shaun Jackman [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=E16EZek-0002HJ-00@dazed \
--to=sjackman@pathwayconnect.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