From: "Mark Powell" <medp@primagraphics•co.uk>
To: <linuxppc-embedded@lists•linuxppc.org>
Subject: Compiling/debugging 405GP and RISCWatch
Date: Wed, 21 Mar 2001 12:59:30 -0000 [thread overview]
Message-ID: <03ee01c0b206$c4878ea0$3000a8c0@primag> (raw)
Hi,
I'm at the beginning of a project using the 405GP. I have HardHat linux
(01.03.03 kernel) up and running on a Walnut eval card. That bit is fine.
However, for one very deeply embedded part of the hardware I can't use linux
(not enough RAM and ROM), I just want a bootstrap to run a single program.
I'm trying to decide on a debugging strategy and I am considering RISCWatch
with the JTAG adaptor. I have experimented with RISCWatch using a network
connection to the Walnut ROM Monitor, but have so far been unable to produce
an executable with the HardHat/GNU tool chain from which RISCWatch can read
debugging symbols. The RISCWatch manual says it can read ELF/DWARF files,
and indeed it seems to download my executable, but gives an error
"DwarfCompilationUnit: invalid FORM = 0"
I would be grateful for any info on these points...
Is it possible to use RISCWatch with the GNU toolchain?
Is it possible to use the RISCWatch/JTAG interface as a backend to gdb?
Any other suggestions for debugging (with no network connection on the
target)?
Any pointers to more info.
TIA
--
Mark Powell, Senior Software Engineer, Primagraphics Limited
New Cambridge House, Litlington, nr.Royston, Herts, SG8 0SS, UK
Tel. +44 1763 852222, Fax. 853324, http://www.primagraphics.co.uk
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-03-21 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 12:59 Mark Powell [this message]
2001-03-21 13:12 ` Compiling/debugging 405GP and RISCWatch Ralph Blach
2001-03-21 13:24 ` Wolfgang Denk
2001-03-21 15:43 ` Kenneth Johansson
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='03ee01c0b206$c4878ea0$3000a8c0@primag' \
--to=medp@primagraphics$(echo .)co.uk \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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