Re: PSIM Support for MPC860

[fche at redhat dot com (Frank Ch. Eigler)]

"Tom Taylor" <ttaylor@ateng.com> writes:

: [...]  No doubt.  However, I only need a limited simulation at first
: to verify that BSP, driver, and application code previously compiled
: and linked by my client using Diab Data tools will operate properly
: after compilation using GCC and linking with pSOS+ and pNA+
: libraries.  [...]

Yes; these are compiler/assembler matters.


: CPM simulation will have to be severely limited.  Fortunately, UPM
: emulation should be unimportant.  I believe that a comprehensive,
: general simulation of the MPC860T would be extremely difficult.

Yes.


: I'm more interested in allowing analysis of interactions with code
: on board-specific peripherals such as the TI 5420 DSP through the
: HPI than in supporting all possible 860T internal peripherals.

If you are contemplating building models of a completely different
processor (the DSP chip), please be aware that psim is somewhat
limited in its integration capabilities with models of this rich
nature.  It might be worth your time to investigate other simulation
frameworks such as sid and modelling systems like cgen.  (Both these
are Red Hat projects on sources.redhat.com.)


: Chip-select simulation will be required.  I guess I'll have to learn
: a lot about the device tree approach; unfortunately it appears that
: the IEEE 1275 OpenBoot standard has been withdrawn.

The OpenBoot references in psim are somewhat illusory.  In psim, they
constitute merely a naming convention for the strings that constitute
configuration of the peripheral models.  There is no OpenBoot firmware
or anything like that.


: [...] I'll submit any of the more general-purpose code--such as I &
: D Cache SPR extensions--for possible inclusion with PSIM when I have
: it working OK.

Great.


- FChE