Functional Description
http://www.motorola.com/computer/literature 4-7
4
Note As outlined in Table 1-4, the snoop capabilities of the
MC68xx040 processor differ from those of the MC68xx060 used
on MVME172P4 series boards. Application software must take
these differences into account.
No-VMEbus-Interface Option
In support of possible future configurations in which the MVME162P4
might be offered as an embedded controller without the VMEbus interface,
certain logic in the VMEchip2 has been duplicated in the Petra chip. (For
the location of the overlapping logic, refer to Chapter 1 in the
MVME1X2P4 VME Embedded Controller Programmer’s Reference
Guide.) As long as the VMEchip2 ASIC is present, the redundant logic is
inhibited in the Petra chip. The enabling signals for these functions are
controlled by software and Petra chip hardware initialization.
Memory Options
The following memory options are available on the different versions of
MVME162P4 boards.
DRAM
MVME162P4 boards are built with 16MB or 32MB synchronous DRAM
(SDRAM). Depending on build options chosen at the time of manufacture,
various versions of the MVME162P4 have the SDRAM configured to
model 1MB, 4MB, 8MB, or 16MB of parity-protected DRAM or 4MB,
8MB, 16MB, or 32MB of ECC-protected DRAM.
The SDRAM memory array itself is always a single-bit error correcting
and multi-bit error detection memory, irrespective of which interface
model you use to access the SDRAM. When the MC2 (parity) memory
controller interface is used to access the SDRAM, single-bit errors are
undetectable to users and multi-bit errors are defined to be parity errors.
Firmware will initialize the memory controller to maintain backward
compatibility with MVME162FX or -LX products. If the Petra ASIC is
supporting MVME162FX functionality, the parity memory controller
model will be enabled by default. If the Petra ASIC is supporting
To Next Page
Loading...
