Emerson, Business-Critical Continuity, Emerson Network Power and the Emerson Network Power logo are trademarks and service
marks of Emerson Electric Co.
All other trademarks are the property of their respective owners.
®
is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
While reasonable efforts have been made to assure the accuracy of this document, Emerson assumes no liability resulting from any
omissions in this document, or from the use of the information obtained therein. Emerson reserves the right to revise this document
and to make changes from time to time in the content hereof without obligation of Emerson to notify any person of such revision or
changes.
Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to
a Emerson website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise altered
without the permission of Emerson,
It is possible that this publication may contain reference to or information about Emerson products (machines and programs),
programming, or services that are not available in your country. Such references or information must not be construed to mean that
Emerson intends to announce such Emerson products, programming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply unless
otherwise agreed to in writing by Emerson.
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in Technical
Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and Documentation clause
at DFARS 252.227-7014 (Jun. 1995).
Contact Address
Emerson Network Power - Embedded Computing
2900 South Diablo Way, Suite 190
Tempe, AZ 85282
USA
Page 3
Safety Summary
Warning
The following general safety precautions must be observed during all phases of operation, service, and repair
of this equipment. Failure to comply with these precautions or with specific warnings elsewhere in this manual
could result in personal injury or damage to the equipment.
The safety precautions listed below represent warnings of certain dangers of which Emerson is aware. You,
as the user of the product, should follow these warnings and all other safety precautions necessary for the
safe operation of the equipment in your operating environment.
Ground the Instrument.
To minimize shock hazard, the equipment chassis and enclosure must be connected to an electrical ground.
If the equipment is supplied with a three-conductor AC power cable, the power cable must be plugged into
an approved three-contact electrical outlet, with the grounding wire (green/yellow) reliably connected to an
electrical ground (safety ground) at the power outlet. The power jack and mating plug of the power cable meet
International Electrotechnical Commission (IEC) safety standards and local electrical regulatory codes.
Do Not Operate in an Explosive Atmosphere.
Do not operate the equipment in any explosive atmosphere such as in the presence of flammable gases or
fumes. Operation of any electrical equipment in such an environment could result in an explosion and cause
injury or damage.
Keep Away From Live Circuits Inside the Equipment.
Operating personnel must not remove equipment covers. Only Factory Authorized Service Personnel or other
qualified service personnel may remove equipment covers for internal subassembly or component
replacement or any internal adjustment. Service personnel should not replace components with power cable
connected. Under certain conditions, dangerous voltages may exist even with the power cable removed. To
avoid injuries, such personnel should always disconnect power and discharge circuits before touching
components.
Use Caution When Exposing or Handling a CRT.
Breakage of a Cathode-Ray Tube (CRT) causes a high-velocity scattering of glass fragments (implosion). To
prevent CRT implosion, do not handle the CRT and avoid rough handling or jarring of the equipment.
Handling of a CRT should be done only by qualified service personnel using approved safety mask and
gloves.
Do Not Substitute Parts or Modify Equipment.
Do not install substitute parts or perform any unauthorized modification of the equipment. Contact your local
Emerson representative for service and repair to ensure that all safety features are maintained.
Observe Warnings in Manual.
Warnings, such as the example below, precede potentially dangerous procedures throughout this manual.
Instructions contained in the warnings must be followed. You should also employ all other safety precautions
which you deem necessary for the operation of the equipment in your operating environment.
To prevent serious injury or death from dangerous voltages, use
extreme caution when handling, testing, and adjusting this
equipment and its components.
Page 4
Flammability
!
Caution
!
Caution
Attention
!
Vors i ch t
!
All Emerson PWBs (printed wiring boards) are manufactured with a flammability rating of 94V0 by UL-recognized manufacturers.
EMI Caution
This equipment generates, uses and can radiate electromagnetic energy. It may cause
or be susceptible to electromagnetic interference (EMI) if not installed and used with
adequate EMI protection.
Lithium Battery Caution
This product contains a lithium battery to power the clock and calendar circuitry. Only properly
trained service personnel should remove or install lithium batteries.
Danger of explosion if battery is replaced incorrectly. Replace battery only with the
same or equivalent type recommended by the equipment manufacturer. Dispose of
used batteries according to the manufacturer’s instructions.
Il y a danger d’explosion s’il y a remplacement incorrect de la batterie. Remplacer
uniquement avec une batterie du même type ou d’un type équivalent recommandé par
le constructeur. Mettre au rebut les batteries usagées conformément aux instructions
du fabricant.
Explosionsgefahr bei unsachgemäßem Austausch der Batterie. Ersatz nur durch
denselben oder einen vom Hersteller empfohlenen Typ. Entsorgung gebrauchter
Batterien nach Angaben des Herstellers.
Page 5
CE Notice (European Community)
!
Warning
Warning
This is a Class A product. In a domestic environment, this product may cause radio
interference, in which case the user may be required to take adequate measures.
Emerson products with the CE marking comply with the EMC Directive (89/336/EEC).
Compliance with this directive implies conformity to the following European Norms:
EN55022 “Limits and Methods of Measurement of Radio Interference Characteristics of
Information Technology Equipment”; this product tested to Equipment Class A
EN 300 386 V.1.2.1 “Electromagnetic compatibility and radio spectrum matters (ERM);
Telecommunication network equipment; Electromagnetic compatibility (EMC) requirements”
System products also fulfill EN60950 (product safety) which is essentially the requirement for
the Low Voltage Directive (73/23/EEC).
Board products are tested in a representative system to show compliance with the above
mentioned requirements. A proper installation in a CE-marked system will maintain the required
EMC/safety performance.
In accordance with European Community directives, a “Declaration of Conformity” has been
made and is on file within the European Union. The “Declaration of Conformity” is available on
request. Please contact your sales representative.
The product has been designed to meet the directive on the restriction of the use of certain
hazardous substances in electrical and electronic equipment (RoHS) Directive 2002/95/EC.
one parallel port, three async and one sync/async serial port.
MVME712M6ETransition module connectors: One DB-25 sync/async serial port,
three DB-25 async serial ports, one AUI connector, one D-36
parallel port, and one 50-pin 8-bit SCSI; includes 3-row DIN P2
adapter module and cable.
IPMC7616E-002Multifunction rear I/O PMC module; 8-bit SCSI, one parallel port,
MVME7616E-001Transition module: Two DB-9 async serial port connectors, two HD-
MVME7616E-011Transition module: Two DB-9 async serial port connectors, two HD-
SIM232DCE5E or DTEEIA-232 DCE or DTE Serial Interface Module.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
MVME761 Compatible I/O
two async and two sync/async serial ports.
26 sync/async serial port connectors, one HD-36 parallel port
connector, and one RJ-45 10/100 Ethernet connector; includes 3row DIN P2 adapter module and cable (for 8-bit SCSI).
26 sync/async serial port connectors, one HD-36 parallel port
connector, and one RJ-45 10/100 Ethernet connector; includes 5row DIN P2 adapter module and cable (for 16-bit SCSI); requires
backplane with 5-row DIN connectors.
xv
Page 16
About This Manual
Model NumberDescription
PMCSPAN26E-002Primary PMCSPAN with original VME Scanbe ejector handles.
PMCSPAN26E-010Secondary PMCSAN with original VME Scanbe ejector handles.
The following paragraphs briefly describe the contents of each chapter.
Chapter 1, Hardware Preparation and Installation, provides a description of the MVME5100 and
its main integrated PMC and IPMC boards. The remainder of the chapter includes an
explanation of the installation procedure, including preparation and jumper setting information.
Chapter 2, Operation, provides a description of the operational functions of the MVME5100
including tips on applying power, a description of the switch settings, the status indicators, I/O
connectors, and system power up information.
Chapter 3, PPCBug Firmware, provides an explanation of the debugger firmware, PPCBug, on
the MVME5100. The chapter includes an overview of the firmware, a section on how to use
PPCBug, a listing of the initialization steps, a brief explanation of the two main configuration
commands CNFG and ENV, and a description of the standard configuration parameters. A
listing of the basic commands are also provided.
Chapter 4, Functional Description, provides a summary of the MVME5100 features, a block
diagram, and a description of the major functional areas.
Chapter 5, RAM500 Memory Expansion Module, provides a description of the RAM500
Memory Expansion Module, a list of features, a block diagram of the module, a table of memory
size allocations, an installation procedure, and pinouts of the module’s top and bottom side
connectors.
Chapter 6, Pin Assignments, provides a listing of all connector and header pin assignments for
the MVME5100.
xvi
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 17
Chapter 7, Programming the MVME5100, provides a description of the memory maps on the
MVME5100 including tables of default processor memory maps, suggested CHRP memory
maps and Hawk PPC register values for suggested memory maps. The remainder of the
chapter provides some programming considerations.
Appendix A, Specifications, provides the standard specifications for the MVME5100, as well as
some general information on cooling.
Appendix B, Troubleshooting, provides a brief explanation of the possible resolutions for basic
error conditions.
Appendix C, Thermal Analysis, gives systems integrators the information necessary to conduct
thermal evaluations of the board in their specific system configuration.
Appendix D, Related Documentation, provides a listing of related documentation for the
MVME5100, including vendor documentation and industry related specifications.
Comments and Suggestions
We welcome and appreciate your comments on our documentation. We want to know what you
think about our manuals and how we can make them better.
About This Manual
Mail comments to us by filling out the following online form:
http://www.emersonnetworkpowerembeddedcomputing.com/ > Contact Us > Online Form
In “Area of Interest” select “Technical Documentation”. Be sure to include the title, part number,
and revision of the manual and tell us how you used it.
Conventions Used in This Manual
The following typographical conventions are used in this document:
bold
is used for user input that you type just as it appears; it is also used
for commands, options and arguments to commands, and names of
programs, directories and files.
italic
is used for names of variables to which you assign values. Italic is
also used for comments in screen displays and examples, and to
introduce new terms.
courier
<Enter>, <Return> or <CR>
MVME51005E Single Board Computer Installation and Use (6806800A38B)
is used for system output (for example, screen displays, reports),
examples, and system prompts.
<CR> represents the carriage return or Enter key.
xvii
Page 18
About This Manual
CTRL
Terminology
A character precedes a data or address parameter to specify the numeric format, as follows (if
not specified, the format is hexadecimal):
An asterisk (*) following a signal name for signals that are level significant denotes that the
signal is true or valid when the signal is low.
An asterisk (*) following a signal name for signals that are edge significant denotes that the
actions initiated by that signal occur on high to low transition.
In this manual, assertion and negation are used to specify forcing a signal to a particular state.
In particular, assertion and assert refer to a signal that is active or true; negation and negate
indicate a signal that is inactive or false. These terms are used independently of the voltage
level (high or low) that they represent. Data and address sizes are defined as follows:
represents the Control key. Execute control characters by pressing
the Ctrl key and the letter simultaneously, for example, Ctrl-d.
0xSpecifies a hexadecimal number
%Specifies a binary number
&Specifies a decimal number
Byte 8 bits, numbered 0 through 7, with bit 0 being the least significant.
Half word16 bits, numbered 0 through 15, with bit 0 being the least
significant.
Word32 bits, numbered 0 through 31, with bit 0 being the least
significant.
Double word64 bits, numbered 0 through 63, with bit 0 being the least
significant.
xviii
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 19
1Hardware Preparation and Installation
Introduction
This chapter provides information on hardware preparation and installation for the MVME5100
Series of Single Board Computers.
1
Note
Unless otherwise specified, the designation “MVME5100” refers to all models of the
MVME5100-series Single Board Computers.
Getting Started
The following subsections include information helpful in preparing your equipment. It includes
and overview of the MVME5100, any equipment needed to complete the installation, and
unpacking instructions.
Overview and Equipment Requirements
The MVME5100 interfaces to a VMEbus system via its P1 and P2 connectors and contains two
IEEE 1386.1 PCI Mezzanine Card (PMC) Slots. The PMC Slots are 64-bit and support both
front and rear I/O.
Additionally, the MVME5100 is user configurable by setting on-board jumpers. Two I/O modes
are possible: PMC mode or SBC mode (also called 761 or IPMC mode). The SBC mode uses
the IPMC712 I/O PMC and the MVME712M Transiton Module, or the IPMC761 I/O PMC and
the MVME761 Transition Module. The SBC mode is backwards compatible with the MVME761
transition card and the P2 adapter card (excluding PMC I/O routing) used on the
MVME2600/2700 product. This mode is accomplished by configuring the on-board jumpers and
by attaching an IPMC761 PMC in PMC slot 1. Secondary Ethernet is configured to the rear.
PMC mode is backwards compatible with the MVME2300/MVME2400 and is accomplished by
simply configuring the on-board jumpers.
The following equipment list is appropriate for use in an MVME5100 system:
❏PMCspan PCI expansion mezzanine module (mates with MVME5100)
❏Peripheral Component Interconnect (PCI) Mezzanine Cards (PMCs) (installed on
an MVME5100 board)
❏RAM500 memory mezzanine modules (installed on an MVME5100 board)
❏VME system enclosure
❏System console terminal
❏Disk drives (and/or other I/O) and controllers
MVME51005E Single Board Computer Installation and Use (6806800A38B)
1
Page 20
1 Hardware Preparation and Installation
Caution
Use ESD
Wrist Strap
❏Operating system (and/or application software)
Unpacking Instructions
Avoid touching areas of integrated circuitry; static discharge can damage these
circuits.
Note
Note
If the shipping carton(s) is/are damaged upon receipt, request that the carrier's agent
be present during the unpacking and inspection of the equipment.
Emerson strongly recommends that you use an antistatic wrist strap and a
conductive foam pad when installing or upgrading a system.
Electronic components, such as disk drives, computer boards and memory
modules, can be extremely sensitive to electrostatic discharge (ESD). After
removing the component from its protective wrapper or from the system, place
the component on a grounded, static-free, and adequately protected working
surface. Do not slide the component over any surface. In the case of a Printed
Circuit Board (PCB), place the board with the component side facing up.
If an ESD station is not available, you can avoid damage resulting from ESD
by wearing an antistatic wrist strap (available locally) that is attached to an
active electrical ground.
A system chassis may not be a suitable grounding source if it is unplugged.
2
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 21
Preparation
This section includes subsections on hardware configuration that may need to be performed
immediately before and after board installation. It includes a brief reminder on setting bits in
control registers, setting jumpers for the appropriate configuration, and other VME data
considerations.
Hardware Configuration
To produce the desired board configuration and to ensure proper operation of the MVME5100,
it may be necessary to perform certain modifications before and after installation. The following
paragraphs discuss the preparation of the MVME5100 hardware components prior to installing
them into a chassis and connecting them.
A software readable header/ switch register (S1) is available on the MVME5100. This switch is
not defined by the hardware and it is shipped in the OFF position, as are all the switches on this
board. This S1 switch is available for user-specific configuration needs via the control registers.
The MVME5100 provides software control over most of its options by setting bits in control
registers. After installing it in a system, you can modify its configuration. For additional
information on the board’s control registers, refer to the MVME5100 Single Board Computer
Programmer's Reference Guide listed in Appendix D, Related Documentation.
1 Hardware Preparation and Installation
It is important to note that some options are not software-programmable. These specific options
are controlled through manual installation or removal of jumpers, and in some cases, the
addition of other interface modules on the MVME5100.
configured jumpers on the MVME5100, and their default settings.
If you are resetting the board jumpers from their default settings, it is important to verify that all
settings are reset properly. For example, the SBC mode requires setting jumpers 4, 10 and 17
for rear Ethernet functions, but it also requires resetting jumpers J6 and J20. Neglecting to
reset J6 and J20 could damage or destroy subsequent PMCs or PrPMCs installed on the base
board at power-up.
The following table lists the manually
Table 1-1. Manually Configured Headers/Jumpers
JumperDescriptionSettingDefault
J1RISCWatch HeaderNone (Factory Use Only)N/A
J2PAL Programming
Header
J4Ethernet Port 2
Selection
(see also J10/J17)
None (Lab Use Only)N/A
For P2 Ethernet Port 2:
Pins 1,2; 3,4; 5,6; 7,8 (set when in
SBC mode, also called 761 mode)NoJumper
For Front Panel Ethernet Port 2:
No Jumpers Installed
Installed
(front
panel)
J6, J20Operation Mode
(Set Both Jumpers)
MVME51005E Single Board Computer Installation and Use (6806800A38B)
J7Flash Memory SelectionPins 1, 2 for Soldered Bank ASockete
Pins 2, 3 for Socketed Bank B
d
Bank B
J10, J17Ethernet Port 2
J15System Controller
J16Soldered Flash
Refer to the section titled Jumper Settings on the next page for additional information.
Note
1. Write protects only outer two 8K boot sectors. Refer to Flash Memory on page 40 for
an complete explanation.
Jumper Settings
Selection
(see also J4)
(VME)
Protection
For Front Panel Ethernet Port 2:
Pins 1, 3 and 2,4 on Both Jumpers
For P2 Ethernet Port 2:
Pins 3, 5 and 4, 6 on Both Jumpers
(set for SBC mode)
Pins 1, 2 for No SCON
Pins 2, 3 for Auto SCON
No Jumper for ALWAYS SCON
Pins 1, 2 Enables Programming of
Flash
Pins 2, 3 Disables Programming of
the upper 64KB of Flash
Front
Panel
Ethernet
Por t 2
Auto
SCON
Flash
Prog.
Enabled
1
Prior to performing the installation instructions, you must ensure that the jumpers are set
properly for your particular configuration. For example, if you are using an IPMC761/MVME761
or IPMC712/MVME712 combination in conjunction with the MVME5100, you must reset the
jumpers for the SBC mode (jumpers J4, J6, J10, J17 and J20). These are factory configured for
the PMC mode. Verify all settings according to the previous table and follow the instructions
below if applicable.
4
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 23
PMC/SBC (761/IPMC) Mode Selection
J10
1 3 5
2 4 6
J17
1 3 5
2 4 6
1 2 3 4 5 6 7 8
PMC I/O Mode
J4
J10
1 3 5
2 4 6
J17
1 3 5
2 4 6
SBC I/O Mode
1 2 3 4 5 6 7 8
J4
For rear panel LAN, jumper
entire 8 pin header on J4
1 Hardware Preparation and Installation
There are five headers associated with the selection of the PMC or SBC mode: J4, J6 J10, J17
and J20. Three of these headers are responsible for secondary Ethernet I/O (J4, J10 and J17)
to either the front panel (PMC mode), or to the P2 connector via J4 (SBC mode). The other two
headers (J6 and J20) ensure proper routing of +/- 12V signal routing. The MVME5100 is set at
the factory for front panel I/O: PMC mode (see Table 1-1). The SBC mode should only be
selected when using one of the IPMC-7xx modules in conjunction with the corresponding
MVME7xx transition module.
Installation Considerations
The MVME5100 draws power from the VMEbus backplane connectors P1 and P2. Connector
P2 is also used for the upper 16 bits of data in 32-bit transfers, and for the upper 8 address lines
in extended addressing mode. The MVME5100 will not function properly without its main board
connected to VMEbus backplane connectors P1 and P2.
Whether the MVME5100 operates as a VMEbus master or as a VMEbus slave, it is configured
for 32 bits of address and 32 bits of data (A32/D32). However, it handles A16 or A24 devices in
the appropriate address ranges. D8 and/or D16 devices in the system must be handled by the
processor software.
If the MVME5100 tries to access off-board resources in a nonexistent location and if the system
does not have a global bus time-out, the MVME5100 waits indefinately for the VMEbus cycle to
complete. This will cause the system to lock up. There is only one situation in which the system
might lack this global bus time-out; that is when the MVME5100 is not the system controller and
there is no global bus time-out elsewhere in the system.
Note
Software can also disable the bus timer by setting the appropriate bits in the Universe
II VMEbus interface.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
5
Page 24
1 Hardware Preparation and Installation
2788 0406
P1P2
J22J24J12J14
J3
J5
J6
J21J23J11J13
XU1XU2
L2
L1
J8
J25
J10 J17
J7
J10
J15
J1
PCI MEZZANINE CARD
10/100 BASE T10/100 BASE T DEBUG
PCI MEZZANINE CARD
SCSI
BUSY
PIB
BUSY
J20
S1
U8
HAWK
ASIC
J9J18J19
J2
Multiple MVME5100 boards may be installed in a single VME chassis; however, each must have
a unique VMEbus address. Other MPUs on the VMEbus can interrupt, disable, communicate
with, and determine the operational status of the processor(s).
Installation
This section discusses the installation of PMCs onto the MVME5100, installation of PMCspan
modules onto the MVME5100, and the installation of the MVME5100 into a VME chassis.
Note
If you have ordered one or more of the optional RAM500 memory mezzanine boards
for the MVME5100, ensure that they are installed on the board prior to proceeding. If
they have not been installed by the factory, and you are installing them yourself, please
refer to Chapter 5, RAM500 Memory Expansion Module, for installation instructions. It
is recommended that the memory mezzainine modules be installed prior to installing
other board accessories, such as PMCs, IPMCs or transition modules.
Figure 1-1. MVME5100 Layout
6
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 25
PMC Modules
Warning
Caution
PMC modules mount on top of the MVME5100. Perform the following steps to install a PMC
module on your MVME5100.
1 Hardware Preparation and Installation
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing and adjusting.
Inserting or removing modules with power applied may result in damage to
module components. Avoid touching areas of integrated circuitry, static
discharge can damage these circuits.
Note
This procedure assumes that you have read the user’s manual that came with your
PMCs.
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to an electrical
ground. Note that the system chassis may not be grounded if it is unplugged. The ESD
strap must be secured to your wrist and to ground throughout the procedure.
2. Perform an operating system shutdown. Turn the AC or DC power off and remove the
AC cord or DC power lines from the system. Remove chassis or system cover(s) as
necessary for access to the VME modules.
3. If the MVME5100 has already been installed in a VMEbus card slot, carefully remove
it as shown in Figure 1-2 and place it with connectors P1 and P2 facing you.
4. Remove the filler plate(s) from the front panel of the MVME5100.
5. Align the PMC module’s mating connectors to the MVME5100’s mating connectors and
press firmly into place.
6. Insert the appropriate number of Phillips screws (typically 4) from the bottom of the
MVME5100 into the standoffs on the PMC module and tighten the screws (refer to
Figure 1-3).
Figure 1-2. MVME5100 Installation and Removal From a VMEbus Chassis
MVME51005E Single Board Computer Installation and Use (6806800A38B)
7
Page 26
1 Hardware Preparation and Installation
Warning
Caution
Figure 1-3. Typical PMC Module Placement on an MVME5100
Primary PMCspan
To install a PMCspan16E-002 PCI expansion module on your MVME5100, perform the
following steps while referring to the figure on the next page:
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing, and adjusting.
Inserting or removing modules with power applied may result in damage to
module components. Avoid touching areas of integrated circuitry, static
discharge can damage these circuits.
Note
This procedure assumes that you have read the user’s manual that was furnished with
your PMCspan and that you have installed the selected PMC modules on to your
PMCspan according to the instructions provided in the PMCspan and PMC manuals.
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to an electrical
ground. Note that the system chassis may not be grounded if it is unplugged. The ESD
strap must be secured to your wrist and to ground throughout the procedure.
2. Perform an operating system shutdown. Turn the AC or DC power off and remove the
AC cord or DC power lines from the system. Remove chassis or system cover(s) as
necessary for access to the VME modules.
3. If the MVME5100 has already been installed in a VMEbus card slot, carefully remove
it as shown in Figure 1-2 and place it with connectors P1 and P2 facing you.
4. Attach the four standoffs to the MVME5100. For each standoff:
8
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 27
2081 9708
PMCspan
MVME5100
1 Hardware Preparation and Installation
– Insert the threaded end into the standoff hole at each corner of the
MVME5100.
– Thread the locking nuts into the standoff tips and tighten.
5. Place the PMCspan on top of the MVME5100. Align the mounting holes in each corner
to the standoffs and align PMCspan connector P4 with MVME5100 connector J25.
Figure 1-4. PMCspan-002 Installation on an MVME5100
6. Gently press the PMCspan and MVME5100 together and verify that P4 is fully seated
in J25.
7. Insert four short screws (Phillips type) through the holes at the corners of the PMCspan
and into the standoffs on the MVME5100. Tighten screws securely.
Secondary
The PMCspan16E-010 PCI expansion module mounts on top of a PMCspan16E-002 PCI
expansion module. To install a PMCspan-010 on your MVME5100, perform the following steps
while referring to the figure on the next page:
PMCspan
MVME51005E Single Board Computer Installation and Use (6806800A38B)
9
Page 28
1 Hardware Preparation and Installation
Warning
Caution
2065 9708
P3
J3
PMCspan16E-010
MVME5100 and
PMCspan16E-002
Assembly
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing, and adjusting.
Inserting or removing modules with power applied may result in damage to
module components. Avoid touching areas of integrated circuitry, static
discharge can damage these circuits.
Note
T
his procedure assumes that you have read the user’s manual that was furnished with
the PMCspan, and that you have installed the selected PMC modules on your
PMCspan according to the instructions provided in the PMCspan and PMC manual
s.
Figure 1-5. PMCspan16E-010 Installation on a PMCspan16E-002
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to an electrical
ground. Note that the system chassis may not be grounded if it is unplugged. The ESD
strap must be secured to your wrist and to ground throughout the procedure.
10
MVME51005E Single Board Computer Installation and Use (6806800A38B)
2. Perform an operating system shutdown. Turn the AC or DC power off and remove the
AC cord or DC power lines from the system. Remove chassis or system cover(s) as
necessary for access to the VME module.
3. If the Primary PMC Carrier Module and MVME5100 assembly is already installed in the
VME chassis, carefully remove it as shown in Figure 1-2 and place it with connectors
P1 and P2 facing you.
Page 29
Warning
Caution
1 Hardware Preparation and Installation
4. Remove four screws (Phillips type) from the standoffs in each corner of the primary PCI
expansion module.
5. Attach the four standoffs from the PMCspan-010 mounting kit to the PMCspan-002 by
screwing the threaded male portion of the standoffs in the locations where the screws
were removed in the previous step.
6. Place the PMCspan-010 on top of the PMCspan-002. Align the mounting holes in each
corner to the standoffs and align PMCspan-010 connector P3 with PMCspan-002
connector J3.
7. Gently press the two PMCspan modules together and verify that P3 is fully seated in
J3.
8. Insert the four screws (Phillips type) through the holes at the corners of PMCspan-010
and into the standoffs on the primary PMCspan-002. Tighten screws securely.
Note
MVME5100
Before installing the MVME5100 into your VME chassis, ensure that the jumpers are configured
properly. This procedure assumes that you have already installed the PMCspan(s) and any
PMCs that you have selected.
Perform the following steps to install the MVME5100 in your VME chassis:
The screws have two different head diameters. Use the screws with the smaller heads
on the standoffs next to VMEbus connectors P1 and P2.
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing, and adjusting.
Inserting or removing modules with power applied may result in damage to
module components. Avoid touching areas of integrated circuitry, static
discharge can damage these circuits.
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to an electrical
ground. Note that the system chassis may not be grounded if it is unplugged. The ESD
strap must be secured to your wrist and to ground throughout the procedure.
2. Perform an operating system shutdown. Turn the AC or DC power off and remove the
AC cord or DC power lines from the system. Remove chassis or system cover(s) as
necessary for access to the VME module.
3. Remove the filler panel from the VMEbus chassis card slot where you are going to
install the MVME5100. If you have installed one or more PMCspan PCI expansion
modules onto your MVME5100, you will need to remove filler panels from one
additional card slot for each PMCspan, above the card slot for the MVME5100.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
– If you intend to use the MVME5100 as system controller, it must
occupy the left-most card slot (slot 1). The system controller must be
in slot 1 to correctly initiate the bus-grant daisy-chain and to ensure
proper operation of the IACK daisy-chain driver.
11
Page 30
1 Hardware Preparation and Installation
– If you do not intend to use the MVME5100 as system controller, it can
occupy any unused card slot.
4. Slide the MVME5100 (and PMCspans if used) into the selected card slot(s). Verify that
the module or module(s) seated properly in the P1 and P2 connectors on the chassis
backplane. Do not damage or bend connector pins.
5. Secure the MVME5100 (and PMCspans if used) in the chassis with the screws in the
top and bottom of its front panel and verify proper contact with the transverse mounting
rails to minimize RF emissions.
Note
Some VME backplanes (such as those used in Emerson Modular Chassis systems)
have an auto-jumpering feature for automatic propagation of the IACK and BG signals.
The step immediately below does not apply to such backplane designs.
6. On the chassis backplane, remove the
GRANT
(BG) jumpers from the header for the card slots occupied by the MVME5100
INTERRUPT ACKNOWLEDGE (IACK) and BUS
and any PMCspan modules.
7. If you intend to use PPCbug interactively, connect the terminal that is to be used as the
Note
PPCbug system console to the
In normal operation, the host CPU controls MVME5100 operation via the VMEbus
DEBUG port on the front panel of the MVME5100.
Universe registers.
8. Replace the chassis or system cover(s) and cable peripherals to the panel connectors
as required.
9. Reconnect the system to the AC or DC power source and turn the system power on.
10. The MVME5100’s green
and the debugger prompt
CPU LED indicates activity as a set of confidence tests is run,
PPC6-Bug> appears.
12
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 31
2Operation
Introduction
This chapter provides operating instructions for the MVME5100 Single Board Computer. It
includes necessary information about powering up the system along with the functionality of the
switches, status indicators and I/O ports on the front panels of the board.
Switches and Indicators
The front panel of the MVME5100, as shown in Figure 1-1, incorporates one dual function
toggle switch
located on the front panel.
(ABT/RST) and two Light-Emitting Diode (LED) status indicators (BFL, CPU)
2
ABT/RST Switch
The ABT/RST switch operates in the following manner: if pressed for less than 5 seconds, the
ABORT function is selected, if pressed for more than 5 seconds, the RESET function is selected.
Each function is described below.
Abort Function
When toggled to ABT, the switch generates an interrupt signal to the processor. The interrupt is
normally used to abort program execution and return control to the debugger firmware located
in the processor and flash memory.
The interrupt signal reaches the processor via ISA bus interrupt line IRQ8. The interrupter
connected to the
Reset Function
When toggled to RST, the switch resets all onboard devices. To generate a reset, the switch
must be depressed for more than five seconds.
The on-board Universe ASIC includes both a global and a local reset driver. When the ASIC
operates as the System Controller, the reset driver provides a global system reset by asserting
the SYSRESET# signal.
ABORT switch is an edge-sensitive circuit, filtered to remove switch bounce.
Additionaly, when the MVME5100 is configured as a System Controller (SCON), a
SYSRESET# signal may be generated by toggling the
up reset, or by a watchdog timeout, or by a control bit in the Miscellaneous Control Register
(MISC_CTL) in the Universe ASIC.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
ABT/RST switch to RST, or by a power-
13
Page 32
2 Operation
Note
SYSRESET# remains asserted for at least 200 ms, as required by the VMEbus
specification.
Status Indicators
There are two Light-Emitting Diode (LED) status indicators located on the MVME5100 front
panel. They are labeled
RST Indicator (DS1)
The yellow BFL LED indicates board failure; this indicator is also illuminated during reset as an
LED test. The
MVME5100 Single Board Computer Programmer’s Reference Guide (V5100A/PG) for
information on these registers.
CPU Indicator (DS2)
The greenCPU LED indicates CPU activity.
Connectors
There are three connectors on the front panel of the MVME5100. Two are bottom-labeled
10/100BASE T and one is labeled DEBUG.
BFL and CPU.
BFL is set if the MODFAIL Register or FUSE Register is set. Refer to the
10/100BASE T Ports
The two RJ-45 ports labeled 10/100BASE T provide the 10BASE T/100BASE TX Ethernet LAN
interface. These connectors are top-labeled with the designation
DEBUG Port
The RJ-45 port labeled DEBUG provides an RS232 serial communications interface, based on
TL16C550 Universal Asynchronous Receiver/Transmitter (UART) controller chip. It is
asynchronous only. For additional information on pin assignments, refer to Chapter 6, Pin
Assignments.
The
DEBUG port may be used for connecting a terminal to the MVME5100 to serve as the
firmware console for the factory installed debugger, PPCBug. The port is configured as follows:
❏8 bits per character
❏1 stop bit per character
❏Parity disabled (no parity)
❏Baud rate = 9600 baud (default baud rate at power-up)
After power-up, the baud rate of the
Por t Format (PF) command.
LAN1 and LAN2.
DEBUG port can be reconfigured by using the debugger’s
14
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 33
System Powerup
STARTUP
INITIALIZATION
MONITOR
BOOTING
POST
Powerup/reset initialization
Initialize devices on the MVME5100
PowerOn Self-Test diagnostics
Firmware-configured boot mechanism
,
Interactive, command-driven on-line PPC
debugger, when terminal connected.
if so configured. Default is no boot.
After you have verified that all necessary hardware preparation is done, that all connections
were made correctly and that the installation is complete, you can power up the system.
Initialization Process
The MPU, hardware and firmware initialization process is performed by the PPCBug firmware
upon system powerup or system reset. The firmware initializes the devices on the MVME5100
in preparation for booting an operating system.
The firmware is shipped from the factory with an appropriate set of defaults. Depending on your
system and specific application, there may or may not be a need to modify the firmware
configuration before you boot the operating system. If it is necessary, refer to Chapter 3,
PPCBug Firmware for additional information on modifying firmware default parameters.
The following flowchart in Figure 2-1 shows the basic initialization process that takes place
during MVME5100 system start-ups.
2Operation
For further information on PPCBug, refer to the following:
❏Chapter 3, PPCBug Firmware
❏Appendix B, Troubleshooting
❏Appendix D, Related Documentation
Figure 2-1. Boot-Up Sequence
MVME51005E Single Board Computer Installation and Use (6806800A38B)
15
Page 34
Page 35
3PPCBug Firmware
Introduction
The PPCBug firmware is the layer of software just above the hardware. The firmware provides
the proper initialization for the devices on the MVME5100 upon powerup or reset.
This chapter describes the basics of the PPCBug and its architecture. It also describes the
monitor (interactive command portion of the firmware), and provides information on using the
PPCBug debugger and the special commands. A complete list of PPCBug commands is also
provided.
For full user information about PPCBug, refer to the PPCBug Firmware Package User’s Manual
and the PPCBug Diagnostics Manual, listed in Appendix D, Related Documentation.
3
PPCBug Overview
The PPCBug debugger firmware is a powerful evaluation and debugging tool for systems built
around Motorola microprocessor. Facilities are available for loading and executing user
programs under complete operator control for system evaluation. The PPCBug provides a high
degree of functionality, user friendliness, portability and ease of maintenance.
The PPCBug also achieves its portability because it was written entirely in the C programming
language, except where necessary to use assembler functions.
PPCBug includes commands for:
❏Display and modification of memory
❏Breakpoint and tracing capabilities
❏A powerful assembler and disassembler useful for patching programs
❏A self-test at powerup feature which verifies the integrity of the system
PPCBug consists of three parts:
❏A command-driven, user-interactive software debugger, described in the PPCBug
Firmware Package User’s Manual, listed in Appendix D, Related Documentation
(hereafter referred to as “debugger” or “PPCBug”).
❏A command-driven diagnostics package for the MVME5100 hardware (hereafter
referred to as “diagnostics”). The diagnostics package is described in the PPCBug
Diagnostics Manual, listed in Appendix D, Related Documentation.
❏A user interface or debug/diagnostics monitor that accepts commands from the
system console terminal.
When using PPCBug, you operate out of either the debugger directory or the diagnostic
directory.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
17
Page 36
3 PPCBug Firmware
❏If you are in the debugger directory, the debugger prompt PPC6-Bug> is
displayed and you have all of the debugger commands at your disposal.
❏If you are in the diagnostic directory, the diagnostic prompt PPC6-Diag>is
displayed and you have all of the diagnostic commands at your disposal as well
as all of the debugger commands.
Because PPCBug is command-driven, it performs its various operations in response to user
commands entered at the keyboard. When you enter a command, PPCBug executes the
command and the prompt reappears. However, if you enter a command that causes execution
of user target code (for example, GO), then control may or may not return to PPCBug,
depending on the outcome of the user program.
Implementation and Memory Requirements
PPCBug is written largely in the C programming language, providing benefits of portability and
maintainability. Where necessary, assembly language has been used in the form of separately
compiled program modules containing only assembler code.
Physically, PPCBug is contained in two socketed 32-pin PLCC Flash devices that together
provide 1MB of storage. The executable code is checksummed at every power-on or reset
firmware entry. The result (which includes a precalculated checksum contained in the flash
devices), is verified against the expected checksum.
PPCBug requires a maximum of 768KB of read/write memory. The debugger allocates this
space from the top of memory. For example, a system containing 64MB (0x04000000) of
read/write memory will place the PPCBug memory locations 0x03F40000 to 0x3FFFFFF.
Additionally, the first 1MB of DRAM is reserved for the exception vector table and stack.
Using PPCBug
PPCBug is command-driven; it performs its various operations in response to commands that
you enter at the keyboard. When the
is ready to accept debugger commands. When the
the debugger is ready to accept diagnostics commands. To switch from one mode to the other,
enter SD.
What you enter is stored in an internal buffer. Execution begins only after you press the Return
or Enter key. This allows you to correct entry errors, if necessary, with the control characters
described in the PPCBug Firmware Package User’s Manual, listed in Appendix D, Related
Documentation.
After the debugger executes the command, the prompt reappears. However, depending on
what the user program does, if the command causes execution of a user target code (that is,
GO), then control may or may not return to the debugger.
PPC6-Bug> prompt appears on the screen, the debugger
PPC6-Diag> prompt appears on the screen,
18
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 37
For example, if a breakpoint has been specified, then control returns to the debugger when the
breakpoint is encountered during execution of the user program. Alternately, the user program
could return to the debugger by means of the System Call Handler routine RETURN (described
in the PPCBug Firmware Package User’s Manual). For more about this, refer to the GD, GO and
GT command descriptions in the PPCBug Firmware Package User’s Manual, listed in Appendix
D, Related Documentation .
A debugger command is made up of the following parts:
❏The command name, either uppercase or lowercase (for example, MD or md)
❏Any required arguments, as specified by command
❏At least one space before the first argument. Precede all other arguments with
either a space or comma.
❏One or more options. Precede an option or a string of options with a semicolon (;).
If no option is entered, the command’s default option conditions are used.
Hardware and Firmware Initialization
3 PPCBug Firmware
The debugger performs the hardware and firmware initialization process. This process occurs
each time the MVME5100 is reset or powered up. The steps listed below are a high-level
outline; be aware that not all of the detailed steps are listed.
1. Sets MPU.MSR to known value.
2. Invalidates the MPU's data/instruction caches.
3. Clears all segment registers of the MPU.
4. Clears all block address translation registers of the MPU.
5. Initializes the MPU-bus-to-PCI-bus bridge device.
6. Initializes the PCI-bus-to-ISA-bus bridge device.
7. Calculates the external bus clock speed of the MPU.
8. Delays for 750 milliseconds.
9. Determines the CPU base board type.
10. Sizes the local read/write memory (that is, DRAM).
11. Initializes the read/write memory controller. Sets base address of memory to
0x00000000.
12. Retrieves the speed of read/write memory.
13. Initializes the read/write memory controller with the speed of read/write memory.
14. Retrieves the speed of read only memory (that is, Flash).
15. Initializes the read only memory controller with the speed of read only memory.
16. Enables the MPU's instruction cache.
17. Copies the MPU's exception vector table from 0xFFF00000 to 0x00000000.
18. Verifies MPU type.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
19
Page 38
3 PPCBug Firmware
19. Enables the superscalar feature of the MPU (superscalar processor boards only).
20. Verifies the external bus clock speed of the MPU.
21. Determines the debugger's console/host ports and initializes the PC16550A.
22. Displays the debugger's copyright message.
23. Displays any hardware initialization errors that may have occurred.
24. Checksums the debugger object and displays a warning message if the checksum
25. Displays the amount of local read/write memory found.
26. Verifies the configuration data that is resident in NVRAM and displays a warning
27. Calculates and displays the MPU clock speed, verifies that the MPU clock speed
28. Displays the BUS clock speed, verifies that the BUS clock speed matches the
failed to verify.
message if the verification failed.
matches the configuration data, and displays a warning message if the verification fails.
configuration data,and displays a warning message if the verification fails.
29. Probes PCI bus for supported network devices.
30. Probes PCI bus for supported mass storage devices.
31. Initializes the memory/IO addresses for the supported PCI bus devices.
32. Executes Self-Test, if so configured. (Default is no Self-Test).
33. Extinguishes the board fail LED, if Self-Test passed and outputs any warning
messages.
34. Executes boot program, if so configured. (Default is no boot.)
35. Executes the debugger monitor (that is, issues the
Default Settings
The following sections provide information pertaining to the firmware settings of the
MVME5100. Default (factory set) Environment (ENV) commands are provided to inform you on
how the MVME5100 was configured at the time it left the factory.
CNFG - Configure Board Information Block
Use this command to display and configure the Board Information Block, which is resident
within the NVRAM. This data block contains various elements detailing specific operational
parameters of the MVME5100. The structure for the board is shown in the following example:
PPC6-Bug> prompt).
Board (PWA) Serial Number = MOT00xxxxxxx
Board Identifier= MVME5100
Artwork (PWA) Identifier= 01-W3518FxxB
MPU Clock Speed= 450
Bus Clock Speed= 100
20
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 39
Ethernet Address= 0001AF2A0A57
Primary SCSI Identifier= 07
System Serial Number= nnnnnnnn
System Identifier= Emerson MVME5100
License Identifier= nnnnnnnn
The Board Information Block parameters shown above are left-justified character (ASCII)
strings padded with space characters.
The Board Information Block is factory-configured before shipment. There is no need to modify
block parameters unless the NVRAM is corrupted.
Refer to the PPCBug Firmware Package User's Manual, listed in Appendix D, Related
Documentationfor a description of CNFG and examples.
ENV - Set Environment
3 PPCBug Firmware
Use the ENV command to view and/or configure interactively all PPCBug operational
parameters that are kept in Non-Volatile RAM (NVRAM).
Refer to the PPCBug Firmware Package User's Manual for a description of the use of ENV.
Additional information on registers in the Universe ASIC that affect these parameters is
contained in your MVME5100 Programmer’s Reference Guide, listed in Appendix D, Related
Documentation.
Listed and described below are the parameters that you can configure using ENV. The default
values shown were those in effect when this publication went to print.
Configuring the PPCBug Parameters
The parameters that can be configured using ENV are:
Bug or System environment [B/S] = B?
BBug is the mode where no system type of
support is displayed. However, system-related
items are still available. (Default)
SSystem is the standard mode of operation, and is
the default mode if NVRAM should fail. System
mode is defined in the PPCBug Firmware
Package User's Manual listed in Appendix D,
Related Documentation.
Maximum Memory Usage (MB,0=AUTO) = 1?
This parameter specifies the maximum number of megabytes the bug is allowed to use.
Allocation begins at the top of physical memory and expands downward as more memory is
required until the maximum value is reached.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
21
Page 40
3 PPCBug Firmware
If a value of zero is specified, memory will continue to be increased as needed until half of the
available memory is consumed (that is, 32MB in a 64MB system). This mode is useful for
determining the full memory required for a specific configuration. Once this is determined, a
hard value may be given to the parameter and it is guaranteed that no memory will be used over
this amount.
The default value for this parameter is one.
Note
The bug does not automatically acquire all of the memory it is allowed. It accumulates
memory as necessary in one megabyte blocks.
Field Service Menu Enable [Y/N] = N?
YDisplay the field service menu.
NDo not display the field service menu. (Default)
Remote Start Method Switch [G/M/B/N] = B?
The Remote Start Method Switch is used when the MVME5100 is cross-loaded from another
VME-based CPU in order to start execution of the cross-loaded program.
GUse the Global Control and Status Register to
pass and start execution of the cross-loaded
program.
MUse the Multiprocessor Control Register (MPCR)
in shared RAM to pass and start execution of the
cross-loaded program.
BUse both the GCSR and the MPCR methods to
pass and start execution of the cross-loaded
program. (Default)
22
NDo not use any Remote Start Method.
Probe System for Supported I/O Controllers [Y/N] = Y?
YAccesses will be made to the appropriate system
buses (for example, VMEbus, local MPU bus) to
determine the presence of supported controllers.
(Default)
NAccesses will not be made to the VMEbus to
determine the presence of supported controllers.
Auto-Initialize of NVRAM Header Enable [Y/N] = Y?
YNVRAM (PReP partition) header space will be
initialized automatically during board
initialization, but only if the PReP partition fails a
sanity check. (Default)
NNVRAM header space will not be initialized
automatically during board initialization.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 41
Network PReP-Boot Mode Enable [Y/N] = N?
YEnable PReP-style network booting (same boot
image from a network interface as from a mass
storage device).
NDo not enable PReP-style network booting.
(Default)
Negate VMEbus SYSFAIL* Always [Y/N] = N?
3 PPCBug Firmware
YNegate the VMEbus SYSFAIL
∗ signal during
board initialization.
NNegate the VMEbus SYSFAIL
∗ signal after
successful completion or entrance into the bug
command monitor. (Default)
The time (in seconds) that a boot from the NVRAM boot list will delay before starting the boot.
The purpose for the delay is to allow you the option of stopping the boot by use of the
key. The time value is from 0-255 seconds. (Default = 5 seconds)
Auto Boot Enable [Y/N] = N?
YThe Autoboot function is enabled.
NThe Autoboot function is disabled. (Default)
Auto Boot at powerup only [Y/N] = N?
boot-path GEV at powerup reset only.
fw-boot-path GEV at any reset. (Default)
BREAK
YAutoboot is attempted at powerup reset only.
NAutoboot is attempted at any reset. (Default)
Auto Boot Scan Enable [Y/N] = Y?
YIf Autoboot is enabled, the Autoboot process
attempts to boot from devices specified in the
scan list (for example,
FDISK/CDROM/TAPE/HDISK). (Default)
NIf Autoboot is enabled, the Autoboot process
uses the Controller LUN and Device LUN to boot.
Auto Boot Scan Device Type List = FDISK/CDROM/TAPE/HDISK?
This is the listing of boot devices displayed if the Autoboot Scan option is enabled. If you modify
the list, follow the format shown above (uppercase letters, using forward slash as separator).
Auto Boot Controller LUN = 00?
Refer to the PPCBug Firmware Package User's Manual for a listing of disk/tape controller
modules currently supported by PPCBug. (Default = 0x00)
Auto Boot Device LUN = 00?
Refer to the PPCBug Firmware Package User's Manual listed in Appendix D, Related
Documentationfor a listing of disk/tape devices currently supported by PPCBug. (Default =
0x00)
Auto Boot Partition Number = 00?
Identifies which disk “partition” is to be booted, as specified in the PowerPC Reference Platform
(PReP) specification. If set to zero, the firmware will search the partitions in order (1, 2, 3, 4)
until it finds the first “bootable” partition. That is then the partition that will be booted. Other
acceptable values are 1, 2, 3 or 4. In these four cases, the partition specified will be booted
without searching.
24
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 43
3 PPCBug Firmware
Auto Boot Abort Delay = 7?
The time in seconds that the Autoboot sequence will delay before starting the boot. The
purpose for the delay is to allow you the option of stopping the boot by use of the
The time value is from 0-255 seconds. (Default = 7 seconds)
Auto Boot Default String [NULL for an empty string] = ?
You may specify a string (filename) which is passed on to the code being booted. The maximum
length of this string is 16 characters. (Default = null string)
ROM Boot Enable [Y/N] = N?
YThe ROMboot function is enabled.
NThe ROMboot function is disabled. (Default)
ROM Boot at power-up only [Y/N] = Y?
YROMboot is attempted at power-up only.
(Default)
BREAK key.
NROMboot is attempted at any reset.
ROM Boot Enable search of VMEbus [Y/N] = N?
YVMEbus address space, in addition to the usual
areas of memory, will be searched for a
ROMboot module.
NVMEbus address space will not be accessed by
ROMboot. (Default)
ROM Boot Abort Delay = 5?
The time (in seconds) that the ROMboot sequence will delay before starting the boot. The
purpose for the delay is to allow you the option of stopping the boot by use of the
BREAK key.
The time value is from 0-255 seconds. (Default = 5 seconds)
ROM Boot Direct Starting Address = FFF00000?
The first location tested when PPCBug searches for a ROMboot module. (Default =
0xFFF00000)
ROM Boot Direct Ending Address = FFFFFFFC?
The last location tested when PPCBug searches for a ROMboot module. (Default =
0xFFFFFFFC)
Network Auto Boot Enable [Y/N] = N?
YThe Network Auto Boot (NETboot) function is
enabled.
NThe NETboot function is disabled. (Default)
MVME51005E Single Board Computer Installation and Use (6806800A38B)
25
Page 44
3 PPCBug Firmware
!
Caution
Network Auto Boot at power-up only [Y/N] = N?
YNETboot is attempted at powerup reset only.
NNETboot is attempted at any reset. (Default)
Network Auto Boot Controller LUN = 00?
Refer to the PPCBug Firmware Package User's Manual, listed in Appendix D, Related
Documentation for a listing of network controller modules currently supported by PPCBug.
(Default = 0x00)
Network Auto Boot Device LUN = 00?
Refer to the PPCBug Firmware Package User's Manual, listed in Appendix D, Related
Documentation for a listing of network controller modules currently supported by PPCBug.
(Default = 0x00)
Network Auto Boot Abort Delay = 5?
The time in seconds that the NETboot sequence will delay before starting the boot. The
purpose for the delay is to allow you the option of stopping the boot by use of the
The time value is from 0-255 seconds. (Default = 5 seconds)
BREAK key.
Network Auto Boot Configuration Parameters Offset (NVRAM) = 00001000?
The address where the network interface configuration parameters are to be saved/retained in
NVRAM; these parameters are the necessary parameters to perform an unattended network
boot. A typical offset might be 0x1000, but this value is application-specific. (Default =
0x00001000)
If you use the NIOT debugger command, these parameters need to be saved
somewhere in the offset range 0x00001000 through 0x000016F7. The NIOT
parameters do not exceed 128 bytes in size. The setting of this ENV pointer
determines their location. If you have used the same space for your own
program information or commands, they will be overwritten and lost.
You can relocate the network interface configuration parameters in this space
by using the ENV command to change the Network Auto Boot Configuration
Parameters Offset from its default of 0x00001000 to the value you need to be
clear of your data within NVRAM.
Memory Size Enable [Y/N] = Y?
YMemory will be sized for SelfTest diagnostics.
(Default)
NMemory will not be sized for SelfTest diagnostics.
Memory Size Starting Address = 00000000?
The default Starting Address is 0x00000000.
26
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 45
3 PPCBug Firmware
Memory Size Ending Address = 02000000?
The default Ending Address is the calculated size of local memory. If the memory start is
changed from 0x0x00000000, this value will also need to be adjusted.
DRAM Speed in NANO Seconds = 15?
The default setting for this parameter will vary depending on the speed of the DRAM memory
parts installed on the board. The default is set to the slowest speed found on the available banks
of DRAM memory.
ROM Bank A Access Speed (ns) = 80?
This defines the minimum access speed for the Bank A Flash Device(s) in nanoseconds.
ROM Bank B Access Speed (ns) = 70?
This defines the minimum access speed for the Bank B Flash Device(s) in nanoseconds.
DRAM Parity Enable [On-Detection/Always/Never - O/A/N] = O?
This parameter also applies to enabling ECC for DRAM.
OL2 Cache parity is enabled upon detection. (Default)
AL2 Cache parity is always enabled.
NL2 Cache parity is never enabled.
PCI Interrupts Route Control Registers (PIRQ0/1/2/3) = 0A0B0E0F?
Initializes the PIRQx (PCI Interrupts) route control registers in the IBC (PCI/ISA bus bridge
controller). The ENV parameter is a 32-bit value that is divided by 4 fields to specify the values
for route control registers PIRQ0/1/2/3. The default is determined by system type as shown:
PIRQ0=0A, PIRQ1=0B, PIRQ2=0E, PIRQ3=0F.
LED/Serial Startup Diagnostic Codes
These codes can be displayed at key points in the initialization of the hardware devices. The
codes are enabled by an ENV parameter.
Serial Startup Code Master Enable [Y/N]=N?
Should the debugger fail to come up to a prompt, the last code displayed will indicate how far
the initialization sequence had progressed before stalling.
Serial Startup Code LF Enable [Y/N]=N?
MVME51005E Single Board Computer Installation and Use (6806800A38B)
27
Page 46
3 PPCBug Firmware
A line feed can be inserted after each code is displayed to prevent it from being overwritten by
the next code. This is also enabled by an ENV parameter:
The list of LED/serial codes is included in the section on MPU, Hardware, and Firmware
Initialization found in Chapter 1 of the PPCBug Firmware Package User’s Manual, listed in
Appendix D, Related Documentation.
Configuring the VMEbus Interface
ENV asks the following series of questions to set up the VMEbus interface for the MVME5100.
To perform this configuration, you should have a working knowledge of the Universe ASIC as
described in your MVME5100 Programmer’s Reference Guide. Also, refer to the Tundra Universe II Users Manual, as listed in Appendix D, Related Documentation for a detailed
description of VMEbus addressing. In general, the PCI slave images describe the VME master
addresses, while the VMEbus slave describes the VME slave addresses.
VME3PCI Master Master Enable [Y/N] = Y?
YSet up and enable the VMEbus Interface.
(Default)
NDo not set up or enable the VMEbus Interface.
PCI Slave Image 0 Control = 00000000?
The configured value is written into the LSI0_CTL register of the Universe chip.
PCI Slave Image 0 Base Address Register = 00000000?
The configured value is written into the LSI0_BS register of the Universe chip.
The configured value is written into the VSI0_BD register of the Universe chip. The value is the
same as the Local Memory Found number already displayed.
The configured value is written into the VSI3_TO register of the Universe chip.
PCI Miscellaneous Register = 10000000?
The configured value is written into the LMISC register of the Universe chip.
Special PCI Slave Image Register = 00000000?
The configured value is written into the SLSI register of the Universe chip.
Master Control Register = 80C00000?
The configured value is written into the MAST_CTL register of the Universe chip.
Miscellaneous Control Register = 52060000?
The configured value is written into the MISC_CTL register of the Universe chip.
User AM Codes = 00000000?
The configured value is written into the USER_AM register of the Universe chip.
Firmware Command Buffer
Firmware Command Buffer Enable = N?
YEnables Firmware Command Buffer execution.
NDisables Firmware Command Buffer execution
(Default).
Firmware Command Buffer Delay = 5?
Defines the number of seconds to wait before firmware begins executing the startup commands
in the startup command buffer. During this delay, you may press any key to prevent the
execution of the startup command buffer.
The default value of this parameter causes a startup delay of 5 seconds.
Firmware Command Buffer:
30
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 49
3 PPCBug Firmware
['NULL' terminates entry]?
The Firmware Command Buffer contents contain the BUG commands which are executed upon
firmware startup.
BUG commands you place into the command buffer should be typed just as you enter the
commands from the command line.
The string 'NULL' on a new line terminates the command line entries.
All PPCBug commands, except for the following, may be used within the command buffer: DU, ECHO, LO, TA, VE.
Note
Interactive editing of the startup command buffer is not supported. If changes are
needed to an existing set of startup commands, a new set of commands with changes
must be reentered.
Standard Commands
The individual debugger commands are listed in the following table. The commands are
described in detail in the PPCBug Firmware Package User’s Manual, listed in Appendix D,
Related Documentation.
Note
Table 3-1. Debugger Commands
CommandDescription
ASAssembler
BCBlock of Memory Compare
BFBlock of Memory Fill
You can list all the available debugger commands by entering the Help (HE) command
alone. You can view the syntax for a particular command by entering HE and the
command mnemonic, as listed below.
BIBlock of Memory Initialize
BMBlock of Memory Move
BSBlock of Memory Search
BRBreakpoint Insert
BVBlock of Memory Verify
CACHEModify Cache State
CMConcurrent Mode
CNFGConfigure Board Information Block
CSChecksum a Block of data
CSARPCI Configuration Space READ Access
MVME51005E Single Board Computer Installation and Use (6806800A38B)
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 51
Table 3-1. Debugger Commands (continued)
CommandDescription
M“Alias” for “MM” Command
MAMacro Define/Display
MAEMacro Edit
MALEnable Macro Expansion Listing
MARMacro Load
MAWMacro Save
MDMemory Display
MDSMemory Display (Sector)
MENUSystem Menu
MMMemory Modify
MMDMemory Map Diagnostic
3 PPCBug Firmware
MMGRAccess Memory Manager
MSMemory Set
MWMemory Write
NABAutomatic Network Bootstrap Operating System
NAPNap MPU
NBHNetwork Bootstrap Operating System and Halt
NBONetwork Bootstrap Operating System
NIOCNetwork I/O Control
NIOPNetwork I/O Physical
NIOTI/O “Teach” for Configuring Network Controller
NOBRBreakpoint Delete
NOCMNo Concurrent Mode
NOMAMacro Delete
NOMALDisable Macro Expansion Listing
NOPAPrinter Detach
NOPFPort Detach
NORBNo ROM Boot
NOSYMDetach Symbol Table
NPINGNetwork Ping
OFOffset Registers Display/Modify
PAPrinter Attach
PBOOTBootstrap Operating System
MVME51005E Single Board Computer Installation and Use (6806800A38B)
33
Page 52
3 PPCBug Firmware
!
Caution
Table 3-1. Debugger Commands (continued)
CommandDescription
PFPort Format
PFLASHProgram FLASH Memory
PSPut RTC into Power Save Mode
RBROMboot Enable
RDRegister Display
REMOTERemote
RESETCold/Warm Reset
RLRead Loop
RMRegister Modify
RSRegister Set
RUNMPU Execution/Status
SDSwitch Directories
SETSet Time and Date
SROMSROM Examine/Modify
STSelf Test
SYMSymbol Table Attach
SYMSSymbol Table Display/Search
TTrace
TATe r m in al A t t a c h
TIMEDisplay Time and Date
TMTransparent Mode
TTTrace to Temporary Breakpoint
VEVerify S-Records Against Memory
VERRevision/Version Display
WLWrite Loop
Although a command (PFLASH) to allow the erasing and reprogramming of
Flash memory is available to you, keep in mind that reprogramming any portion
of Flash memory will erase everything currently contained in Flash, including
the PPCBug debugger, if the target address addresses the bank in which it
resides.
Diagnostics
The PPCBug hardware diagnostics are intended for testing and troubleshooting the
MVME5100.
34
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 53
3 PPCBug Firmware
In order to use the diagnostics, you must switch to the diagnostic directory. You may switch
between directories by using the SD (Switch Directories) command. You may view a list of the
commands in the directory that you are currently in by using the HE (Help) command.
If you are in the debugger directory, the debugger prompt
debugger commands are available. Diagnostics commands cannot be entered at the PPC6-Bug> prompt.
If you are in the diagnostic directory, the diagnostic prompt
the debugger and diagnostic commands are available.
PPCBug’s diagnostic test groups are listed in Table 3-2. Note that not all tests are performed
on the MVME5100. Using the HE command, you can list the diagnostic routines available in
each test group. Refer to the PPCBug Diagnostics Manual, listed in Appendix D, Related
Documentation for complete descriptions of the diagnostic routines and instructions on how to
MVME51005E Single Board Computer Installation and Use (6806800A38B)
35
Page 54
3 PPCBug Firmware
Notes
1. You may enter command names in either uppercase or lowercase.
2. Some diagnostics depend on restart defaults that are set up only in a particular
restart mode. Refer to the documentation on a particular diagnostic for the correct
mode.
3. Test Sets marked with an asterisk (*) are not available on the MVME5100 (unless
an IPMC712 or IPMC761 is mounted). The ISABRDGE test is only performed if an
IPMC761 is mounted on the MVME5100. If the MVME5100 is operating in PMC mode
(IPMC761 is not mounted), then the test suite is bypassed.
36
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 55
4Functional Description
Introduction
This chapter provides a functional description for the MVME5100 Single Board Computer. The
MVME5100 is a high-performance product featuring PowerPlus II architecture with a choice of
PowerPC processors—either the MPC7410 with AltiVec™ technology for algorithmic intensive
computations or the low-power MPC750.
The MVME5100 incorporates a highly optimized PCI interface and memory controller enabling
up to 582MB memory read bandwidth and 640MB burst write bandwidth.
The optimization of the memory bus is as important as optimization of the system bus in order
to achieve maximum system performance. The MVME5100’s advanced PowerPlus II
Architecture supports full PCI throughput of 264MB without starving the CPU of its memory.
4
Additional features of the MVME5100 include dual Ethernet ports, dual serial ports and up to
17MB of Flash.
Features Summary
The table below lists the general features for the MVME5100. Refer to Appendix A,
Specifications, for additional product specifications and information.
Table 4-1. MVME5100 General Features
FeatureSpecification
Microprocessors and
Bus Clock Frequency
L2 Cache (Optional)1MB (MPC750) or 2MB (MPC7410) using burst-mode
MemoryEEPROM, on-board programmable
Main Memory
(SDRAM)
NVRAM32KB (4KB available for users)
Memory ControllerHawk System Memory Controller (SMC)
PCI Host BridgeHawk PCI Host Bridge (PHB)
Interrupt ControllerHawk Multi-Processor Interrupt Controller (MPIC)
MPC7410 @400 or 500 MHz Internal Clock Frequency
MPC750 @450 MHz Internal Clock Frequency
Bus Clock Frequency up to 100 MHz
SRAM modules.
1MB via two 32-pin PLCC/CLCC sockets;
16MB Surface Mount
PC100 ECC SDRAM with 100 MHz bus
32MB to 512MB on board, expandable to
1.5GB via RAM500 memory mezzanine
MVME51005E Single Board Computer Installation and Use (6806800A38B)
37
Page 56
4 Functional Description
FeatureSpecification
Peripheral SupportDual 16550-Compatible Asynchronous Serial Port’s
VMEbusTundra Universe Controller, 64-bit PCI
PCI/PMC/ExpansionTwo 32/64-bit PMC Slots With Front-Panel I/O,
MiscellaneousCombined RESET and ABORT Switch
Form Factor6U VME
Routed to the Front Panel RJ45 Connnector (COM1)
and On-Board Header (COM2)
Dual Ethernet Interfaces, one routed to the Front
Panel RJ45, One Routed to the Front Panel RJ45 or
Optionally Routed to P2, RJ45 on MVME761
Programmable Interrupter & Interrupt Handler
Programmable DMA Controller With Link List Support
Full System Controller Functions
P2 Rear I/O (MVME2300 Routing)
One PCI Expansion Connector (for the PMCSpan)
Status LEDs
Features Descriptions
General
As stated earlier, the MVME5100 is a high-performance VME based Single Board Computer
featuring PowerPlus II architecture with a choice of processors. The board can be equipped with
either the MPC7410 processor with AltiVec™ technology for algorithmic intensive computations
or with the low-power MPC750 for low-power or field applications.
Designed to meet the needs of OEMs servicing the military and aerospace, industrial
automation and semiconductor process equipment market segments, the MVME5100 is
available in both commercial grade (0° to 55° C) and industrial grade (–20° to 71° C)
temperatures.
The MVME5100 has two Input/Output (I/O) modes of operation: PMC and SBC (also called 761
mode or IPMC mode). In PMC mode, it is fully backwards compatible with previous generation
dual PMC products such as the MVME2300 and MVME2400.
In the SBC mode, the MVME5100 is backwards compatible with the corresponding Emerson
MVME712 or MVME761 transition board originated for use with previous generation singleboard computer products, such as the MVME2600 and MVME2700.
It is important to note that MVME712 and MVME761 compatibility is accomplished with the
addition of the corresponding IPMC712 or IPMC761 (an optional add-on PMC card). The
IPMC712 and IPMC761 provides rear I/O support for one single-ended ultra-wide SCSI device,
one parallel port, four serial ports (two synchronous for 761 and one for 712, and two
asynchronous/synchronous for 761 and three for 712) and I
ASIC. This multi-function PMC card is offered with the MVME5100 as a factory bundled
configuration.
2
C functionality through the Hawk
The following diagram illustrates the architecture of the MVME5100 Single Board Computer.
38
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 57
Processor
MPC7410
100 MHz MPC604 Processor
Bus
VME P1
PCI Expansion
System
Registers
FLASH
1MB to 17MB
Clock
Generator
VME Bridge
Universe 2
Ethernet 1
10/100TX
Buffers
RTC/NVRAM/WD
M48T37V
TL16C550
UART/9pin
Front Panel
VME P2
RJ45
PMC FrontI/O
PMC Front I/O
SLot1
Slot2
2,64-bit PMC Slots
L2 Cache
1M,2M
Ethernet 2
10/100TX
10/100TX
RJ45
10/100TX
Hawk X-bus
RJ45
DEBUG
planar
712/761 or PMC
IPMC761 RECEPTACLE
Mezzanine SDRAM
32MB to 512MB
SDRAM
32MB to 512MB
HDR
Hawk Asic
System Memory Controller (SMC)
and PCI Host Bridge (PHB)
TL16C550
UART
33MHz 32/64-bit PCI
Local Bus
MPC750
4 Functional Description
Figure 4-1. MVME5100 Block Diagram
Processor
The MVME5100 incorporates a BGA foot print that supports both the MCP7410 and the
MCP75x processors. The maximum external processor bus speed is 100 MHz.
Note
The MCP7410 is configured to operate only with the PowerPC 60xbus interface.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
39
Page 58
4 Functional Description
System Memory Controller and PCI Host Bridge
The on-board Hawk ASIC provides the bridge function between the processor’s bus and the
PCI bus. It provides 32-bit addressing and 64-bit data; however, 64-bit addressing (dual
address cycle) is not supported. The ASIC also supports various processor external bus
frequencies up to
100 MHz.
There are four programmable map decoders for each direction to provide flexible address
mappings between the processor and the PCI bus. The ASIC also provides an Multi-Processor
Interrupt Controller (MPIC) to handle various interrupt sources. They are: four MPIC timer
interrupts, interrupts from all PCI devices and two software interrupts.
Memory
The following subsections describe various memory capabilities on the MVME5100 including
Flash memory and ECC SDRAM memory.
Flash Memory
The MVME5100 contains two banks of Flash memory. Bank B consists of two 32-pin devices
which can be populated with 1MB of Flash memory (only 8-bit writes are supported for this
bank). Refer to the application note following for more write-protect information on this product.
Bank A has 4 16-bit Smart Voltage FLASH SMT devices. With 32Mbit flash devices, the flash
memory size is 16MB. Note that only 32-bit writes are supported for this bank of flash memory.
The Write Protect function provides a hardware method of protecting certain boot sectors. If the
system asserts V IL (low signal) on the WP#/ACC pin, the device disables the program and
erase capability, independently of whether those sectors were protected or unprotected using
the method described in the Sector/Sector Block Protection and Unprotection of the AMD
datasheet. The two outermost 8Kbyte boot sectors are the two sectors containing the lowest
addresses in a bottom-boot-configured device, or the two sectors containing the highest
addresses in a top-boot-configured device.
The aforementioned implemented device (at the time of this printing is the only qualified Flash
device used on this product) is a top-boot device, and as such, the write protected area is in the
upper 16KB of each device. Since it uses 4 devices for the soldered Flash bank, the write
protected region corresponds to the upper 64KB of the soldered Flash memory map. Thus the
address range of $F4FF 0000 to F4FF FFFF is the write protected region when the J16 header
is jumpered across pins 2 and 3.
Application Note: For Am29DL322C or Am29DL323C, 32Megabit (4M x 8-Bit/2M x
16-bit) CMOS 3.0 Volt-only Flash Memory.
If PPCBug tries to write to those write-protected address areas when
pins 2-3 on J16 are set, the command will simply not finish (i.e., erase sector function stops at
$F4FF 0000).
40
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 59
ECC SDRAM Memory
The MVME5100’s on-board memory and optional memory mezzanines allow for a variety of
memory size options. Memory size can be 64 or 512MB for a total of 1.5GB on-board and
mezzanine ECC memory. The memory is controlled by the hardware which provides single-bit
error correction and double-bit error detection (ECC is calculated over 72-bits).
Either 1 or 2 mezzanines can be installed. Each mezzanine will add 1 bank of SDRAM memory
of 256 or 512MB. A total of 1GB of mezzanine memory can be added. Refer to Chapter 5,
RAM500 Memory Expansion Module for more information.
P2 Input/Output (I/O) Modes
The MVME5100 has two P2 I/O modes (SBC and PMC) that are user- configurable with
jumpers on the board (J6 and J20). The jumpers route the on-board Ethernet port 2 to row C of
the P2 connector. Ethernet jumpers (J4, J10, and J17) should also be configured.
The SBC mode (also called 761 or IPMC mode) are backwards compatible with the
corresponding MVME712 and MVME761 transition cards and the P2 adapter card (excluding
PMC I/O routing) used on the MVME2600/2700. The SBC mode is accomplished by configuring
the on-board jumpers and attaching an IPMC712 or IPMC761 PMC in PMC slot 1 of the
MVME5100.
4 Functional Description
PMC mode is backwards compatible with the MVME2300/MVME2400. PMC mode is
accomplished by simply configuring the on-board jumpers.
Note
Refer to Chapter 6, Pin Assignments for P2 Input/Output Mode jumper settings.
Input/Output Interfaces
The following subsections describe the major I/O interfaces on the MVME5100 including
Ethernet, VMEbus, asynchronous communications ports, real-time clock/NVRAM/Watchdog
Timer, other timer interfaces, interrupt routing capabilities and IDSEL routing capabilities.
Ethernet Interface
The MVME5100 incorporates dual Ethernet interfaces (Port 1 and Port 2) via two Fast Ethernet
PCI controller chips.
The Port 1 10BaseT/100BaseTX interface is routed to the front panel. The Port 2 Ethernet
interface is routed to either the front panel or the P2 connector as configured by jumpers. The
front panel connectors are of the RJ45 type.
Every board is assigned two Ethernet Station Addresses. The address is $0001AFXXXXX
where XXXXX is the unique number assigned to each interface. Each Ethernet Station Address
is displayed on a label attached to the PMC front-panel keep-out area.
In addition, LAN 1 Ethernet address is stored in the configuration area of the NVRAM specified
by the Boot ROM and in SROM.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
41
Page 60
4 Functional Description
VMEbus Interface
The VMEbus interface is provided by the Universe II ASIC. Refer to the Universe II User’s
Manual, as listed in Appendix D, Related Documentation, for additional information.
Asynchronous Communications
The MVME5100 provides dual asynchronous debug ports. The serial signals COM1 and COM2
are routed through appropriate EIA-232 drivers and receivers to an RJ45 connector on the front
panel (COM1) and an on-board connector (COM2). The external signals are ESD protected.
Real-Time Clock & NVRAM & Watchdog Timer
The MVME5100’s design incorporates 32KB of non-volatile static RAM, along with a real-time
clock and a watchdog function an integrated device. Refer to the M48T37V CMOS 32Kx8 Timekeeper SRAM Data Sheet, as referenced in Appendix D, Related Documentation for
additional programming and engineering information.
Timers
Timers and counters on the MVME5100 are provided by the board’s hardware (Hawk ASIC).
There are four 32-bit timers on the board that may be used for system timing or to generate
periodic interrupts.
Interrupt Routing
Legacy interrupt assignment for the PCI/ISA Bridge is maintained to ensure software
compatibility between the MVME5100 and the MVME2700 while in SBC mode.
This is accomplished by using the corresponding on-board IPMC712 or IPMC761 connector to
route the PCI/ISA Bridge interrupt signal to the external interrupt 0 of the Hawk ASIC (MPIC).
Note
The SCSI device on either the IPMC712 or IPMC761 uses the standard INTA# pin J1104 of PMC Slot 1.
IDSEL Routing
Legacy IDSEL assignment for the PCI/ISA Bridge is also maintained to ensure software
compatibility between MVME5100 and the MVME2700 while in SBC mode (also called 761 or
IPMC mode).
This is accomplished by using either the on-board IPMC712 or IPMC761 connector to route
IDSEL (AD11) to the PCI/ISA Bridge on the IPMC712 or IPMC761.
Note
When a standard PMC card (not the IPMC712 or IPMC761) is plugged into slot 1, its IDSEL
assignment corresponds to the standard IDSEL pin J12-25 and shall be connected to AD16.
42
MVME51005E Single Board Computer Installation and Use (6806800A38B)
The SCSI device on the IPMC712 and IPMC761 uses the standard IDSEL pin J12-25
connected to AD16.
Page 61
5RAM500 Memory Expansion Module
Overview
The RAM500 memory expansion module can be used on the MVME5100 as an option for
additional memory capability. Each expansion module is a single bank of SDRAM with either
256 or 512MB of available ECC memory. Currently, two expansion modules can be used in
tandum to produce an additional expanded memory capability of 1GB. There are two
configurations of the board to accommodate tandum usage. The bottom expansion module has
both a bottom and top connector: one to plug into the base board, and one to mate with the
second RAM500 module. The top expansion module is designed with just a bottom connector
to plug into the lower RAM500 module. The RAM500 incorporates a Serial ROM for system
memory Serial Presence Detect (SPD) data.
A maximum of two expansion modules are allowed: one bottom and one top. If only one module
is used, the RAM500 module with the top configuration is recommended.
5
Features
The following table lists the features of the RAM500 memory expansion module:
Table 5-1. RAM500 Feature Summary
Form FactorDual sided mezzanine, with screw/post attachment to host board
SROM Single 256x8 I
SDRAMDouble-Bit-Error detect, Single-Bit-Error correct across 72 bits
128, 256, or 512MB mezzanine memory @ 100MHz
Memory Expansion
Flexibility
Any RAM500 memory size can be attached to the host board
followed by any secondary RAM500 memory size for maximum
memory expansion flexibility.
Functional Description
The following sections describe the physical and electrical structure of the RAM500 memory
expansion module.
2
C SROM for Serial Presence Detect Data
MVME51005E Single Board Computer Installation and Use (6806800A38B)
43
Page 62
5 RAM500 Memory Expansion Module
RAM500 Description
The RAM500 is a memory expansion module that is used on the MVME5100 Single Board
Computer. The RAM500 is based on a single memory mezzanine board design with the
flexibility of being populated with different sized SDRAM components and SPD options to
provide a variety of memory configurations. The design of the RAM500 allows any memory size
module to connect to and operate with any other available memory size module.
The optional RAM500 memory expansion module is currently available in three sizes: 128MB,
256MB, and 512MB, with a total added capacity of 1GB. The SDRAM memory is controlled by
the Hawk ASIC, which provides single-bit error correction and double-bit error detection. ECC
is calculated over 72-bits. Refer to the MVME5100 Single Board Computer Programmer’s Reference Guide (V5100A/PG) for more information.
The RAM500 consists of a single bank/block of memory. The memory block size is dependent
upon the SDRAM devices installed. Refer to Tabl e 5 - 2 for memory options.
The RAM500 memory expansion module is connected to the host board with a 140-pin AMP
0.6mm Free Height plug connector. If the expansion module is designed to accommodate
another RAM500 module, the bottom expansion module will have two 140-pin AMP connectors
installed: one on the bottom side of the module, and one on the top side of the module. The
RAM500 memory expansion module draws +3.3V through this connector.
When populated, the optional RAM500 memory expansion memory blocks should appear as
Block C and Block E to the Hawk ASIC. Block C and E are used because each of the module’s
SPD is defined to correspond to two banks of memory each: C and D for the first SPD and E
and F for the second SPD.
The RAM500 SPD uses the SPD JEDEC standard definition and is accessed at address $AA
or $AC. Refer to the following section on SROM for more details.
Table 5-2. RAM500 SDRAM Memory Size Options
RAM500 Memory
Size
32 Mbytes64 Mbit4Mx165*
64 Mbytes128 Mbit8Mx165*
128 Mbytes256 Mbit16Mx165*
64 Mbytes64 Mbit8Mx89
128 Mbytes128 Mbit16Mx89
256 Mbytes256 Mbit32Mx89
Device SizeDevice
Organization
Number of
Devices
44
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 63
Bottom-side MVME5100-MEZ Connector
A,
BA,
WE_L,
RAS_L,
CAS_L,
Buffer
LVTH162244
Top-side MVME5100-MEZ Connector
DQMB1
DQ,
CKD
1 Bank of 9 (x8)
SDRAMS
CS_E_L
DQ,
CKD
DQMB0
CS_C_L
DQMB0
CS_C_L
DQMB1
CS_E_L
A,
BA,
WE_L,
RAS_L,
CAS_L,
Note: DQMB1, CS_E_L, A1_SPD,CLK3,4 from Bottom
Connector is routed to Top connector
at the DQMB0, CS_C_L and A0_SPD,CLK1,2 pins.
SROM
SPD
SCL
SDA
SCL
SDA
A1_SPD
A0_SPD
CLK1,2,3,4
CLK1,2
CLK1,2
CLK3,4
5 RAM500 Memory Expansion Module
Figure 5-1. RAM500 Block Diagram
SROM
The RAM500 memory expansion module contains a single 3.3V, 256 x 8, Serial EEPROM
device (AT24C02). The Serial EEPROM provides Serial Presence Detect (SPD) storage of the
module memory subsystem configuration. The RAM500 SPD is software addressable by a
unique address as follows: The first RAM500 attached to the host board has its SPD
addressable at $AA. The second RAM500 attached to the host board has its SPD addressable
at $AC. This dynamic address relocation of the RAM500 SPD shall be done using the bottomside connector signal A1_SPD and A0_SPD.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
45
Page 64
5 RAM500 Memory Expansion Module
Host Clock Logic
The host board provides four SDRAM clocks to the memory expansion connector. The
frequency of the RAM500 CLKS is the same as the host board.
RAM500 Module Installation
One or more RAM500 memory expansion modules can be mounted on top of the MVME5100
for additional memory capacity. To upgrade or install a RAM500 module, refer to Figure 5-2 and
proceed as follows:
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis
as a ground. The ESD strap must be secured to your wrist and to ground throughout
the procedure.
2. Perform an operating system shutdown. Turn the AC or DC power off and remove the
AC cord or DC power lines from the system. Remove the chassis or system cover(s)
as necessary for access to the CompactPCI boards.
3. Carefully remove the MVME5100 from its VME card slot and lay it flat, with connectors
P1 and P2 facing you.
4. Inspect the RAM500 module that is being installed on the MVME5100 host board
(bottom configuration if two are being installed, top configuration if only one is being
installed) to ensure that standoffs are installed in the three mounting holes on the
module.
5. With standoffs installed in the three mounting holes on the RAM500 module, align the
standoffs and the P1 connector on the module with the three holes and the J16
connector on the MVME5100 host board and press the two connectors together until
they are firmly seated in place.
Figure 5-2. RAM500 Module Placement on MVME5100
46
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 65
6. (Optional step) If a second RAM500 module is being used, align the top connector on
the bottom RAM500 module with the bottom connector on the top RAM500 module and
press the two connectors together until the connectors are seated in place.
7. Insert the three short Phillips screws through the holes at the corners of the RAM500
and screw them into the standoffs.
8. Turn the entire assembly over, and fasten the three nuts provided to the standoff posts
on the bottom of the MVME5100 host board.
9. Reinstall the MVME5100 assembly in its proper card slot. Be sure the host board is well
seated in the backplane connectors. Do not damage or bend connector pins.
10. Replace the chassis or system cover(s), reconnect the system to the AC or DC power
source, and turn the equipment power on.
RAM500 Connectors
RAM500 memory expansion modules are populated with one or two connectors. If the module
is to be used in tandum with a second RAM500 module, the “bottom” module will have two
connectors: one to mate with the MVME5100 host board (P1), and one to mate with the “top”
RAM500 module (J1). The “top” RAM500 module has only one connector, since it needs to
mate only with the RAM500 module directly underneath it and because an added connector on
a tandum RAM500 configuration would exceed the height limitations in some backplanes. If
only one RAM500 module is being used, a top module, single connector configuration is used.
5 RAM500 Memory Expansion Module
A 4H plug and receptacle are used on both boards to provide a 4 millimeter stacking height
between dual RAM500 cards and the host board.
The following subsections specify the pin assignments for the connectors on the RAM500.
Bottom Side Memory Expansion Connector (P1)
The bottom side connector on the RAM500 is a 140-pin AMP 0.6mm Free Height mating plug.
This plug includes common ground contacts that mate with standard AMP receptacle
assemblies or AMP GIGA assemblies with ground plates. A single memory expansion module
will have 1 bank of SDRAM for a maximum of 5Mbytes of memory. Attaching a second memory
module to the first module will provide 2 banks of SDRAM with a maximum of 1Gigabytes.
Table 5-3. RAM500 Bottom Side Connector (P1)Pin Assignments
1GND*GND*2
3DQ00DQ014
5DQ02DQ036
7DQ04DQ058
9DQ06DQ0710
11+3.3V+3.3V12
13DQ08DQ0914
15DQ10DQ1116
MVME51005E Single Board Computer Installation and Use (6806800A38B)
47
Page 66
5 RAM500 Memory Expansion Module
Table 5-3. RAM500 Bottom Side Connector (P1)Pin Assignments
17DQ12DQ1318
19DQ14DQ1520
21GND*GND*22
23DQ16DQ1724
25DQ18DQ1926
27DQ20DQ2128
29DQ22DQ2330
31+3.3V+3.3V32
33DQ24DQ2534
35DQ26DQ2736
37DQ28DQ2938
39DQ30DQ3140
41GND*GND*42
43DQ32DQ3344
45DQ34DQ3546
47DQ36DQ3748
49DQ38DQ3950
51+3.3V+3.3V52
53DQ40DQ4154
55DQ42DQ4356
57DQ44DQ4558
59DQ46DQ4760
61GND*GND*62
63DQ48DQ4964
65DQ50DQ5166
67DQ52DQ5368
69+3.3V+3.3V70
71DQ54DQ5572
73DQ56DQ5774
75DQ58DQ5976
77DQ60DQ6178
79GND*GND*80
81DQ62DQ6382
83CKD00CKD0184
48
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 67
5 RAM500 Memory Expansion Module
Table 5-3. RAM500 Bottom Side Connector (P1)Pin Assignments
85CKD02CKD0386
87CKD04CKD0588
89+3.3V+3.3V90
91CKD06CKD0792
93BA1BA094
95A12A1196
97A10A0998
99GND*GND*100
101A08A07102
103A06A05104
105A04A03106
107A02A01108
109+3.3V+3.3V110
111A00CS_C0_L112
113CS_E0_LGND*114
115CS_C1_LCS_E1_L116
117WE_LRAS_L118
119GND*GND*120
121CAS_L+3.3V122
123+3.3VDQMB0124
125DQMB1SCL126
127SDAA1_SPD128
129A0_SPDMEZZ1_L130
131MEZZ2_LGND132
133GNDSDRAMCLK1134
135SDRAMCLK3+3.3V136
137SDRAMCLK4SDRAMCLK2138
139GND*GND*140
*Common GND pins mate to a GIGA assembly with a ground plate. The GIGA assembly is an
enhanced electrical performance receptacle and plug from AMP that includes receptacles
loaded with contacts for grounding circuits at 9 or 10 signal circuits. These ground contacts
mate with grounding plates on both sides of the plug assemblies.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
49
Page 68
5 RAM500 Memory Expansion Module
Top Side Memory Expansion Connector (J1)
The top side memory expansion connector is a 140-pin AMP 0.6mm Free Height receptacle.
This receptacle includes common ground contacts that mate with standard AMP plug
assemblies or AMP GIGA assemblies with ground plates. A single memory module will have
one bank of SDRAM for a maximum of 512MB of memory. The pin assignments for this
connector are as follows:
Table 5-4. RAM500 Top Side Connector (J1)Pin Assignments
1GND*GND*2
3DQ00DQ014
5DQ02DQ036
7DQ04DQ058
9DQ06DQ0710
11+3.3V+3.3V12
13DQ08DQ0914
15DQ10DQ1116
17DQ12DQ1318
19DQ14DQ1520
21GND*GND*22
23DQ16DQ1724
25DQ18DQ1926
27DQ20DQ2128
29DQ22DQ2330
31+3.3V+3.3V32
33DQ24DQ2534
35DQ26DQ2736
37DQ28DQ2938
39DQ30DQ3140
41GND*GND*42
43DQ32DQ3344
45DQ34DQ3546
47DQ36DQ3748
49DQ38DQ3950
51+3.3V+3.3V52
53DQ40DQ4154
55DQ42DQ4356
57DQ44DQ4558
50
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 69
5 RAM500 Memory Expansion Module
Table 5-4. RAM500 Top Side Connector (J1)Pin Assignments (continued)
59DQ46DQ4760
61GND*GND*62
63DQ48DQ4964
65DQ50DQ5166
67DQ52DQ5368
69+3.3V+3.3V70
71DQ54DQ5572
73DQ56DQ5774
75DQ58DQ5976
77DQ60DQ6178
79GND*GND*80
81DQ62DQ6382
83CKD00CKD0184
85CKD02CKD0386
87CKD04CKD0588
89+3.3V+3.3V90
91CKD06CKD0792
93BA1BA094
95A12A1196
97A10A0998
99GND*GND*100
101A08A07102
103A06A05104
105A04A03106
107A02A01108
109+3.3V+3.3V110
111A00CS_E0_L112
113GND*114
115CS_E1_L116
117WE_LRAS_L118
119GND*GND*120
121CAS_L+3.3V122
123+3.3VDQMB1124
125SCL126
MVME51005E Single Board Computer Installation and Use (6806800A38B)
51
Page 70
5 RAM500 Memory Expansion Module
Table 5-4. RAM500 Top Side Connector (J1)Pin Assignments (continued)
127SDA128
129A1_SPDMEZZ2_L130
131GND132
133GNDSDRAMCLK3134
135+3.3V136
137SDRAMCLK4138
139GND*GND*140
*Common GND pins mate to GIGA assemblies with ground plates.
RAM500 Programming Issues
The RAM500 contains no user programmable registers, other than the Serial Presence Detect
(SPD) Data.
Serial Presence Detect (SPD) Data
This register is partially described for the RAM500 within the MVME5100 Single Board
Computer Programmer’s Reference Guide. The register is accessed through the I
of the Hawk ASIC on the host board (MVME5100). The RAM500 SPD is software addressable
by a unique address as follows: The first RAM500 attached to the host board has has an SPD
address of $AA. The second RAM500 attached to the top of the first RAM500 has an SPD
address of $AC.
2
C interface
52
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 71
6Pin Assignments
Introduction
This chapter provides information on pin assignments for various jumpers and connectors on
the MVME5100 Single Board Computer.
Summary
The following tables summarize all of the jumpers and connectors:
The following table provides information about the jumper settings associated with th
MVME5100 Single Board Computer. The table below provides a brief description of each
jumper and the appropriate setting(s) for proper board operation.
JumperDescriptionSettingDefault
J1RISCWatch HeaderNone (Factory Use Only)N/A
J2PAL Programming HeaderNone (Lab Use Only)N/A
MVME51005E Single Board Computer Installation and Use (6806800A38B)
53
Page 72
6Pin Assignments
JumperDescriptionSettingDefault
J4Ethernet Port 2 Selection
(set in conjunction with
jumpers J10 and J17)
J6, J20Operation Mode
(Set Both Jumpers)
J7Flash Memory Selection
at Boot
J10, J17Ethernet Port 2 Selection
(set in conjunction with jumper
J4)
J15System Controller (VME)Pins 1,2 for No SCON
J16Soldered Flash ProtectionPins 1,2 Enables Programming of
For “P2” Ethernet Port 2:
Pins 1,2; 3,4; 5,6; 7,8 (set for
712/761)
For “Front Panel” Ethernet Port 2:
No Jumpers Installed
Pins 1,2 for PMC ModePMC
Pins 2,3 for SBC Mode (761 Mode)
Pins 1,2 for Soldered Bank ASocketed
Pins 2,3 for Socketed Bank B
For “Front Panel” Ethernet Port 2:
Pins 1,3 and 2,4 on Both Jumpers
For “P2” Ethernet Port 2:
Pins 3,5 and 4,6 on Both Jumpers
(set for 712/761)
Pins 2,3 for Auto SCON
No Jumper for ALWAYS SCON
Flash
Pins 2,3 Disables Programming of
the upper 64KB of Flash
No
Jumper
Installed
(front
panel)
Mode
Bank B
Front
Panel
Ethernet
Por t 2
Auto
SCON
Flash
Prog.
Enabled
Connectors
IPMC761 Connector (J3) Pin Assignments
This connetor is used to provide an interface to the IPMC761 module signals and is located near
J11. The pin assignments for this connector are as follows:
Table 6-1. IPMC761 Connector Pin Assignments
PinAssignmentPin
1I2CSCLI2CSDA2
3GNDGND4
5DB8#GND6
7GNDDB9#8
9DB10#+3.3V 10
11+3.3VDB11#12
13DB12#GND14
15GNDDB13#16
17DB14#+3.3V18
54
MVME51005E Single Board Computer Installation and Use (6806800A38B)
This connector is used to provide memory expansion capability. A single memory mezzanine
card provides a maximum of 256MB of memory. Attaching another memory mezzanine to the
first mezzanine provides an additional 512MB of expansion memory. The pin assignments for
this connector are as follows:
PIN 130, 131, MEZZ1_L, MEZZ2_L, configures the board’s local bus frequency. If a
single mezzanine is attached to the board, MEZZ1_L will be pulled down on the board.
If a second mezzanine is attached on-top to the first, MEZZ2_L will be pulled down on
the board. This may cause the clock generation logic to set the local bus frequency to
83.33 MHz if necessary.
PCI Expansion Connector (J25) Pin Assignments
This connector is used to provide PCI/PMC expansion capability. The pin assignments for this
connector are as follows:
MVME51005E Single Board Computer Installation and Use (6806800A38B)
These connectors provide 32/64-bit PCI interfaces and P2 I/O for two optional add-on PCI
Mezzanine Cards (PMC). The pin assignments for these connectors are as follows.
The VMEbus connector P1 provides power and VME signals for 24-bit address and 16-bit data.
The pin assignments for the connector are specified by the IEEE P1014-1987 VMEbus
Specification and the VME64 Extension Standard.
Row B of connector P2 provides power to the MVME5100, and to the upper eight VMEbus
address lines, and additional 16 VMEbus data lines. Rows A, C, Z and D provide power and
interface signals to the MVME762 transition module. The pin assignments for connector P2 in
PMC mode are as follows:
Table 6-7. Pin Assignments for Connector P2 in PMC Mode
The VMEbus connector P1 provides power and VME signals for 24-bit address and 16-bit data.
The pin assignments for the connector are specified by the IEEE P1014-1987 VMEbus
Specification and the VME64 Extension Standard.
Row B of connector P2 provides power to the MVME5100 and to the upper 8 VMEbus address
lines and additional 16 VMEbus data lines.
Rows A, C, Z and D provide power and interface signals to the MVME712 or MVME761
transition module in SBC mode (also called 761 mode and IPMC mode).
It is important to note that the PMC I/O routing to row D and Z are not the same as
MVME2600/2700. The PMC I/O routing for row D and row Z is the same as the PMC mode with
the exception of pins Z1, 3, 5, 7, 9, 11, 13, 15 and 17 which are used for extended SCSI.
Note
The pin assignments for the P2 connector using the IPMC761 or the IPMC712 are listed in the
following two tables:
A PMC card installed in slot 2 of an MVME5100 in SBC mode MUST NOT connect to
J24-2, 5, 8, 11, 14, 17, 20, 23 and 26 since they are connected to the extended SCSI
signals of the MVME5100.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Since the P2 adaptor card for the MVmE712M is a three (3) row connector, signals on
Rows Z and D are not routed to the MVME712M. Thus
(a) although the IPMC712 controller is capable of 16-bit (wide) SCSI operations only 8bit (narrow) transfers are supported through the MVME712M
(b) PMC I/O from site two (2) is not available through the MVME712M
(c) Please remember the caution stated on page 5-25 that a PMC located at site two
(2) may not connect to pins J24-2, 5, 8, 11, 14, 17, 20, 23 and 26.
10 BaseT/100 BaseTx Connector Pin Assignments
The board’s dual 10 BaseT/100 BaseTx RJ45 connectors (J9 and J18) are located on the front
plate. The connections provide two LAN connections (LAN1-J18 and LAN2-J9). The pin
assignments for these connectors are as follows:
PinAssignment
1TD+
MVME51005E Single Board Computer Installation and Use (6806800A38B)
A standard RJ45 connector located on the front panel and a 9-pin header located near the
bottom edge of the MVME5100 provides the interface to the serial debug ports. The RJ45
connector is for COM1 and the 9-pin header is for COM2.
The pin assignments for these connectors are as follows:
PinAssignment
1DCD
2RTS
3GNDC
4TXD
5RXD
6GNDC
7CTS
8DTR
PinAssignment
1DCD
2DSR
3RXD
4RTS
5TXD
6CTS
7DTR
8RI
9GND
72
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 91
7Programming the MVME5100
Introduction
This chapter provides basic information useful in programming the MVME5100. This includes
a description of memory maps, control and status registers, PCI arbitration, interrupt handling,
sources of reset and big/little-endian issues.
For additional programming information about the MVME5100, refer to the MVME5100-Series
Single Board Computer Programmer’s Reference Guide, listed in Appendix D, Related
Documentation .
For programming information about the PMCs, refer to the applicable user’s manual furnished
with the PMCs.
7
Memory Maps
There are multiple buses on the MVME5100 and each bus domain has its own view of the
memory map. The following sections describe the MVME5100 memory organization from the
following three points of view:
❏The mapping of all resources as viewed by the MPU (processor bus memory map)
❏The mapping of onboard resources as viewed by PCI local bus masters (PCI bus
memory map)
❏The mapping of onboard resources as viewed by VMEbus masters (VMEbus
memory map)
Additional, more detailed memory maps can be found in the MVME5100-Series Single Board Computer Programmer’s Reference Guide, listed in Appendix D, Related Documentation.
Processor Bus Memory Map
The processor memory map configuration is under the control of the PHB and SMC portions of
the Hawk ASIC. The Hawk adjusts system mapping to suit a given application via
programmable map decoder registers. At system power-up or reset, a default processor
memory map takes over.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
73
Page 92
7 Programming the MVME5100
Default Processor Memory Map
The default processor memory map that is valid at power-up or reset remains in effect until
reprogrammed for specific applications. Table 7-1 defines the entire default map ($00000000
to $FFFFFFFF).
Table 7-1. Default Processor Memory Map
Processor AddressSizeDefinition
StartEnd
0000 00007FFF FFFF2GBNot Mapped
8000 00008080 FFFF8M+64KZero-based PCI/ISA I/O Space
For an example of the CHRP memory map, refer to the following table. For detailed processor
memory maps, including suggested CHRP- and PREP-compatible memory maps, refer to the
MVME5100-Series Single Board Computer Programmer’s Reference Guide.
The first 1MB of ROM/FLASH Bank A (soldered Flash up to 8MB) appears in this range
after a reset if the rom_b_rv control bit in the SMC’s ROM B Base/Size register is
cleared. If the rom_b_rv control bit is set, this address range maps to ROM/FLASH
Bank B (socketed 1MB Flash).
74
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 93
Processor Memory Map
The following table describes a suggested CHRP Memory Map from the point of view of the
processor. This memory map is an alternative to the PREP memory map. Note: in all
recommended CHRP maps, the beginning of PCI Memory Space is determined by the end of
DRAM rounded up to the nearest 256MB-boundry as required by CHRP. For example, if
memory was 1G on the baseboard and 192MB on a mezzanine, the beginning of PCI memory
would be rounded up to address 0x50000000 (1G + 256M).
2. The actual Power Plus II size of each ROM/FLASH bank may vary.
3. The first 1MB of ROM/FLASH Bank A appears at this range after a reset if the
rom_b_rv control bit is cleared. If the rom_b_rv control bit is set, this address maps to
ROM/FLASH Bank B.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
75
Page 94
7 Programming the MVME5100
4. The only method to generate a PCI Interrupt Acknowledge cycle (8259 IACK) is to
perform a read access to the Hawks PIACK Register at 0xFEFF0030.
5. VME should be placed at the top of PCI memory space.
The following table shows the programmed values for the associated Hawk PCI Host Bridge
Registers for the suggested Processor Memory Map.
Table 7-3. Hawk PPC Register Values for Suggested Memory Map
AddressRegister NameRegister Name
FEFF 0040MSADD0X000 F3FF [X:1..8]
FEFF 0044MSOFF0 & MSATT00000 00C2
FEFF 0048MSADD1FE00 FE7F
FEFF 004CMSOFF1 & MSATT10200 00C0
FEFF 0050MSADD20000 0000
FEFF 0054MSOFF2 & MSATT20000 0000
FEFF 0058MSADD30000 0000
FEFF 005CMSOFF3 & MSATT30000 0000
PCI Memory Map
Following a reset, the Hawk ASIC disables all PCI slave map decoders. The MVME5100 is fully
capable of supporting both PREP and CHRP PCI Memory Maps with RAM size limited to 2GB.
VME Memory Map
The MVME5100 is fully capable of supporting both the PREP and the CHRP VME Memory
Maps examples with RAM size limited to 2GB.
PCI Local Bus Memory Map
The PCI memory map is controlled by the MPU/PCI bus bridge controller portion of the Hawk
ASIC and by the Universe PCI/VME bus bridge ASIC. The Hawk and Universe devices adjust
system mapping to suit a given application via programmable map decoder registers.
No default PCI memory map exists. Resetting the system turns the PCI map decoders off, and
they must be reprogrammed in software for the intended application.
For detailed PCI memory maps, including suggested CHRP- and PREP-compatible memory
maps, refer to the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
VMEbus Memory Map
The VMEbus is programmable. Like other parts of the MVME5100 memory map, the mapping
of local resources as viewed by VMEbus masters varies among applications.
76
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 95
The Universe PCI/VME bus bridge ASIC includes a user-programmable map decoder for the
VMEbus-to-local-bus interface. The address translation capabilities of the Universe enable the
processor to access any range of addresses on the VMEbus.
Recommendations for VMEbus mapping, including suggested CHRP- and PREP-compatible
memory maps, can be found in the MVME5100-Series Single Board Computer Programmer’s Reference Guide. Figure 7-1 shows the overall mapping approach from the standpoint of a
VMEbus master.
Programming Considerations
Good programming practice dictates that only one MPU at a time have control of the
MVME5100 control registers. Of particular note are:
❏Registers that modify the address map
❏Registers that require two cycles to access
❏VMEbus interrupt request registers
7 Programming the MVME5100
PCI Arbitration
There are seven potential PCI bus masters on the MVME5100:
❏Hawk ASIC (MPU/PCI bus bridge controller)
❏Winbond W83C554 PIB (PCI/ISA bus bridge controller)
❏DECchip 21143 Ethernet controller
❏Universe II ASIC (PCI/VME bus bridge controller)
❏PMC Slot 1 (PCI mezzanine card)
❏PMC Slot 2 (PCI mezzanine card)
❏PCI Expansion Slot
The Winbond W83C554 PIB device supplies the PCI arbitration support for these seven types
of devices. The PIB supports flexible arbitration modes of fixed priority, rotating priority and
mixed priority, as appropriate in a given application. Details on PCI arbitration can be found in
the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
77
Page 96
7 Programming the MVME5100
VMEBUS
11553.00 9609
VME A24
VME A16
VME A24
VME A16
VME A24
VME A16
VME A24
VME A16
PROGRAMMABLE
SPACE
PCI MEMORYPROCESSOR
PCI MEMORY
SPACE
PCI/ISA
MEMORY SPACE
PCI
I/O SPACE
MPC
RESOURCES
NOTE 1
NOTE 1
NOTE 2
NOTE 3
ONBOARD
MEMORY
1. Programmable mapping done by Hawk ASIC.
2. Programmable mapping performed via PCI Slave images in Universe ASIC.
3. Programmable mapping performed via Special Slave image (SLSI) in Universe ASIC.
NOTES:
Figure 7-1. VMEbus Master Mapping
The arbitration assignments for the MVME5100 are shown in Table 7-4.
Table 7-4. PCI Arbitration Assignments
PCI Bus RequestPCI Master(s)
PIB (Internal)PIB
CPUHawk ASIC
Request 0PMC Slot 2
Request 1PMC Slot 1
Request 2PCI Expansion Slot
Request 3Ethernet
Request 4Universe ASIC (VMEbus)
78
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Page 97
Interrupt Handling
11559.00 9609
PIB
(8529 Pair)
Processor
INT_
MCP_
Hawk MPIC
INT
SERR_& PERR_
PCI Interrupts
ISA Interrupts
The Hawk ASIC, which controls the PHB (PCI Host Bridge) and the MPU/local bus interface
functions on the MVME5100, performs interrupt handling as well. Sources of interrupts may be
any of the following:
❏The Hawk ASIC itself (timer interrupts, transfer error interrupts or memory error
interrupts)
❏The processor (processor self-interrupts)
❏The PCI bus (interrupts from PCI devices)
❏The ISA bus (interrupts from ISA devices)
Figure 7-2 illustrates interrupt architecture on the MVME5100. For details on interrupt handling,
refer to the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
7 Programming the MVME5100
Figure 7-2. MVME5100 Interrupt Architecture
MVME51005E Single Board Computer Installation and Use (6806800A38B)
79
Page 98
7 Programming the MVME5100
Hawk MPIC
PMC Slot 1
INTA#
INTB# INTC#
INTD#
PMC Slot 2
INTA#
INTB# INTC#
INTD#
PCIX Slot
INTA#
INTB# INTC#
INTD#
IRQ9
IRQ10
IRQ11 IRQ12
The MVME5100 routes the interrupts from the PMCs and PCI expansion slots as follows:
DMA Channels
Sources of Reset
The PIB supports seven DMA channels. They are not functional on the MVME5100.
The MVME5100 has nine potential sources of reset:
1. Power-on reset
2.
RST switch (resets the VMEbus when the MVME5100 is system controller)
3. Watchdog timer Reset function controlled by the SGS-Thomson MK48T559
timekeeper device (resets the VMEbus when the MVME5100 is system controller)
4. ALT_RST
∗ function controlled by the Port 92 register in the PIB (resets the VMEbus
when the MVME5100 is system controller)
5. PCI/ISA I/O Reset function controlled by the Clock Divisor register in the PIB
6. The VMEbus SYSRESET
∗ signal
7. VMEbus Reset sources from the Universe ASIC (PCI/VME bus bridge controller): the
System Software reset, Local Software Reset and VME CSR Reset functions.
Note
On the MVME5100, Watchdog Timer 2 is a source of reset only if component R206 is
installed on the board.
Tab le 7- 5 shows which devices are affected by the various types of resets. For details on using
resets, refer to the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
80
MVME51005E Single Board Computer Installation and Use (6806800A38B)
reset
VME Local SW reset√√√ √
VME CSR reset√√√ √
Hot reset (Port 92)√√√ √
PCI/ISA reset√√
Endian Issues
The MVME5100 supports both little-endian (e.g., Windows NT) and big-endian (e.g., AIX)
software. The PowerPC processor and the VMEbus are inherently big-endian, while the PCI
bus is inherently little-endian. The following sections summarize how the MVME5100 handles
software and hardware differences in big- and little-endian operations. For further details on
endian considerations, refer to the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
Hawk
sor
√√√ √ √
√√√ √ √
ASIC
PCI
Devices
ISA
Devices
VMEbus
(as system
controller)
Processor/Memory Domain
The MPC750 processor can operate in both big-endian and little-endian mode. However, it
always treats the external processor/memory bus as big-endian by performing address rearrangementand reordering when running in little-endian mode. The MPC registers in the
Hawk MPU/PCI bus bridge controller, SMC memory controller, as well as DRAM, Flash and
system registers, always appear as big-endian.
Role of the Hawk ASIC
Because the PCI bus is little-endian, the PHB portion of the Hawk performs byte swapping in
both directions (from PCI to memory and from the processor to PCI) to maintain address
invariance while programmed to operate in big-endian mode with the processor and the
memory subsystem.
In little-endian mode, the PHB reverse-rearranges the address for PCI-bound accesses and
rearranges the address for memory-bound accesses (from PCI). In this case, no byte swapping
is done.
MVME51005E Single Board Computer Installation and Use (6806800A38B)
81
Page 100
7 Programming the MVME5100
PCI Domain
The PCI bus is inherently little-endian. All devices connected directly to the PCI bus operate in
little-endian mode, regardless of the mode of operation in the processor’s domain.
PCI and Ethernet
Ethernet is byte-stream-oriented; the byte having the lowest address in memory is the first one
to be transferred regardless of the endian mode. Since the PHB maintains address invariance
in both little-endian and big-endian mode, no endian issues should arise for Ethernet data. Bigendian software must still take the byte-swapping effect into account when accessing the
registers of the PCI/Ethernet device, however.
Role of the Universe ASIC
Because the PCI bus is little-endian while the VMEbus is big-endian, the Universe PCI/VME bus
bridge ASIC performs byte swapping in both directions (from PCI to VMEbus and from VMEbus
to PCI) to maintain address invariance, regardless of the mode of operation in the processor’s
domain.
VMEbus Domain
The VMEbus is inherently big-endian. All devices connected directly to the VMEbus must
operate in big-endian mode, regardless of the mode of operation in the processor’s domain.
In big-endian mode, byte-swapping is performed first by the Universe ASIC and then by the
PHB. The result is transparent to big-endian software (a desirable effect).
In little-endian mode, however, software must take the byte-swapping effect of the Universe
ASIC and the address reverse-rearranging effect of the PHB into account.
For further details on endian considerations, refer to the MVME5100-Series Single Board Computer Programmer’s Reference Guide.
82
MVME51005E Single Board Computer Installation and Use (6806800A38B)
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.