Emerson, Business-Critical Continuity, Emerson Network Power and the Emerson Network Power logo are trademarks and service
marks of Emerson Electric Co.
owners.
®
Intel
is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
™
and all other Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other
Java
countries.
Microsoft
Microsoft Corporation.
PICMG
Industrial Computer Manufacturers Group.
UNIX
®
, Windows® and Windows Me® are registered trademarks of Microsoft Corporation; and Windows XP™ is a trademark of
®
, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logos are registered trademarks of the PCI
®
is a registered trademark of The Open Group in the United States and other countries.
2008 Emerson Electric Co. All other product or service names are the property of their respective
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 content hereof without obligation of Emerson to notify any person of such revision or
changes.
Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to
a Emerson website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise
altered without the permission of Emerson,
It is possible that this publication may contain reference to or information about Emerson products (machines and programs),
programming, or services that are not available in your country. Such references or information must not be construed to mean that
Emerson intends to announce such Emerson products, programming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply
unless otherwise agreed to in writing by Emerson.
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in
Technical Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and
Documentation clause at DFARS 252.227-7014 (Jun. 1995).
MVME3100 Single Board Computer Installation and Use (6806800M28C)
11
List of Figures
12
MVME3100 Single Board Computer Installation and Use (6806800M28C)
About this Manual
Overview of Contents
This manual is divided into the following chapters and appendices:
Hardware Preparation and Installation, provides MVME3100 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 MVMEM3100.
MOTLoad Firmware, describes the basic features of the MOTLoad firmware product.
Functional Description, describes the MVME3100 and the MVME721 RTM on a block diagram
level.
Pin Assignments, provides pin assignments for various headers and connectors on the
MMVE3100 single-board computer.
Memory Maps, provides information on memory maps and system and configuration registers.
Programming Details, provides additional programming information including IDSEL mapping,
interrupt assignments for the MPC8540 interrupt controller, Flash memory, two-wire serial
interface addressing, and other device and system considerations.
Specifications, provides power requirements and environmental specifications.
Related Documentation, provides a listing of related Emerson 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 MVME3100 Single-Board Computer Installation and Use manual provides the information you
will need to install and configure your MVME3100 single-board computer and MVME721 rear
transition module (RTM). It provides specific preparation and installation information, and data
applicable to the board.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
13
About this Manual
About this Manual
As of the printing date of this manual, the MVME3100 supports the models listed below.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
About this Manual
AbbreviationDescription
TSOPThin Small Outline Package
UARTUniversal Asynchronous Receiver/Transmitter
UNIXUNIX operating system
USBUniversal Serial Bus
VIOInput/Output Voltage
VITAVMEbus International Trade Association
VMEVersaModule Eurocard
VMEbusVersaModule Eurocard bus
VPDVital Product Data
WPWrite Protect
Conventions
The following table describes the conventions used throughout this manual.
NotationDescription
0x00000000Typical notation for hexadecimal numbers (digits are
0 through F), for example used for addresses and
offsets
0b0000Same for binary numbers (digits are 0 and 1)
boldUsed to emphasize a word
ScreenUsed for on-screen output and code related elements
or commands in body text
Courier + BoldUsed to characterize user input and to separate it
from system output
ReferenceUsed for references and for table and figure
descriptions
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
MVME3100 Single Board Computer Installation and Use (6806800M28C)
17
About this Manual
About this Manual
NotationDescription
...Repeated item for example node 1, node 2, ..., node
.
.
.
..Ranges, for example: 0..4 means one of the integers
|Logical OR
12
Omission of information from example/command
that is not necessary at the time being
0,1,2,3, and 4 (used in registers)
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
18
Indicates a property damage message
No danger encountered. Pay attention to important
information
MVME3100 Single Board Computer Installation and Use (6806800M28C)
About this Manual
Summary of Changes
This manual has been revised and replaces all prior editions.
Part NumberPublication DateDescription
6806800M28CDecember 2012Added Declaration of Conformity on page 22.
6806800M28BAugust 2011Updated Safety Noteson page 148 and
Sicherheitshinweise on page 152.
6806800M28AApril 2011EA version
MVME3100 Single Board Computer Installation and Use (6806800M28C)
19
About this Manual
About this Manual
20
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Hardware Preparation and Installation
1.1Overview
The MVME3100 is a single-slot, single-board computer based on the MPC8540 PowerQUICC
III™ integrated processor. The MVME3100 provides serial ATA (sATA), USB 2.0, 2eSST VMEbus
interfaces, dual 64-bit/100 MHz PMC sites, up to 128MB of Flash, dual 10/100/1000 Ethernet,
one 10/100 Ethernet, and five serial ports. This board supports front and rear I/O and a single
SODIMM module for DDR memory. Access to rear I/O is available with the MVME721 rear
transition module (RTM).
Front-panel connectors on the MVME3100 board include: one RJ-45 connector for the Gigabit
Ethernet, one RJ-45 connector for the asynchronous serial port, one USB port with one type A
connector, one sATA port with one external sATA connector, and a combined reset and abort
switch.
Rear-panel connectors on the MVME721 board include: one RJ-45 connector for each of the
10/100 and 10/100/1000 BaseT Ethernets and four RJ-45 connectors for the asynchronous
serial ports. The RTM also provides two planar connectors for one PIM with rear I/O.
Chapter 1
1.2Getting Started
This section provides an overview of the steps necessary to install and power up the
MVME3100 and a brief section on unpacking and ESD precautions.
1.2.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 Guidelines on page 22
Identify various components on the board.MVME3100 Layouton page 23
Install the MVME3100 board in a chassis.on page 30
MVME3100 Single Board Computer Installation and Use (6806800M28C)
21
Hardware Preparation and Installation
Table 1-1 Startup Overview (continued)
What you need to do...Refer to...
Connect any other equipment you will be usingConnecting to Peripheralson page 31
Verify the hardware is installed.Completing the Installationon page 33
1.2.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.
If the shipping carton is damaged upon receipt, request that the carrier’s agent be present
during the unpacking and inspection of the equipment.
Damage of Circuits
zElectrostatic discharge and incorrect installation and removal of the product can
damage circuits or shorten their life.
zBefore touching the product make sure that your are working in an ESD-safe
environment or wear an ESD wrist strap or ESD shoes. Hold the product by its edges and
do not touch any components or circuits.
1.3Declaration of Conformity
For Declaration of Conformity, refer MVME3100 Series Declaration of Conformity.
1.4Configuring 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 MVME3100, you may
need to carry out certain hardware modifications before installing the module.
22
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Hardware Preparation and Installation
Most options on the MVME3100 are software configurable. Configuration changes are made
by setting bits in control registers after the board is installed in a system.
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.
1.4.1MVME3100 Layout
Figure 1-1 on page 25 illustrates the placement of the jumpers, headers, connectors, switches,
and various other components on the MVME3100.
There are two switch blocks which have user-selectable settings. Refer to Table 1-2, Tab le 1-3 ,
and Table 1-4 for switch settings. There is one switch on the MVME721. Refer to Table 1-5 and
Table 1-6 for switch settings.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
23
Hardware Preparation and Installation
The MVME3100 is factory tested and shipped with the configuration described in the following
sections.
24
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Hardware Preparation and Installation
Figure 1-1Board Layout
J25J24
J30J28
J2
J13 J14
J11 J12
J23
J21 J22
P1
P2
U21
J4
U1012
U1003
U1010
U5000
U1014
U1020
U1019
U1049
U1050
U1024
U1012
U1000
U1007
U1052
U1025
U1026
U1027
U1046
U1047
U1051
1
1
S4
S3
MVME3100 Single Board Computer Installation and Use (6806800M28C)
25
Hardware Preparation and Installation
1.4.2Configuration Switch (S4)
An 8-position SMT configuration switch controls the VME SCON setting, Flash bank writeprotect, and the safe start ENV settings. It also selects the Flash boot image. The default setting
on all switch positions is OFF.
Table 1-2 Configuration Switch (S4) Settings
Setting
SwitchPos.
NotesOFF (Factory Default)ON
SAFE_START1Normal ENV settings
should be used.
BOOT BLOCK
SELECT
FLASH BANK WP3Entire Flash is not write-
Reserved4
VME SCON
AUTO/MANUAL
MODE
MANUAL VME
SCON SELECT
Reserved7
2Flash memory map is
normal and boot block A
is selected.
protected.
5Auto-SCON mode.Manual SCON mode.Manual SCON mode
6Non-SCON mode.Always SCON mode.This switch is only
Safe ENV settings
should be used.
Boot block B is
selected and mapped
to the highest
address.
Flash is writeprotected.
This switch status is
readable from System
St atu s r egi st er 1 , b it 5.
Software may check
this bit and act
accordingly.
works in conjunction
with the VME SCON
SELECT switch.
effective when the
VME SCON
AUTO/MANUAL
MODE switch is ON.
26
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Isolates the board
HRESET from TRST
and allows the board
to reset without
resetting the
MPC8540 JTAG/COP
interface.
1.4.3Geographical Address Switch (S3)
The TSi148 VMEbus Status register provides the VMEbus geographical address of the
MVME3100. This switch reflects the inverted states of the geographical address signals.
Applications not using the 5-row backplane can use the geographical address switch to assign
a geographical address.
Figure 1-2Geographical Address Switch Settings
NotesOFF (Factory Default)ON
This switch should
remain in the OFF
position unless a
MPC8540 emulator is
attached.
Table 1-3 Geographical Address Switch Assignments
PositionSW1SW2
FunctionNot
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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 I/O keying pins must be installed in the
holes. 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. The default factory configuration is for 3.3V
PMC I/O voltage.
1.4.5RTM SEEPROM Address Switch (S1)
A 4-position SMT configuration switch is located on the RTM to set the device address of the
RTM serial EEPROM device. The switch settings are defined in the following table.
Table 1-5 RTM EEPROM Address Switch Assignments
PositionSW1SW2SW3SW4
FunctionA0A1A2Not Used
OFF111
Table 1-6 EEPROM Address Settings
Device AddressA(2:0)SW1SW2SW3
$A0000ONONON
$A2001OFFONON
$A4010ONOFFON
$A6011OFFOFFON
$A8100ONONOFF
$AA (Factory)101OFFONOFF
MVME3100 Single Board Computer Installation and Use (6806800M28C)
29
Hardware Preparation and Installation
Table 1-6 EEPROM Address Settings (continued)
Device AddressA(2:0)SW1SW2SW3
$AC110ONOFFOFF
$AE111OFFOFFOFF
The RTM EEPROM address switches must be set for address $AA in order for this device to be
accessible by MotLoad.
1.5Installing Hardware
Damage of the Product and Additional Devices and Modules
zIncorrect installation or removal of additional devices or modules may damage the
product or the additional devices or modules.
zBefore installing or removing additional devices or modules, read the respective
documentation.
Damage of Circuits
zElectrostatic discharge and incorrect installation and removal of the product can
damage circuits or shorten their life.
zBefore touching the product make sure that your are working in an ESD-safe
environment or wear an ESD wrist strap or ESD shoes. Hold the product by its edges and
do not touch any components or circuits.
Product Malfunction
zSwitches marked as “Reserved” might carry production-related functions and can
cause the product to malfunction if their setting is changed.
zDo not change settings of switches marked as “reserved”.
30
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Hardware Preparation and Installation
Procedure
Use the following steps to install the MVME3100 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 MVME3100 into the guides of the chassis.
4. Ensure that the levers of the two injector/ejectors are in the outward position.
5. Slide the MVME3100 into the chassis until resistance is felt.
6. Simultaneously move the injector/ejector levers in an inward direction.
7. Verify that the MVME3100 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 MVME3100.
To remove the board from the chassis, press the red locking tabs (IEEE handles only) and
reverse the procedure.
1.6Connecting to Peripherals
When the MVME3100 is installed in a chassis, you are ready to connect peripherals and apply
power to the board.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
31
Hardware Preparation and Installation
Figure 1-1 on page 25 shows the locations of the various connectors while Table 1-7 and Tab l e
1-8 list them for you. Refer to Chapter 5, Pin Assignments for the pin assignments of the
connectors listed below.
Damage of the Product and Additional Devices and Modules
zIncorrect installation or removal of additional devices or modules damages the product
or the additional devices or modules.
zBefore installing or removing additional devices or modules, read the respective
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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
33
Hardware Preparation and Installation
34
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Startup and Operation
2.1Introduction
This chapter gives you information about the:
zPower-up procedure
zRuntime 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 MVME3100:
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)
Chapter 2
zOn powering up, the MVME3100 brings up the MOTLoad prompt, MVME3100>
2.3Switches and Indicators
The MVME3100 board provides a single push button switch that provides both abort and reset
(ABT/RST) functions. When the switch is pressed for less than five seconds, an abort interrupt
is generated to the processor. If the switch is held for more than five seconds, a board hard reset
is generated. The board hard reset will reset the MPC8540, local PCI/PCI-X buses, Ethernet
PHYs, serial ports, Flash devices, and PLD(s). If the MVME3100 is configured as the VME system
controller, the VME bus and local TSi148 reset input are also reset.
The MVME3100 has four front-panel indicators. The following table describes these indicators:
Table 2-1 Front-Panel LED Status Indicators
FunctionLabelColorDescription
Board FailFAILYellowBoard has a failure. After Power On or reset, this
LED is ON until extinguished by firmware or
software.
User DefinedUSER 1GreenThis indicator is illuminated by software
assertion of its corresponding register bit.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
35
Startup and Operation
Table 2-1 Front-Panel LED Status Indicators (continued)
FunctionLabelColorDescription
GENET 1 Link /
Speed
GENET 1 ActivityACTBlinking GreenActivity proportional to bandwidth utilization.
SPEEDOffNo link
Yellow10/100Base-T operation
Green1000Base-T operation
OffNo activity
36
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Startup and Operation
Figure 2-1Front Panel LEDs and Connectors
ABORT/RESET
G ENET 1
COM 1
SATA 1
USER 1
SPEED
PMC 1
PMC 2
FAIL
ACT
MVME3100 Single Board Computer Installation and Use (6806800M28C)
37
Startup and Operation
The MVME721 rear transition module also has four status indicators. The following table
describes these indicators:
Table 2-2 MVME721 LED Status Indicators
FunctionLabelColorDescription
GENET 2 Link/SpeedSPEEDOffNo link
Yellow10/100Base-T operation
Green1000Base-T operation
GENET 2 ActivityACTBlinking GreenActivity proportional to bandwidth utilization.
OffNo activity
ENET 1 Link/SpeedSPEEDOffNo link
Yellow10/100Base-T operation
ENET 1 ActivityACTBlinking GreenActivity proportional to bandwidth utilization.
OffNo activity
Table 2-3 Additional Onboard Status Indicators
FunctionLabelColorDescription
User
Defined LED
2
User
Defined LED
3
Power
Supply Fail
sATA 0
Activity
DS7
(silkscreen)
DS8
(silkscreen)
DS1
(silkscreen)
DS4
(silkscreen)
GreenThis indicator is illuminated by software assertion of its
corresponding register bit.
GreenThis indicator is illuminated by software assertion of its
corresponding register bit.
RedThis indicator is illuminated to indicate a power supply
fail condition.
GreensATA 0 activity indicator
sATA 1
Activity
38
DS5
(silkscreen)
GreensATA 1 activity indicator
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Startup and Operation
Table 2-3 Additional Onboard Status Indicators (continued)
FunctionLabelColorDescription
MPC8540
Ready
GENET 1
Link Quality
GENET 2
Link Quality
DS3
(silkscreen)
DS2
(silkscreen)
DS3[Same as DS2}
GreenIndicates that the MPC8540 has completed the reset
Off
Slow Blink
Green
Fast Blink Green
Green
operation and is not in a power-down state. The
MPC8540 Ready is multiplexed with the MPC8540
TRIG_OUT so the LED can be programmed to indicate
one of three trigger events based on the value in the
MPC8540 TOSR register.
Extremely poor Signal to Noise ratio - cannot receive data
Poor SNR - receive errors detected
Fair SNR - close to data error threshold
Good SNR on link
MVME3100 Single Board Computer Installation and Use (6806800M28C)
39
Startup and Operation
40
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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 B, Related
Documentation, for more details.
Chapter 3
3.2Implementation and Memory Requirements
The implementation of MOTLoad and its memory requirements are product specific. The
MVME3100 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 Emerson 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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
41
MOTLoad Firmware
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.
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).
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.
42
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
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.
Table 3-1 MOTLoad Commands
CommandDescription
asOne-Line Instruction Assembler
bcb
bch
bcw
bd Temp Sho wDisplay Cu rrent Boa rd Temper atu re
bfb
bfh
bfw
blkCpBlock Copy
blkFmtBlock Format
blkRdBlock Read
blkShowBlock Show Device Configuration Data
blkVeBlock Verify
blkWrBlock Write
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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
46
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
Table 3-1 MOTLoad Commands (continued)
CommandDescription
testDiskTest Disk
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
MVME3100 Single Board Computer Installation and Use (6806800M28C)
47
MOTLoad Firmware
Table 3-1 MOTLoad Commands (continued)
CommandDescription
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, MVME3100).
Example:
MVME3100>
If an invalid MOTLoad command is entered at the MOTLoad command line prompt, MOTLoad
displays a message that the command was not found.
Example:
48
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
MVME3100> mytest
"mytest" not found
MVME3100>
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:
MVME3100> version
Copyright: Motorola Inc.1999-2002, All Rights Reserved
MOTLoad RTOS Version 2.0
PAL Version 0.1 (Motorola MVME3100)
Example:
MVME3100> ver
Copyright: Motorola Inc. 1999-2002, All Rights Reserved
MOTLoad RTOS Version 2.0
PAL Version 0.1 (Motorola MVME3100)
If the partial command string cannot be resolved to a single unique command, MOTLoad will
inform the user that the command was ambiguous.
Example:
MVME3100> te
"te" ambiguous
MVME3100>
MVME3100 Single Board Computer Installation and Use (6806800M28C)
49
MOTLoad Firmware
3.4.1Command Line Rules
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:
MVME3100> flashProgram –d/dev/flash0 –n00100000
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
MVME3100> 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
MVME3100> help testRam
50
MVME3100 Single Board Computer Installation and Use (6806800M28C)
-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
MVME3100>
3.5Firmware Settings
The following sections provide additional information pertaining to the VME firmware settings
of the MVME3100. A few VME settings are controlled by hardware jumpers while the majority
of the VME settings are managed by the firmware command utility vmeCfg.
3.5.1Default VME Settings
As shipped from the factory, the MVME3100 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 B, Related Documentation.
zMVME3100> vmeCfg -s -m
Displaying the selected Default VME Setting
- interpreted as follows:
VME PCI Master Enable [Y/N] = Y
MVME3100>
The PCI Master is enabled.
zMVME3100> vmeCfg –s –r234
Displaying the selected Default VME Setting
- interpreted as follows:
VMEbus Master Control Register = 00000003
MVME3100>
MVME3100 Single Board Computer Installation and Use (6806800M28C)
51
MOTLoad Firmware
The VMEbus Master Control Register is set to the default (RESET) condition.
zMVME3100> vmeCfg –s –r238
Displaying the selected Default VME Setting
- interpreted as follows:
VMEbus Control Register = 00000008
MVME3100>
The VMEbus Control Register is set to a Global Timeout of 2048 μseconds.
zMVME3100> 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
MVME3100>
The CRG Attribute Register is set to the default (RESET) condition.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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:
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
MVME3100 Single Board Computer Installation and Use (6806800M28C)
55
MOTLoad Firmware
zvmeCfg –s –r40C
Displays User AM Codes Register state
zvmeCfg –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:
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
zvmeCfg –e –r400
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
56
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
3.5.5Deleting VME Settings
To delete the changeable VME setting (restore default value), type the following 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
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
MVME3100 Single Board Computer Installation and Use (6806800M28C)
57
MOTLoad Firmware
3.6Remote Start
As described in the MOTLoad Firmware Package User's Manual, listed in Appendix B, 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 MVME3100. 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
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
B, Related Documentation.
The MVME3100 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 B, Related
Documentation, but are noted here for reference:
58
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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 MVME3100 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 MVME3100’s IBCA needs to be mapped appropriately through the master’s VMEbus
bridge. For example, to use remote start using mailbox 0 on an MVME3100 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 MVME3100, 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:
zInitialize cache, MMU, FPU, and other CPU internal items
zInitialize the memory controller
zSearch 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.
zSearch 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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
59
MOTLoad Firmware
zIf 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.
zExecute 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
th e im age as bei ng P ower O n Se lf Tes t (PO ST) , US ER, or M CG. MOTLo ad i s an MCG ima ge. PO ST
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:
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)
60
MVME3100 Single Board Computer Installation and Use (6806800M28C)
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
...
MVME3100>
MVME3100 Single Board Computer Installation and Use (6806800M28C)
61
MOTLoad Firmware
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
ImageRamAddressunsigned integer1RAM address
ImageOffsetunsigned integer1Offset from header start to entry
ImageFlagsunsigned integer1Refer to Image Flagson page 63
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;
62
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
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
ImageRamAddress
before execution
IMAGE_MCG0x00000002MCG-specific image
IMAGE_POST0x00000004POST image
DONT_AUTO_RUN0x00000008Image not to be executed
zCOPY_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.
zIMAGE_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.
zIMAGE_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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
63
MOTLoad Firmware
zDONT_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:
zThe MMU is disabled.
zL1 instruction cache has been initialized and is enabled.
zL1 data cache has been initialized (invalidated) and is disabled.
zL2 cache is disabled.
zL3 cache is disabled.
zRAM has been initialized and is mapped starting at CPU address 0.
zIf RAM ECC or parity is supported, RAM has been scrubbed of ECC or parity errors.
zThe active Flash bank (boot) is mapped from the upper end of the address space.
zIf specified by COPY_TO_RAM, the image has been copied to RAM at the address specified
by ImageRamAddress.
zCPU register R1 (the stack pointer) has been initialized to a value near the end of RAM.
zCPU 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 MVME3100 */
void globalData;/* 16K, zeroed, user defined */
unsigned int reserved[12];
} altBootData_t;
64
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
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.
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 MVME3100, 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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
65
MOTLoad Firmware
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
....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 programm ed 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
66
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MOTLoad Firmware
'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
...
MVME3100>
3.11Startup Sequence
The firmware startup sequence following reset of MOTLoad is to:
zInitialize cache, MMU, FPU, and other CPU internal items
zInitialize the memory controller
zSearch 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.
zSearch 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.
zIf 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.
zExecute 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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
67
MOTLoad Firmware
68
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
4.1Overview
This chapter describes the MVME3100 and the MVME721 rear transition module (RTM) on a
block diagram level.
4.2Features
The following tables list the features of the MVME3100 and its RTM.
Table 4-1 MVME3100 Features Summary
FeatureDescription
Chapter 4
Processor/Host
Controller/Memory Controller
System Memory— One SODIMM socket
I2C Interface— One 8KB VPD serial EEPROM
Flash— 128MB soldered Flash with two alternate 1MB boot sectors selectable
— Up to DDR333, ECC
— One or two banks of memory on a single SODIMM
— Two 64KB user configuration serial EEPROMs
— One real-time clock (RTC) with removable battery
— One temperature sensor
— Interface to SPD(s) on SODIMM and P2 for RTM VPD
via a hardware switch
— Hardware switch or software bit write protection for entire logical bank
MVME3100 Single Board Computer Installation and Use (6806800M28C)
69
Functional Description
Table 4-1 MVME3100 Features Summary (continued)
FeatureDescription
PCI InterfaceBus A:
— 66 MHz PCI-X mode
— One TSi148 VMEbus controller
— O ne serial ATA (sATA) controller
— One MPC8540
— Two PCI6520 PCI-X-to-PCI-X bridges (primary side)
Bus B:
— 33/66/100 MHz PCI/PCI-X (PCI 2.2 and PCI-X 1.0b compliant)
— Two +3.3V/5V selectable VIO, 64-bit, single-wide PMC sites or one
double-wide PMC site (PrPMC ANSI/VITA 32-2003 and PCI-X Auxiliary
ANSI/VITA 39-2003 compliant)
— One PCI6520 PCI-X-to-PCI-X bridge (secondary side)
Bus C (-1263 version):
— 33 MHz PCI (PCI 2.2 compliant)
— One USB 2.0 controller
— One PCI expansion connector for interface to PMCspan
— One PCI6520 PCI-X-to-PCI-X bridge (secondary side)
I/O— One front panel RJ45 connector with integrated LEDs for front I/O: one
serial channel
— One front panel RJ45 connector with integrated LEDs for front I/O: one
10/100/1000 Ethernet channel
— One front panel external sATA data connector for front I/O: one sATA
channel
— One front panel USB Type A upright receptacle for front I/O: one USB
2.0 channel (-1263 version)
— PMC site 1 front I/O and rear P2 I/O
— PMC site 2 front I/O
Serial ATA— One four-channel sATA controller: one channel for front-panel I/O, one
channel for planar I/O, one channel for future rear P0 I/O, and one
channel is not used
— One planar data connector and one planar power connector for an
interface to the sATA hard disk drive
USB (-1263 version)— One four-channel USB 2.0 controller: one channel for front panel
Ethernet— Two 10/100/1000 MPC8540 Ethernet channels for front-panel I/O and
rear P2 I/O
— One 10/100 MPC8540 Ethernet channel for rear P2 I/O
70
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
Table 4-1 MVME3100 Features Summary (continued)
FeatureDescription
Serial Interface— One 16550-compatible, 9.6 to 115.2 KBAUD, MPC8540, asynchronous
serial channel for front-panel I/O
— One quad UART controller to provide four 16550-compatible, 9.6 to
115.2 KBAUD, asynchronous serial channels for rear P2 I/O
Timers— Four 32-bit MPC8540 timers
— Four 32-bit timers in a PLD
Watchdog Timer— One MPC8540 watchdog timer
VME Interface— VME64 (ANSI/VITA 1-1994) compliant
— VME64 Extensions (ANSI/VITA 1.1-1997) compliant
— 2eSST (ANSI/VITA 1.5-2003) compliant
— VITA 41.0, version 0.9 compliant
— Two five-row P1 and P2 backplane connectors
— One TSi148 VMEbus controller
Form Factor— Standard 6U VME
Miscellaneous— One front-panel reset/abort switch
— Four front-panel status indicators: 10/100/1000 Ethernet link/speed
and activity, board fail, and user software controlled LED
— Six planar status indicators: one power supply status LED, two user
software controlled LEDs, three sATA activity LEDs (one per channel)
— One standard 16-pin COP header
— Boundary scan support
— Switches for VME geographical addressing in a three-row backplane
Software Support— VxWorks operating system
— Linux operating system
Table 4-2 MVME721 RTM Features Summary
FeatureDescription
I/O— One five-row P2 backplane connector for serial and Ethernet I/O
passed from the MVME3100
— Four RJ-45 connectors for rear-panel I/O: four asynchronous serial
channels
— Two RJ-45 connectors with integrated LEDs for rear panel I/O: one
10/100/1000 Ethernet channel and one 10/100 Ethernet channel
— One PIM site with rear-panel I/O
MVME3100 Single Board Computer Installation and Use (6806800M28C)
71
Functional Description
Table 4-2 MVME721 RTM Features Summary (continued)
FeatureDescription
Miscellaneous— Four status indicators: 10/100/1000 and 10/100 Ethernet link/speed
and activity LEDs
72
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
4.3Block Diagrams
Figure 4-1 shows a block diagram of the overall board architecture and Figure 4-2 shows a
block diagram of the MVME721 rear transition module architecture.
Figure 4-1MVME3100 Block Diagram
MVME3100 Single Board Computer Installation and Use (6806800M28C)
73
Functional Description
Figure 4-2MVME721 RTM Block Diagram
4390 0106
PIM 10
PIM
U
S
B
sATA
P2
P0
GigE
RJ45
GigE 2
10/100
Serial Port 4
Serial Port 3
Serial Port 2
Serial Port 1
VPD
8K8
I2C Bus
Rear Panel
Future Option
10/100
RJ45
Serial
RJ45
Serial
RJ45
Serial
RJ45
Serial
RJ45
PMC 1 Jn4 10
sATA 3
USB 2
Future Option
4.4Processor
The MVME3100 supports the MPC8540 processor. The processor core frequency runs at 833
or 667 MHz. The MPC8540 has integrated 256KB L2 cache.
4.5System Memory
The MPC8540 provides one standard DDR SDRAM SODIMM socket. This socket supports
standard single or dual bank, unbuffered, SSTL-2 DDR-I, JESD8-9B compliant, SODIMM module
74
with ECC. The MPC8540 DDR memory interface supports up to 166 MHz (333 MHz data rate)
operation.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
4.6Local Bus Interface
The MVME3100 uses the MPC8540 local bus controller (LBC) for access to on-board Flash and
I/O registers. The LBC has programmable timing modes to support devices of different access
times, as well as device widths of 8, 16, and 32 bits.
The MVME3100 uses the LBC in GPCM (general purpose chip select machine) mode to
interface to two physical banks of on-board Flash, an on-board quad UART (QUART), on-board
32-bit timers, and the System Control/Status registers. Refer to the MVME3100 Single-Board
Computer Programmer’s Reference Guide listed in Appendix B, Related Documentation, for the
LBC bank and chip select assignments.
4.6.1Flash Memory
The MVME3100 provides one physical bank of soldered-on Flash memory. The bank is
composed of two physical Flash devices configured to operate in 16-bit mode to form a 32-bit
Flash bank. The default configuration for the MVME3100-1263 is 128MB using two 512Mb
devices, and for the MVME3100-1152 it is 64MB using two 256Mb devices.
Refer to the MVME3100 Single-Board Computer Programmer’s Reference Guide listed in
Appendix B, Related Documentation, for more information.
4.6.2Control and Timers Logic
The MVME3100 control and timers logic resides on the local bus. This logic provides the
following functions on the board:
zLocal bus address latch
zChip selects for Flash banks and QUART
zSystem Control and Status registers
zFour 32-bit tick timers
zReal-time clock (RTC) 1 MHz reference clock
Refer to the MVME3100 Single-Board Computer Programmer’s Reference Guide listed in Appendix
B, Related Documentation, for more information.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
75
Functional Description
4.7I2C Serial Interface and Devices
The MVME3100 provides the following on-board I2C serial devices connected to the MPC8540
I2C controller interface:
z8KB serial EEPROM for VPD
zTwo 64KB serial EEPROMs for user configuration data storage
z256 byte serial EEPROM on SODIMM for SPD
zMaxim DS1375 RTC
zMaxim DS1621 temperature sensor
z8KB serial EEPROM on RTM VPD
The Maxim DS1375 RTC implemented on the MVME3100 provides an alarm interrupt routed
to the MPC8540 programmable interrupt controller (PIC). A Maxim DS32KHz temperature
controlled crystal oscillator provides the RTC reference. A battery backup circuit for the RTC is
provided on board.
The Maxim DS1621 digital temperature sensor provides a measure of the temperature of the
board.
2
The I
C interface is also routed to the on-board SODIMM socket. This allows the serial presence
detect (SPD) in the serial EEPROM, which is located on the memory module, to be read and
used to configure the memory controller accordingly. Similarly, the I2C interface is routed to
the P2 connector for access to the serial EEPROM located on the RTM. The device address for
the RTM serial EERPOM is user-selectable using configuration switches on the RTM.
Refer to the MVME3100 Single-Board Computer Programmer’s Reference Guide in Appendix B,
Related Documentation, for more information.
4.8Ethernet Interfaces
The MVME3100 provides one 10/100 and two 10/100/1000 Mb/s full duplex Ethernet
interfaces using the MPC8540 Fast Ethernet Controller (FEC) and two Triple Speed Ethernet
Controllers (TSEC). A Broadcom BCM5461S PHY is used for each TSEC interface, and each TSEC
interface and PHY is configured to operate in GMII mode. One Gigabit Ethernet interface is
routed to a front-panel RJ-45 connector with integrated LEDs for speed and activity indication.
The other Gigabit Ethernet interface is routed to P2 for rear I/O.
76
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
A Broadcom BCM5221 PHY is used for the FEC interface. The Fast Ethernet interface is routed
to P2 for rear I/O. Isolation transformers are provided on-board for each interface. The assigned
PHY addresses for the MPC8540 MII management (MIIM) interface can be found in the
MVME3100 Single-Board Computer Programmer’s Reference Guide, listed in Appendix B,
Related Documentation.
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.
4.9Asynchronous Serial Ports
The MVME3100 board contains one front-access asynchronous serial port interface using serial
port 0 from the MPC8540 dual UART (DUART) device. This serial port is routed to the RJ-45
front-panel connector.
This board also contains one quad UART (QUART) device connected to the MPC8540 device
controller bus to provide additional asynchronous serial ports. The QUART provides four
asynchronous serial ports,
SP1 — SP4, which are routed to the P2 connector. Refer to the ST16C554D Datasheet listed in
Appendix B, Related Documentation, for additional details and/or programming information.
4.10PCI/PCI-X Interfaces and Devices
The MVME3100 provides three separate PCI/PCI-X bus segments. Bus segment A operates in
66MHz PCI-X mode and is connected to the MPC8540, the Tsi148 VME controller, the serial ATA
(sATA) controller, and two PCI-X-to-PCI-X bridges. Bus segment B is bridged between bus A and
the two PMC sites and operates in 33/66 MHz PCI or 66/100 MHz PCI-X mode depending on
the slowest speed PMC installed. Bus segment C is bridged between bus A, the USB controller,
and the PMCspan connector. Bus C operates at 33 MHz PCI mode.
4.10.1MPC8540 PCI-X Interface
The MPC8540 PCI-X controller is configured to operate in PCI-X mode only, host bridge mode.
Bus A mode switch must be in "OFF" position in order to be fixed in PCI-X mode. The mode
cannot be changed by software. Refer to the MPC8540 Reference Manual listed in Appendix B,
Related Documentation, for additional details and/or programming information.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
77
Functional Description
4.10.2TSi148 VME Controller
The VMEbus interface for the MVME3100 is provided by the TSi148 ASIC. The TSi148 provides
the required VME, VME extensions, and 2eSST functions. Transceivers are used to buffer the
VME signals between the TSi148 and the VME backplane. Refer to the TSi148 User's Manual
listed in Appendix B, Related Documentation, for additional details and/or programming
information.
4.10.3Serial ATA Host Controller
The sATA host controller uses the Silicon Image SiI3124A PCI-X to Serial ATA Controller. This
device provides four sATA channels at 1.5Gb/s and is compliant with the Serial ATA: High speed serialized AT Attachment Specification, Revision 1.0. It also supports the native command
queuing feature of sATA II.
The MVME3100 uses two of the four sATA channels. Channel 0 is routed to a sATA connector
mounted on the front panel for an external drive connection. Channel 1 is routed to a planar
sATA connector for an "inside the chassis" drive connection. Collocated with the planar
connector is a sATA power connector. The sATA controller can operate in legacy (Native PCI
IDE) and Direct Port Access (DPA) mode.
The MVME3100 provides two programmable LEDs to indicate sATA channel activity.
Refer to the SiI3124A PCI-X to Serial ATA Controller Datasheet listed in Appendix B, Related
Documentation, for additional details and/or programming information
4.10.4PCI-X-to-PCI-X Bridges
The MVME3100 uses two PLX PCI6520 PCI-X-to-PCI-X bridges to isolate the primary PCI bus,
bus A. These bridges isolate bus A from bus B with the PMC sites and from bus C with the USB
controller and PMCspan interface. The PCI6520 is a 64-bit, 133 MHz, PCI-X r1.0b compliant
device. It operates asynchronously between 33 MHz and 133 MHz on either primary or
secondary port. Refer to the PCI6520CB Data Book listed in Appendix B, Related
Documentation, for additional details and/or programming information.
78
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
4.10.5PCI Mezzanine Card Slots
The MVME3100 provides two PMC sites that support standard PMCs or PrPMCs. Both PMC sites
are located on PCI bus B and operate at the same speed and mode as determined by the
slowest PMC module. The board routing supports a maximum of 100 MHz PCI-X operation on
each site. Signaling voltage (Vio) for the two PMC sites is dependent on keying pin installation
options and can be configured for 5V or 3.3V. Both sites must be configured for the same Vio
voltage or the Vio voltage will be disabled. Each PMC site has enough 3.3V and 5V power
allocated to support a 25 watt (max) PMC or PrPMC from either supply.
PMC slot 1 supports:
FeatureDescription
Mezzanine Type:PMC = 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
PMC slot 2 supports:
FeatureDescription
Mezzanine Type:PMC = PCI Mezzanine Card
Mezzanine Size:S1B = Single width and standard depth
(75mm x 150mm) with front panel
PMC Connectors: J21, J22, and J23 (32/64-bit PCI with front I/O)
Signalling Voltage: VIO = +3.3V (+5V tolerant) or +5V, selected by keying pin
You cannot use 3.3V and 5V PMCs together; the voltage keying pin on slots 1 and 2 must be
identical. When in 5V 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.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
79
Functional Description
In this case, the MVME3100 supports:
FeatureDescription
Mezzanine Type:PMC = PCI Mezzanine Card
Mezzanine Size:Double width and standard depth
(150mm x 150mm) with front panel
PMC Connectors: J11, J12, J13, J14, J21, J22, and J23
(32/64-bit PCI with front and rear I/O) on J14 only
Signaling Voltage:VIO = +3.3V (+5V tolerant) or +5V, selected by keying pin
On PMC site 1, the user I/O — J14 signals will only support the low-current, high-speed signals
and are not to be used for any current bearing power supply usage. The maximum current
rating of each pin/signal is 100 mA.
4.10.6USB
The USB 2.0 host controller provides USB ports with integrated transceivers for connectivity
with any USB-compliant device or hub. USB channel 1 is routed to a single USB connector
located at the front panel. DC power to the front panel USB port is supplied via a USB power
switch, which provides soft-start, current limiting, over-current detection, and power enable
for port 1. Refer to the μPD720101 USB 2.0 Host Controller Datasheet listed in Appendix B,
Related Documentation, for additional details.
4.10.7PMC Expansion
The MVM3E3100 provides additional PMC module capability through the use of a connector
on bus C that is compatible with the PMCspan boards. Up to four additional PMC modules may
be added by using existing PMCspan boards. Refer to the PMCspan PMC Adapter Carrier Board Installation and Use manual listed in Appendix B, Related Documentation, for additional details.
80
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Functional Description
4.11General-Purpose Timers
There are a total of eight independent, 32-bit timers. Four timers are integrated into the
MPC8540 and four timers are in the PLD. The four MPC8540 timers are clocked by the RTC
input, which is driven by a 1 MHz clock. The clock source for the four timers in the PLD is 25
MHz. Refer to the MPC8540 Reference Manual listed in Appendix B, Related Documentation, for
additional details and/or programming information.
4.12Real-time Clock Battery
There is an on-board Renata SMT battery holder on the MVME3100. This SMTU2430-1 holder
allows for quick and easy replacement of a 3V button cell lithium battery (CR2430), which
provides back-up power to the on-board DS1375 RTC. A battery switching circuit provides
automatic switching between the 3.3V and battery voltages. The battery provides backup
power to the RTC for a minimum of one year at nominal temperature.
4.13Reset Control Logic
The sources of reset on the MVME3100 are the following:
zPower-up
zReset switch
zWatchdog timer
zSystem Control register bit
zVMEbus reset
A board-level hard reset generates a reset for the entire board including the MPC8540, local
PCI/PCI-X buses, Ethernet PHYs, serial ports, Flash devices, and PLD(s). If the MVME3100 is
configured as the VME system controller, the VME bus and local TSi148 reset input are also
reset.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
81
Functional Description
4.14Debug Support
The MVME3100 provides a boundary scan header for boundary scan test access and device
programming. This board also provides a separate standard COP header for MPC8540 COP
emulation.
82
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Pin Assignments
5.1Overview
This chapter provides pin assignments for various connectors and headers on the MMVE3100
single-board computer and the MVME721 transition module.
The following headers are described in this chapter:
zBoundary Scan Header (J24)
zProcessor COP Header (J25)
5.2Connectors
This section describes the pin assignments and signals for the connectors on the MVME3100.
MVME3100 Single Board Computer Installation and Use (6806800M28C)
83
Pin Assignments
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:
There is one 10/100 and two 10/100/1000Mb/s full duplex Ethernet interfaces using the
MPC8540 Fast Ethernet Controller (FEC) and two Triple Speed Ethernet Controllers (TSEC). One
Gigabit Ethernet interface is routed to a front-panel RJ-45 connector with integrated LEDs for
speed and activity indication. The other Gigabit Ethernet interface and the 10/100 interface
are routed to P2 for rear I/O. The pin assignments for these connectors are as follows:
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Pin Assignments
5.2.4Serial Port Connectors (COM1/J41A, COM2—COM5/J2A-D)
There is one front access asynchronous serial port interface (SP0) that is routed to the RJ-45
front-panel con nector. There are four asynchronous ser ial por t int erfa ces, SP1 — SP4, wh ich are
routed to the P2 connector. The pin assignments for these connectors are as follows:
Table 5-10 COM Port Connector Pin Assignments
PinSignal
1No connect
2RTS
3GND
4TX
5RX
6GND
7CTS
8No connect
5.2.5VMEbus P1 Connector
The VME P1 connector is a 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-11 VMEbus P1 Connector Pin Assignments
ROW ZROW AROW BROW CROW D
1Reserved D00BBSY*D08+5V1
2GNDD01BCLR*D09GND2
3Reserved D02ACFAIL*D10Reserved3
4GNDD03BG0IN*D11Reserved4
5ReservedD04BG0OUT*D12Reserved5
6GNDD05BG1IN*D13Reserved6
7Reserved D06BG1OUT*D14Reserved7
MVME3100 Single Board Computer Installation and Use (6806800M28C)
MVME3100 Single Board Computer Installation and Use (6806800M28C)
Pin Assignments
5.2.6VMEbus P2 Connector
The VME P2 connector is a 160-pin DIN. Row B of the P2 connector provides power to the
MVME3100 and to the upper eight VMEbus address lines and additional 16 VMEbus data lines.
The pin assignments for the P2 connector are the same for both the MVME3100 and
MVME721, and are as follows:
Table 5-12 VME P2 Connector Pinouts
PinP2-ZP2-AP2-BP2-CP2-D
1SP1RXPMC1_IO2+5VPMC1_IO1E1-1+
2GNDPMC1_IO4GNDPMC1_IO3E1-1-
3SPITXPMC1_IO6VRETRY_LPMC1_IO5GND
4GNDPMC1_IO8VA24PMC1_IO7E1-2+
5SP1CTSPMC1_IO10VA25PMC1_IO9E1-2-
6GNDPMC1_IO12VA26PMC1_IO11 GND
7SP1RTSPMC1_IO14VA27PMC1_IO13NC
8GNDPMC1_IO16VA28PMC1_IO15NC
9SP2RXPMC1_IO18VA29PMC1_IO17GND
10GNDPMC1_IO20VA30PMC1_IO19NC
11SP2TXPMC1_IO22VA31PMC1_IO21NC
12GNDPMC1_IO24GNDPMC1_IO23GND
13SP2CTSPMC1_IO26+5VPMC1_IO25I2C_SDA
14GNDPMC1_IO28VD16PMC1_IO27I2C_SCL
15SP2RTSPMC1_IO30VD17PMC1_IO29E1_LINK
16GNDPMC1_IO32VD18PMC1_IO31E1_ACT
17SP3RXPMC1_IO34VD19PMC1_IO33E2_LINK
18GNDPMC1_IO36VD20PMC1_IO35E2_ACT
19SP3TXPMC1_IO38VD21PMC1_IO37GND
20GNDPMC1_IO40VD22PMC1_IO39E2-4-
21SP3CTSPMC1_IO42VD23PMC1_IO41E2-4+
22GNDPMC1_IO44GNDPMC1_IO43GND
MVME3100 Single Board Computer Installation and Use (6806800M28C)
PMC Host I/O connector J10 routes only power and ground from VME P2. There are no Host I/O
signals on this connector. The MVME3100 routes PMC I/O from J14 of PMC Slot 1 to VME P2
rows A and C. The MVME721 routes these signals (pin-for-pin) from VME P2 to PMC I/O Module
connector J14. See Table 5-13 and Table 5-6 for the pin assignments.