Compiling/debugging 405GP and RISCWatch

Compiling/debugging 405GP and RISCWatch

[Mark Powell]

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/

Re: Compiling/debugging 405GP and RISCWatch

[Ralph Blach]

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

Mark,

Yes, this is sadly true.  There is a bug in gcc which causes this to
happen.
With the Walnut kit, the evaluation copy of the Metaware compiler is
shipped.  You might want to try this.

Chip


Mark Powell wrote:
>
> 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
>

[-- Attachment #2: Card for Ralph Blach --]
[-- Type: text/x-vcard, Size: 247 bytes --]

begin:vcard
n:Blach;Ralph
tel;work:919-543-1207
x-mozilla-html:TRUE
url:www.ibm.com
org:IBM MicroElectronics
adr:;;3039 Cornwallis		;RTP;NC;27709;USA
version:2.1
email;internet:rcblach@raleigh.ibm.com
x-mozilla-cpt:;15936
fn:Ralph Blach
end:vcard

Re: Compiling/debugging 405GP and RISCWatch

[Wolfgang Denk]

In message <03ee01c0b206$c4878ea0$3000a8c0@primag> you wrote:
>
> 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"

Another suggestion: replace the Walnut ROM Monitor  by  PPCBoot,  the
Open  Source Firmware project (see ppcboot.sourceforge.net), and load
and run your program under PPCboot. This  is  explicitely  supported;
see the code in the examples directory.

> 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)?

Get yourself a BDI2000. It's a great tool and  works  perfectly  with
GDB, even for Linux, where MMU support is essential.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
When a program is being  tested,  it  is  too  late  to  make  design
changes.                  -- Geoffrey James, "The Tao of Programming"

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Compiling/debugging 405GP and RISCWatch

[Kenneth Johansson]

Mark Powell wrote:
>
>
> Is it possible to use the RISCWatch/JTAG interface as a backend to gdb?

No target exist now that Iam aware of.
The thing that prevent one from beeing written is that the help on the commands that the
riscwatch probe can do is to poor.

for ex. the help for dump is
---
help dump

  dump - upload processor memory in absolute file format

    dump -h <addr>..<addr> - upload hp format (requires transfer protocol)
    dump -b <addr>..<addr> - send data in binary (valid with -h option)
    dump -n <addr>..<addr> - send data in fast binary format
---

This dose not actually work if you trace a dump from the rwppc program you see that
a @<memory_type> is also needed.

On the other hand nobody has tried to make the interface difficult so its probably
quite easy to reverse engineer it.

What you need for gdb is a way to start/stop the cpu and to read/write registers and memory.

Its only the command for writing that is not obvious from the ascii trace that I did.



--
Kenneth Johansson
Ericsson Business Innovation AB   Tel: +46 8 404 71 83
Viderögatan 3                     Fax: +46 8 404 72 72
164 80 Stockholm                  kenneth.johansson@inn.ericsson.se

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/