All other product or service names are the property of their respective owners.
Intel® is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
PICMG®, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logo s are registered trademarks of the
PCI Industrial Computer Manufacturers Group.
Notice
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 conten t hereof without obligation of Emerson to notify any person of such revision or
changes.
Electronic versions of this material ma y be re ad onlin e, d ownl oaded for personal use, or referenced in another do cument as a URL to
a Emerson website. The text itself ma y not be published commerci ally in print or electronic form, edited, transl ated, or otherwise altered
without the permission of Emerson,
It is possible that this publication may contain reference to or information about Emerson pro ducts (machines and programs),
programming, or services that are not av ailable in your country. Such references or information must not be construed to mean that
Emerson intends to announce such Emerson products, prog ramming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or ind irectly, to the U.S . Go ve rnment, the follo wing notice shall apply u nless
otherwise agreed to in writing by Emerson.
Use, duplication, or disclosure by th e Government is subject t o restrictions as set forth in subparag raph (b)(3) of the Rights i n Technical
Data clause at DF ARS 25 2.227-7013 (No v. 1995) and of the Rights in Noncommerci al Computer Softw are and D ocumentation clau se
at DFARS 252.227-7014 (Jun. 1995).
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
9
Page 10
List of Figures
10
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 11
About this Manual
Overview of Contents
This manual is divided into the following chapters and appendices:
Chapter 1, Hardware Preparation and Installation, provides MVME5500 board preparation and
installation instructions for both the board and accessories. Also included are the power-up
procedure.
Chapter 2, Functional Description, describes the MVME5500 on a block diagram level.
Chapter 3, RAM55006E Memory Ex pansion Module, provides a description of the RAM5500
memory expansion module, as well as installation instructions and connector pin assignments.
Chapter 4, MOTLoad Firmware, describes the basic features of the MOTLoad firmware
product.
Chapter 5, Connector Pin Assignments , provides pin assignments for various headers and
connectors on the MMVE5500 single-board computer.
Appendix A, Specifications, provides power requirements and environmental specifications.
Appendix B, Thermal Validation, provides information to conduct thermal evaluations and
identifies thermally significant components along with their maximum allowable operating
temperatures.
Appendix C, Related Documentation, provides a listing of related Emerson manuals, vendor
documentation, and industry specifications.
The MVME55006E Single-Board Computer Installation and Use manual provides the
information you will need to install and configure your MVME55006E single-board computer. It
provides specific preparation and installation information, and data applicable to the board. The
MVME55006E single-board computer will hereafter be referred to as the MVME5500.
As of the printing date of this manual, the MVME5500 supports the models listed below.
MVME712M6ETransition module with one DB-25 sync/async serial port, three DB-25
parallel port, three async and one sync/async serial ports.
async serial port, one AUI connector, one D-36 parallel port and one 50pin 8-bit SCSI; includes 3-row DIN P2 adapter board and cable.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
11
Page 12
About this Manual
Model NumberDescription
MVME7616E-001Multifunction rear I/O PMC module; 8-bit SCSI, one parallel port, two
MVME7616E-011Transition module with two DB-9 async serial port connectors, two HD-26
PMCSPAN26E-002Primary PMCSPAN with original VME IEEE ejector handles.
PMCSPAN26E-010Secondary PMCSPAN with original VME IEEE ejector handles.
PMCSPAN16E-002Primary PMCSPAN with Scanbe ejector handles.
PMCSPAN16E-010Secondary PMCSPAN with Scanbe ejector handles.
Conventions
The following table describes the conventions used throughout this manual.
async and two sync/async serial ports. Transition module with two DB-9
async serial port connectors, two HD-26 sync/async serial port
connectors, one HD-36 parallel port connector, one RJ-45 10/100 Ethernet
connector; includes 3-row DIN P2 adapter board and cable (for 8-bit
SCSI).
sync/async serial port connectors, one HD-36 parallel port connector, one
RJ-45 10/100 Ethernet connector; includes 5-row DIN P2 adapter board
and cable (for 16-bit SCSI); requires backplane with 5-row DIN
connectors.
NotationDescription
0x00000000Typical notation for hexadecimal numbers (digits
0b0000Same for binary numbers (digits are 0 and 1)
boldUsed to emphasize a word
ScreenUsed for on-screen output and code related
Courier + BoldUsed to characterize user input and to separate it
ReferenceUsed for references and for table and figure
File > ExitNotation for selecting a submenu
<text>Notation for variables and keys
[text]Notation for softw are buttons to click on the screen
...Repeated item for example node 1, node 2, ...,
.
.
.
..Ranges, for ex ample: 0..4 means one of the
|Logical OR
are 0 through F), for example used for addresses
and offsets
elements or commands in body text
from system output
descriptions
and parameter description
node 12
Omission of information from example/command
that is not necessary at the time being
integers 0,1,2,3, and 4 (used in registers)
12
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 13
NotationDescription
Indicates a hazardous situation which, if not
avoided, could result in death or serious injury
Indicates a hazardous situation which, if not
avoided, may result in minor or moderate injury
Indicates a property damage message
No danger encountered. Pay attention to
important information
About this Manual
Summary of Changes
This manual has been revised and replaces all prior editions.
DateChangePageReplaces
March 2008Updated to Emerson style standards.6806800A37C
February 2007Default setting for J32 is [1-2]
Default setting for J28 is [1-2}
PMC Mode for J28 and J32 is factory default
P2 PMC 2 I/O mode for J102-J110 is factory
default
P2 IPMC I/O is [2-3]
January 2007Default setting for J102 - J110 is [1-2].226806800A37A
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.
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.
20, 226806800A37B
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
13
Page 14
About this Manual
14
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 15
Hardware Preparation and Installation
1.1Overview
This chapter contains the following information:
zBoard and accessory preparation and installation instructions
zESD precautionary notes
1.2Introduction
The MVME5500 is a single-board computer based on the PowerPC MPC7457 processor and
the Marvell GT-64260B host bridge with a dual PCI interface and memory controller. On-board
payload includes two PMC slots, two SDRAM banks, an expansion connector for two additional
banks of SDRAM, 8MB boot Flash ROM, one 10/100/1000 Ethernet port, one 10/100 Ethernet
port, 32MB expansion Flash ROM, two serial ports, NVRAM and a real-time clock.
1
The MVME5500 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 MVME5500 is user-configurable b y 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 transition module, or the IPMC761 I/O PMC and
the MVME761 transition modu le . The SBC mode is bac kw a rds compat ib le wi th the M VME761
transition module and the P2 adapter card (excluding PMC I/O routing) used on the MVME5100
product. This mode is accomplished by configuring the on-board jumpers and by attaching an
IPMC761 PMC in PMC slot 1. Secondary Ether net is configured to the rear.
PMC mode is backwards compatible with the MVME5100 and is accomplished by configuring
the on-board jumpers.
1.3Getting Started
This section provides an overview of the steps necessary to install and power up the
MVME5500 and a brief section on unpacking and ESD precautions.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
15
Page 16
Hardware Preparation and InstallationOverview of Startup Procedures
1.4Overview of Startup Procedures
The following table lists the things you will need to do before you can use this board and tells
where to find the information you need to perform each step. Be sure to read this entire chapter,
including all Caution and Warning notes, before you begin.
Table 1-1 Startup Overview
What you need to do...Refer to...
Unpack the hardware.Unpacking Guidelineson page 16
Configure the hardware by setting
jumpers on the board.
Install the MVME5500 board in a chassis. Procedureon page 33
Connect any other equipment you will be
using
Verify the hardware is installed.Completing the Installationon page 35
Configuring the Board on page 18
Connection to Peripherals on page 34
1.5Unpacking Guidelines
Unpack the equipment from the shipping cart on. Refer to the packing list and verify that all items
are present. Save the packing material for storing and reshipping of equipment.
If the shipping carton is damaged upon receipt, request that the carrier’s agent be present
during the unpacking and inspection of the equipment.
Product Damage
Avoid touching areas of integrated circuitry; static discharge can damage circuits.
Inserting or removing modules with power applied may result in damage to module
components.
16
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 17
Configuring the HardwareHardware Preparation and Installation
ESD
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 flat on a grounded,
static-free surface (and, in the cas e of a board, component side up). Do not slide the
component over any surface.
If an ESD station is not available, you can avoid damage resulting from ESD by
wearing an antistatic wrist strap (available at electr onics stores) that is attached to an
active electrical ground. Note that a system chassis may not be grounded if it is
unplugged.
Personal Injury or Death
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing, and adjusting.
1.6Configuring the Hardware
This section discusses certain hardware and software tasks that may need to be performed
prior to installing the board in a chassis.
To produce the desired configuration and ensure proper operation of the MVME5500, you may
need to carry out certain hardware modifications before installing the module.
Most options on the MVME5500 are software configurable. Configuration changes are made
by setting bits in control registers after the board is installed in a system.
Jumpers and switches are used to control those options that are not software configurable.
These settings are described fur t her on in this section. If you are resetting the board jumpers
or switches from their default settings, it is important to verify that all settings are reset properly.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
17
Page 18
Hardware Preparation and InstallationConfiguring the Board
1.6.1Configuring the Board
Figure 1-1 illustrates the placement of the jumpers, headers, switches, connectors, and various
other components on the MVME5500. There are several manually configurable headers and
switches on the MVME5500 and their settings are shown in Table 1-2. Each default setting is
enclosed in brackets. For pin assignments on the MVME5500, refer to Chapter 5, Connector
Pin Assignments.
Table 1-2 MVME5500 Jumper Settings
Jumpers /
SwitchesFunctionSettings
J6, J100, J7,
J101
J8Flash Boot Bank Select
S3-1Flash 0 Programming
S5-1Safe Start ENV Header[OFF]
S3-2Flash 0 Block Write
S3-4Non-Standard Option
S5-2SROM Initialization
S4-1PCI Bus 0.0 Speed
J27VME SCON Select
J28, J32PMC/SBC Mode Selection
Ethernet 2 Selection
Headers
(see also J34, J97, J98,
J99)
Refer to the hint on page 7
for a configuration
limitation.
Header
Enable Header
Protect Header
Header
Enable Switch
Header
Header
Headers
(set both jumpers)
Refer to page 7 for a
notice about configuring
for IPMC mode.
2-3 on all
[1-2 on all]
No jumper installed
[1-2]
2-3
OFF
[ON]
ON
OFF
[ON]
[OFF]For factory use only
OFF
[ON]
[OFF]
ON
No jumper installed
1-2
[2-3]
1-2 on both
2-3 on both
[1-2 on J28]
[2-3 on J32]
Rear P2 Ethernet (SBC mode)
Front-panel Ethernet
Boots from Flash 0
Boots from Flash 0
Boots from Flash 1
Disables Flash 0 writes
Enables Flash 0 writes
Normal ENV settings used
during boot
Safe ENV settings used during
boot
All of the headers described below are used in conjunction with each other to select various
modes of operation for 10/100BaseT Ethernet, PMC/SBC mode, and P2 I/O mode.
1.6.2.1Ethernet
Four 3-pin planar headers (J6, J7, J100, J101) and four 2-pin planar headers (J34, J97, J98,
J99) are for 10/100/BaseT Ethernet 2 selection.
Ethernet 1 is the Gigabit Ethernet port and is front panel only.
20
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
For J6, J100, J7 and J101, install jumpers across pins 2-3 on all four headers for rear P2
Ethernet. For front-panel Ethernet, install jumpers across pins 1-2 on all four headers.
If the rear P2 Ethernet is selected by jumpers J6, J7, J100, and J101, the Ether n e t
signals also connect to PMC 1 user I/O connector J14. If a PMC card is plugged into
PMC slot 1, there may be a conflict between the I/O from the PMC card and the rear
Ethernet signals. This conflict does not occur with the IPMC761 or IPMC712 modules.
For J34, J97, J98 and J99, no jumpers are installed for front-panel Ethernet. For rear P2
Ethernet, install jumpers across pins 1-2 on all four headers when in SBC/IPMC761 mode.
1.6.2.2PMC/SBC Mode Selection
The MVME5500 is set at the factory for PMC mode. The SBC/IPMC761 mode should only be
selected when using the IPMC761 module in conju nct io n w it h the MVME 76 1 transition
module.The PMC mode should be selected when using PMC modules with specific user I/O in
conjunction with the corresponding transition module. PMC mode should also be selected when
using PrPMC modules.
Two 3-pin planar headers (J28, J32) control the supply of +/- 12 v olts to the P2 connector; one
or both of these voltages are required by the MVME712 or MVME761 module when operating
in SBC mode. For PMC mode, jumpers are installed across pins 1-2 on both headers. For
SBC/IPMC761 mode, install jumpers across pins 2-3 on both headers. For SBC/IPMC712
mode, install a jumper across pins 2-3 for J32 and install a jumper across pins 1-2 for J28.
Product Damage
When J28 is configured for SBC/IPMC mode, –12V is supplied to P2 pin A30. If there
is an incompatible board plugged into this P2 slot, damage may occur.
When J32 is configured for SBC/IPMC mode, +12V is supplied to P2 pin C7. If there is
an incompatible board plugged into this P2 sl ot, damage may occur.
1.6.2.3P2 I/O Selection
Nine 3-pin planar headers (J102 –J110) are for P2 I/O selection. Jumpers are installed across
pins 1-2 on all nine headers when in PMC mode. Install jumpers across pins 2-3 on all nine
headers when in SBC/IPMC761 or SBC/IPMC712 mode to connect the e xtended SCSI signals
to P2.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
21
Page 22
Hardware Preparation and Installation Ethernet 2, PMC/SBC Mode, and P2 I/O Selection Headers (J6, J7, J28,
Figure 1-2Front Panel and Rear P2 Ethernet Settings
(factory configuration)
Rear P2 Ethernet
Front-Panel Ethernet
J6
3 2 1
J7
1 2 3
J100J100
3 2 1
J101J101
1 2 3
J34
1
2
J97
1
2
J98
1
2
J99
1
2
Figure 1-3J28 and J32 Settings
J6
J7
J34
J97
J98
J99
3 2 1
1 2 3
3 2 1
1 2 3
1
2
1
2
1
1
2
2
22
(factory configuration)
PMC Mode
J28
3 2 1
J32
3 2 1
SBC/IPMC761 Mode
J28
J32
Figure 1-4J102 - J110 Settings
(factory configuration)
P2 PMC 2 I/O
J102 –
J110
3 2 1
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
3 2 1
3 2 1
(extended SCSI)
P2 IPMC I/O
J102 –
J110
SBC/IPMC712 Mode
J28
3 2 1
J32
3 2 1
3 2 1
Page 23
Flash Boot Bank Select Header (J8)Hardware Preparation and Installation
1.6.3Flash Boot Bank Select Header (J8)
A 3-pin planar header selects the boot Flash bank. No jumper or a jumper installed across pins
1-2 selects Flash 0 as the boot bank. A jumper installed across pins 2-3 selects Flash 1 as the
boot bank.
Figure 1-5J8 Settings
J8
1
2
3
Boots from Flash device 0
Boots from Flash device 0Boots from Flash device 0
(factory configuration)
J8
1
2
3
Boots from Flash device 1
J8
1
2
3
1.6.4Flash 0 Programming Enable Switch (S3-1)
This switch enables/disables programming of Flash 0 as a means of protecting the contents
from being corrupted. The switch set to OFF disables all Flash 0 programming. The switch set
to ON enables the programming, this is the factory setting.
Figure 1-6S3-1 Settings
S3-1
1
Disables Flash 0 writes
ON
1
Enables Flash 0 writes
ON
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
23
Page 24
Hardware Preparation and InstallationSafe St art ENV Switch (S5-1)
1.6.5Safe Start ENV Switch (S5-1)
This switch selects programmed or safe start ENV settings. When set to OFF, it indicates that
the programmed ENV settings should be used during boot. Set to ON indicates that the safe
ENV settings should be used.
Figure 1-7S5-1 Settings
S5-1
1
2
Normal ENV settings used
during boot
(factory configuration)
ON
1
2
Safe ENV settings used
during boot
ON
1.6.6Flash 0 Block Write Protect Switch (S3-2)
This switch supports the Intel J3 Flash family write protect feature. Set to OFF, it enables the
lock-down mechanism. Blocks locked down cannot be unlocked with the unlock command. The
switch must be set to ON in order to override the lock-down function and enable blocks to be
erased or programmed through software. Refer to the Intel J3 Flash data sheet, listed in
Appendix C, Related Documentation, for further details.
Figure 1-8S3-2 Settings
S3-2
1
2
3
4
ON
1
2
3
4
ON
24
Disable Flash 0 J3
block writes
Enable Flash 0 J3
block writes
(factory configuration)
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 25
SROM Initialization Enable Switch (S5-2)Hardware Preparation and Installation
1.6.7SROM Initialization Enable Switch (S5-2)
This switch enables/disables the GT-64260B SROM initialization. When set to 2, it enables the
GT-64260B device initialization via I2C SROM. Set to ON disables this initialization sequence.
Figure 1-9S5-2 Settings
S5-2
1
2
Enable SROM initialization
ON
1
2
Disable SROM initialization
(factory configuration)
ON
1.6.8PCI Bus 0.0 Speed Switch (S4-1)
This switch can force PCI bus 0.0 to run at 33 MHz rather than the standard method of allowing
the PMC board to control whether the bus runs at 33 MHz or 66 MHz. Set to 1, it allows the
PMC board to choose the PCI 0.0 bus speed. Set to ON forces PCI bus 0.0 to run at 33 MHz.
Figure 1-10 S4-1 Settings
S4-1
1
2
PMC board controls
PCI 0.0 bus speed
(factory configuration)
ON
1
2
Force PCI bus 0.0
to run at 33 MHz
ON
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
25
Page 26
Hardware Preparation and InstallationVME SCON Select Header (J27)
1.6.9VME SCON Select Header (J27)
A 3-pin planar header allows the choice for auto/enable/disable SCON VME configuration. A
jumper installed across pins 1-2 configures for SCON disabled. A jumper installed across pin s
2-3 configures for auto SCON. No jumper installed configures for SCON always enabled.
Figure 1-11 J27 Settings
J27
1
2
3
Always SCON
J27
1
2
3
No SCON
(factory configuration)
1.6.10PCI Bus 1.0 Speed Switch (S4-2)
This switch can force PCI bus 1.0 to run at 33 MHz rather than the standard method of allowing
the PMC board to control whether the bus runs at 33 MHz or 66 MHz. Set to 1, it allows the
PMC board to choose the PCI 1.0 bus speed. Set to ON forces PCI bus 1.0 to run at 33 MHz.
Figure 1-12 S4-2 Settings
S4-2
1
2
PMC board controls
PCI 1.0 bus speed
(factory configuration)
ON
1
2
Force PCI bus 1.0
to run at 33 MHz
ON
J27
1
2
3
Auto-SCON
26
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 27
EEPROM Write Protect Switch (S3-3)Hardware Preparation and Installation
1.6.11EEPROM Write Protect Switch (S3-3)
This switch enables/disables prog ramming of the on-board EEPROMs as a means of protecting
the contents from being corrupted. Set to 1, it disables EEPROM programming by driving the
WP pin to a logic high. Set to ON to program any of the EEPROMs at addresses A0, A6, A8,
and/or AA.
Figure 1-13 S3-3 Settings
S3-3
1
2
3
4
Disables EEPROM
programming
ON
1
2
3
4
Enables EEPROM programming
(factory configuration)
ON
1.6.12Setting the PMC Vio Keying Pin
Signalling voltage (Vio) is determined by the location of the PMC Vio keying pin. Each site can
be independently configured for either +5V or +3.3V signalling. The option selected can be
determined by observing the location of the Vio keying pin.
Figure 1-14 VIO Keying Pin Settings
+3.3V key option on a PMC board +5V key option on a PMC board
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
27
Page 28
Hardware Preparation and InstallationInstalling the RAM5500 Module
1.7Installing the RAM5500 Module
Procedure
To upgrade or install a RAM5500 module, refer to 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 VME boards.
3. Carefully remove the MVME5500 from its VME card slot and lay it flat, with
connectors P1 and P2 facing you.
4. Inspect the RAM5500 module that is being installed on the MVME5500 host board
to ensure that standoffs are installed in the four mounting holes on the module.
5. With standoffs installed in the four mounting holes on the RAM5500 module, align
the standoffs and the P1 connector on the module with the four holes and the P4
connector on the MVME5500 host board and press the two connectors together
until they are firmly seated in place.
28
6. Turn the entire assembly over and fasten the four short Phillips screws to the
standoffs of the RAM5500.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 29
Installing PMCsHardware Preparation and Installation
7. Reinstall the MVME5500 assembly in its proper card slot f ollowing the procedure i n
the next section. Be sure t he host board is well sea ted in the back plane connectors.
Do not damage or bend connector pins.
8. Replace the chassis or system cover(s), reconnect the system to the AC or DC
power source and turn the equipment power on.
1.8Installing PMCs
This section discusses the installation of a PMC module onto the MVME5500 and the
installation of a primary and secondary PMCspan module onto the PMC/MVME5500 proce ssor
module.
If you have ordered one or more of the optional RAM500 memory mezzanine boards for the
MVME5500, 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 ref er to Installing the
RAM5500 Module on page 28 for installation instructions. It is recommended that the memory
mezzanine modules be installed prior to installing other board accessories, such as PMCs,
IPMCs or transition modules.
1.8.1Mounting the PMC Module
PMC modules mount on top of the MVME5500. Perform the following steps to install a
PMCmodule on your MVME5500.
Personal Injury or Death
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing and adjusting.
Product Damage
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.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
29
Page 30
Hardware Preparation and InstallationPrimary PMCspan
Procedure
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 y our 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 cov er(s)
as necessary for access to the VME modules.
3. If the MVME5500 has already been installed in a VMEbus card slot, carefully
remove it as shown in Figure 1-17 and place it with connectors P1 and P2 facing
you. Remove the filler plate(s) from the front panel of the MVME5500.
4. Insert the approp riate number of Phillips scre ws (typically 4 ) from the bottom of the
MVME5500 into the standoffs on the PMC module and tighten the screws (refer to
Figure 1-15).
5. Align the PMC module’s mating connectors to the MVME5500’ s mating connectors
and press firmly into place.
Figure 1-15 Typical Placement of a PMC Module on a VME Module
1.8.2Primary PMCspan
To install a PMCspan26E-002 PCI expansion module on your MVME5500, perform the
following steps while referring to the figure on the next page:
30
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 31
Primary PMCspanHardware Preparation and Installation
Procedure
This procedure assumes that you have read the user’s manual that was furnished with your
PMCspan.
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 y our 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 cov er(s)
as necessary for access to the VME modules.
3. If the MVME5500 has already been installed in a VMEbus card slot, carefully
remove it as shown in Figure 1-17 and place it with connectors P1 and P2 facing
you.
4. Attach the four standoffs to the MVME5500. For each standoff:
Insert the threaded end into the standoff hole at each corner of the MVME5500 an d
thread the locking nuts into the standoff tips and tighten.
5. Place the PMCspan on top of the MVME5500. Align the mounting holes in each
corner to the standoffs and align PMCspan connector P4 with MVME5100
connector J25.
Figure 1-16 PMCspan Installation on a VME Module
PMCspan
MVME5500
2081 9708
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
31
Page 32
Hardware Preparation and InstallationSecondary PMCspan
6. Gently press the PMCspan and MVME5500 together and verify that P4 is fully
seated in J4.
7. Insert four short screws (Phillips type) through the holes at the corners of the
PMCspan and into the standoffs on the MVME5500. Tighten screws securely.
1.8.3Secondary PMCspan
The PMCspanx6E-010 PCI expansion module mounts on top of a PMCspanx6E-002. T o install
a PMCspanx6E-010, perform the following steps while referring to the figure on the next page:
Personal Injury or Death
Dangerous voltages, capable of causing death, are present in this equipment.
Use extreme caution when handling, testing and adjusting.
Product Damage
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.
Procedure
This 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 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 y our 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 cov er(s)
as necessary for access to the VME module
3. If the Primary PMC Carrier Module and MVME5500 assembly is already installed in
the VME chassis, carefully remove it as shown in Figure 1-17 and place it with
connectors P1 and P2 facing you.
32
4. Remove four screws (Phillips type) from the standoffs i n each corner of the primary
PCI expansion module.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 33
Installing the BoardHardware Preparation and Installation
5. Attach the four standoffs from the PMCspanx6E-010 mounting kit to the
PMCspanx6E-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 PMCspanx6E-010 on top of the PMCspanx6E-002. Align the mounting
holes in each corner to the standoffs and align PMCspanx6E-010 connector P3 with
PMCspanx6E-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
PMCspanx6E-010 and into the standoffs on the primary PMCspanx6E-002. Tighten
screws securely.
The screws have two different head diameters. Use the screws with the smaller
heads on the standoffs next to VMEbus connectors P1 and P2.
You are now ready to install the module into the VME chassis. Follow the procedure, Installing
the Board on page 33.
1.9Installing the Board
Procedure
Use the following steps to install the MVME5500 into your computer chassis.
1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to an
electrical ground (refer to Unpacking Guidelines). The ESD strap must be secured
to your wrist and to ground throughout the procedure.
2. Remove any filler panel that might fill that slot.
3. Install the top and bottom edge of the MVME5500 into the guides of the chassis.
Only use injector handles for board insertion to avoid damage/deformation to the
front panel and/or PCB.
4. Ensure that the levers of the two injector/ejectors are in the outward position.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
33
Page 34
Hardware Preparation and InstallationConnection to Peripherals
5. Slide the MVME5500 into the chassis until resistance is felt.
Figure 1-17 Installation into a Typical VME Chas sis
6. Simultaneously move the injector/ejector levers in an inward direction.
7. Verify that the MVME5500 is prop erly seated and secure it to th e chassis using the
two screws located adjacent to the injector/ejector levers.
8. Connect the appropriate cables to the MVME5500.
1.9.1Connection to Peripherals
When the MVME5500 is installed in a chassis, you are ready to connect peripher als and apply
power to the board.
Figure 1-1 on page 20 shows the locations of the various connectors while Table 1-3 lists them
for you. Refer to Chapter 5, Connector Pin Assignments for the pin assignments of the
connectors listed below.
If a PMC module is plugged into PMC slot 1, the memory mezzanine card cannot be used
because the PMC module covers the memory mezzanine connector.
V erify that hardware is installed and the power/peripheral cables connected are appropriate for
your system configuration.
Replace the chassis or system cover , reconnect the system to the A C or DC power source, and
turn the equipment power on.
1.10Startup and Operation
This section gives you information about:
zThe power-up procedure
zSwitches and indicators
1.11Applying Power
After you verify that all necessary hardware preparation is complete and all connections are
made correctly, you can apply power to the system.
When you are ready to apply power to the MVME5500:
zVerify that the chassis power supply voltage setting matches the voltage present in the
country of use (if the power supply in your system is not auto-sensing)
zOn powering up, the MVME5500 brings up the MotLoad prompt, MVME5500>
1.12Switches and Indicators
The MVME5500 board provides a single push button switch that provides both Abort and Reset
(ABT/RST) functions. When the switch is depressed for less than three seconds, an abort
interrupt is generated to the processor. If the switch is held for more than three seconds, a
board hard reset is generated.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
35
Page 36
Hardware Preparation and InstallationSwitches and Indicators
The MVME5500 has two front-panel indicators:
zBFL, software controlled. Asserted by firmware (or other software) to indicate a
configuration problem (or other failure).
zCPU, connected to a CPU bus control signal to indicate bus activity.
The following table describes these indicators:
Table 1-4 Front-Panel LED Status Indicators
FunctionLabelColorDescription
CPU Bus ActivityCPUGreenCPU bus is busy.
Board FailBFLYellowBoard has a failure.
36
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 37
Functional Description
2.1Overview
This chapter describes the MVME5500 on a block diagram level.
2.2Block Diagram
Table 2-1 shows a block diagram of the overall board architecture.
Figure 2-1Block Diagram
2
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
37
Page 38
Functional DescriptionFeatures
2.3Features
The followin g table lists the features of the MVME5500.
Table 2-1 MVME5500 Features Summary
FeatureDescription
Processor– Single 1 GHz MPC7457 processor
L3 Cache– 2MB using DDR SRAM
Flash– 8MB Flash soldered on board
System Memory– Two banks on board for 512MB using 256MB devices
Memory Controller– Provided by GT-64260B
Processor Host Bridge– Provided by GT-64260B
PCI Interfaces– Provided by GT-64260B
Interrupt Controller– Provided by GT-64260B
Counters/Timers– Eight 32-bit counters/timers in GT-64260B
I2C– Provided by GT-64260B
NVRAM– 32KB provided by MK48T37
Real Time Clock– Provided by MK48T37
Watchdog Timers– One in GT-64260B
On-board Peripheral
Support
– Bus clock frequency at 133 MHz
– Bus clock frequency at 200 MHz
– 32MB expansion Flash soldered on board
– Expansion connector for a mezzanine board with two banks for
512MB using 256Mb devices
– Double-bit-error detect, single-bit-error correct across 72 bits
– Bus clock frequency at 133 MHz
– Supports one to four banks of SDRAM for up to 1GB per bank
– Supports MPX mode or 60x mode
– T wo ind ependent 64-bit interfaces, one compliant to PCI spec re v
2.1 (Bus 0.0) and the other compliant to PCI spec rev 2.2 (Bus 1.0)
– Bus clock frequency at 66 MHz
– Provided by the HiNT PCI 6154 secondary interface
– One 64-bit interface, compliant to PCI spec rev 2.1 (Bus 0.1)
– Bus clock frequency at 33 MHz
– Interrupt sources internal to GT-64260B
– Up to 32 external interrupt inputs
– Up to seven interrupt outputs
– Master or slave capable
– On-board serial EEPROMs for VPD, SPD, GT-64260B init, and
user data storage
– One in MK48T37
– Each watchdog timer can generate interrupt or reset, software
selectable
– One 10/100/1000BaseT Ethernet interface, one 10/100BaseT
Ethernet interface
– Dual 16C550 compatible UARTs
38
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 39
ProcessorFunctional Description
Table 2-1 MVME5500 Features Summary (continued)
FeatureDescription
PCI Mezzanine Cards– Two PMC sites (one shared with the expansion memory and has
PCI Expansion– One expansion connector for interface to PMCspan
Miscellaneous– Reset/Abort switch
Form Factor– Standard VME
IPMC capability)
– Front-panel status indicators, Run and Board Fail
2.4Processor
The MVME5500 supports the MPC7457 processor in the 483-pin CBGA package. The
processor consists of a processor core, an internal 256KB L2 and an internal L3 tag and
controller, which supports a backside L3 cache.
2.5L3 Cache
The MVME5500 uses two 8Mb DDR synchronous SRAM devices for the processor’ s L3 cache
data SRAM. This gives the processor a total of 2MB of L3 cache. These SRAM devices require
a 2.5V core voltage. The MVME5500 provides 1.5V as the SRAM I/O voltage. The L3 bus
operates at 200 MHz.
2.6System Controller
The GT-64260B system controller for P owerPC architecture processors is a single chip solution
that provides the following features:
zA 64-bit interface to the CPU bus
zA 64-bit SDRAM interface
zA 32-bit generic device interface for Flash, etc.
zTwo 64-bit, 66 MHz PCI bus interfaces
zThree 10/100Mb Ethernet MAC ports (two ports not used)
zA DMA engine for moving data between the buses
zAn interrupt controller
zAn I2C device controller
zPowerPC bus arbiter
zCounter/timers
zWatchdog timer
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
39
Page 40
Functional DescriptionCPU Bus Interface
Each of the device buses are de-coupled from each other, enabling concurrent operation of the
CPU bus, PCI buses and access to SDRAM. Refer to the GT-64260B System Controller for PowerPC Processors Data Sheet, listed in Appendix C, Related Documentation, for more
details.
2.6.1CPU Bus Interface
The GT-64260B supports MPX or 60x bus mode operation. The MVME5500 board has
jumper/build option resistors to select either operating mode at power-up.
2.6.2Memory Controller Interface
The GT-64260B can access up to four banks of SDRAM for a total of 1GB of SDRAM memory.
The memory bus is capable of operating up to 133 MHz.
The MVME5500 board has two banks on board and a connector for an expansion mezzanine
board with two additional banks.
2.6.3Interrupt Controller
The MVME5500 uses the interrupt controller integrated into GT-64260B to manage the GT64260B internal interrupts, as well as the external interrupt requests. The external interrupt
sources include the following:
The interrupt controller provides up t o seve n interrupt output pins f or various interrupt functions .
For additional details regarding the external interrupt assignments, refer to the MVME5500 Single-Board Computer Programmer’s Reference Guide.
2.6.4I2C Serial Interface and Devices
A two-wire serial interface for the MVME5500 board is provided by a master/slave capable I2C
serial controller integrated into the GT-64260B device. The I2C serial controller provides two
basic functions. The first function is to optionally provide GT-64260B register initialization
following a reset. The GT-64260B can be configured (by setting jumper J17) to automatically
read data out of a serial EEPROM following a reset and initialize any number of internal
registers. In the second function, the controller is used by the system software to read the
contents of the VPD EEPROM contained on the MVME5500 board, along with the SPD
EEPROM(s), to further initialize the memory controller and other interfaces.
40
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 41
Direct Memory Access (DMA)Functional Description
The MVME5500 board contains the following I2C serial devices:
z256 byte EEPROM for fixed GT-64260B initialization
z8KB EEPROM for VPD
z8KB EEPROM for user-defined VPD
z256 byte EEPROM for SPD
zDS1621 temperature sensor
The 8KB EEPROM devices are implemented using Atmel AT24C64 devices. These devices
use two byte addressing to address the 8KB of the device.
2.6.5Direct Memory Access (DMA)
The GT-64260B has an 8-channel DMA controller integrated in the device. Each DMA channel
is capable of moving data between any source and any destination. This controller can be
programmed to move up to 16MB of data per transaction. The GT-64260B DMA channels also
support chained mode of operation. For additional details regarding the GT-64260B DMA
capability, refer to the GT-64260B System Controller for PowerPC Processors Data Sheet,
listed in Appendix C, Related Documentation.
2.6.6Timers
The GT-64260B supplies eight 32-bit counters/timers, each of which can be programmed to
operate as a counter or a timer. The timing reference is based on the GT-64 26 0B Tclk input,
which is set at 133 MHz. Each counter/timer is capable of generating an interrupt.
The GT-64260B also has an internal 32-bit watchdog timer that can be configured to generate
an NMI or a board reset. After the watchdog timer is enabled, it becomes a free running counter
that must be serviced periodically to k eep it from expiring. F ollowing reset, the watchdog timer
is disabled.
The watchdog timer has two output pins, WDNMI and WDE. The WDNMI is asserted after the
timer is enabled and the 24-bit NMI_V AL count is reached. The WDNMI pin is connected to one
of the GT-64260B interrupt input pins so that an interrupt is generated when the NMI_VAL
count is reached. The WDE pin is asserted after the watchdog timer is enabled and the 32-bit
watchdog count expires. The WDE pin is connected to the board reset logic so that a board
reset is generated when WDE is asserted. For additional details, refer to the GT-64260B
System Controller for PowerPC Processors Data Sheet, listed in Appendix C, Related
Documentation.
2.7Flash Memory
The MVME5500 contains two banks of Flash memory accessed via the device controller
contained within the GT-6 4260B. The standard MVME5500 product is built with the 128Mb
devices.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
41
Page 42
Functional DescriptionSystem Memory
2.8System Memory
System memory for the MVME5500 is provided by one to four banks of ECC synchronous
DRAM in two banks. During system initialization, the firmware determines the presence and
configuration of each memory bank installed by reading the contents of the serial presence
detection (SPD) EEPROM on the board, and another one on the expansion memory module.
The system firmware then initializes the GT-64260B memory controller for proper operation
based on the contents of the serial presence detection EEPROM.
If a PMC module is plugged into PMC slot 1, the memory mezzanine card cannot be used
because the PMC module covers the memory mezzanine connector.
2.9PCI Local Buses and Devices
The GT-64260B on the MVME5500 provides two independent 64-bit, 33/66 MHz PCI buses.
The GT-64260B documen tation refers to these buses as PCI Bus 0 and PCI Bus 1.
The devices on Bus 1 are the GT-64260B PCI bridge 1, one 32/64-bit PMC slot, and an
825544EI LAN device. The devices on Bus 0 are the GT-64260B PCI bridge 0, one 32/64-bit
PMC slot and a HiNT PCI 6154 PCI-to-PCI bridge. For the purpose of this document, Bus 1 is
also identified as PCI Bus 1.0, and Bus 0 is also identified as PCI Bus 0.0.
2.9.1Gigabit Ethernet Interface
The MVME5500 provides a Gigabit Ethernet transceiver interface (1000BaseT) using an Intel
82544EI integrated Ethernet device (Ethernet 1). It also supports 100BaseTX and 10BaseT
modes of operation. The Ethernet interface is accessed via an industry-standard, front-panel
mounted RJ-45 connector.
2.9.210/100Mb Ethernet Interface
The 10/100Mb Ethernet interface (Ethernet 2) comes from the GT-64260B , and connects to an
external PHY. This port can be routed to a front-panel RJ-45 connector or to the P2 connector
with user-configurable jumpers.
Each Ethernet interface is assigned an Ethernet Station Address. The address is unique for
each device. The Ethernet Station Address is displayed on a label affixed to the board. The
assembly policy is to assign MAC addresses in such a manner that the higher value MAC
address is assigned to Ethernet port 1 and the lower to Ethernet port 2.
In addition, the Gigabit Ethernet address is stored in a configuration ROM interfaced to the
82544EI device, while the 10/100Mb Ethernet address is stored in the on-board VPD serial
EEPROM.
42
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 43
PCI-to-PCI BridgesFunctional Description
2.9.3PCI-to-PCI Bridges
The MVME5500 uses a PCI 2.1 compliant, 66 MHz capable, HiNT PCI 6154 PCI-to-PCI bridge.
The primary side connects to PCI Bus 0.0 of the GT-64260B and PMC/IPMC slot 1. The
secondary side connects to PCI Bus 0.1 on which a PMC expansion connector and the VME
controller resides.
2.9.4PMC Sites
The MVME5500 board supports two PMC sites. Both sites support processor PMC boards with
two IDSELs and two arbitration request/grant pairs. Slot 1 is connected to PCI Bus 0.0 of the
GT-64260B and is 66 MHz capable. Slot 2 is connected to PCI Bus 1.0 of the GT-64260B and
is also 66 MHz capable.
If a PMC module is plugged into PMC slot 1, the memory mezzanine card cannot be used
because the PMC module covers the memory mezzanine connector.
2.9.5PCI IDSEL Definition
PCI device configuration registers are accessed by using the IDSEL signal of each PCI agent
to an A/D signal as defined in the Peripheral Component Interconnect (PCI) Local Bus
Specification, Revision 2.2. IDSEL definitions for the MVME5500 are shown in the MVME5500
Single-Board Computer Programmer’s Reference Guide.
2.9.6PCI Bus Arbitration
PCI arbitration for the MVME5500 PCI Buses 0.0 and 1.0 is provided by an external arbiter
PLD. The arbiter PLD implements a round-robin priority algorithm. PCI arbitration for PCI Bus
0.1 is provided by the HiNT PCI 6154 secondary internal arbiter.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
43
Page 44
Functional DescriptionAsynchronous Serial Ports
2.10Asynchronous Serial Ports
The MVME5500 board uses two TL16C550C universal asynchronous receiver/transmitters
(UARTs) interf aced to the GT-64260B device bus to provide the asynchronous serial interfaces.
EIA232 drivers and receivers reside on board. COM1 signals are wired to an RS-232
transceiver that interfaces to the front-panel RJ-45 connector. COM2 signals are also wired to
a transceiver that interfaces to an on-board 9-pin header (refer to Chapter 5, Connector Pin
Assignments, for more details). An on-board 1.8432 MHz oscillator provides the baud rate clock
for the UARTs.
Figure 2-2COM1 Asynchronous Serial Port Connections (RJ-45)
DCD
RXD
TXD
DTR
GND
RTS
CTS
1
5
4
8
3
6
RJ45 Connector
2
7
DCD#
SIN
SOUT
DTR#
DSR#
TL16C550C
RTS#
CTS#
RI#
NC
NC
2.11Real Time Clock and NVRAM
The SGS-Thomson M48T37V is used by the MVME5500 board to provide 32KB of non-volatile
static RAM, real-time clock and watchdog timer. The watchdog timer, if enabled, can be
programmed to generate either an interrupt or system reset if it expires. Refer to the MK48T37V Data Sheet for programming information.
The M48T37V consists of two parts:
zA 44-pin 330mil SOIC device that contains the RTC, the oscillator, 32KB of SRAM and
gold-plated sockets for the SNAPHAT battery.
zA SNAPHAT battery that houses the cr ystal and the battery.
The SNAPHAT battery package is mounted on top of the SOIC MT48T37V device after the
completion of the surface mount process. The battery housing is keyed to prevent reverse
insertion.
44
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 45
System Control and Status RegistersFunctional Description
2.12System Control and Status Registers
The MVME5500 CPU board contain s System Control and Status Registers mapped into Bank
1 of the GT-64260B device bus interface. Refer for the MMVE5500 Single-Board Computer Programmer’s Reference Guide for details.
2.13Sources of Reset
The sources of reset on the MVME5500 are the following:
zPower-up
zAbort/Reset Switch
zNVRAM Watchdog Timer
zGT-64260B Watchdog Timer
zSystem Control register bit
zVME Bus Reset
2.14VME Interface
The MVME5500 provides a Unive r se II controller for the VMEbus interface.
2.15PMC Expansion
The MVME5500 provides a PMC expansion connector to add more PMC interfaces than the
two on the MVME5500 board. The connector is a Mictor AMP 767096-3 connector.
2.16Debug Support
The MVME5500 provides a boundary scan header (J18) and a COP (Riscwatch) header for
debug capability.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
45
Page 46
Functional DescriptionDebug Support
46
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 47
RAM55006E Memory Expansion
Module
3.1Overview
The RAM55006E memory expansion module can b e used on the MVME5500 as an option for
additional memory capabili ty. The expansion module has two banks of SDRAM with up to
512MB of available ECC memory. The RAM55006E incorporates a serial ROM (SROM) for
system memory serial presence detect (SPD) data. The RAM55006E will hereafter be called
the RAM5500.
3.2Features
The followin g table lists the features of the RAM5500 memory e x p an si on modu l e:
Table 3-1 RAM5500 Feature Summary
Form FactorDual-Sided Mezzanine
SROMSingle 256 x 8 I2C SROM for SPD data
SDRAMDouble-bit error detect, single-bit error correct across 72 bits;
3
512MB mezzanine memory (two banks of 256MB memory in each) at 133 MHz
3.3Functional Description
The following sections describe the physical and electrical structure of the RAM5500 memory
expansion module.
3.3.1RAM5500 Description
The RAM5500 is a memory expansion module that is used on the MVME5500 single board
computer. It is based on a single memory mezzanine board design with two banks of memory.
Each bank is 256MB of ECC memory using 256Mb devices in 32MB x 8 device organization.
The RAM5500 provides a total added capacity of 512MB to the MVME5500. The SDRAM
memory is controlled by the GT-64260B, which provides single-bit error correction and doublebit error detection. ECC is calculated over 72-bits. The on-board I2C SROM contains SPD data
for the two banks, which is used by the memory controller for configuration. Refer to the
MVME5500 Single Board Computer Programmer’s Reference Guide (V5500A/PG) for more
information.
The RAM5500 memory expansion module is connected to the host board with a 140-pin AMP
4mm Free Height plug connector. This memory expansion module draws +3.3V through this
connector.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
47
Page 48
RAM55006E Memory Expansion ModuleSROM
The RAM5500 SPD uses the SPD JEDEC standard definition and is accessed at address $A2.
Refer to the following section on SROM for more details.
Figure 3-1RAM500 Block Diagram
CLK (0:8)
Bank of 9 (x8)
SDRAM
Registers
AVC16722
A,
BA,
WE_L,
RAS_L,
CAS_L,
CS_C_L,
CS_D_L
3.3.2SROM
The RAM5500 memory expansion module contains a single +3.3V, 256 x 8, serial EEPROM
device (AT24C02). The serial EEPROM provides SPD storage of the module memory
subsystem configuration. The RAM5500 SPD is software addressable by a unique address.
3.3.3Clocks
The host board provides one SDRAM clock to the memory expansion connector. The frequency
of the RAM5500 CLKS is the same as the host board. This clock is used to generate the onboard SDRAM clocks using a phase lock loop zero delay clock driver.
Registers
AVC16374
DQM
MVME5500 Mezzanine Connector
SROM
SPD
SCL
SDA
A1_SPD
A0_SPD
PLL
Clock
Driver
CLK1
3.4Memory Expansion Connector Pin Assignments
The P1 connector on the RAM5500 is a 140-pin AMP 4mm Free Height mating plug. This plug
includes common ground contacts that mate with standard AMP receptacle assemblies or AMP
GIGA assemblies with ground plates. Refer to Memory Expansion Connector (P4)on page 86
for the P4 pin assignments.
48
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
*Common GND pins mate to a GIGA assembly with a ground plate. The GIGA assemb ly 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.
The RAM5500 contains no user programmable register, other than the SPD data.
3.5.1Serial Presence Detect (SPD) Data
This register is partially described for the RAM5500 within the MVME5500 Single Board
Computer Programmer’s Reference Guide. The register is accessed through the I2C interface
of the GT -64260B on the host board (MVME5500). The RAM5500 SPD is software addressable
by a unique address .
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
51
Page 52
RAM55006E Memory Expansion ModuleSerial Presence Detect (SPD) Data
52
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 53
MOTLoad Firmware
4.1Overview
This chapter describes the basic features of the MOTLoad firmware product, designed as the
next generation initialization, debugger and diagnostic tool for high-performance embedded
board products using state-of-the-art system memory controllers and bridge chips, such as the
GT-64260B.
In addition to an overview of the product, this chapter includes a list of standard MOTLoad
commands and the default VME settings that are changeable by the user, as allowed by the
firmware.
The MOTLoad firmware package serves as a board power-up and initialization package, as well
as a vehicle from which user applications can be booted. A secondary function of the MOTLoad
firmware is to serve in some respects as a test suite providing individual tests for certain
devices.
4
MOTLoad is controlled through an easy-to-use, UNIX-like, command line interface. The
MOTLoad software package is similar to many end-user applications designed for the
embedded market, such as the real time operating systems currently available.
Refer to the MOTLoad Firmware Package User’s Manual, listed in Appendix C, Related
Documentation, for more details.
4.2Implementation and Memory Requirements
The implementation of MOTLoad and its memory requirements are product specific. The
MVME5500 single-board computer (SBC) is offered with a wide range of memory (for e xample,
DRAM, external cache, Flash). Typically, the smallest amount of on-board DRAM that a
Emerson SBC has is 32MB. Each supported Emerson product line has its own unique
MOTLoad binary image(s). Currently the largest MOTLoad compressed image is less than 1MB
in size.
4.3MOTLoad Commands
MOTLoad supports two types of commands (applications): utilities and tests. Both types of
commands are invoked from the MOTLoad command line in a similar fashion. Beyond that,
MOTLoad utilities and MOTLoad tests are distinctly different.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
53
Page 54
MOTLoad FirmwareUtilities
4.3.1Utilities
The definition of a MOTLoad utility application is very broad. Simply stated, it is considered a
MOTLoad command if it is not a MOTLoad test. Typically, MOTLoad utility applications are
applications that aid the user in some way (that is, they do something useful). From the
perspective of MOTLoad, examples of utility applications are: configuration, data/status
displays, data manip ul a ti on , help routines, data/status monitors, etc.
Operationally, MOTLoad utility applications differ from MOTLoad test applications in several
ways:
zOnly one utility application operates at any given time (that is, multiple utility applications
cannot be executing concurrently).
zUtility applications may interact with the user. Most test applications do not.
4.3.2Tests
A MOTLoad test application determines whether or not the hardware meets a given standard.
Test applications are validation tests. Validation is conformance to a specification. Most
MOTLoad tests are designed to directly validate the functionality of a specific SBC subsystem
or component. These tests validate the operation of such SBC modules as: dynamic memory,
external cache, NVRAM, real time clock, etc.
All MOTLoad tests are designed to validate functionality with minimum user interaction. Once
launched, most MOTLoad tests operate automatically without any user interaction. There are a
few tests where the functionality being validated requires user interaction (that is, switch tests ,
interactive plug-in hardware modules, etc.). Most MOTLoad test results (error-data/status-data)
are logged, not printed. All MOTLoad tests/commands have complete and separate
descriptions (refer to the MOTLoad Firmware Package User’s Manual for this information).
All devices that are available to MOTLoad for validation/verification testing are represented by
a unique device path string. Most MOTLoad tests require the operator to specify a test device
at the MOTLoad command line when invoking the test.
A listing of all device path strings can be displayed through the devShow command. If an SBC
device does not have a device path string, it is not supported by MOTLoad and can not be
directly tested. There are a few exceptions to the device path string requirement, like testing
RAM, which is not considered a true device and can be directly tested without a device path
string. Refer to the devShow command description page in the MOTLoad Firmware Package User’s Manual.
Most MOTLoad tests can be organized to execute as a group of related tests (a testSuite)
through the use of the testSuite command. The expert operator can customize their testing
by defining and creating a custom testSuite(s). The list of built-in and user-defined MOTLoad
testSuites, and their test contents, can be obtained by entering testSuite -d at the
MOTLoad prompt. All testSuites that are included as part of a product specific MOTLoad
firmware package are product specific. For more information, refer to the testSuite
command description page in the MOTLoad Firmware Pac k ag e Use r ’s Manual.
54
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 55
Command ListMOTLoad Firmware
Test results and test status are obtained through the testStatus, errorDisplay, and
taskActive commands. Refer to the appropriate command description page in the MOTLoad
Firmware Pac kag e Use r ’s Manual for more information.
4.3.3Command List
The following table provides a list of all current MOTLoad commands. Products supported by
MOTLoad may or may not employ the full command set. Typin g help at the MOTLoad
command prompt will display all commands supported by MOTLoad for a given product.
Table 4-1 MOTLoad Commands
CommandDescription
asOne-Line Instruction Assembler
bcb
bch
bcw
bdTempShowDisplay Current Board Temperature
bfb
bfh
bfw
blkCpBlock Copy
blkFmtBlock Format
blkRdBlock Read
blkShowBlock Show Device Configuration Data
blkVeBlock Verify
blkWrBlock Write
bmb
cdDirISO9660 File System Directory Listing
cdGetISO9660 File System File Load
clearClear the Specified Status/History Table(s)
cmTurns on Concurrent Mode
Block Compare Byte/Halfword/Word
Block Fill Byte/Halfword/Word
Block Move Byte/Halfword/Word
Block Search Byte/Halfword/Word
Block Verify Byte/Halfword/Word
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
55
Page 56
MOTLoad FirmwareCommand List
Table 4-1 MOTLoad Commands (continued)
CommandDescription
csb
csh
csw
devShowDisplay (Show) Device/Node Table
diskBootDisk Boot (Direct-Access Mass-Storage Device)
downLoadDown Load S-Record from Host
dsOne-Line Instruction Disassembler
echoEcho a Line of Text
elfLoaderELF Object File Loader
errorDisplayDisplay the Contents of the Test Error Status Table
evalEvaluate Expression
execProgramExecute Program
fatDirFAT File System Directory Listing
fatGetFAT File System File Load
fdShowDisplay (Show) File Discriptor
flashLockFlash Memory Sector Lock
flashProgramFlash Memory Program
flashShowDisplay Flash Memory Device Configuration Data
flashUnlockFlash Memory Sector Unlock
gdGo Execute User-Program Direct (Ignore Break-Points)
gevDeleteGlobal Environment Variable Delete
gevDumpGlobal Environment Variable(s) Dump (NVRAM Header + Data)
gevEditGlobal Environment Variable Edit
gevInitGlobal Environment Variable Area Initialize (NVRAM Header)
gevListGlobal Environment Variable Labels (Names) Listing
gevShowGlobal Environment Variable Show
gnGo Execute User-Program to Next Instruction
goGo Execute User-Program
gtGo Execute User-Program to Temporary Break-Point
hbdDisplay History Buffer
hbxExecute History Buffer Entry
helpDisplay Command/Test Help Strings
l2CacheShowDisplay state of L2 Cache and L2CR register contents
l3CacheShowDisplay state of L3 Cache and L3CR register contents
Calculates a Checksum Specified by Command-line Options
56
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 57
Command ListMOTLoad Firmware
Table 4-1 MOTLoad Commands (continued)
CommandDescription
mdb
mdh
mdw
memShowDisplay Memory Allocation
mmb
mmh
mmw
mpuForkExecute program from idle processor
mpuShowDisplay multi-processor control structure
mpuStartStart the other MPU
netBootNetwork Boot (BOOT/TFTP)
netShowDisplay Network Interface Configuration Data
netShutDisable (Shutdown) Network Interface
netStatsDisplay Network Interface Statistics Data
noCmTurns off Concurrent Mode
pciDataRdRead PCI Device Configuration Header Register
pciDataWrWrite PCI Device Configuration Header Register
pciDumpDump PCI Device Configuration Header Register
pciShowDisplay PCI Device Configuration Header Register
pciSpaceDisplay PCI Device Address Space Allocation
pingPing Network Host
portSetPort Set
portShowDisplay Port Device Configuration Data
rdUser Program Register Display
resetReset System
rsUser Program Register Set
setSet Date and Time
sromReadSROM Read
sromWriteSROM Write
staSymbol Table Attach
stlSymbol Table Lookup
stopStop Date and Time (Power-Save Mode)
taskActiveDisplay the Contents of the Active Task Table
tcTrace (Single-Step) User Program
tdTrace (Single-Step) User Program to Address
testDiskTest Disk
Memory Display Bytes/Halfwords/Words
Memory Modify Bytes/Halfwords/Words
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
57
Page 58
MOTLoad FirmwareCommand List
Table 4-1 MOTLoad Commands (continued)
CommandDescription
testEnetPtPEthernet Point-to-Point
testNvramRdNVRAM Read
testNvramRdWrNVRAM Read/Write (Destructive)
testRamRAM Test (Directory)
testRamAddrRAM Addressing
testRamAltRAM Alternating
testRamBitToggleRAM Bit Toggle
testRamBounceRAM Bounce
testRamCodeCopyRAM Code Copy and Execute
testRamEccMonitorMonitor for ECC Errors
testRamMarchRAM March
testRamPatternsRAM Patterns
testRamPermRAM Permutations
testRamQuickRAM Quick
testRamRandomRAM Random Data Patterns
testRtcAlarmRTC Alarm
testRtcResetRTC Reset
testRtcRollOverRTC Rollover
testRtcTickRTC Tick
testSerialExtLoopSerial External Loopback
testSeriallntLoopSerial Internal Loopback
testStatusDisplay the Contents of the Test Status Table
testSuiteExecute Test Suite
testSuiteMakeMake (Create) Test Suite
testWatchdogTimerTests the Accuracy of the Watchdog Timer Device
tftpGetTFTP Get
tftpPutTFTP Put
timeDisplay Date and Time
transparentModeTransparent Mode (Connect to Host)
tsShowDisplay Task Status
upLoadUp Load Binary Data from Target
versionDisplay Version String(s)
vmeCfgManages user specified VME configuration parameters
vpdDisplayVPD Display
vpdEditVPD Edit
waitWait for Test Completion
58
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 59
Using the Command Line InterfaceMOTLoad Firmware
Table 4-1 MOTLoad Commands (continued)
CommandDescription
waitProbeWait for I/O Probe to Complete
4.4Using the Command Line Interface
Interaction with MOTLoad is performed via a command line interface through a serial port on
the single board computer, which is connected to a terminal or terminal emulator (for example,
Window’s Hypercomm). The default MOTLoad serial port settings are: 9600 baud, 8 bits, no
parity.
The MOTLoad command line interface is similar to a UNIX command line shell interface.
Commands are initiated by entering a valid MOTLoad command (a text string) at the MOTLoad
command line prompt and pressing the carriage-return ke y to signify the end of input. MOTLoad
then performs the specified action. An example of a MOTLoad command line prompt is shown
below. The MOTLoad prompt changes according to what product it is used on (for example,
MVME6100, MVME3100, MVME5500).
Example:
MVME5500>
If an invalid MO TLoad command is entered at the MOTLoad command line prompt, MOTLoad
displays a message that the command was not found.
Example:
MVME5500> mytest
"mytest" not found
MVME5500>
If the user enters a partial MOTLoad command string that can be resolved to a unique valid
MOTLoad command and presses the carriage-return key, the command is executed as if the
entire command string had been entered. This feature is a user-input shortcut that minimizes
the required amount of command line input. MOTLoad is an ever changing firmware package,
so user-input shortcuts may change as command additions are made.
Example:
MVME5500>[ver]sion
Copyright: Motorola Inc.1999-2005, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 1.0 RM01
Mon Aug 29 15:24:13 MST 2005
MVME5500>
Example:
MVME5500> ver
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
59
Page 60
MOTLoad FirmwareRules
Copyright: Motorola Inc.1999-2005, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 1.0 RM01
Mon Aug 29 15:24:13 MST 2005
MVME5500>
If the partial command string cannot be resolved to a single unique command, MOTLoad
informs the user that the command was ambiguous.
Example:
MVME5500> te
"te" ambiguous
MVME5500>
4.4.1Rules
There are a few things to remember when entering a MOTLoad command:
zMultiple commands are permitted on a single command line, provided they are separated
by a single semicolon (;).
zSpaces separate the various fields on the command line (command/arguments/options).
zThe argument/option identifier character is always preceded by a hyphen (-) character.
zOptions are identified by a single character.
zOption arguments immediately follow (no spaces) the option.
zAll commands, command options, and device tree strings are case sensitive.
Example:
MVME5500> flashProgram –d/dev/flash0 –n00100000
For more information on MOTLoad operation and function, refer to the MOTLoad Firmware
Package User’s Manual.
4.4.2Help
Each MOTLoad firmware package has an extensive, product-specific help facility that can be
accessed through the help command. The user can enter help at the MOTLoad command
line to display a complete listing of all available tests and utilities.
Example
MVME5500> help
For help with a specific test or utility the user can enter the following at the MOTLoad prompt:
help <command_name>
60
The help command also supports a limited form of pattern matching. Refer to the help
command page.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
-a Ph: Address to Start (Default = Dynamic Allocation)
-b Ph: Block Size (Default = 16KB)
-i Pd: Iterations (Default = 1)
-n Ph: Number of Bytes (Default = 1MB)
-t Ph: Time Delay Between Blocks in OS Ticks (Default = 1)
-v O : Verbose Output
MVME5500>
4.5Firmware Settings
The following sections provide additional information pertaining pertaining to the MVME5500
VME bus interface settings as configured by MOTLoad. A few VME settings are controlled by
hardware jumpers while the majority of the VME settings are managed by the firmware
command utility vmeCfg.
4.5.1Default VME Settings
As shipped from the factory, the firmware on the MVME5500 will program default values into
the Universe II VME Interface chip. The firmware allows certain VME settings to be changed in
order for the user to customize his/her environment. The following is a description of the default
VME settings that are changeable by the user. For more information, refer to the MOTLoad
User’s Manual and Tundra’s Universe II User Manual, listed in Appendix C, Related
Documentation.
zVME3PCI Master Enable = Y
N = Do not set up or enable the VMEbus Interface.
Y= Set up and enable the VMEbus Interface.
zPCI Slave Image 0
This image is set to zeroes and thus disabled.
zPCI Slave Image 1 Control = C0820000
Sets LSI1_CTL to indicate that this image is enabled, write posting is enabled, VMEbus
data width is 32 bits, VMEbus address space is A32, data and non-supervisory AM
encoding, no BL T transf ers to the VMEbus, and to accept addresses in PCI memory space.
zPCI Slave Image 1 Base Address Register = 91000000
Sets LSI1_BS to indicate that the lower bound of PCI memory addresses to be transferred
to the VMEbus by this image is 0x91000000.
Sets LSI1_BD to indicate that the upper bound of PCI memory addresses to be transferred
by this image is 0xB0000000.
zPCI Slave Image 1 Translation Offset = 70000000
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
61
Page 62
MOTLoad FirmwareDefault VME Settings
Sets LSI1_TO to indicate that the PCI memory address is to be translated by 0x70000000
before presentation on the VMEbus; the result of the translation is: 0x91000000 +
0x70000000 = 0x101000000, thus 0x01000000 on the VMEbus.
zPCI Slave Image 2 Control = C0410000
Sets LSI2_CTL to indicate that this image is enabled, write posting is enabled, VMEbus
data width is 16 bits, VMEbus address space is A24, data and non-supervisory AM
encoding, no BL T transf ers to the VMEbus, and to accept addresses in PCI memory space.
zPCI Slave Image 2 Base Address Register = B0000000
Sets LSI2_BS to indicate that the lower bound of PCI memory addresses to be transferred
to the VMEbus by this image is 0xB0000000.
Sets LSI2_BD to indicate that the upper bound of PCI memory addresses to be transferred
by this image is 0xB1000000.
zPCI Slave Image 2 Translation Offset = 400000000
Sets LSI2_TO to indicate that the PCI memory address is to be translated by 0x40000000
before presentation on the VMEbus; the result of the translation is: 0xB0000000 +
0x40000000 = 0xF0000000, thus 0xF0000000 on the VMEbus.
zPCI Slave Image 3 Control = C0400000
Sets LSI3_CTL to indicate that this image is enabled, write posting is enabled, VMEbus
data width is 16 bits, VMEbus address space is A16, data and non-supervisory AM
encoding, no BL T transf ers to the VMEbus, and to accept addresses in PCI memory space.
zPCI Slave Image 3 Base Address Register = B3FF0000
Sets LSI3_BS to indicate that the lower bound of PCI memory addresses to be transferred
to the VMEbus by this image is 0xB3FF0000.
Sets LSI3_BD to indicate that the upper bound of PCI memory addresses to be transferred
by this image is 0xB4000000.
zPCI Slave Image 3 Translation Offset = 4C000000
Sets LSI3_TO to in dicate that th e PCI memory address is to be tran slated b y 0x4C0000 00
before presentation on the VMEbus; the result of the translation is: 0xB3FF0000 +
0x4C000000 = 0xFFFF0000, thus 0xFFFF0000 on the VMEbus.
zPCI Slave Image 4 -7
These images are set to zeroes and thus disabled.
zVMEbus Slave Image 0 Control = E0F20000
Sets VSI0_CTL to indicate that this image is enabled, write and read posting is enabled,
program/data and supervisory AM coding, data width is 32 bits, VMEbus A32 address
space, 64-bit PCI transfers are disabled, PCI Lock on RMW cycles are disabled, and to
transfer into PCI memory space.
zVMEbus Slave Image 0 Base Address Register = 00000000
Sets VSI0_BS to define the lower bound of VME addresses to be transferred to the local
PCI bus is 0x00000000.
Sets VSI0_TO to define that no translation of the VMEbus address is to occur when
transferred to the local PCI b us . According to the CHRP map in use by MOTLoad, this will
result in transfers to local DRAM; that is, 0x00000000 on the VMEbus is 0x00000000 in
local DRAM.
zVMEbus Slave Image 1 - 7
These images are set to zeroes and thus disabled.
zVMEbus Register Access Image Control Register = 00000000
The VRAI_CTL register is disabled.
zVMEbus Register Access Image Base Address Register = 00000000
The contents of the VRAI_BS register are not applicable since the image is disabled.
zPCI Miscellaneous Register = 10000000
The LMISC register is set for Universe I compatibility and the coupled window timer is
disabled.
zSpecial PCI Slave Image Register = 00000000
The SLSI register is disabled.
zMaster Control Register = 00C00000
The MAST_CTL register is set to retry forev er bef ore the PCI master signals error , transf er
128 bytes on posted writes before release, use VMEbus request level 3, request mode =
Demand, Release When Done, align PCI transfers on 32 bytes and use PCI bus 0.
zMiscellaneous Control Register = 52040000
Sets MISC_CTL register to utilize 256 second VMEbus timeout, round robin arbitration, 256
second arbitration timeout, do not use BI-mode and assertion of VIRQ1 is to be ignored.
VMEbus A32/D32 addresses from 0x00000000 to (local DRAM size) address the local
memory of the MVME5500.
The followin g sectio ns provide additional information pertaining to the VME firmware settings
of the MVME5500. A few VME settings are controlled by hardware jumpers while the majority
of the VME settings are managed by the firmware command utility vmeCfg.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
63
Page 64
MOTLoad FirmwareDefault VME Settings
4.5.1.1CR/CSR Settings
The firmware supports both Auto Slot ID and Geographical Addressing for assigning the
CR/CSR base address dependent on a hardware jumper setting. See the VME64 Specification
and the VME64 Extensions for details. As a result, a 512K byte CR/CSR area can be accessed
from the VMEbus using the CR/CSR AM code.
4.5.1.2Displaying VME Settings
To display the changeable VME setting, type the following at the firmware prompt:
zvmeCfg -s -m
Displays Master Enable state
zvmeCfg -s -i(0 - 7)
Displays selected Inbound Window state
zvmeCfg -s -o(0 - 7)
Displays selected Outbound Window state
zvmeCfg -s -r184
Displays PCI Miscellaneous Register state
zvmeCfg -s -r188
Displays Special PCI Target Image Register state
zvmeCfg -s -r400
Displays Master Control Register state
zvmeCfg -s -r404
Displays Miscellaneous Control Register state
zvmeCfg -s -r40C
Displays User AM Codes Register state
zvmeCfg -s -rF70
Displays VMEbus Register Access Image Control Register state
4.5.1.3Editing VME Settings
To edit the changeable VME setting, type the following at the firmware prompt:
zvmeCfg -e -m
Edits Master Enable state
zvmeCfg -e -i(0 - 7)
Edits selected Inbound Window state
zvmeCfg -e -o(0 - 7)
Edits selected Outbound Window state
zvmeCfg -e -r184
Edits PCI Miscellaneous Register state
zvmeCfg -e -r188
Edits Special PCI Target Image Register state
64
zvmeCfg -e -r400
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 65
Default VME SettingsMOTLoad Firmware
Edits Master Control Register state
zvmeCfg -e -r404
Edits Miscellaneous Control Register state
zvmeCfg -e -r40C
Edits User AM Codes Register state
zvmeCfg -e -rF70
Edits VMEbus Register Access Image Control Register state
4.5.1.4Deleting VME Settings
T o delete the changeable VME setting (restore default value), type the f ollowing at the firmware
prompt:
zvmeCfg -d -m
Deletes Master Enable state
zvmeCfg -d -i(0 - 7)
Deletes selected Inbound Window state
zvmeCfg -d -o(0 - 7)
Deletes selected Outbound Window state
zvmeCfg -d -r184
Deletes PCI Miscellaneous Register state
zvmeCfg -d -r188
Deletes Special PCI Target Image Register state
zvmeCfg -d -r400
Deletes Master Control Register state
zvmeCfg -d -r404
Deletes Miscellaneous Control Register state
zvmeCfg -d -r40C
Deletes User AM Codes Register state
zvmeCfg -d -rF70
Deletes VMEbus Register Access Image Control Register state
4.5.1.5Restoring Default VME Settings
To restore all of the changeable VME setting back to their default settings, type the following at
the firmware prompt:
vmeCfg -z
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
65
Page 66
MOTLoad FirmwareRemote Start
4.6Remote Start
As described in the MOTLoad Firmware Package User's Manual, listed in Appendix C, Related
Documentation, remote start allows the user to obtain information about the target board,
download code and/or data, modify memory on the target, and ex ecute a downloaded program.
These transactions occur across the VMEbus in the case of the MVME5500. MOTLoad uses
one of four mailboxes in the Universe II as the inter-board communication address (IBCA)
between the host and the target.
CR/CSR slave addresses configured by MOTLoad are assigned according to the installation
slot in the backplane, as indicated by the VME64 Specification. For reference, the following
values are provided:
CR/CSR space for a board in the 1st slot will start at 0x0008.0000
CR/CSR space for a board in the 2nd slot will start at 0x0010.0000
CR/CSR space for a board in the 3rd slot will start at 0x0018.0000
CR/CSR space for a board in the 4th slot will start at 0x0020.0000
CR/CSR space for a board in the 5th slot will start at 0x0028.0000
CR/CSR space for a board in the 6th slot will start at 0x0030.0000
CR/CSR space for a board in the 7th slot will start at 0x0038.0000
CR/CSR space for a board in the 8th slot will start at 0x0040.0000
CR/CSR space for a board in the 9th slot will start at 0x0048.0000
CR/CSR space for a board in the ath slot will start at 0x0050.0000
CR/CSR space for a board in the bth slot will start at 0x0058.0000
CR/CSR space for a board in the cth slot will start at 0x0060.0000
For further details on CR/CSR space, please refer to the VME64 Specification, listed in
Appendix C, Related Documentation.
The MVME5500 uses a Tundra Universe II for its VME bridge. The offsets of the mailboxes in
the Universe II are defined in the Universe II User Manual, listed in Appendix C, Related
Documentation, but are noted here for reference:
Mailbox 0 is at offset 7f348 in the CR/CSR space
Mailbox 1 is at offset 7f34C in the CR/CSR space
Mailbox 2 is at offset 7f350 in the CR/CSR space
Mailbox 3 is at offset 7f354 in the CR/CSR space
The selection of the mailbox used by remote start on an individual MVME5500 is determined
by the setting of a global environment variable (GEV). The default mailbox is zero . Another GEV
controls whether remote start is enabled (default) or disabled. Refer to the Remote Start
chapter in the MOTLoad Firmware Package User's Manual for remote start GEV definitions.
The MVME5500’s IBCA needs to be mapped appropriately through the master’s VMEbus
bridge. For example, to use remote start using mailbox 0 on an MVME5500 installed in slot 5,
the master would need a mapping to support reads and writes of address 0x002ff348 in VME
CR/CSR space (0x280000 + 0x7f348).
66
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 67
Connector Pin Assignments
5.1Introduction
This chapter provides pin assignments for various headers and connectors on the MMVE5500
single-board computer.
This section discusses the various connectors on the MVME5500.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
67
Page 68
Connector Pin AssignmentsAsynchronous Serial Port Connector (J1)
5.2.1Asynchronous Serial Port Connector (J1)
An RJ-45 receptacle is located on the front panel of the MVME5500 board to provide the
interface to the COM1 serial port. The pin assignments for this connector are as follows:
Table 5-1 COM1 Connector (J1) Pin Assignments
PinSignal
1DCD
2RTS
3GNDC
4TXD
5RXD
6GNDC
7CTS
8DTR
5.2.2Ethernet Connectors (J2)
Dual RJ-45 connectors are located on the front panel of the MVME5500 to provide the interface
to the 10/100/1000BaseTX Ethernet ports. The pin assignments for these connectors are as
follows:
Table 5-2 Ethernet Connector (J2) Pin Assignments
Pin1000BaseTX10/100BaseT
1MDIO0_PTD+
2MDIO0_NTD–
3MDIO1_PRD+
4MDIO2_PAC Ter m inated
5MDIO2_NAC Terminated
6MDIO1_NRD–
7MDIO3_PAC Ter m inated
8MDIO3_NAC Terminated
68
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 69
IPMC Connector (J3)Connector Pin Assignments
5.2.3IPMC Connector (J3)
One 40-pin Molex .635 mm (.025") pitch board-to-board receptacle (52885) is used to provide
a planar interface to IPMC module signals. This receptacle mates with the Molex 53627 plug
thus providing the 10.0 mm stacking height of the PMC card. The pin assignments for this
connector are as follows:
One 114-pin Mictor connector with a center row of power and ground pins is used to provide
PCI/PMC expansion capability. The pin assignments for this connector are as follows:
5.2.9Asynchronous Serial Port (COM2) Planar Connector (J33)
A 10-pin 0.100" planar connector provides the interface to a second asynchronous serial debug
port. The pin assignments for this connector are as follows:
The VME P1 and P2 connectors are 160-pin DINs. The P1 connector provides power and VME
signals for 24-bit address and 16-bit data. The pin assignments for the P1 connector are
specified by the VME64 Extension Standard (refer to Appendix C, Related Documentation, for
the link to this specification).
Row B of the P2 connector provides power to the MVME5500 and to the upper eight VMEbus
address lines, and additional 16 VMEbus data lines. Please read the notes below as they
pertain to the P2 connector.
1. When J28 is configured for IPMC mode, –12V is supplied to P2 pin A30. If there is an
incompatible board plugged into this P2 slot, damage may occur.
2. When J32 is configured for IPMC mode, +12V is supplied to P2 pin C7. If there is an
incompatible board plugged into this P2 slot, damage may occur.
3. J102 – J110 should be configured for PMC 2 I/O to connect PMC slot 2 user I/O from J24
to the P2 connector.
The pin assignments for the P2 connector are as follows:
The VME P1 and P2 connectors are 160-pin DINs. The P1 connector provides power and VME
signals for 24-bit address and 16-bit data. The pin assignments for the P1 connector are
specified by the VME64 Extension Standard (refer to Appendix C, Related Documentation, for
the link to this specification).
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Row B of the P2 connector provides power to the MVME5500 and to the upper eight VMEbus
address lines, and additional 16 VMEbus data lines. Please read the configuration notes below
as they apply to the P2 connector.
1. When J28 is configured for IPMC mode, –12V is supplied to P2 pin A30. If there is an
incompatible board plugged into this P2 slot, damage may occur.
2. When J32 is configured for IPMC mode, +12V is supplied to P2 pin C7. If there is an
incompatible board plugged into this P2 slot, damage may occur.
3. J102 – J110 should be configured for IPMC I/O to connect the IPMC extended SCSI signals
from J3 to the P2 connector.
The pin assignments for the P2 connector are as follows:
Functionality for rows A and C and Z (Z1, 3, 5, 7, 9, 11, 13, 15, and 17) is provided by the
IPMC761 in slot 1 and the MVME5500 Ethernet port 2.
5.2.12Memory Expansion Connector (P4)
One 140-pin connector is used to provide memory expansion capability. This connector
interfaces to up to two additional banks of memory . The pin assignments f or this connector are
as follows:
If a PMC module is plugged into PMC slot 1, the memory mezzanine card cannot be used
because the PMC module covers the memory mezzanine connector.
All of the headers described below are used in conjunction with each other to select various
modes of operation for 10/100BaseT Ethernet, PMC/SBC mode and P2 I/O mode.
88
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Four 3-pin 2 mm planar headers and four 2-pin 2 mm planar headers are for 10/100/BaseT
Ethernet 2 selection. Ethernet 1 is the Gigabit Ethernet port and is front panel only. The
pin assignments for these headers are as follows:
For rear P2 Ethernet, install jumpers across pins 2-3 on all four headers (J6, J7, J100 and
J101). For front-panel Ethernet, install jumpers across pins 1-2 on all four headers.
If the rear P2 Ethernet is selected by jumpers J6, J7, J100 and J101, the Ethernet signals also
connect to PMC 1 user I/O connector J14. If a PMC card is plugged into PMC 1, there may be
a conflict between the I/O from the PMC card and the rear Ethernet signals. This conflict does
not occur with the IPMC761 or IPMC712 modules.
For rear P2 Ethernet, install jumpers on all four headers (J34, J97, J98 and J99) when in
SBC/IPMC761 mode. No jumpers are installed for front-panel Ethernet.
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Two 3-pin planar headers on the MVME5500 are for PMC/SBC mode selection. For PMC
mode, install jumpers across pins 1-2 on both headers. For SBC/IPMC761 mode, install
jumpers across pins 2-3 on both headers. For SBC/IPMC712 mode, install a jumper across pins
2-3 for J32 and install a jumper across pins 1-2 for J28. Selection notes follow the table. The
pin assignments for these headers are as follows:
1. When J28 is configured for SBC/IPMC mode, –12V is supplied to P2 pin A30. If there is an
incompatible board plugged into this P2 slot, damage may occur.
2. When J32 is configured for SBC/IPMC mode, +12V is supplied to P2 pin C7. If there is an
incompatible board plugged into this P2 slot, damage may occur.
3. Install jumpers across pins 1-2 on both headers to select PMC mode. Install jumpers across
pins 2-3 on both headers to select SBC/IPMC761 mode. Install a jumper across pins 2-3
on J32 and install a jumper across pins 1-2 on J28 to select SBC/IPMC712 mode.
90
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Nine 3-pin 2 mm planar headers are for P2 I/O selection. Install jumpers across pins 1-2 on all
nine headers to select PMC 2 I/O for P2 in PMC mode. Install jumpers across pins 2-3 on all
nine headers to select IPMC I/O for P2 in SBC/IPMC761 or SBC/IPMC712 mode. The pin
assignments for these headers are as follows:
J4 - 1 to 9,11 to 16, 18,20 to 24, 26,28, 30 to 35,37, 39, 42,44, 46, 48,50 to 52, 54,56, 58, 60 to
P1 -
P2 -
J14-1,3,5,7
Pair
Ethernet
+12v
J100,
J101
J-45
C7
C7
64
PMC1_IO (3, 1, 7, 5, 11, 9, 15, 13, 17, 21,
19, 25, 24, 29, 27, 31, 33, 37, 35, 41, 39,
43, 38, 40, 44, 42, 48, 46, 45, 47, 49, 51,
50, 52, 54, 56, 60, 58, 62, 64, 53, 55, 59,
57, 63, 61)
PMC1_IO(13)
P2_PMC1_IO(13)
J32
PMC1_IO(60)
P1 -
A30
P2 -
A30
P2_PMC1_IO(60)
-12v
J14-13
J28
P1-Z1 to Z17
(odd pins)
P2-Z1 to Z17
J102-
J110
P2_PMC2_IO(2,5,8,11,14,17,20,23,26)
PMC2_IO(2,5,8,11,14,17,20,23,26)
J14-60
J24-2,5,8,11,14,17,20,23,26
J3 - 2 to 64
(even pins)
PMC2_IO (1, 3, 4, 6, 7, 9, 10, 12, 13, 15,
16, 18, 19, 21, 22, 24, 25, 27, 28, 30, 31,
33, 34, 36, 37, 39, 40, 42, 43, 45, 44, 46)
PMC1_IO
P1 - A19 to
(odd pins)
J3
PMC2_IO
A32, C5, C6,
C8 to C32
P2
PMC1_IO (64:1)
P1 - D1 to
D30, Z29,
Z31
P2
PMC2_IO (46:1)
J14
J24
Note: All PMC I/O nets are 0.010" wide for current
carrying capability on the MVME5500.
94
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 95
Flash Boot Bank Select Header (J8)Connector Pin Assignments
5.3.2Flash Boot Bank Select Header (J8)
A 3-pin 2 mm planar header selects the boot Flash ba nk. No jumper or a jumper installed across
pins 1-2 selects Flash 0 as the boot bank. A jumper installed across pins 2-3 selects Flash 1 as
the boot bank. The pin assignments for this header are as follows:
Table 5-24 Flash Boot Bank Select Header (J8) Pin Assignments
PinSignal
1GND
2BANK_SEL
3+3.3V
5.3.3VME SCON Select Header (J27)
A 3-pin 2 mm planar header allows the choice for auto/enable/disable SCON VME
configuration. A jumper installed across pins 1-2 configures for SCON disabled. A jumper
installed across pins 2-3 configures for auto SCON. No jumper installed configures for SCON
always enabled. The pin assignments for this header are as follows:
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 97
ASpecifications
A.1Power Requirements
In its standard configuration, the MVME5500 requires +5V, +12V, and
–12V for operation. On-board converters supply the processor core voltage, +3.3V, +1.5V,
+1.8V, and +2.5V.
A.1.1Supply Current Requirements
Table A-1 provides an estimate of the typical and maximum curre nt requ ired from each of the
input supply voltages.
Table A-1 Power Requirements
ModelPower +5V ± 5%
MVME5500-0163Typical: 6.7 A
MVME5500-0163 with memory mezzanineTypical: 7.5A
MVME5500-0163 with IPMC712/761Typical: 7.60 A
A
Maximum: 8.0 A
Maximum: 9.0 A
Maximum: 9.2 A
In a 3-row chassis, PMC current should be limited to 19.8 watts (total of both PMC slots). In a
5-row chassis, PMC current should be limited to 46.2 watts (total of both PMC slots).
A.2Environmental Specifications
Table A-2 lists the environmental specifications, along with the board dimensions.
Table A-2 MVME5500 Specifications
CharacteristicsSpecifications
Operating Temperature0° to +55° C (forced air cooling required)
400 LFM (linear feet per minute) of forced air cooling is
recommended for operation in the upper temperature range.
Storage Temperature–40° to 70° C
Relative HumidityOperating: 5% to 90% non-condensing
Non-operating: 5% to 95% non-condensing
VibrationNon-operating: 1 G sine sweep, 5–100 Hz,
horizontal and vertical (NEBS1)
Physical Dimensions6U, 4HP wide (233 mm x 160 mm x 20 mm)
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
97
Page 98
SpecificationsEnvironmental Specifications
Table A-2 MVME5500 Specifications (continued)
CharacteristicsSpecifications
MTBF207,058 hours
98
MVME55006E Single-Board Computer Installation and Use (6806800A37D)
Page 99
BThermal Validation
B.1Overview
Board component temperatures are affected by ambient temperature, air flow , board electrical
operation and software operation. In order to evaluate the thermal performance of a circuit
board assembly, it is necessary to test the board under actual operating conditions. These
operating conditions vary depending on system design.
While Emerson performs thermal analysis in a representative system to verify operation within
specified ranges, refer to Appendix A, Specifications, you should evaluate the thermal
performance of the board in your application.
This appendix provides systems integrators with information which can be used to conduct
thermal evaluations of the board in their specific system configuration. It identifies thermally
significant components and lists the corresponding maximum allowable component operating
temperatures. It also provides example procedures for component-level temperature
measurements.
B
B.2Thermally Significant Components
The following table summarizes components that exhibit significant temperature rises. These
are the components that should be monitored in order to assess thermal performance. The
table also supplies the component reference designator and the maximum allowable operating
temperature.
You can find components on the board by their reference designators as shown in Figure B-2
and Figure B-1. V e rsions of the board that are not fully populated may not contai n some of these
components.
The preferred measurement location for a component may be junction, case, or air as specified
in the table. Junction temperature refers to the temperature measured by an on-chip thermal
device. Case temperature refers to the temperature at the top, center surf ace of the component.
Air temperature refers to the ambient temperature near the component.