Re: Architectures and PSIM

[Ron McCall <rmccall@sikorsky.com>]

Elena,

Looks like the latest CVS version works!  I did the following:

bash$ powerpc-eabi-gdb main.elf
(gdb) target sim -f psim.tree
(gdb) set architecture powerpc:603
(gdb) load main.elf
(gdb) break main
(gdb) run
(gdb) info all-registers

At this point, I see r0-r31, f0-f31, pc, ps, cr, lr, ctr, xer, fpscr,
sr0-sr15, pvr, ibat0u-ibat3u, ibat0l-ibat3l, dbat0u-dbat3u,
ibat0l-ibat3l, sdr1, dar, dsisr, sprg0-sprg3, srr0, srr1, tbl, tbu, dec,
dadr, ear, hid0, hid1, iabr, dmiss, dcmp, hash1, hash2, imiss, icmp and
rpa.  This is exactly what I needed.  Thank you so much for the tip!

Ron McCall

On Mon, Aug 12, 2002 at 01:43:41PM -0400, Ron McCall wrote:
> Sure, I will give the latest cvs version a try and will report back the
> results.  Thanks!
> 
> Ron McCall
> 
> On Mon, Aug 12, 2002 at 01:36:14PM -0400, Elena Zannoni wrote:
> > I am no expert on the uses of psim, so I cannot really help with the
> > device tree, etc. But....
> > 
> > I have seen the behavior above, (gdb not listing the correct set of
> > available architectures), could you try the current cvs main line
> > instead?
> > 
> > Note that psim will not digest a connection from gdb *after* the
> > architecture has been explicitly set by the set architecture command.
> > You should first connect, then change the architecture.
> > 
> > There are 2 patches that I committed to main trunk gdb and I don't
> > think were included in 5.2.1:
> > 
> > this one stops psim from complaining about lack of altivec registers:
> > http://sources.redhat.com/ml/gdb-patches/2002-04/msg00535.html
> > 
> > this one makes psim understand the architecture parameter set by gdb
> > before connection:
> > http://sources.redhat.com/ml/gdb-patches/2002-06/msg00305.html
> > 
> > Elena

-- 
Ron McCall
Sikorsky Aircraft
203-386-4695
rmccall@sikorsky.com