Re: Architectures and PSIM

[Elena Zannoni <ezannoni at redhat dot com>]

Ron McCall writes:
 > Hi,
 > 
 > I am having trouble getting PSIM to simulate a 603e processor (operating
 > environment).  With the device tree shown below, I can execute
 > privileged instructions so I am in the operating environment but I
 > cannot access any of the OEA registers (and it is trying to read AltiVec
 > registers which comes up with an error).  Here is what I have done:
 > 
 > First, I built and installed gdb 5.2.1 as follows:
 > 
 > bash$ ../gdb-5.2.1/configure --prefix=/opt/gcc-ppc-3.1.1
 > --build=sparc-sun-solaris2.8 --host=sparc-sun-solaris2.8
 > --target=powerpc-eabi --enable-sim-powerpc
 > bash$ make
 > bash# make install
 > 
 > Next, I created a device tree in a file named psim.tree as follows (note
 > the specification of the 603e processor and operating mode):
 > 
 > /openprom/init/register/msr 0x40
 > /openprom/init/register/sp 0x100000
 > /openprom/trace/dump-device-tree 0x0
 > /openprom/options/env "operating"
 > /openprom/options/model "603e"
 > /openprom/options/oea-interrupt-prefix 0x1
 > /openprom/vm/stack-base 0xf0000
 > /openprom/vm/nr-bytes 0x10000
 > 
 > Next, I load my bare board executable as follows:
 > 
 > $ powerpc-eabi-gdb main.elf
 > vr0            psim_read_register() invalid register name `vr0'
 > 
 > (gdb) info reg hid0
 > hid0: invalid register
 > (gdb) show architecture
 > The target architecture is set automatically (currently powerpc:common)
 > (gdb) set architecture
 > Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1,
 > rs6000:rsc, rs6000:rs2, powerpc:common, auto.
 > 
 > Note that I don't get any choices of PowerPC besides common although I
 > see support for the 403, 403GC, 505, 860/850, 601, 602, 603/603e,
 > 604/604e, 750/740 and 7400 in gdb/rs6000-tdep.c.
 > 

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

 > I have also tried adding the --with-cpu=603e option to configure but
 > that didn't seem to change anything.  Can anyone tell me what I am doing
 > wrong?
 > 
 > Thanks!
 > 
 > Ron McCall