Intel® is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Java™ and all other Java-based marks are trademarks or registered trademarks of Oracle America, Inc. in the U.S. and other countries.
Microsoft®, Windows® and Windows Me® are registered trademarks of Microsoft Corporation; and Windows XP™ is a trademark of
Microsoft Corporation.
PICMG®, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logos are registered trademarks of the PCI
Industrial Computer Manufacturers Group.
UNIX® is a registered trademark of The Open Group in the United States and other countries.
Notice
While reasonable efforts have been made to assure the accuracy of this document, Artesyn assumes no liability resulting from any
omissions in this document, or from the use of the information obtained therein. Artesyn reserves the right to revise this document
and to make changes from time to time in the content hereof without obligation of Artesyn 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
an Artesyn website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise
altered without the permission of Artesyn.
It is possible that this publication may contain reference to or information about Artesyn 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
Artesyn intends to announce such Artesyn 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 Artesyn.
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).
MVME6100 Single Board Computer Installation and Use (6806800D58H)
9
Page 10
List of Figures
10
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 11
About this Manual
Overview of Contents
This manual is divided into the following chapters and appendices:
Hardware Preparation and Installation, provides MVME6100 board preparation and installation
instructions, as well as ESD precautionary notes.
Startup and Operation, provides the power-up procedure and identifies the switches and
indicators on the MVMEM6100.
MOTLoad Firmware, describes the basic features of the MOTLoad firmware product.
Functional Description, describes the MVME6100 on a block diagram level.
Pin Assignments, provides pin assignments for various headers and connectors on the
MMVE6100 single-board computer.
Specifications, provides power requirements and environmental specifications.
Thermal Validation, provides information to conduct thermal evaluations and identifies
thermally significant components along with their maximum allowable operating
temperatures.
Related Documentation, provides a listing of related Artesyn manuals, vendor documentation,
and industry specifications.
Safety Notes summarizes the safety instructions in the manual.
Sicherheitshinweise is a German translation of the Safety Notes chapter.
The MVME61006E Series Single-Board Computer Installation and Use manual provides the
information you will need to install and configure your MVME61006E single-board computer
(hereinafter referred to as MVME6100). It provides specific preparation and installation
information, and data applicable to the board.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
11
Page 12
About this Manual
About this Manual
As of the printing date of this manual, the MVME61006E supports the models listed below.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 13
TermDefinition
IEEEInstitute of Electrical and Electronics Engineers
LEDLight Emitting Diode
MHzMegahertz
MCPMulti-Chip Package
MRAMMagnetoresistive Random Access Memory
OSOperating System
PCBPrinted Circuit Board
PCIPeripheral Component Interconnect
PCI-EPCI Express
PCI-XPeripheral Component Interconnect eXtended
PIMPCI Mezzanine Card Input/Output Module
About this Manual
PLDProgrammable Logic Device
PMCPCI Mezzanine Card (IEEE P1386.1)
PrPMCProcessor PCI Mezzanine Card
RTCReal-Time Clock
RTMRear Transition Module
SATASerial AT Attachment
SDRSingle Data Rate
UARTUniversal Asynchronous Receiver-Transmitter
USBUniversal Serial Bus
VITAVMEbus International Trade Association
VMEVersa Module Eurocard
XMCPCI Express Mezzanine Card
MVME6100 Single Board Computer Installation and Use (6806800D58H)
13
Page 14
Conventions
The following table describes the conventions used throughout this manual.
NotationDescription
0x00000000Typical notation for hexadecimal numbers (digits are
0b0000Same for binary numbers (digits are 0 and 1)
boldUsed to emphasize a word
ScreenUsed for on-screen output and code related elements
Courier + BoldUsed to characterize user input and to separate it
ReferenceUsed for references and for table and figure
About this Manual
About this Manual
0 through F), for example used for addresses and
offsets
or commands in body text
from system output
descriptions
14
File > ExitNotation for selecting a submenu
<text>Notation for variables and keys
[text]Notation for software buttons to click on the screen
and parameter description
...Repeated item for example node 1, node 2, ..., node
12
.
.
.
..Ranges, for example: 0..4 means one of the integers
|Logical OR
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Omission of information from example/command
that is not necessary at the time being
0,1,2,3, and 4 (used in registers)
Page 15
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 is the third edition of the Installation and Use manual. It supersedes the November 2007
edition and incorporates the following changes.
Part NumberDateChanges
6806800D58HJune 2014Replaced "DDR" with "SDR" in Featureson page 63, L3 Cache on
page 66, and in the Figure 4-1.
Re-branded to Artesyn template.
6806800D58GDecember 2012Added section Declaration of Conformity on page 19.
6806800D58FAugust 2011Added Safety Noteson page 119 and Sicherheitshinweise on
page 123.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
15
Page 16
About this Manual
Part NumberDateChanges
6806800D58EMarch 2009Added csUserAltBoot command to Table "MOTLoad
Commands" on page 37, editorial changes
6806800D58DApril 2008Updated to Emerson publications style.
6806800D58CJanuary 2008Updated to remove two incorrect sources of reset. See Reset
Control Logicon page 75. Table 5-13 on page 94 was updated
to indicate both possible uses of pins C1, C2, C3, C4, Z25, Z27,
Z29, and Z31 (when J30 is configured for rear Ethernet and
when J30 is configued for full PMC mode).
6806800D58BNovember 2007Updated to better describe how to configure the VIO keying
pins for the PMC sites. See PMC I/O Voltage Configuration on
page 25. Also, Table 5-12 on page 93 was updated to identify
the Geographical Addressing pins on Row D of the P1
connector and minor updates were made to correct the hot
link to the literature catalog web site and update the reader
comments link.
About this Manual
16
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 17
Hardware Preparation and Installation
1.1Overview
This chapter contains the following information:
Board preparation and installation instructions
ESD precautionary notes
1.2Description
The MVME6100 is a single-slot, single-board computer based on the MPC7457 processor, the
MV64360 system controller, the Tsi148 VME Bridge ASIC, up to 1 GB of ECC-protected DDR
DRAM, up to 128MB of flash memory, and a dual Gigabit Ethernet interface.
Front panel connectors on the MVME6100 board include: two RJ-45 connectors for the Gigabit
Ethernet, one RJ-45 connector for the asynchronous serial port with integrated LEDs for
BRDFAIL and CPU run indication, and a combined reset and abort switch.
Chapter 1
The MVME6100 is shipped with one additional asynchronous serial port routed to an on-board
header.
The MVME6100 contains two IEEE1386.1 PCI, PCI-X capable mezzanine card slots. The PMC
slots are 64-bit capable and support both front and rear I/O. All I/O pins of PMC slot 1 and 46
I/O pins of PMC slot 2 are routed to the 5-row DIN, P2 connector. I/O pins 1 through 64 from
J14 of PMC slot 1 are routed to row C and row A of P2. I/O pins 1 through 46 from J24 of PMC
slot 2 are routed to row D and row Z of P2.
The MVME6100 has two planar PCI buses (PCI0 and PCI1). In order to support a more generic
PCI bus hierarchy nomenclature, the MV64360 PCI buses will be referred to in this document
as PCI bus 0 (root bridge instance 0, bus 0) and PCI bus 1 (root bridge instance 1, bus 0). PCI bus
1 connects to PMC slots 1 and 2 of the board. PCI bus 0 connects to the Tsi148 VME Bridge ASIC
and PMCspan bridge (PCI6520). This interface operates at PCI-X (133 MHz) speed. Both PCI
planar buses are controlled by the MV64360 system controller.
Voltage Input/Output (VIO) for PCI bus 1 is set by the location of the PMC keying pins; both pins
should be set to designate the same VIO, either +3.3V or +5V.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
17
Page 18
Hardware Preparation and Installation
The MVME6100 board interfaces to the VMEbus via the P1 and P2 connectors, which use 5-row
160-pin connectors as specified in the VME64 Extension Standard. It also draws +12V and +5V
power from the VMEbus backplane through these two connectors. The +3.3V, +2.5V, +1.8V,
and processor core supplies are regulated on-board from the +5V power.
For maximum VMEbus performance, the MVME6100 should be mounted in a VME64x
compatible backplane (5-row). 2eSST transfers are not supported when a 3-row backplane is
used.
The MVME6100 supports multiple modes of I/O operation. By default, the board is configured
for Ethernet port 2 to the front panel (non-specific transition module), and PMC slot 1 in IPMC
mode. The board can be configured to route Ethernet port 2 to P2 and support MVME712M or
MVME761 transition modules. The front/rear Ethernet and transition module options are
configured by jumper block J30.
Selection of PMC slot 1 in PMC or IPMC mode is done by the jumper blocks J10, J15-J18, and
J25-J28 (see Table 1-2 on page 22). IPMC mode is selected when an IPMC712 or IPMC761
module is used. If an IPMC is used, J30 should be configured for the appropriate transition
module (see J30 configuration options as illustrated in Front/Rear Ethernet and Transition Module
Options Header (J30) on page 26).
18
The IPMC712 and IPMC761 use AD11 as the IDSEL line for the Winbond PCI-ISA bridge device.
This device supplies the four serial and one parallel port of the IPMC7xx module. The Discovery
II PHB (MV64360) does not recognize address lines below AD16. For this reason, although an
IPMC7xx module may be used on an MVME6100, the serial and parallel ports are not available,
nor addressable. This issue will be resolved at a later date.
Other functions, such as Ethernet and SCSI interfaces, are function independent of the
Winbond IDSEL line. The wide SCSI interface can only be supported through IPMC connector
J3.
PMC mode is backwards compatible with the MVME5100 and MVME5500 and is accomplished
by configuring the on-board jumpers.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 19
Hardware Preparation and Installation
1.3Declaration of Conformity
Following is the Declaration of Conformity for MVME6100.
Figure 1-1Declaration of Conformity
E
C Declaration of Conformity
According to EN 17050-1:2004
Manufacturer’s Name:
Manufacturer’s Address:
Declares that the following product, in accordance with the requirements of 2004/108/EC, 2006/95/EC, 2011/65/
EU and their amending directives,
Product:
Model Name/Number:
has been designed and manufactured to the following specifications:
EN55022: (A1: 2000 + A2: 2003):1998 Class A
EN55024: (A1: 2001 + A2: 2003):1998
2011/65/EU RoHS Directive
As manufacturer we hereby declare that the product named above has been designed to comply with the relevant sections of the above referenced specifications. This product complies with the essential health and safety
requirements of the above specified directives. We have an internal production control system that ensures
compliance between the manufactured products and the technical documentation.
Artesyn Embedded Computing
Embedded Computing
Zhongshan General Carton Box Factory Co. Ltd. No 62, Qi
Guan Road West, Shiqi District, 528400 Zhongshan City
Guangdong, PRC
Tom Tuttle, Manager, Product Testing Services Date (MM/DD/YYYY)
MVME6100 Single Board Computer Installation and Use (6806800D58H)
12/06/2012______
19
Page 20
Hardware Preparation and Installation
1.4Getting Started
This section provides an overview of the steps necessary to install and power up the
MVME6100 and a brief section on unpacking and ESD precautions.
1.4.1Overview 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 20
Configure the hardware by setting jumpers on the board.Configuring the Hardware on page 21
Install the MVME6100 board in a chassis.Installing the Bladeon page 30
Connect any other equipment you will be usingConnecting to Peripheralson page 30
Verify the hardware is installed.Completing the Installationon page 31
1.4.2Unpacking Guidelines
Unpack the equipment from the shipping carton. Refer to the packing list and verify that all
items are present. Save the packing material for storing and reshipping of equipment.
20
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 21
Hardware Preparation and Installation
If the shipping carton is damaged upon receipt, request that the carrier’s agent be present
during the unpacking and inspection of the equipment.
Avoid touching areas of integrated circuitry; static discharge can damage circuits.
Artesyn 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 case 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 electronics stores) that is attached to an active electrical
ground. Note that a system chassis may not be grounded if it is unplugged.
Inserting or removing modules with power applied may result in damage to module
components.
Dangerous voltages, capable of causing death, are present in this equipment. Use extreme
caution when handling, testing, and adjusting.
1.5Configuring 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 MVME6100, you may
need to carry out certain hardware modifications before installing the module.
Most options on the MVME6100 are software configurable. Configuration changes are made
by setting bits in control registers after the board is installed in a system.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
21
Page 22
Hardware Preparation and Installation
Jumpers/switches are used to control those options that are not software configurable. These
jumper settings are described further on in this section. If you are resetting the board jumpers
from their default settings, it is important to verify that all settings are reset properly.
Figure 1-2 illustrates the placement of the jumpers, headers, connectors, switches, and various
other components on the MVME6100. There are several manually configurable headers on the
MVME6100 and their settings are shown in Table 1-2. Each header’s default setting is enclosed
in brackets. For pin assignments on the MVME6100, refer to Chapter 5, Pin Assignments.
Items in brackets are factory default settings.
Table 1-2 Jumper and Switch Settings
Jumper/S
witchFunctionSettings
J7SCON Header[No jumper installed]
1-2
2-3
J10,
J15–J18,
J25–J28
J30Front/Rear Ethernet and
S3SROM Configuration Switch,
S4Flash Boot Bank Select
PMC/IPMC Selection Headers[Jumper installed]
1-2
[2-3]
Refer to Front/Rear Ethernet and Transition Module
Transition Module Options
Header
sets board Geographical
Address
Configuration Switch, sets
Write Protect A, Write Protect
B, Boot Bank Select, and Safe
Start
Options Header (J30) on page 26 for details.
Refer to SROM Configuration Switch (S3) on page 27 for
details.
Refer to Flash Boot Bank Select Configuration Switch (S4)
on page 29 for details.
Auto-SCON
Always SCON
No SCON
PMC I/O
IPMC I/O for IPMC7xx
support (default)
22
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 23
Hardware Preparation and Installation
The MVME6100 is factory tested and shipped with the configuration described in the following
sections.
Figure 1-2Component Layout
PCI MEZZANINE CARDPCI MEZZANINE CARD
10/100/1000
10/100/1000 DEBUG
LAN 1LAN 2
J42J8
J9
J93
J19
J21
J23
J13
J11
U32
J29
PMC
IPMC
J22
J24
J12
J14
P1
J3
J30
P2
J7
S4
1 2 3 4
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
S1S3
U12
ABT/RST
S2
MVME6100 Single Board Computer Installation and Use (6806800D58H)
J4
4296 0604
23
Page 24
1.5.1SCON Header (J7)
A 3-pin planar header allows the choice for auto/enable/disable SCON VME configuration. A
jumper installed across pins 1 and 2 configures for SCON always enabled. A jumper installed
across pins 2 and 3 configures for SCON disabled. No jumper installed configures for auto
SCON.
Nine 3-pin planar headers are for PMC/IPMC mode I/O selection for PMC slot 1. These nine
headers can also be combined into one single header block where a block shunt can be used as
a jumper.
24
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 25
Hardware Preparation and Installation
A jumper installed across pins 1 and 2 on all nine headers selects PMC1 for PMC I/O mode. A
jumper across pins 2 and 3 on all nine headers selects IPMC I/O mode.
Figure 1-4PMC/IPMC Header Settings
IPMC P2 I/O for IPMC Mode
(factory configuration)
J10
J15
J16
J17
J18
J25
J26
J27
J28
1
2
3
1
2
3
1
2
3
1
2
3
1
2
3
1
2
3
PMC1 P2 I/O for PMC Mode
J10
1
2
3
J15
1
2
3
J16
1
2
3
J17
1
2
3
J18
1
2
3
1
2
3
1.5.3PMC I/O Voltage Configuration
The onboard PMC sites may be configured to support 3.3V or 5.0V I/O PMC modules. To
support 3.3V or 5.0V I/O PMC modules, both PMC sites on the MVME6100 have I/O keying
pins. One pin must be installed in each PMC site and both PMC sites must have their keying pins
configured he same way. If both keying pins are not in the same location or if the keying pins
are not installed, the PMC sites will not function. Note that setting the PMC I/O voltage to 5.0V
forces the PMC sites to operate in PCI mode instead of PCI-X mode.
J25
1
2
3
1
2
3
J26
1
2
3
1
2
3
J27
1
2
3
J28
1
2
3
The VIO keying pins are the silver colored pins located either in the middle of each set of four
PMC site connectors or just in front of those connectors. They serve two functions on the
MVME6100: both as jumpers to select the PCIbus VIO signaling voltage for the PMC sites, and
as keys to permit mounting of PMC cards that are compatible with that VIO signaling voltage
MVME6100 Single Board Computer Installation and Use (6806800D58H)
25
Page 26
Hardware Preparation and Installation
(or to exclude incompatible PMC cards). In the default position in the middle of the four PMC
site connectors, the signaling voltage for the PMC sites is set to 5.0V. When the keying pins are
moved to the alternate location in front of their set of four PMC connectors, the signaling
voltage for the PMC sites is set for 3.3V.
The keying pins for both PMC sites must be set to the same signaling voltage. Note also that
the signaling voltage has an effect on the PCI bus clock speed for the PMC sites. At 5.0V
signaling, the PCI bus clock speed is limited to 33 MHz, whereas 3.3V signaling voltage
supports conventional PCIbus clock speeds of 33 or 66 MHz, and PCIx clock speeds of 66 or
100MHz.
A PMC card that requires 5.0V VIO only signaling has a hole in the middle of its four PMC
connectors, such that it fits over the MVME6100's keying pin in that location. With the
MVME6100's keying pin in the 3.3V location, that PMC card would be physically unable to be
mounted. Similarly, a PMC card that requires 3.3V VIO-only signaling has its keying hole
located just to the front of its four PMC connectors, and will only fit to the MVME6100 when
the keying pin is located there. However, most modern PMC cards are universal with respect to
the VIO signaling voltage they support, and have keying holes in both locations; that is, they
will fit on the MVME6100's PMC site with the key in either location. For these PMC cards, it is
recommended setting the MVME6100's keying pins to the 3.3V VIO signaling position, to
allow the maximum PCIbus clock speed.
1.5.4Front/Rear Ethernet and Transition Module Options Header
(J30)
A 40-pin planar header allows for selecting P2 options. Jumpers installed across Row A pins 310 and Row B pins 3-10 enable front Ethernet access. Jumpers installed across Row B pins 3-10
and Row C pins 3-10 enable P2 (rear) Gigabit Ethernet. Only when front Ethernet is enabled can
the jumpers be installed across Row C and Row D on pins 1-10 to enable P2 (rear) PMC I/O. Note
that all jumpers must be installed across the same two rows (all between Row A and Row B
and/or Row C and Row D, or all between Row B and Row C).
26
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 27
Hardware Preparation and Installation
0
1
2
3
1234
e
1
2
3
1234
The following illustration shows jumper setting options for J30. The factory default is shown
where applicable:
Figure 1-5Front/Rear Ethernet Option Settings
J30 Options
1
1
1
1
1
1
1
1
Front Ethernet
(Default)
PMC I/O TO P2
(Default)
10
20
30
40
10
20
30
40
11
21
31
11
21
31
1
1
Rear Ethernet
MVME 712M
Transition Module
10
20
30
40
10
20
30
40
1
11
21
31
Non-Specific T ransition Modul
1
11
21
31
(Default)
MVME 761
Transition Module
4294
Refer to Front/Rear Ethernet and Transition Module Options Header (J30) on page 103 for
connector pin assignments.
1.5.5SROM Configuration Switch (S3)
A part of the 8-position SMT switch, S3 enables/disables the MV64360 SROM initialization and
all I2C EEPROM write protection.
The SROM Init switch is OFF to disable the MV64360 device initialization via the I2C SROM. The
switch is ON to enable this sequence.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
27
Page 28
Hardware Preparation and Installation
The SROM WP switch is OFF to enable write protection on all I2C. The switch is ON to disable
2
C EEPROM write protection.
the I
Table 1-3 SROM Configuration Switch (S3)
Position21
FUNCTIONSROM WPSROM_INIT
DEFAULT (OFF)WPNo SROM_INIT
S3 position 3-8 defines the VME Geographical Address if the MVME6100 is installed in a 3-row
backplane. The following is the pinout:
PositionFunction
3VMEGAP_L
4VMEGA4_L
5VMEGA3_L
6VMEGA2_L
7VMEGA1_L
8VMEGA0_L
Setting the individual position to ON forces the corresponding signal to zero. If the board is
installed in a 5-row backplane, the geographical address is defined by the backplane and
positions 3-8 of S3 should be set to OFF. The default setting is OFF.
28
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 29
Hardware Preparation and Installation
1.5.6Flash Boot Bank Select Configuration Switch (S4)
A 4-position SMT configuration switch is located on the board to control Flash Bank B Boot
block write-protect and Flash Bank A write-protect. Select the Flash Boot bank and the
programmed/safe start ENV settings.
It is recommended that Bank B Write Protect always be enabled.
The Bank B Boot WP switch is OFF to indicate that the Flash Bank B Boot block is writeprotected. The switch is ON to indicate no write-protection of Bank B Boot block.
The Bank A WP switch is OFF to indicate that the entire Flash Bank A is write-protected. The
switch is ON to indicate no write-protection of Bank A Boot block.
When the Boot Bank Sel Switch is ON, the board boots from Bank B, when OFF, the board boots
from Bank A. Default is ON (boot from Bank B).
When the Safe Start switch is set OFF, normal boot sequence should be followed by MOTLoad.
When ON, MOTLoad executes Safe Start, during which the user can select the Alternate Boot
Image.
Table 1-4 Configuration Switch (S4)
Position4321
FUNCTION
BANK B BOOT WP
FACTORY DEFAULTOFF
WP
MVME6100 Single Board Computer Installation and Use (6806800D58H)
BANK A WP
ON
No WP
BOOT BANK SEL
ON
Bank B
SAFE START
OFF
Norm ENV
29
Page 30
1.6Installing the Blade
Procedure
Use the following steps to install the MVME6100 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 MVME6100 into the guides of the chassis.
Hardware Preparation and Installation
Only use injector handles for board insertion to avoid damage/deformation to the front
panel and/or PCB. Deformation of the front panel can cause an electrical short or other
board malfunction.
4. Ensure that the levers of the two injector/ejectors are in the outward position.
5. Slide the MVME6100 into the chassis until resistance is felt.
6. Simultaneously move the injector/ejector levers in an inward direction.
7. Verify that the MVME6100 is properly seated and secure it to the chassis using the
two screws located adjacent to the injector/ejector levers.
8. Connect the appropriate cables to the MVME6100.
To remove the board from the chassis, press the red locking tabs (IEEE handles only) and
reverse the procedure.
1.7Connecting to Peripherals
When the MVME6100 is installed in a chassis, you are ready to connect peripherals and apply
power to the board.
30
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 31
Hardware Preparation and Installation
Figure 1-2 on page 23 shows the locations of the various connectors while Table 1-5 lists them
for you. Refer to Chapter 5, Pin Assignments for the pin assignments of the connectors listed
below.
Verify 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 AC or DC power source, and
turn the equipment power on.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
31
Page 32
Hardware Preparation and Installation
32
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 33
Startup and Operation
2.1Introduction
This chapter gives you information about the:
Power-up procedure
Switches and indicators
2.2Applying 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 MVME6100:
Verify 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)
Chapter 2
On powering up, the MVME6100 brings up the MOTLoad prompt, MVME6100>
2.3Switches and Indicators
The MVME6100 board provides a single pushbutton 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. The board hard reset will reset the MPC7457, MV64360, Tsi148
VME Bridge ASIC, PCI6520, PMC1/2 slots, both Ethernet PHYs, serial ports, PMCspan slot, both
flash banks, and the device bus control PLD. If the MVME6100 is enabled for VME system
controller, the VME bus will be reset and local reset input is sent to the Tsi148 VME controller.
The MVME6100 has two front-panel indicators:
BDFAIL, software controlled and asserted by firmware (or other software) to indicate a
configuration problem (or other failure)
CPU, connected to a CPU bus control signal to indicate bus transfer activity
MVME6100 Single Board Computer Installation and Use (6806800D58H)
33
Page 34
Startup and Operation
The following table describes these indicators:
Table 2-1 Front-Panel LED Status Indicators
FunctionLabelColorDescription
CPU Bus ActivityCPUGreenCPU bus is busy
Board FailBDFAILYellowBoard has a failure
34
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 35
MOTLoad Firmware
3.1Overview
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. This chapter includes a list of standard MOTLoad commands, the default VME and
firmware settings that are changeable by the user, remote start, and the alternate boot
procedure.
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.
Chapter 3
3.2Implementation and Memory Requirements
The implementation of MOTLoad and its memory requirements are product specific. The
MVME6100 single-board computer (SBC) is offered with a wide range of memory (for example,
DRAM, external cache, flash). Typically, the smallest amount of on-board DRAM that an
Artesyn SBC has is 32 MB. Each supported product line has its own unique MOTLoad binary
image(s). Currently the largest MOTLoad compressed image is less than 1 MB in size.
3.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.
3.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 manipulation, help routines, data/status monitors, etc.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
35
Page 36
Operationally, MOTLoad utility applications differ from MOTLoad test applications in several
ways:
Only one utility application operates at any given time (that is, multiple utility applications
cannot be executing concurrently)
Utility applications may interact with the user. Most test applications do not.
3.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 (errordata/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).
MOTLoad Firmware
36
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.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 37
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 Package User’s Manual.
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 Package User’s Manual for more information.
3.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. Typing help at the MOTLoad
command prompt will display all commands supported by MOTLoad for a given product.
MOTLoad Firmware
For a detailed description of these commands refer to the MOTLoad Firmware Package User’s
Manual.
Table 3-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
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Block Compare Byte/Halfword/Word
Block Fill Byte/Halfword/Word
37
Page 38
Table 3-1 MOTLoad Commands (continued)
CommandDescription
blkVeBlock Verify
blkWrBlock Write
MOTLoad Firmware
bmb
bmh
bmw
brAssign/Delete/Display User-Program Break-Points
bsb
bsh
bsw
bvb
bvh
bvw
cdDirISO9660 File System Directory Listing
cdGetISO9660 File System File Load
clearClear the Specified Status/History Table(s)
cmTurns on Concurrent Mode
csb
csh
csw
csUserAltBootChecksums user boot images specified in the alternete boot image
Block Move Byte/Halfword/Word
Block Search Byte/Halfword/Word
Block Verify Byte/Halfword/Word
Calculates a Checksum Specified by Command-line Options
header at the beginning of files to be programmed into flash memory.
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
40
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 41
Table 3-1 MOTLoad Commands (continued)
CommandDescription
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
testEnetPtPEthernet Point-to-Point
testNvramRdNVRAM Read
testNvramRdWrNVRAM Read/Write (Destructive)
testRamRAM Test (Directory)
testRamAddrRAM Addressing
testRamAltRAM Alternating
MOTLoad Firmware
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
MVME6100 Single Board Computer Installation and Use (6806800D58H)
41
Page 42
MOTLoad Firmware
Table 3-1 MOTLoad Commands (continued)
CommandDescription
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
waitProbeWait for I/O Probe to Complete
3.4Using the Command Line Interface
Interaction with MOTLoad is performed via a command line interface through a serial port on
the SBC, 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 key 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, MVME5500, MVME6100).
Example:
42
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 43
MOTLoad Firmware
MVME6100>
If an invalid MOTLoad command is entered at the MOTLoad command line prompt, MOTLoad
displays a message that the command was not found.
Example:
MVME6100> mytest
"mytest" not found
MVME6100>
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 will be 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:
MVME6100> version
Copyright: Motorola Inc.1999-2002, All Rights Reserved
MOTLoad RTOS Version 2.0
PAL Version 0.1 (Motorola MVME6100)
Example:
MVME6100> ver
Copyright: Motorola Inc. 1999-2002, All Rights Reserved
MOTLoad RTOS Version 2.0
PAL Version 0.1 (Motorola MVME6100)
If the partial command string cannot be resolved to a single unique command, MOTLoad will
inform the user that the command was ambiguous.
Example:
MVME6100> te
"te" ambiguous
MVME6100>
MVME6100 Single Board Computer Installation and Use (6806800D58H)
43
Page 44
3.4.1Command Line Rules
There are a few things to remember when entering a MOTLoad command:
Multiple commands are permitted on a single command line, provided they are separated
by a single semicolon (;)
Spaces separate the various fields on the command line (command/arguments/options)
The argument/option identifier character is always preceded by a hyphen (-) character
Options are identified by a single character
Option arguments immediately follow (no spaces) the option
All commands, command options, and device tree strings are case sensitive
Example:
MVME6100> flashProgram –d/dev/flash0 –n00100000
MOTLoad Firmware
For more information on MOTLoad operation and function, refer to the MOTLoad Firmware
Package User’s Manual.
3.4.2Command Line Help
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
MVME6100> help
For help with a specific test or utility the user can enter the following at the MOTLoad prompt:
help <command_name>
The help command also supports a limited form of pattern matching. Refer to the help
command page.
Example
MVME6100> help testRam
44
MVME6100 Single Board Computer Installation and Use (6806800D58H)
-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
MVME6100>
3.5Firmware Settings
The following sections provide additional information pertaining to the VME firmware settings
of the MVME6100. A few VME settings are controlled by hardware jumpers while the majority
of the VME settings are managed by the firmware command utility vmeCfg.
MOTLoad Firmware
3.5.1Default VME Settings
As shipped from the factory, the MVME6100 has the following VME configuration
programmed via Global Environment Variables (GEVs) for the Tsi148 VME controller. The
firmware allows certain VME settings to be changed in order for the user to customize the
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 Tsi148 User Manual, listed in Appendix C, Related Documentation.
MVME6100> vmeCfg -s -m
Displaying the selected Default VME Setting
- interpreted as follows:
VME PCI Master Enable [Y/N] = Y
MVME6100>
The PCI Master is enabled.
MVME6100> vmeCfg –s –r234
Displaying the selected Default VME Setting
- interpreted as follows:
VMEbus Master Control Register = 00000003
MVME6100>
MVME6100 Single Board Computer Installation and Use (6806800D58H)
45
Page 46
MOTLoad Firmware
The VMEbus Master Control Register is set to the default (RESET) condition.
MVME6100> vmeCfg –s –r238
Displaying the selected Default VME Setting
- interpreted as follows:
VMEbus Control Register = 00000008
MVME6100>
The VMEbus Control Register is set to a Global Timeout of 2048 seconds.
MVME6100> vmeCfg –s –r414
Displaying the selected Default VME Setting
- interpreted as follows:
CRG Attribute Register = 00000000
CRG Base Address Upper Register = 00000000
CRG Base Address Lower Register = 00000000
MVME6100>
The CRG Attribute Register is set to the default (RESET) condition.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 47
MOTLoad Firmware
Inbound window 0 (ITAT0) is not enabled; Virtual FIFO at 256 bytes, 2eSST timing at
SST320, respond to 2eSST, 2eVME, MBLT, and BLT cycles, A32 address space, respond to
Supervisor, User, Program, and Data cycles. Image maps from 0x00000000 to 0x1FFF0000
on the VMbus, translates 1x1 to the PCI-X bus (thus 1x1 to local memory). To enable this
window, set bit 31 of ITAT0 to 1.
For Inbound Translations, the Upper Translation Offset Register needs to be set to 0xFFFFFFFF to
ensure proper translations to the PCI-X Local Bus.
Outbound window 1 (OTAT1) is enabled, 2eSST timing at SST320, transfer mode of 2eSST,
A32/D32 Supervisory access. The window accepts transfers on the PCI-X Local Bus from
0x91000000-0xAFFF0000 and translates them onto the VMEbus using an offset of
0x70000000, thus an access to 0x91000000 on the PCI-X Local Bus becomes an access to
0x01000000 on the VMEbus.
Outbound window 2 (OTAT2) is enabled, 2eSST timing at SST320, transfer mode of SCT,
A24/D32 Supervisory access. The window accepts transfers on the PCI-X Local Bus from
0xB0000000-0xB0FF0000 and translates them onto the VMEbus using an offset of
0x40000000, thus an access to 0xB0000000 on the PCI-X Local Bus becomes an access to
0xF0000000 on the VMEbus.
Outbound window 3 (OTAT3) is enabled, 2eSST timing at SST320, transfer mode of SCT,
A16/D32 Supervisory access. The window accepts transfers on the PCI-X Local Bus from
0xB3FF0000-0xB3FF0000 and translates them onto the VMEbus using an offset of
0x4C000000, thus an access to 0xB3FF0000 on the PCI-X Local Bus becomes an access to
0xFFFF0000 on the VMEbus.
Outbound window 7 (OTAT7) is enabled, 2eSST timing at SST320, transfer mode of SCT,
CR/CSR Supervisory access. The window accepts transfers on the PCI-X Local Bus from
0xB1000000-0xB1FF0000 and translates them onto the VMEbus using an offset of
0x4F000000, thus an access to 0xB1000000 on the PCI-X Local Bus becomes an access to
0x00000000 on the VMEbus.
3.5.2Control Register/Control Status Register Settings
The CR/CSR base address is initialized to the appropriate setting based on the Geographical
address; that is, the VME slot number. 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.
3.5.3Displaying VME Settings
To display the changeable VME setting, type the following at the firmware prompt:
vmeCfg –s –m
Displays Master Enable state
vmeCfg –s –i(0 - 7)
Displays selected Inbound Window state
vmeCfg –s –o(0 - 7)
Displays selected Outbound Window state
vmeCfg –s –r184
Displays PCI Miscellaneous Register state
vmeCfg –s –r188
Displays Special PCI Target Image Register state
vmeCfg –s –r400
Displays Master Control Register state
vmeCfg –s –r404
Displays Miscellaneous Control Register state
MVME6100 Single Board Computer Installation and Use (6806800D58H)
49
Page 50
vmeCfg –s –r40C
Displays User AM Codes Register state
vmeCfg –s –rF70
Displays VMEbus Register Access Image Control Register state
3.5.4Editing VME Settings
To edit the changeable VME setting, type the following at the firmware prompt:
vmeCfg –e –m
Edits Master Enable state
vmeCfg –e –i(0 - 7)
Edits selected Inbound Window state
vmeCfg –e –o(0 - 7)
Edits selected Outbound Window state
MOTLoad Firmware
vmeCfg –e –r184
Edits PCI Miscellaneous Register state
vmeCfg –e –r188
Edits Special PCI Target Image Register state
vmeCfg –e –r400
Edits Master Control Register state
vmeCfg –e –r404
Edits Miscellaneous Control Register state
vmeCfg –e –r40C
Edits User AM Codes Register state
vmeCfg –e –rF70
Edits VMEbus Register Access Image Control Register state
50
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 51
3.5.5Deleting VME Settings
To delete the changeable VME setting (restore default value), type the following at the
firmware prompt:
vmeCfg –d –m
Deletes Master Enable state
vmeCfg –d –i(0 - 7)
Deletes selected Inbound Window state
vmeCfg –d –o(0 - 7)
Deletes selected Outbound Window state
vmeCfg –d –r184
Deletes PCI Miscellaneous Register state
vmeCfg –d –r188
Deletes Special PCI Target Image Register state
MOTLoad Firmware
vmeCfg –d –r400
Deletes Master Control Register state
vmeCfg –d –r404
Deletes Miscellaneous Control Register state
vmeCfg –d –r40C
Deletes User AM Codes Register state
vmeCfg –d –rF70
Deletes VMEbus Register Access Image Control Register state
3.5.6Restoring 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
MVME6100 Single Board Computer Installation and Use (6806800D58H)
51
Page 52
3.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 execute a downloaded
program. These transactions occur across the VMEbus in the case of the MVME6100. MOTLoad
uses one of four mailboxes in the Tsi148 VME controller 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:
Slot PositionCS/CSR Starting Address
10x0008.0000
20x0010.0000
MOTLoad Firmware
30x0018.0000
40x0020.0000
50x0028.0000
60x0030.0000
70x0038.0000
80x0040.0000
90x0048.0000
A0x0050.0000
B0x0058.0000
C0x0060.0000
For further details on CR/CSR space, please refer to the VME64 Specification, listed in Appendix
C, Related Documentation.
The MVME6100 uses a Discovery II for its VME bridge. The offsets of the mailboxes in the
Discovery II are defined in the Discovery II User Manual, listed in Appendix C, Related
Documentation, but are noted here for reference:
52
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 53
MOTLoad Firmware
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 MVME6100 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
appendix in the MOTLoad Firmware Package User's Manual for remote start GEV definitions.
The MVME6100’s IBCA needs to be mapped appropriately through the master’s VMEbus
bridge. For example, to use remote start using mailbox 0 on an MVME6100 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).
3.7Alternate Boot Images and Safe Start
Some later versions of MOTLoad support Alternate Boot Images and a Safe Start recovery
procedure. If Safe Start is available on the MVME6100, Alternate Boot Images are supported.
With Alternate Boot Image support, the bootloader code in the boot block examines the upper
8MB of the flash bank for Alternate Boot images. If an image is found, control is passed to the
image.
3.8Firmware Startup Sequence Following Reset
The firmware startup sequence following reset of MOTLoad is to:
Initialize cache, MMU, FPU, and other CPU internal items
Initialize the memory controller
Search the active flash bank, possibly interactively, for a valid POST image. If found, the
POST images executes. Once completed, the POST image returns and startup continues.
Search the active flash bank, possibly interactively, for a valid USER boot image. If found,
the USER boot image executes. A return to the boot block code is not anticipated.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
53
Page 54
If a valid USER boot image is not found, search the active flash bank, possibly interactively,
for a valid MCG boot image; anticipated to be upgrade of MCG firmware. If found, the
image is executed. A return to the boot block code is not anticipated.
Execute the recovery image of the firmware in the boot block if no valid USER or MCG
image is found
During startup, interactive mode may be entered by either setting the Safe Start
jumper/switch or by sending an <ESC> to the console serial port within five seconds of the
board reset. During interactive mode, the user has the option to display locations at which valid
boot images were discovered, specify which discovered image is to be executed, or specify that
the recovery image in the boot block of the active Flash bank is to be executed.
3.9Firmware Scan for Boot Image
The scan is performed by examining each 1MB boundary for a defined set of flags that identify
the image as being Power On Self Test (POST), USER, or MCG. MOTLoad is an MCG image. POST
is a user-developed Power On Self Test that would perform a set of diagnostics and then return
to the bootloader image. User would be a boot image, such as the VxWorks bootrom, which
would perform board initialization. A bootable VxWorks kernel would also be a USER image.
Boot images are not restricted to being MB or less in size; however, they must begin on a 1MB
boundary within the 8MB of the scanned flash bank. The Flash Bank Structure is shown below:
MOTLoad Firmware
54
AddressUsage
0xFFF00000 to 0xFFFFFFFFBoot block. Recovery code
0xFFE00000 to 0XFFFFFFFFReserved for MCG use. (MOTLoad update image)
0xFFD00000 to 0xFFDFFFFF
(FBD00000 or F7D00000)
0xFFC00000 to 0xFFCFFFFF
(FBC00000 or F7C00000)
....Alternate boot images
0xFF899999 to 0xFF8FFFFF
(Fb800000 or F3800000)
First possible alternate image (Bank B / Bank A actual)
Second possible alternate image (Bank B / Bank A actual)
Last possible alternate image (Bank B / Bank A actual)
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 55
MOTLoad Firmware
The scan is performed downwards from boot block image and searches first for POST, then
USER, and finally MCG images. In the case of multiple images of the same type, control is
passed to the first image encountered in the scan.
Safe Start, whether invoked by hitting ESC on the console within the first five seconds following
power-on reset or by setting the Safe Start jumper, interrupts the scan process. The user may
then display the available boot images and select the desired image. The feature is provided to
enable recovery in cases when the programmed Alternate Boot Image is no longer desired. The
following output is an example of an interactive Safe Start:
ABCDEInteractive Boot Mode Entered
boot> ?
Interactive boot commands:
'd':show directory of alternate boot images
'c':continue with normal startup
'q':quit without executing any alternate boot image
'r [address]':execute specified (or default) alternate image
'p [address]':execute specified (or default) POST image
'?':this help screen
'h':this help screen
boot> d
Addr FFE00000 Size 00100000 Flags 00000003 Name: MOTLoad
Addr FFD00000 Size 00100000 Flags 00000003 Name: MOTLoad
boot> c
NOPQRSTUVabcdefghijk#lmn3opqrsstuvxyzaWXZ
Copyright Motorola Inc. 1999-2004, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 0.b EA02
...
MVME6100>
MVME6100 Single Board Computer Installation and Use (6806800D58H)
55
Page 56
3.10Boot Images
Valid boot images whether POST, USER, or MCG, are located on 1MB boundaries within flash.
The image may exceed 1MB in size. An image is determined valid through the presence of two
"valid image keys" and other sanity checks. A valid boot image begins with a structure as
defined in the following table:
NameTypeSizeNotes
UserDefinedunsigned integer8User defined
ImageKey 1unsigned integer10x414c5420
ImageKey 2unsigned integer10x424f4f54
ImageChecksumunsigned integer1Image checksum
ImageSizeunsigned integer1Must be a multiple of 4
ImageNameunsigned character32User defined
MOTLoad Firmware
ImageRamAddressunsigned integer1RAM address
ImageOffsetunsigned integer1Offset from header start to entry
ImageFlagsunsigned integer1Refer to Image Flags on page 57
ImageVersionunsigned integer1User defined
Reservedunsigned integer8Reserved for expansion
3.10.1Checksum Algorithm
The checksum algorithm is a simple unsigned word add of each word (4 byte) location in the
image. The image must be a multiple of 4 bytes in length (word-aligned). The content of the
checksum location in the header is not part of the checksum calculation. The calculation
assumes the location to be zero. The algorithm is implemented using the following code:
Unsigned int checksum(
Unsigned int *startPtr,/* starting address */
Unsigned int endPtr/* ending address */
) {
unsigned int checksum=0;
while (startPtr < endPtr) {
checksum += *startPtr;
56
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 57
startPtr++;
}
return(checksum);
}
3.10.2Image Flags
The image flags of the header define various bit options that control how the image will be
executed.
Table 3-2 MOTLoad Image Flags
NameValueInterpretation
COPY_TO_RAM0x00000001Copy image to RAM at
MOTLoad Firmware
ImageRamAddress
before execution
IMAGE_MCG0x00000002MCG-specific image
IMAGE_POST0x00000004POST image
DONT_AUTO_RUN0x00000008Image not to be executed
COPY_TO_RAM
If set, this flag indicates that the image is to be copied to RAM at the address specified in
the header before control is passed. If not set, the image will be executed in flash. In both
instances, control will be passed at the image offset specified in the header from the base
of the image.
IMAGE_MCG
If set, this flag defines the image as being an Alternate MOTLoad, as opposed to USER,
image. This bit should not be set by developers of alternate boot images.
IMAGE_POST
If set, this flag defines the image as being a power-on self-test image. This bit flag is used
to indicate that the image is a diagnostic and should be run prior to running either USER or
MCG boot images. POST images are expected, but not required, to return to the boot
block code upon completion.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
57
Page 58
DONT_AUTO_RUN
If set, this flag indicates that the image is not to be selected for automatic execution. A
user, through the interactive command facility, may specify the image to be executed.
MOTLoad currently uses an Image Flag value of 0x3, which identifies itself as an Alternate
MOTLoad image that executes from RAM. MOTLoad currently does not support execution
from flash.
3.10.3User Images
These images are user-developer boot code; for example, a VxWorks bootrom image. Such
images may expect the system software state to be as follows upon entry:
The MMU is disabled.
MOTLoad Firmware
L1 instruction cache has been initialized and is enabled.
L1 data cache has been initialized (invalidated) and is disabled.
L2 cache is disabled.
L3 cache is disabled.
RAM has been initialized and is mapped starting at CPU address 0.
If RAM ECC or parity is supported, RAM has been scrubbed of ECC or parity errors.
The active Flash bank (boot) is mapped from the upper end of the address space.
If specified by COPY_TO_RAM, the image has been copied to RAM at the address specified
by ImageRamAddress.
CPU register R1 (the stack pointer) has been initialized to a value near the end of RAM.
CPU register R3 is added to the following structure:
typedef struct altBootData {
unsigned int ramSize;/* board's RAM size in MB */
void flashPtr;/* ptr to this image in flash */
char boardType[16];/* name string, eg MVME6100 */
void globalData;/* 16K, zeroed, user defined */
unsigned int reserved[12];
} altBootData_t;
58
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 59
3.10.4Alternate Boot Data Structure
The globalData field of the alternate boot data structure points to an area of RAM which was
initialized to zeroes by the boot loader. This area of RAM is not cleared by the boot loader after
execution of a POST image, or other alternate boot image, is executed. It is intended to provide
a user a mechanism to pass POST image results to subsequent boot images.
The boot loader performs no other initialization of the board than that specified prior to the
transfer of control to either a POST, USER, or MCG image. Alternate boot images need to
initialize the board to whatever state the image may further require for its execution.
POST images are expected, but not required, to return to the boot loader. Upon return, the
boot loader proceeds with the scan for an executable alternate boot image. POST images that
return control to the boot loader must ensure that upon return, the state of the board is
consistent with the state that the board was in at POST entry. USER images should not return
control to the boot loader.
MOTLoad Firmware
3.10.5Alternate Boot Images and Safe Start
Some later versions of MOTLoad support alternate boot images and a safe start recovery
procedure. If safe start is available on the MVME6100, alternate boot images are supported.
With alternate boot image support, the boot loader code in the boot block examines the upper
8 MB of the flash bank for alternate boot images. If an image is found, control is passed to the
image.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
59
Page 60
3.10.6Boot Image Firmware Scan
The scan is performed by examining each 1 MB boundary for a defined set of flags that identify
the image as being POST, USER, or Alternate MOTLoad. POST is a user-developed Power On Self
Test that would perform a set of diagnostics and then return to the boot loader image. USER
would be a boot image, such as the VxWorks bootrom, which would perform board
initialization. A bootable VxWorks kernel would also be a USER image. Boot images are not
restricted to being 1 MB or less in size; however, they must begin on a 1 MB boundary within
the 8 MB of the scanned flash bank. The flash bank structure is shown below:
AddressUsage
0xFFF00000 to 0xFFFFFFFFBoot block. Recovery code.
0xFFE00000 to 0XFFFFFFFFBackup MOTLoad image
0xFFD00000 to 0xFFDFFFFFFirst possible alternate image
0xFFC00000 to 0xFFCFFFFFSecond possible alternate image
MOTLoad Firmware
....Alternate boot images
0xFF899999 to 0xFF8FFFFFBottom of flash (flash size varies per product)
The scan is performed downwards beginning at the location of the first possible alternate
image and searches first for POST, then USER, and finally Alternate MOTLoad images. In the
case of multiple images of the same type, control is passed to the first image encountered in
the scan.
Safe Start, whether invoked by hitting ESC on the console within the first five seconds following
power-on reset or by setting the Safe Start jumper, interrupts the scan process. The user may
then display the available boot images and select the desired image. The feature is provided to
enable recovery in cases when the programmed Alternate Boot Image is no longer desired. The
following output is an example of an interactive Safe Start:
ABCDEInteractive Boot Mode Entered
boot> ?
Interactive boot commands:
'd':show directory of alternate boot images
'c':continue with normal startup
'q':quit without executing any alternate boot image
'r [address]':execute specified (or default) alternate image
'p [address]':execute specified (or default) POST image
'?':this help screen
60
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 61
'h':this help screen
boot> d
Addr FFE00000 Size 00100000 Flags 00000003 Name: MOTLoad
Addr FFD00000 Size 00100000 Flags 00000003 Name: MOTLoad
boot> c
NOPQRSTUVabcdefghijk#lmn3opqrsstuvxyzaWXZ
Copyright Motorola Inc. 1999-2004, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 0.b EA02
...
MVME6100>
3.11Startup Sequence
The firmware startup sequence following reset of MOTLoad is to:
Initialize cache, MMU, FPU, and other CPU internal items
MOTLoad Firmware
Initialize the memory controller
Search the active flash bank, possibly interactively, for a valid Power On Self Test (POST)
image. If found, the POST images executes. Once completed, the POST image returns and
startup continues.
Search the active flash bank, possibly interactively, for a valid USER boot image. If found,
the USER boot image executes. A return to the boot block code is not anticipated.
If a valid USER boot image is not found, search the active flash bank, possibly interactively,
for a valid Alternate MOTLoad boot image; anticipated to be an upgrade of alternate
MOTLoad firmware. If found, the image is executed. A return to the boot block code is not
anticipated.
Execute the recovery image of the firmware in the boot block if no valid USER or alternate
MOTLoad image is found
During startup, interactive mode may be entered by either setting the Safe Start
jumper/switch or by sending an <ESC> to the console serial port within five seconds of the
board reset. During interactive mode, the user has the option to display locations at which valid
boot images were discovered, specify which discovered image is to be executed, or specify that
the recovery image in the boot block of the active flash bank is to be executed.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
61
Page 62
MOTLoad Firmware
62
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 63
Functional Description
4.1Overview
This chapter describes the MVME6100 on a block diagram level.
4.2Features
The following table lists the features of the MVME6100.
Table 4-1 MVME6100 Features Summary
FeatureDescription
Processor– Single 1.267 GHz MPC7457 processor
– Bus clock frequency at 133 MHz
– 36-bit address, 64-bit data buses
– Integrated L1 and L2 cache
Chapter 4
L3 Cache– Bus clock frequency at 211 MHz (when supported by processor)
– Up to 2MB using SDR SRAM
Flash– Two banks (A & B) of soldered Intel StrataFlash devices
– 8 to 64MB supported on each bank
– Boot bank is switch selectable between banks
– Bank A has combination of software and hardware write-protect
scheme
– Bank B top 1MB block can be write-protected through
software/hardware write-protect control
System Memory– Two banks on board for up to 1Gb using 256Mb or 512Mb devices
– 32KB provided by MK48T37 with SnapHat battery backup
MVME6100 Single Board Computer Installation and Use (6806800D58H)
63
Page 64
Functional Description
Table 4-1 MVME6100 Features Summary (continued)
FeatureDescription
On-board Peripheral Support– Dual 10/100/1000 Ethernet ports routed to front panel RJ-45
connectors, one optionally routed to P2 backplane
– Two asynchronous serial ports provided by an ST16C554D; one
serial port is routed to a front panel RJ-45 connector and the second
serial port is routed to an on-board header (J29, as factory default
build configuration).
PCI/PMC– Two 32/64-bit PMC slots with front-panel I/O plus P2 rear I/O as
specified by IEEE P1386
– 33/66 MHz PCI or 66/100 MHz PCI-X
VME Interface– Tsi148 VME 2eSST ASIC provides:
Eight programmable VMEbus map decoders
A16, A24, A32, and A64 address
8-bit, 16-bit, and 32-bit single cycle data transfers
8-bit, 16-bit, 32-bit, and 64-bit block transfers
Supports SCT, BLT, MBLT, 2eVME, and 2eSST protocols
8 entry command and 4KB data write post buffer
4KB read ahead buffer
64
PMCspan Support– One PMCspan slot
– Supports 33/66 MHz, 32/64-bit PCI bus
– Access through PCI6520 bridge to PMCspan
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 65
4.3Block Diagram
PC
04
Figure 4-1 shows a block diagram of the overall board architecture.
Figure 4-1MVME6100 Block Diagram
Functional Description
211 MHz SDR
133 MHz
Processor Bus
Gigabit
Ethernet
RJ-45
Gigabit
Ethernet
Jumper
Selectable
RJ-45
4.4Processor
The MVME6100 supports the MPC7457 with adjustable core voltage supply. The maximum
external processor bus speed is 133 MHz. The processor core frequency runs at 1.267 GHz or
the highest speed MPC7457 can support, which is determined by the processor core voltage,
the external speed, and the internal VCO frequency. MPX bus protocols are supported on the
board. The MPC7457 has integrated L1 and L2 caches (as the factory build configuration) and
supports an L3 cache interface with on-chip tags to support up to 2MB of off-chip cache. +2.5V
signal levels are used on the processor bus.
L3 Cache
2MB
MPC7457
1.267 GHz
Discovery II
Host
Bridge
64-bit/133 MHz PCI-X
64-bit/33/66/100 MHz PCI-X
PMC
Slot 1
Rows A&C
64-pins
DDR RAM
512MB-1GB
DDR RAM
512MB-1GB
133 MHz
Memory Bus
Device Bus
FP I/O
Rows D&Z
46-pins
P2P1
IPMC
Slot 2
FP I/O
RTC
NVRAM
TSI148
VME
Soldered
Flash
Bank A
64MB
Soldered
Flash
Bank B
64MB
Serial
P-P Bridge
PMC Span
Connector
RJ-45
header
32/64-bit,
33/66 MHz
4250 06
MVME6100 Single Board Computer Installation and Use (6806800D58H)
65
Page 66
4.5L3 Cache
The MVME6100 external L3 cache is implemented using two 8Mb SDR SRAM devices. The L3
cache bus is 72-bits wide (64 bits of data and 8 bits of parity) and operates at 211 MHz. The L3
cache interface is implemented with an on-chip, 8-way, set-associative tag memory. The
external SRAMs are accessed through a dedicated L3 cache port that supports one bank of
SRAM. The L3 cache normally operates in copyback mode and supports system cache
coherency through snooping. Parity generation and checking may be disabled by
programming the L3CR register. Refer to the PowerPC Apollo Microprocessor Implementation Definition Book IV listed inAppendix C, Related Documentation.
4.6System Controller
The MV64360 is an integrated system controller for high performance embedded control
applications. The following features of the MV64360 are supported by the MVME6100:
Functional Description
The MV64360 has a five-bus architecture comprised of:
A 72-bit interface to the CPU bus (includes parity)
A 72-bit interface to DDR SDRAM (double data rate-synchronous DRAM) with ECC
A 32-bit interface to devices
Two 64-bit PCI/PCI-X interfaces
In addition to the above, the MV64360 integrates:
Three Gigabit Ethernet MACs (only two are used on the MVME6100)
2Mb SRAM
Interrupt controller
Four general-purpose 32-bit timers/counters
2
I
C interface
Four channel independent DMA controller
66
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 67
All of the above interfaces are connected through a cross bar fabric. The cross bar enables
concurrent transactions between units. For example, the cross bar can simultaneously control:
A Gigabit Ethernet MAC fetching a descriptor from the integrated SRAM
The CPU reading from the DRAM
The DMA moving data from the device bus to the PCI bus
4.6.1CPU Bus Interface
The CPU interface (master and slave) operates at 133 MHz and +2.5V signal levels using MPX
bus modes. The CPU bus has a 36-bit address and 64-bit data buses. The MV64360 supports up
to eight pipelined transactions per processor. There are 21 address windows supported in the
CPU interface:
Four for SDRAM chip selects
Five for device chip selects
Functional Description
Five for the PCI_0 interface (four memory + one I/O)
Five for the PCI_1 interface (four memory + one I/O)
One for the MV64360 integrated SRAM
One for the MV64360 internal registers space
Each window is defined by base and size registers and can decode up to 4GB space (except for
the integrated SRAM, which is fixed to 256KB). Refer to the MV64360 Data Sheet, listed in
Appendix C, Related Documentation, for additional information and programming details.
4.6.2Memory Controller Interface
The MVME6100 supports two banks of DDR SDRAM using 256Mb/ 512Mb DDR SDRAM
devices on-board. 1Gb DDR non-stacked SDRAM devices may be used when available. 133
MHz operation should be used for all memory options. The SDRAM supports ECC and the
MV64360 supports single-bit and double-bit error detection and single-bit error correction of
all SDRAM reads and writes.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
67
Page 68
The SDRAM controller supports a wide range of SDRAM timing parameters. These parameters
can be configured through the SDRAM Mode register and the SDRAM Timing Parameters
register. Refer to the MV64360 Data Sheet, listed in Appendix C, Related Documentation, for
additional information and programming details.
The DRAM controller contains four transaction queues—two write buffers and two read
buffers. The DRAM controller does not necessarily issue DRAM transactions in the same order
that it receives the transactions. The MV64360 is targeted to support full PowerPC cache
coherency between CPU L1/L2 caches and DRAM.
4.6.3Device Controller Interface
The device controller supports up to five banks of devices, three of which are used for Flash
Banks A and B, NVRAM/RTC. Each bank supports up to 512MB of address space, resulting in
total device space of 1.5GB. Serial ports are the fourth and fifth devices on the MVME6100.
Each bank has its own parameters register as shown in the following table.
Functional Description
Table 4-2 Device Bus Parameters
DeviceBankDescription
Flash Bank ADevice Bus Bank 0Bank width 32-bit, parity disabled
Flash Bank BDevice Bus Boot BankBank width 32-bit, parity disabled
Real-Time Clock
Serial Ports
Board Specific Registers
4.6.4PCI/PCI-X Interfaces
The MVME6100 provides two 32/64-bit PCI/PCI-X buses, operating at a maximum frequency
of 100 MHz when configured to PCI-X mode, and run at 33 or 66 MHz when running
conventional PCI mode. PCI bus 1 is connected to the PMC slots 1 and 2.
The maximum PCI-X frequency of 100 MHz supported by PCI bus 1 may be reduced depending
on the number and/or type of PMC/PrPMC installed. If PCI bus 1 is set to +5V VIO, it runs at 33
MHz. VIO is set by the keying pins (they are both a keying pin and jumper). Both pins must be
set for the same VIO on the PCI-X bus.
Device Bus Bank 1Bank width 8-bit, parity disabled
68
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 69
PCI bus 0 is connected to the Tsi148 device and PMCspan bridge. PCI bus 0 is configured for 133
MHz PCI-X mode.
The MV64360 PCI interfaces are fully PCI rev. 2.2 and PCI-X rev 1.0 compliant and support both
address and data parity checking. The MV64360 contains all of the required PCI configuration
registers. All internal registers, including the PCI configuration registers, are accessible from
the CPU bus or the PCI buses.
4.6.5Gigabit Ethernet MACs
The MVME6100 supports two 10/100/1000Mb/s full duplex Ethernet ports connected to the
front panel via the MV64360 system controller. Ethernet access is provided by front panel RJ45 connectors with integrated magnetics and LEDs. Port 1 is a dedicated Gigabit Ethernet port
while a configuration header is provided for port 2 front or rear P2 access Refer to Front/Rear
Ethernet and Transition Module Options Header (J30) for more information.
Each Ethernet interface is assigned an Ethernet Station Address. The address is unique for each
device. The Ethernet Station Addresses are displayed on labels attached to the PMC front-panel
keep-out area.
Functional Description
The MV64360 is not integrated with a PHY for the Ethernet interfaces. External PHY is the
Broadcom BCM5461S 10/100/1000BaseT Gigabit transceiver with SERDES interface. Refer to
Appendix C, Related Documentation for more information.
4.6.6SRAM
The MV64360 integrates 2Mb of general-purpose SRAM. It is accessible from the CPU or any of
the other interfaces. It can be used as fast CPU access memory (6 cycles latency) and for off
loading DRAM traffic. A typical usage of the SRAM can be a descriptor RAM for the Gigabit
Ethernet ports.
4.6.7General-Purpose Timers/Counters
There are four 32-bit wide timers/counters on the MV64360. Each timer/counter can be
selected to operate as a timer or as a counter. The timing reference is based on the MV64360
Tclk input, which is set at 133 MHz. Each timer/counter is capable of generating an interrupt.
Refer to the MV64360 Data Sheet, listed in Appendix C, Related Documentation, for additional
information and programming details.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
69
Page 70
4.6.8Watchdog Timer
The MV64360 internal watchdog timer is a 32-bit count-down counter that can be used to
generate a non-maskable interrupt or reset the system in the event of unpredictable software
behavior. After the watchdog timer is enabled, it becomes a free running counter that must be
serviced periodically to keep it from expiring. Refer to the MV64360 Data Sheet, listed in
Appendix C, Related Documentation, for additional information and programming details.
4.6.9I2O Message Unit
I2O compliant messaging for the MVME6100 board is provided by an I2O messaging unit
integrated into the MV64360 system controller. The MV64360 messaging unit includes
hardware hooks for message transfers between PCI devices and the CPU. This includes all of
the registers required for implementing the I2O messaging, as defined in the Intelligent I/O
(I2O) Standard specification. For additional details regarding the I2O messaging unit, refer to
the MV64360 Data Sheet, listed in Appendix C, Related Documentation.
Functional Description
4.6.10Four Channel Independent DMA Controller
The MV64360 incorporates four independent direct memory access (IDMA) engines. Each
IDMA engine has the capability to transfer data between any two interfaces. Refer to the
MV64360 Data Sheet, listed in Appendix C, Related Documentation, for additional information
and programming details.
4.6.11I2C Serial Interface and Devices
A two-wire serial interface for the MVME6100 board is provided by a master/slave capable I2C
serial controller integrated into the MV64360 device. The I2C serial controller provides two
basic functions. The first function is to optionally provide MV64360 register initialization
following a reset. The MV64360 can be configured (by switch setting) 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 MVME6100 board, along with the SPD EEPROMs for on-board
memory to further initialize the memory controller and other interfaces.
70
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 71
The MVME6100 board contains the following I2C serial devices:
8KB EEPROM for user-defined MV64360 initialization
8KB EEPROM for VPD
8KB EEPROM for user data
Two 256 byte EEPROMs for SPD
DS1621 temperature sensor
One 256 byte EEPROM for PMCspan PCIx-PCIx bridge use
The 8KB EEPROM devices are implemented using Atmel AT24C64A devices or similar parts.
These devices use two byte addressing to address the 8KB of the device.
4.6.12Interrupt Controller
The MVME6100 uses the interrupt controller integrated into the MV64360 device to manage
the MV64360 internal interrupts as well as the external interrupt requests. The interrupts are
routed to the MV64360 MPP pins from on-board resources as shown in the MVME6100 Programmer’s Guide. The external interrupt sources include the following:
Functional Description
On-board PCI device interrupts
PMC slot interrupts
VME interrupts
RTC interrupt
Watchdog timer interrupts
Abort switch interrupt
External UART interrupts
Ethernet PHY interrupts
IPMC761 interrupts
PMCspan interrupts
For additional details regarding the external interrupt assignments, refer to the MVME6100
Programmer’s Guide.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
71
Page 72
4.6.13PCI Bus Arbitration
PCI arbitration is performed by the MV64360 system controller. The MV64360 integrates two
PCI arbiters, one for each PCI interface (PCI bus 0/1). Each arbiter can handle up to six external
agents plus one internal agent (PCI bus 0/1 master). The internal PCI arbiter REQ#/GNT# signals
are multiplexed on the MV64360 MPP pins. The internal PCI arbiter is disabled by default (the
MPP pins function as general-purpose inputs). Software configures the MPP pins to function as
request/grant pairs for the internal PCI arbiter. The arbitration pairs for the MVME6100 are
assigned to the MPP pins as shown in the MVME6100 Programmer’s Guide.
4.7VMEbus Interface
The VMEbus interface is provided by the Tsi148 ASIC. Refer to the Tsi148 User’s Manual available
from Tundra Semiconductor for additional information as listed in Appendix C, Related
Documentation. 2eSST operations are not supported on 3-row backplanes. You must use
VME64x (VITA 1.5) compatible backplanes, such as 5-row backplanes, to achieve maximum
VMEbus performance.
Functional Description
4.8PMCspan Interface
The MVME6100 provides a PCI expansion connector to add more PMC interfaces than the two
on the MVME6100 board. The PMCspan interface is provided through the PCI6520 PCIx/PCIx
bridge.
4.9Flash Memory
The MVME6100 contains two banks of flash memory accessed via the device controller bus
contained within the MV64360 device. Both banks are soldered on board and have different
write-protection schemes.
72
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 73
4.10System Memory
MVME6100 system memory consists of double-data-rate SDRAMs. The DDR SDRAMs support
two data transfers per clock cycle. The memory device is a standard monolithic (32M x 8 or
64M x 8) DDR, 8-bit wide, 66-pin, TSSOPII package. Both banks are provided on board the
MVME6100 and operate at 133 MHz clock frequency with both banks populated.
4.11Asynchronous Serial Ports
The MVME6100 board contains one EXAR ST16C554D quad UART (QUART) device connected
to the MV64360 device controller bus to provide asynchronous debug ports. The QUART
supports up to four asynchronous serial ports, two of which are used on the MVME6100.
COM1 is an RS232 port and the TTL- level signals are routed through appropriate EIA-232
drivers and receivers to an RJ-45 connector on the front panel. Unused control inputs on COM1
and COM2 are wired active. The reference clock frequency for the QUART is 1.8432 MHz. All
UART ports are capable of signaling at up to 115 Kbaud.
Functional Description
4.12PCI Mezzanine Card Slots
The MVME6100 board supports two PMC slots. Two sets of four EIA-E700 AAAB connectors are
located on the MVME6100 board to interface to the 32-bit/64-bit IEEE P1386.1 PMC to add any
desirable function. The PMC slots are PCI/PCI-X 33/66/100 capable.
PMC/IPMC slot 1 supports:
Mezzanine Type:PMC/IPMC = PCI Mezzanine Card
Mezzanine Size:S1B = Single width and standard depth
(75mm x 150mm) with front panel
PMC Connectors: J11, J12, J13, and J14 (32/64-bit PCI with front and rear I/O)
Signaling Voltage: VIO = +3.3V (+5V tolerant) or +5V, selected by keying pin
MVME6100 Single Board Computer Installation and Use (6806800D58H)
73
Page 74
Functional Description
PMC slot 2 supports:
Mezzanine Type:PMC = PCI Mezzanine Card
Mezzanine Size:S1B = Single width and standard depth
(75mm x 150mm) with front panel
PMC Connectors: J21, J22, J23, and J24 (32/64-bit PCI with front and rear I/O)
Signalling Voltage: VIO = +3.3V (+5V tolerant) or +5V, selected by keying pin
You cannot use 3.3V and 5.0V PMCs together; the voltage keying pin on slots 1 and 2 must
be identical. When in 5.0V mode, the bus runs at 33 MHz.
In addition, the PMC connectors are located such that a double-width PMC may be installed in
place of the two single-width PMCs.
Signaling Voltage:VIO = +3.3V (+5.0V tolerant) or +5.0V, selected by keying pin
On either PMC site, the user I/O – Jn4 signals will only support the low-current, high-speed
signals and not for any current bearing power supply usage. The maximum current rating of
each pin/signal is 250 mA.
74
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 75
Functional Description
4.13Real-Time Clock/NVRAM/Watchdog Timer
The real-time clock/NVRAM/watchdog timer is implemented using an integrated SGSThompson M48T37V Timekeeper SRAM and Snaphat battery. The minimum M48T37V
watchdog timer time-out resolution is 62.5 msec (1/16s) and maximum time-out period is 124
seconds. The interface for the Timekeeper and SRAM is connected to the MV64360 device
controller bus on the MVME6100 board. Refer to the MV64360 Data Sheet, listed in Appendix C,
Related Documentation, for additional information and programming details.
4.14IDSEL Routing
PCI device configuration registers are accessed by using the IDSEL signal of each PCI agent to
an A/D signal as defined in version 2.2 of the PCI specification. IDSEL assignments to on-board
resources are specified in the MVME6100 Programmer’s Guide.
4.15Reset Control Logic
The sources of reset on the MVME6100 are the following:
Powerup
Reset Switch
NVRAM Watchdog Timer
MV64360 Watchdog Timer
VMEbus controller – Tsi148 ASIC
System Control register bit
4.16Debug Support
The MVME6100 provides JTAG/COP headers for debug capability for Processor as well as PCI0
bus use. These connectors are not populated as factory build configuration.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
75
Page 76
4.17Processor JTAG/COP Headers
The MVME6100 provides JTAG/COP connectors for JTAG/COP emulator support (RISCWatch
COP J42), as well as supporting board boundary scan capabilities (Boundary Scan header J8).
Functional Description
76
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 77
Pin Assignments
5.1Overview
This chapter provides pin assignments for various headers and connectors on the MMVE6100
single-board computer.
Front/Rear Ethernet and Transition Module Options Header (J30)
Processor JTAG/COP Header (J42)
5.2Connectors
The following tables provide a brief description of the connector, the pin assignments, and
signal descriptions for standard and nonstandard connectors on the MVME6100.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
77
Page 78
5.2.1PMC Expansion Connector (J4)
One 114-pin Mictor connector with a center row of power and ground pins is used to provide
PCI expansion capability. The pin assignments for this connector are as follows:
All PMC expansion signals are dedicated PMC expansion PCI bus signals.
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 81
5.2.2Gigabit Ethernet Connectors (J9, J93)
Access to the dual Gigabit Ethernet is provided by two transpower RJ-45 connectors with
integrated magnetics and LEDs located on the front panel of the MVME6100. The pin
assignments for these connectors are as follows:
A standard RJ-45 connector located on the front panel of the MVME6100 provides the interface
to the asynchronous serial debug port. The pin assignments for this connector are as follows:
Table 5-11 COM1 Connector (J19) Pin Assignments
PinSignal
1DCD
2RTS
3GNDC
4TX
5RX
6GNDC
7CTS
8DTR
92
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 93
5.2.5VMEbus P1 Connector
The VME P1 connector is an 160-pin DIN. The P1 connector provides power and VME signals for
24-bit address and 16-bit data. The pin assignments for the P1 connector is as follows:
Table 5-12 VMEbus P1 Connector Pin Assignments
ROW ZROW AROW BROW CROW D
1Reserved D00BBSY*D08Reserved1
2GNDD01BCLR*D09Reserved2
3Reserved D02ACFAIL* D10Reserved3
4GNDD03BG0IN*D11Reserved4
5ReservedD04BG0OUT*D12Reserved5
6GNDD05BG1IN*D13Reserved6
7Reserved D06BG1OUT*D14Reserved7
Pin Assignments
8GNDD07BG2IN*D15Reserved8
9ReservedGNDBG2OUT*GNDReserved
(Geographical
Address, parity)
10GNDSYSCLKBG3IN*SYSFAIL*Reserved (GA0)10
11ReservedGNDBG3OUT*BERR*Reserved (GA1)11
12GNDDS1*BR0*SYSRESET*Reserved12
13ReservedDS0*BR1*LWORD*Reserved (GA2)13
14GNDWRITE*BR2*AM5Reserved14
15ReservedGNDBR3*A23Reserved (GA3)15
16GNDDTACK*AM0A22Reserved16
17ReservedGNDAM1A21Reserved (GA4)17
18GNDAS*AM2A20Reserved18
19ReservedGNDAM3A19Reserved19
20GNDIACK*GNDA18Reserved20
21ReservedIACKIN*SERAA17Reserved21
22GNDIACKOUT*SERBA16Reserved22
9
MVME6100 Single Board Computer Installation and Use (6806800D58H)
The VME P2 connector is an 160-pin DIN. Row B of the P2 connector provides power to the
MVME6100 and to the upper eight VMEbus address lines and additional 16 VMEbus data lines.
The pin assignments for the P2 connector are as follows:
The default configuration for P2, C27-C30 are connected to PMC0_IO (53,55,57,59).
5.2.7VMEbus P2 Connector (IPMC Mode)
The VME P2 connector is an 160-pin DIN. Row B of the P2 connector provides power to the
MVME6100 and to the upper eight VMEbus address lines and additional 16 VMEbus data lines.
The pin assignments for the P2 connector are as follows:
Table 5-14 VME P2 Connector Pinouts with IPMC712
PinRow ZRow ARow BRow CRow D
PMC1_45
(J24-45)
GND31
VPC32
30
1PMC2_2DB0#+5VRD-PMC2_1 (J24-1)
2GNDDB1#GNDRD+PMC2_3 (J24-3)
3PMC2_5DB2#N/CTD-PMC2_4 (J24-4)
4GNDDB3#VA24TD+PMC2_6 (J24-6)
MVME6100 Single Board Computer Installation and Use (6806800D58H)
97
Page 98
Pin Assignments
Table 5-14 VME P2 Connector Pinouts with IPMC712 (continued)
MVME6100 Single Board Computer Installation and Use (6806800D58H)
Page 99
Pin Assignments
Table 5-14 VME P2 Connector Pinouts with IPMC712 (continued)
PinRow ZRow ARow BRow CRow D
32GNDRTXC4+5VDCD2VPC
Table 5-15 VME P2 Connector Pinouts with IPMC761
PinRow ZRow ARow BRow CRow D
1DB8#DB0#+5VRD- (10/100)PMC2_1 (J24-1)
2GNDDB1#GNDRD+ (10/100)PMC2_3 (J24-3)
3DB9#DB2#RETRY#TD- (10/100)PMC2_4 (J24-4)
4GNDDB3#VA24TD+ (10/100)PMC2_6 (J24-6)
5DB10#DB4#VA25Not UsedPMC2_7 (J24-7)
6GNDDB5#VA26Not UsedPMC2_9 (J24-9)
7DB11#DB6#VA27+12VFPMC2_10 (J24-10)
8GNDDB7#VA28PRSTB#PMC2_12 (J24-12)
9DB12#DBP#VA29PRD0PMC2_13 (J24-13)
10GNDATN#VA30PRD1PMC2_15 (J24-15)
11DB13#BSY#VA31PRD2PMC2_16 (J24-16)
12GNDACK#GNDPRD3PMC2_18 (J24-18)
13DB14#RST#+5VPRD4PMC2_19 (J24-19)
14GNDMSG#VD16PRD5PMC2_21 (J24-21)
15DB15#SEL#VD17PRD6PMC2_22 (J24-22)
16GNDD/C#VD18PRD7PMC2_24 (J24-24)
17DBP1#REQ#VD19PRACK#PMC2_25 (J24-25)
18GNDO/I#VD20PRBSYPMC2_27 (J24-27)
19PMC2_29
(J24-29)
20GNDSLIN#VD22PRSELPMC2_30 (J24-30)
21PMC2_32
(J24-32)
22GNDRXD3GNDPRFLT#PMC2_33 (J24-33)
AFD#VD21PRPEPMC2_28 (J24-28)
TXD3VD23INIT#PMC2_31 (J24-31)
MVME6100 Single Board Computer Installation and Use (6806800D58H)
99
Page 100
Pin Assignments
Table 5-15 VME P2 Connector Pinouts with IPMC761 (continued)
PinRow ZRow ARow BRow CRow D
23PMC2_35
(J24-35)
24GNDTRXC3VD25RXD1_232PMC2_36 (J24-36)
RTXC3VD24TXD1_232PMC2_34 (J24-34)
25PMC2_38
(J24-38)
26GNDRXD4VD27CTS1_232PMC2_39 (J24-39)
27PMC2_41
(J24-41)
28GNDTRXC4VD29RXD2_232PMC2_42 (J24-42)
29PMC2_44
(J24-44)
30GND-12VFVD31CTS2_232PMC2_45 (J24-45)
31PMC2_46
(J24-46)
32GNDMCLK+5VMDIVPC
Rows A and C and Zs (Z1, 3, 5, 7, 9, 11, 13, 15, and 17) functionality is provided by the IPMC761
in slot 1 and the MVME6100 Ethernet port 2.
5.3Headers
The next subsections provide a description of each header and its settings and/or pin
assignments. Refer to Configuring the Hardware on page 21 for details on setting the headers.
TXD4VD26RTS1_232PMC2_37 (J24-37)
RTXC4VD28TXD2_232PMC2_40 (J24-40)
VD30RTS2_232PMC2_43 (J24-43)
MSYNC#GNDMDOGND
100
MVME6100 Single Board Computer Installation and Use (6806800D58H)
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.