MVME2600 Series
Single Board Computer
Installation and Use
V2600A/IH3
July 2001 Edition
?? Copyright 1998, 2001 Motorola, Inc.
All rights reserved.
Printed in the United States of America.
Motorola?? and the Motorola symbol are registered trademarks of Motorola, Inc. AIX?? is a registered trademark of International Business Machines Corporation. PowerPC?? is a registered trademark of International Business Machines.
SNAPHAT?? , TIMEKEEPER?? , and ZEROPOWER?? are registered trademarks of STMicroelectronics.
All other products mentioned in this document are trademarks or registered trademarks of their respective holders.
Safety Summary
The following general safety precautions must be observed during all phases of operation, service, and repair of this equipment. Failure to comply with these precautions or with specific warnings elsewhere in this manual could result in personal injury or damage to the equipment.
The safety precautions listed below represent warnings of certain dangers of which Motorola is aware. You, as the user of the product, should follow these warnings and all other safety precautions necessary for the safe operation of the equipment in your operating environment.
Ground the Instrument.
To minimize shock hazard, the equipment chassis and enclosure must be connected to an electrical ground. If the equipment is supplied with a
Do Not Operate in an Explosive Atmosphere.
Do not operate the equipment in any explosive atmosphere such as in the presence of flammable gases or fumes. Operation of any electrical equipment in such an environment could result in an explosion and cause injury or damage.
Keep Away From Live Circuits Inside the Equipment.
Operating personnel must not remove equipment covers. Only Factory Authorized Service Personnel or other qualified service personnel may remove equipment covers for internal subassembly or component replacement or any internal adjustment. Service personnel should not replace components with power cable connected. Under certain conditions, dangerous voltages may exist even with the power cable removed. To avoid injuries, such personnel should always disconnect power and discharge circuits before touching components.
Use Caution When Exposing or Handling a CRT.
Breakage of a
Do Not Substitute Parts or Modify Equipment.
Do not install substitute parts or perform any unauthorized modification of the equipment. Contact your local Motorola representative for service and repair to ensure that all safety features are maintained.
Observe Warnings in Manual.
Warnings, such as the example below, precede potentially dangerous procedures throughout this manual. Instructions contained in the warnings must be followed. You should also employ all other safety precautions which you deem necessary for the operation of the equipment in your operating environment.
To prevent serious injury or death from dangerous voltages, use extreme caution when handling, testing, and adjusting this equipment and its
Warning components.
Flammability
All Motorola PWBs (printed wiring boards) are manufactured with a flammability rating of
EMI Caution
This equipment generates, uses and can radiate electromagnetic energy. It
!may cause or be susceptible to electromagnetic interference (EMI) if not
Caution installed and used with adequate EMI protection.
Lithium Battery Caution
This product contains a lithium battery to power the clock and calendar circuitry.
Danger of explosion if battery is replaced incorrectly. Replace battery only
!with the same or equivalent type recommended by the equipment
Caution manufacturer. Dispose of used batteries according to the manufacturer???s instructions.
Il y a danger d???explosion s???il y a remplacement incorrect de la batterie.
!Remplacer uniquement avec une batterie du m??me type ou d???un type
Attention ??quivalent recommand?? par le constructeur. Mettre au rebut les batteries usag??es conform??ment aux instructions du fabricant.
Explosionsgefahr bei unsachgem????em Austausch der Batterie. Ersatz nur
!durch denselben oder einen vom Hersteller empfohlenen Typ. Entsorgung
Vorsicht gebrauchter Batterien nach Angaben des Herstellers.
CE Notice (European Community)
Motorola Computer Group products with the CE marking comply with the EMC Directive (89/336/EEC). Compliance with this directive implies conformity to the following European Norms:
EN55022 ???Limits and Methods of Measurement of Radio Interference Characteristics of Information Technology Equipment???; this product tested to Equipment Class B
System products also fulfill EN60950 (product safety) which is essentially the requirement for the Low Voltage Directive (73/23/EEC).
Board products are tested in a representative system to show compliance with the above mentioned requirements. A proper installation in a
In accordance with European Community directives, a ???Declaration of Conformity??? has been made and is on file within the European Union. The ???Declaration of Conformity??? is available on request. Please contact your sales representative.
Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any omissions in this document, or from the use of the information obtained therein. Motorola reserves the right to revise this document and to make changes from time to time in the content hereof without obligation of Motorola 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 the Motorola Computer Group website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise altered without the permission of Motorola, Inc.
It is possible that this publication may contain reference to or information about Motorola 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 Motorola intends to announce such Motorola 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 Motorola, Inc.
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
Motorola, Inc.
Computer Group
2900 South Diablo Way
Tempe, Arizona 85282
Contents
vii
viii
ix
x
xi
List of Figures
xiii
List of Tables
xv
xvi
About This Manual
This manual provides general information, hardware preparation and installation instructions, operating instructions, and a functional description of the MVME2603/2604 family of single board computers.
As of the publication date, the information presented in this manual applies to the following MVME2603 and MVME2604 models:
xvii
Summary of Changes
This is the third edition of the Installation and Use manual. It supersedes the May 1998 edition and incorporates the following updates.
Overview of Contents
Chapter 1, Hardware Preparation and Installation, provides general information, hardware preparation and installation instructions, operating instructions, and a functional description of the MVME2603/2604 family of single board computers.
Chapter 2, Operating Instructions, supplies information for use of the MVME2603/2604 family of single board computers in a system configuration.
Chapter 3, Functional Description, describes the MVME2603/2604 single board computer on a block diagram level.
Chapter 4, Connector Pin Assignments, provides pin assignments for the interconnect signals for the MVME2603/2604 family of single board computers.
Chapter 5, PPCBug, describes the basics of PPCBug and its architecture, describes the monitor (interactive command portion of the firmware) in detail, and gives information on actually using the PPCBug debugger and the special commands.
Chapter 6, CNFG and ENV Commands, contains information about the CNFG and ENV commands. These two commands are used to change configuration information and command parameters interactively.
xviii
Appendix A, Specifications, lists the general specifications for
MVME2603/2604 base boards.
Appendix B, Serial Interconnections, describes the MVME2603/2604 serial communications interfaces.
Appendix C, Troubleshooting CPU Boards: Solving Startup Problems, supplies the user with troubleshooting tips before having to call for help.
Appendix D, Related Documentation, lists all documentation related to the MVME2603/2604 single board computer.
Comments and Suggestions
Motorola welcomes and appreciates your comments on its documentation. We want to know what you think about our manuals and how we can make them better. Mail comments to:
Motorola Computer Group
Reader Comments DW164
2900 S. Diablo Way
Tempe, Arizona 85282
You can also submit comments to the following
In all your correspondence, please list your name, position, and company. Be sure to include the title and part number of the manual and tell how you used it. Then tell us your feelings about its strengths and weaknesses and any recommendations for improvements.
xix
Conventions Used in This Manual
The following typographical conventions are used in this document:
bold
is used for user input that you type just as it appears; it is also used for commands, options and arguments to commands, and names of programs, directories and files.
italic
is used for names of variables to which you assign values. Italic is also used for comments in screen displays and examples, and to introduce new terms.
courier
is used for system output (for example, screen displays, reports), examples, and system prompts.
<Enter>, <Return> or <CR>
<CR> represents the carriage return or Enter key.
Ctrl
represents the Control key. Execute control characters by pressing the Ctrl key and the letter simultaneously, for example,
xx
Hardware Preparation and
Installation 1
Introduction
The MVME2603/2604 is a
The complete MVME2603/2604 consists of the base board plus:
???An ECC DRAM module (RAM200) for memory
???An optional PCI mezzanine card (PMC) for additional versatility
???An optional carrier board for additional PCI expansion
The block diagram in Figure
MVME2603/2604 base board.
Hardware Preparation and Installation
Figure
Equipment Required
The following equipment is required to complete an MVME2603/2604 system:
???VME system enclosure
???System console terminal
???Operating system (and/or application software)
???Disk drives (and/or other I/O) and controllers
???Transition module (MVME712M or MVME761) and connecting cables
MVME2603/2604 VME modules are
Overview of Startup Procedure
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
Hardware Preparation and Installation
Table
Unpacking Instructions
Note If the shipping carton is damaged upon receipt, request that the carrier???s agent be present during the unpacking and inspection of the equipment.
!
Caution
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.
Avoid touching areas of integrated circuitry; static discharge can damage circuits.
Hardware Configuration
To produce the desired configuration and ensure proper operation of the MVME2603/2604, you may need to carry out certain hardware modifications before installing the module.
The MVME2603/2604 provides software control over most options: by setting bits in control registers after installing the module in a system, you can modify its configuration. (The MVME2603/2604 control registers are described in Chapter 3, Functional Description, and/or in the MVME2600 Series Single Board Computer Programmer???s Reference Guide, as listed in Appendix D, Related Documentation.)
Some options, however, are not
MVME2603/2604 Base Board Preparation
Figure
???Cache mode control (J3)
???Flash bank selection (J10)
???Serial Port 4 receive clock configuration (J16)
???Serial Port 4 transmit clock configuration (J17)
???Serial Port 4 transmit clock receiver buffer control (J20)
???Serial Port 3 transmit clock configuration (J18)
???System controller selection (J22)
In conjunction with the serial port settings on the base board, serial ports on the associated MVME712M or MVME761 transition module are also manually configurable. For a discussion of the configurable items on the transition module, refer to MVME712M Transition Module Preparation on page
The MVME2603/2604 is factory tested and shipped with the configurations described in the following sections. The MVME2603/2604???s required and
Cache Mode Control (J3)
256KB of L2 cache memory is available on the MVME2603/2604. L2 cache operation is transparent to users, but its
Flash Bank Selection (J10)
The MVME2603/2604 base board has provision for 1MB of
The Flash memory is organized in either one or two banks, each bank either 16- or
To enable Flash bank A (4MB or 8MB of firmware resident on soldered- in devices on the RAM200 mezzanine), place a jumper across header J10 pins 1 and 2. To enable Flash bank B (1MB of firmware located in sockets on the base board), place a jumper across header J10 pins 2 and 3.
Serial Port 4 Receive Clock Configuration (J16)
In synchronous serial communications, you can configure Serial Port 4 on the MVME2603/2604 to use the clock signals provided by the RxC signal line. On
To complete the configuration of Serial Port 4, you must set the following configuration headers as well:
???J17 (Serial Port 4 transmit clock configuration)
???J20 (Serial Port 4 transmit clock receiver buffer control)
???J15 on the MVME712M transition module or J3 on the MVME761 transition module (Serial Port 4 clock configuration)
Figure
For additional details on the configuration of those headers, refer to
MVME712M Transition Module Preparation on page
(factory configuration)
MVME2603/2604 Base Board Preparation
J1 1
J2 2
A1
B1
C1
D1
P1
Figure
Serial Port 4 Transmit Clock Configuration (J17)
In synchronous serial communications, you can configure Serial Port 4 on the MVME2603/2604 to use the clock signals provided by the TxC signal line. Header J17 configures port 4 to either drive or receive TxC. The factory configuration has port 4 set to receive TxC.
To complete the configuration of Serial Port 4, you must set the following configuration headers as well:
???J16 (Serial Port 4 receive clock configuration)
???J20 (Serial Port 4 transmit clock receiver buffer control)
???J15 on the MVME712M transition module or J3 on the MVME761 transition module (Serial Port 4 clock configuration)
Figure
For additional details on the configuration of those headers, refer to
MVME712M Transition Module Preparation on page
(factory configuration)
Serial Port 4 Transmit Clock Receiver Buffer Control (J20)
As described in other sections, a complete configuration of Serial Port 4 requires that you set the following jumper headers on the MVME2603/2604 or the transition module:
???J16 (Serial Port 4 receive clock configuration) on MVME712M- compatible versions of the base board
???J17 (Serial Port 4 transmit clock configuration)
???J20 (Serial Port 4 transmit clock receiver buffer control) on
???J15 on the MVME712M transition module or J3 on the MVME761 (Serial Port 4 clock configuration)
A transmit clock receiver buffer (controlled by header J20) is associated with Serial Port 4. Installing a jumper on J20 enables the buffer. Removing the jumper disables the buffer. The factory configuration has the Serial Port 4 buffer enabled.
J20 remains open on
Figure
Hardware Preparation and Installation
For additional details on the configuration of those headers, refer to
MVME712M Transition Module Preparation on page
Serial Port 3 Transmit Clock Configuration (J18)
In synchronous serial communications using the MVME761 transition module, you can configure Serial Port 3 on the MVME2603/2604 to use the clock signals provided by the TxC signal line. On MVME761- compatible versions of the base board, header J18 configures port 3 to either drive or receive TxC. The factory configuration has port 3 set to receive TxC. J18 remains open on
To complete the configuration of Serial Port 3, you must set J2 on the MVME761 transition module (Serial Port 3 clock configuration) as well.
Figure
MVME2603/2604 Base Board Preparation
For additional details on the configuration of the MVME761 headers, refer to MVME761 Transition Module Preparation on page
(factory configuration)
System Controller Selection (J22)
The MVME2603/2604 is
Remote Status and Control
The MVME2603/2604 front panel LEDs and switches are mounted on a removable mezzanine board. Removing the LED mezzanine makes the mezzanine connector (J1, a keyed
Table
MVME712M Transition Module Preparation
The MVME712M transition module (Figure
The features of the MVME712M include:
???A parallel printer port
???An Ethernet interface supporting AUI connections
???One synchronous/asynchronous, and three asynchronous only,
???An SCSI interface (via P2 adapter) for connection to both internal and external devices
???
???Provision for modem connection
???Green LED for SCSI terminator power; yellow LED for Ethernet transceiver power
The features of the P2 adapter board include:
???A
MVME712M Transition Module Preparation
???
???Fused SCSI terminator power developed from the +5VDC present at connector P2
???A
Serial Ports
Serial ports 1 through 4 are configurable as modems (DCE) for connection to terminals, or as terminals (DTE) for connection to modems. The MVME712M is shipped with the serial ports configured for DTE operation. Serial port DCE/DTE configuration is accomplished by positioning jumpers on one of two headers per port. The following table lists the serial ports with their corresponding jumper headers.
Table
The next six figures illustrate the MVME2603/2604 base board and MVME712M transition module with the interconnections and jumper settings for DCE/DTE configuration on each serial port.
Serial Port 4 Clock Configuration
Port 4 can be configured via J15 (Figure
J15
TRXC4 TO PORT 4 PIN 15
TRXC4 TO PORT 4 PIN 17 TRXC4 TO PORT 4 PIN 24
RTXC4 TO PORT 4 PIN 24
RTXC4 TO PORT 4 PIN 17 RTXC4 TO PORT 4 PIN 15
Figure
Hardware Preparation and Installation
Figure
MVME712M Transition Module Preparation
Figure
Hardware Preparation and Installation
MVME2603/2604
Z85230
TXDA
RTSA#
DCDA#
RXDA
CTSA#
TRXCA# +5V
DCE
RTXCA#+5V
Z8536
DTR3#
LLB3# +5V
RLB3# +5V
DSR3#
R13# +5V
TM3# +5V
5
DTR
20
TXD
2
RTS
4
DCD
8
NOTE: J18 OPEN
11551.00 9609
Figure
MVME712M Transition Module Preparation
MVME2603/2604
Z85230
TXDA
RTSA#
DCDA#
RXDA
CTSA#
TRXCA# +5V
DTE
RTXCA#+5V
Z8536
DTR3#
LLB3# +5V
RLB3# +5V
DSR3#
R13# +5V
TM3# +5V
4
DCD
8
RXD
3
CTS
5
DTR
20
GND
7
NOTE: J18 OPEN
11551.00 9609
Figure
Hardware Preparation and Installation
Figure
MVME712M Transition Module Preparation
Figure
P2 Adapter Preparation
Preparation of the P2 adapter for the MVME712M consists of removing or installing the SCSI terminating resistors. Figure
For further information on the preparation of the transition module and the
P2 adapter, refer to the user???s manual for the MVME712M (listed in
Appendix D, Related Documentation) as necessary.
cb211 9212
Figure
MVME761 Transition Module Preparation
The MVME761 transition module (Figure
The features of the MVME761 include:
???A parallel printer port (IEEE
???An Ethernet interface supporting 10BaseT/100BaseTX connections
???Two
???Two synchronous serial ports (SERIAL 3 and SERIAL 4 on the front panel), configurable for
???Two
The features of the P2 adapter board for the MVME761 include:
???A
???
???Fused SCSI terminator power developed from the +5V DC present at connector P2
???A
Hardware Preparation and Installation
Figure
Serial Ports 1 and 2
On
Configuration of Serial Ports 3 and 4
The synchronous serial ports, Serial Port 3 and Serial Port 4, are configurable through a combination of serial interface module (SIM) selection and jumper settings. The following table lists the SIM connectors and jumper headers corresponding to each of the synchronous serial ports.
Port 3 is routed to board connector J7. Port 4 is available at board connector J8. Eight serial interface modules are available:
???
???
???V.35 (DCE and DTE)
???X.21 (DCE and DTE)
You can configure Serial Ports 3 and 4 for any of the above serial protocols by installing the appropriate serial interface module and setting the corresponding jumper. SIMs can be ordered separately as required.
Hardware Preparation and Installation
Headers J2 and J3 are used to configure Serial Port 3 and Serial Port 4, respectively, in tandem with SIM selection. With the jumper in position
When installing the SIM modules, note that the headers are keyed for proper orientation.
For further information on the preparation of the transition module, refer to the user???s manual for the MVME761 (listed in Appendix D, Related Documentation) as necessary.
The next three figures illustrate the MVME2603/2604 base board and MVME761 transition module with the interconnections and jumper settings for DCE/DTE configuration on each serial port.
MVME761 Transition Module Preparation
Figure
Hardware Preparation and Installation
MVME761
Figure
MVME761 Transition Module Preparation
Figure
P2 Adapter Preparation
The P2 adapter for the MVME761 transition module routes the synchronous and asynchronous serial, parallel, and Ethernet signals to the MVME761. The P2 adapter also has a
Preparation of the P2 adapter for the MVME761 consists of installing a jumper on header J1 to enable the SCSI terminating resistors if necessary. Figure
MVME761 Transition Module Preparation
For further information on the preparation of the transition module and the P2 adapter, refer to the user???s manual for the MVME761 (listed in Appendix D, Related Documentation) as necessary.
1933 9610
Figure
P2 Adapter Preparation
The MVME761 transition module uses a
Preparation of the P2 adapter for the MVME761 consists of installing a jumper on header J5 to enable the SCSI terminating resistors if necessary. Figure
Hardware Preparation and Installation
For further information on the preparation of the transition module and the P2 adapter, refer to the user???s manual for the MVME761 (listed in Appendix D, Related Documentation) as necessary.
1999 9701
Figure
Hardware Installation
Use ESD
Wrist Strap
The following sections discuss the placement of mezzanine cards on the MVME2603/2604 base board, the installation of the complete MVME2603/2604 VME module assembly and transition module into a VME chassis, and the system considerations relevant to the installation. Before installing the MVME2603/2604, ensure that the serial ports and all header jumpers are configured as desired.
In most cases, the mezzanine
Should it be necessary to install mezzanines on the base board, refer to the following sections for a brief description of the installation procedure.
Motorola 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,
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.
RAM200 Memory Mezzanine Installation
The RAM200 DRAM mezzanine mounts on top of the MVME2603/2604 base board. To upgrade or install a RAM200 mezzanine, refer to
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
3.Carefully remove the MVME2603/2604 from its VMEbus card slot and lay it flat, with connectors P1 and P2 facing you.
4.Place the RAM200 mezzanine module on top of the base board. Connector J9 on the underside of the RAM200 should connect smoothly with the corresponding connector J7 on the MVME2603/2604.
11661.00 9611
Figure
5.Insert the four short Phillips screws through the holes at the corners of the RAM200, into the standoffs on the MVME2603/2604. Tighten the screws.
6.Reinstall the MVME2603/2604 assembly in its proper card slot. Be sure the module is well seated in the backplane connectors. Do not damage or bend connector pins.
7.Replace the chassis or system cover(s), reconnect the system to the AC or DC power source, and turn the equipment power on.
PMC Module Installation
PCI mezzanine card (PMC) modules mount beside the RAM200 mezzanine on top of the MVME2603/2604 base board. To install a PMC module, refer to Figure
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
3.Carefully remove the MVME2603/2604 from its VMEbus card slot and lay it flat, with connectors P1 and P2 facing you.
Hardware Installation
4. Remove the PCI filler from the front panel.
11661.00 9611
Figure
5.Slide the edge connector of the PMC module into the front panel opening from behind and place the PMC module on top of the base board. The four connectors on the underside of the PMC module should then connect smoothly with the corresponding connectors (J11/12/13/14) on the MVME2603/2604.
6.Insert the two short Phillips screws through the holes at the forward corners of the PMC module, into the standoffs on the MVME2603/2604. Tighten the screws.
7.Reinstall the MVME2603/2604 assembly in its proper card slot. Be sure the module is well seated in the backplane connectors. Do not damage or bend connector pins.
8.Replace the chassis or system cover(s), reconnect the system to the AC or DC power source, and turn the equipment power on.
PMC Carrier Board Installation
PCI mezzanine card (PMC) carrier boards mount above the RAM200 mezzanine and (if installed) PMC module on the MVME2603/2604 base board. To install a PMC carrier board for additional PCI expansion, refer to Figure
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
3.Carefully remove the MVME2603/2604 from its VMEbus card slot and lay it flat, with connectors P1 and P2 facing you.
4.If PMC modules are to be installed on the carrier board, install the modules at this point.
11661.00 9611
Figure
5.Remove the LED module screw located at the upper front corner of the base board. Install a short (0.394 inch) standoff in its place.
Hardware Preparation and Installation
6.At the other three corners of the base board, install long (0.737 inch) standoffs.
7.Place the PMC carrier board on top of the base board. The connector on the underside of the carrier board should connect smoothly with the corresponding connector J5 (located between P1 and P2) on the MVME2603/2604.
8.Insert the four short Phillips screws through the holes at the corners of the carrier board, into the standoffs on the MVME2603/2604. Tighten the screws.
9.Reinstall the MVME2603/2604 assembly in its proper card slot. Be sure the module is well seated in the backplane connectors. Do not damage or bend connector pins.
10.Replace the chassis or system cover(s), reconnect the system to the AC or DC power source, and turn the equipment power on.
MVME2603/2604 VME Module Installation
!
Caution
With mezzanine board(s) installed and headers properly configured, proceed as follows to install the MVME2603/2604 in the VME chassis:
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
Inserting or removing modules with power applied may result in damage to module components.
!
Warning
Dangerous voltages, capable of causing death, are present in this equipment. Use extreme caution when handling, testing, and adjusting.
3.Remove the filler panel from the card slot where you are going to install the MVME2603/2604.
???If you intend to use the MVME2603/2604 as system controller, it must occupy the
???If you do not intend to use the MVME2603/2604 as system controller, it can occupy any unused
!
Caution
4.Slide the MVME2603/2604 into the selected card slot. Be sure the module is well seated in the P1 and P2 connectors on the backplane. Do not damage or bend connector pins.
Avoid touching areas of integrated circuitry; static discharge can damage these circuits
5.Secure the MVME2603/2604 in the chassis with the screws provided, making good contact with the transverse mounting rails to minimize RF emissions.
6.On the chassis backplane, remove the INTERRUPT ACKNOWLEDGE (IACK) and BUS GRANT (BG) jumpers from the header for the card slot occupied by the MVME2603/2604.
Note Some VME backplanes (for example, those used in Motorola "Modular Chassis" systems) have an
Hardware Preparation and Installation
7.If necessary, install an MVME712M or MVME761 transition module and cable it to the MVME2603/2604 as described in the following sections of this document.
8.Replace the chassis or system cover(s), cable peripherals to the panel connectors as appropriate, reconnect the system to the AC or DC power source, and turn the equipment power on.
MVME712M Transition Module Installation
This section applies to
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
The MVME2600,
!mistakenly connected to the MVME761 transition modules instead of the
Caution correct MVME712 family of boards.
Note In models of the MVME2603/2604 that are configured for MVME712M I/O mode, the pin assignments of VMEbus connector P2 are fully compatible with other transition modules of the MVME712 series.
!
Caution
3.Remove the filler panel(s) from the appropriate card slot(s) at the front or rear of the chassis. (You may need to shift other modules in the chassis to allow space for the MVME712M, which has a double- wide front panel.)
4.Attach the P2 adapter board to the P2 backplane connector at the slot occupied by the MVME2603/2604 VME module.
5.Route the
Avoid touching areas of integrated circuitry; static discharge can damage these circuits
6.Secure the MVME712M in the chassis with the screws provided, making good contact with the transverse mounting rails to minimize RF emissions.
7.Referring to the user???s manual for the MVME712M (listed in Appendix D, Related Documentation), route the
Note The SCSI cabling can be configured in a number of ways to accommodate various device and system configurations. Figure
Hardware Preparation and Installation
8.Replace the chassis or system cover(s), making sure no cables are pinched. Cable the peripherals to the panel connectors, reconnect the system to the AC or DC power source, and turn the equipment power on.
Note Not all peripheral cables are provided with the MVME712M; you may need to fabricate or purchase certain cables. (To minimize radiation, Motorola recommends shielded cable for peripheral connections where possible.)
MVME761 Transition Module Installation
This section applies to
1.Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the chassis as a ground. The ESD strap must be secured to your wrist and to ground throughout the procedure.
2.Perform an operating system shutdown. Turn the AC or DC power off and remove the AC cord or DC power lines from the system. Remove chassis or system cover(s) as necessary for access to the VME modules.
The MVME2600,
!mistakenly connected to the MVME712 family of boards instead of the
Caution correct MVME761 transition modules.
Note In
3.Remove the filler panel(s) from the appropriate card slot(s) at the front or rear of the chassis. (You may need to shift other modules in the chassis to allow space for the cabling to the MVME761.)
Hardware Installation
4.Attach the P2 adapter board to the P2 backplane connector at the slot occupied by the MVME2603/2604 VME module.
Figure
!
Caution
5.Route the
Avoid touching areas of integrated circuitry; static discharge can damage these circuits
Hardware Preparation and Installation
6.Secure the MVME761 in the chassis with the screws provided, making good contact with the transverse mounting rails to minimize RF emissions.
Note The cabling can be configured in a number of ways to accommodate various device and system configurations.
Figure
7.Replace the chassis or system cover(s), making sure no cables are pinched. Cable the peripherals to the panel connectors, reconnect the system to the AC or DC power source, and turn the equipment power on.
Note Not all peripheral cables are provided with the MVME761; you may need to fabricate or purchase certain cables. (To minimize radiation, Motorola recommends shielded cable for peripheral connections where possible.)
System Considerations
The MVME2603/2604 draws power from VMEbus backplane connectors P1 and P2. P2 is also used for the upper 16 bits of data in
Whether the MVME2603/2604 operates as a VMEbus master or as a VMEbus slave, it is configured for 32 bits of address and 32 bits of data (A32/D32). However, it handles A16 or A24 devices in the address ranges indicated in Chapter 2, Operating Instructions. D8 and/or D16 devices in the system must be handled by the PowerPC processor software. Refer to the memory maps in Chapter 2, Operating Instructions.
System Considerations
The MVME2603/2604 contains shared onboard DRAM (and, optionally, secondary cache memory) whose base address is
MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation, for more information.
If the MVME2603/2604 tries to access offboard resources in a nonexistent location and is not system controller, and if the system does not have a global bus timeout, the MVME2603/2604 waits forever for the VMEbus cycle to complete. This will cause the system to lock up. There is only one situation in which the system might lack this global bus timeout: when the MVME2603/2604 is not the system controller and there is no global bus timeout elsewhere in the system.
Multiple MVME2603/2604s may be installed in a single VME chassis. In general, hardware multiprocessor features are supported.
Other MPUs on the VMEbus can interrupt, disable, communicate with, and determine the operational status of the processor(s). One register of the GCSR (global control/status register) set includes four bits that function as location monitors to allow one MVME2603/2604 processor to broadcast a signal to any other MVME2603/2604 processors. All eight registers are accessible from any local processor as well as from the VMEbus.
The MVME2603/2604 VME module draws +5V DC, +12V DC, and
MVME2603/2604 VME Module
The MVME2603/2604 VME module furnishes +12V DC and (in MVME761 I/O mode)
Hardware Preparation and Installation
the
In MVME712M I/O mode, the MVME2603/2604 supplies SCSI terminator power through a 1A fuse (F1) located on the P2 adapter board. If the fuse is blown, the SCSI device(s) may function erratically or not at all. With the P2 adapter board cabled to a transition module and with an SCSI bus connected to the transition module, the green SCSI LED on the module illuminates when SCSI terminator power is available. If the SCSI LED on the transition module flickers during SCSI bus operation, check fuse F1 on the P2 adapter board.
Note Because any device on the SCSI bus can provide the TERMPWR signal, and because the MVME2603/2604 FUS LED monitors the status of several voltages, the LED does not directly indicate the condition of any single fuse. If the FUS LED flickers or goes out, check all the fuses (polyswitches).
In MVME761 I/O mode, the MVME2603/2604 supplies SCSI terminator power through a polyswitch (resettable fuse) located on the P2 adapter board.
The MVME2603/2604 base board supplies a SPEAKER_OUT signal to the
On the MVME2603/2604 base board, the standard serial console port (COM1) serves as the PPCBug debugger console port. The firmware console should be set up as follows:
???Eight bits per character
???One stop bit per character
???Parity disabled (no parity)
???Baud rate of 9600 baud
System Considerations
9600 baud is the
Operating Instructions 2
Introduction
This chapter supplies information for use of the MVME2603/2604 family of Single Board Computers in a system configuration. Here you will find the
Applying Power
After you have verified that all necessary hardware preparation has been done, that all connections have been made correctly, and that the installation is complete, you can power up the system. The MPU, hardware, and firmware initialization process is performed by the PowerPC PPCBug
The firmware is shipped from the factory with an appropriate set of defaults. In most cases there is no need to modify the firmware configuration before you boot the operating system.
The following flowchart shows the basic initialization process that takes place during PowerPC system startup.
For further information on PPCBug, refer to Chapter 5, PPCBug; to Appendix C, Troubleshooting CPU Boards: Solving Startup Problems; or to the PPCBug Firmware Package User???s Manual, listed in Appendix D, Related Documentation.
Operating Instructions
STARTUP
SYSTEM
INITIALIZATION
CONSOLE
DETECTION
RUN SELFTESTS
(IF ENABLED)
AUTOBOOT
(IF ENABLED)
OPERATING
SYSTEM
11734.00 9702
Figure
The MVME2603/2604 front panel has ABORT and RESET switches and six LED
When activated by software, the ABORT switch can generate an interrupt signal from the base board to the processor at a
The interrupter connected to the ABORT switch is an
RESET Switch (S2)
The RESET switch resets all onboard devices; it also drives a SYSRESET??? signal if the MVME2603/2604 is the system controller.
The Universe ASIC includes both a global and a local reset driver. When the Universe operates as the VMEbus system controller, the reset driver provides a global system reset by asserting the VMEbus signal SYSRESET???. A SYSRESET??? signal may be generated by the RESET switch, a
Similarly, the Universe ASIC supplies an input signal and a control bit to initiate a local reset operation. By setting a control bit, software can maintain a board in a reset state, disabling a faulty board from participating in normal system operation. The local reset driver is enabled even when the Universe ASIC is not system controller. Local resets may be generated by the RESET switch, a
There are six LEDs on the MVME2603/2604 front panel: CHS, BFL, CPU,
PCI, FUS, and SYS.
??? CHS (DS1, yellow). Checkstop; driven by the MPC603/604 status lines on the MVME2603/2604. Lights when a halt condition from the processor is detected.
??? BFL (DS2, yellow). Board Failure; lights when the BRDFAIL??? signal line is active.
??? CPU (DS3, green). CPU activity; lights when the DBB??? (Data Bus Busy) signal line on the processor bus is active.
??? PCI (DS4, green). PCI activity; lights when the IRDY??? (Initiator Ready) signal line on the PCI bus is active. This indicates that the PCI mezzanine (if installed) is active.
??? FUS (DS5, green). Fuse OK; lights when +5V DC, +12V DC, and
Note Because the FUS LED monitors the status of several voltages on the MVME2603/2604, it does not directly indicate the condition of any single fuse. If the LED flickers or goes out, check all the fuses (polyswitches).
??? SYS (DS6, green). System Controller; lights when the Universe ASIC in the MVME2603/2604 is the VMEbus system controller.
Memory Maps
Memory Maps
There are three points of view for memory maps:
???The mapping of all resources as viewed by the processor (MPU bus memory map)
???The mapping of onboard resources as viewed by PCI local bus masters (PCI bus memory map)
???The mapping of onboard resources as viewed by VMEbus masters (VMEbus memory map)
The following sections give a general description of the MVME2603/2604 memory organization from the above three points of view. Detailed memory maps can be found in the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation.
Processor Memory Map
The processor memory map configuration is under the control of the Raven bridge controller ASIC and the Falcon memory controller chip set. The Raven and Falcon devices adjust system mapping to suit a given application via programmable map decoder registers. At system
Operating Instructions
Default Processor Memory Map
The default processor memory map that is valid at
Table
Notes
1.Default map for PCI/ISA I/O space. Allows software to determine whether the system is
2.The first 1MB of ROM/Flash bank A (soldered 4MB or 8MB ROM/Flash) appears in this range after a reset if the rom_b_rv control bit in the Falcon???s ROM B Base/Size register is cleared. If the rom_b_rv control bit is set, this address range maps to ROM/Flash bank B (socketed 1MB ROM/Flash).
Memory Maps
For detailed processor memory maps, including suggested CHRP- and
PCI Local Bus Memory Map
The PCI memory map is controlled by the Raven MPU/PCI bus bridge controller ASIC and by the Universe PCI/VME bus bridge ASIC. The Raven and Universe devices adjust system mapping to suit a given application via programmable map decoder registers.
No default PCI memory map exists. Resetting the system turns the PCI map decoders off, and they must be reprogrammed in software for the intended application.
For detailed PCI memory maps, including suggested CHRP- and PREP- compatible memory maps, refer to the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation.
VMEbus Memory Map
The VMEbus is programmable. Like other parts of the MVME2603/2604 memory map, the mapping of local resources as viewed by VMEbus masters varies among applications.
The Universe PCI/VME bus bridge ASIC includes a
Recommendations for VMEbus mapping, including suggested CHRP- and
Good programming practice dictates that only one MPU at a time have control of the MVME2603/2604 control registers. Of particular note are:
???Registers that modify the address map
???Registers that require two cycles to access
???VMEbus interrupt request registers
Programming Considerations
ONBOARD
MEMORY
PCI MEMORY
SPACE
PCI/ISA
MEMORY SPACE
PCI
I/O SPACE
MPC
RESOURCES
NOTE 2
NOTE 1
NOTE 3
NOTE 1
PROGRAMMABLE
SPACE
VME A24
VME A16
VME A24
VME A16
VME A24
VME A16
VME A24
VME A16
NOTES: 1. Programmable mapping done by Raven ASIC.
11553.00 9609
2.Programmable mapping performed via PCI Slave images in Universe ASIC.
3.Programmable mapping performed via Special Slave image (SLSI) in Universe ASIC.
Figure
There are seven potential PCI bus masters on the MVME2603/2604 single board computer:
???Raven ASIC (MPU/PCI bus bridge controller)
???Winbond W83C553 PIB (PCI/ISA bus bridge controller)
???DECchip 21140 Ethernet controller
???SYM53C825A SCSI controller
???Universe ASIC (PCI/VME bus bridge controller)
???PMC Slot 1 (PCI mezzanine card)
???PMC Slot 2 (PCI expansion)
The Winbond W83C553 PIB device supplies the PCI arbitration support for these seven types of devices. The PIB supports flexible arbitration modes of fixed priority, rotating priority, and mixed priority, as appropriate in a given application. Details on PCI arbitration can be found in the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation.
The arbitration assignments for the MVME2603/2604 are shown in the following table.
Table
The Raven ASIC, which controls PHB (PCI Host Bridge) MPU/local bus interface functions on the MVME2603/2604, performs interrupt handling as well. Sources of interrupts may be any of the following:
???The Raven ASIC itself (timer interrupts or transfer error interrupts)
???The processor (processor
???The Falcon chip set (memory error interrupts)
???The PCI bus (interrupts from PCI devices)
???The ISA bus (interrupts from ISA devices)
Figure
Operating Instructions
INT
INT_
SERR_& PERR_
PCI Interrupts
ISA Interrupts
11559.00 9609
Figure
The PIB supports seven DMA channels. Channels 0 through 3 support
Table
Sources of Reset
The MVME2603/2604 SBC has eight potential sources of reset:
1.
2.RESET switch (resets the VMEbus when the MVME2603/2604 is system controller)
3.Watchdog timer Reset function controlled by the
Operating Instructions
4.ALT_RST??? function controlled by the Port 92 register in the PIB (resets the VMEbus when the MVME2603/2604 is system controller)
5.PCI/ISA I/O Reset function controlled by the Clock Divisor register in the PIB
6.The VMEbus SYSRESET??? signal
7.VMEbus Reset sources from the Universe ASIC (PCI/VME bus bridge controller): the System Software reset and Local Software Reset.
The following table shows which devices are affected by the various types of resets. For details on using resets, refer to the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation.
Table
The MVME2603/2604 supports both
Processor/Memory Domain
The MPC603/604 processor can operate in both
Role of the Raven ASIC
Because the PCI bus is
In
PCI Domain
The PCI bus is inherently
Operating Instructions
PCI and SCSI
SCSI is
PCI and Ethernet
Ethernet is also
Role of the Universe ASIC
Because the PCI bus is
VMEbus Domain
The VMEbus is inherently
In
In
Functional Description 3
Introduction
This chapter describes the MVME2603/2604 single board computer on a block diagram level. The General Description provides an overview of the MVME2603/2604, followed by a detailed description of several blocks of circuitry. Figure
Detailed descriptions of other MVME2603/2604 blocks, including programmable registers in the ASICs and peripheral chips, can be found in the Programmer???s Reference Guide, listed in Appendix D, Related Documentation. Refer to it for a functional description of the MVME2603/2604 in greater depth.
Features
The following table summarizes the features of the MVME2603/2604 single board computers.
Functional Description
General Description
General Description
The MVME2603/2604 is a VME module single board computer equipped with a PowerPC Series microprocessor. The MVME2603 is equipped with a PowerPC 603 microprocessor; the MVME2604 has a PowerPC 604.
256KB L2 cache (level 2 secondary cache memory) is available as an option on all versions.
As shown in the Features section, The MVME2603/2604 offers many standard features desirable in a computer
A key feature of the MVME2603/2604 family is the PCI (Peripheral Component Interconnect) bus. In addition to the
Functional Description
Block Diagram
60X System Bus
PS/2 Floppy
Parallel
Keyboard
Mouse
Async Serial
Falcon
Dram
Falcon
ISA Local Resource Bus
FLASH
33MHz
11540.00 96111
Figure
Block Diagram
SCSI Interface
The MVME2603/2604 VME module supports mass storage subsystems through the
The MVME2603/2604 routes its SCSI lines through the P2 connector to the MVME712M transition module (as illustrated in Figure
The SCSI bus is
SCSI Termination
The individual configuring the system must ensure that the SCSI bus is properly terminated at both ends.
In MVME712M I/O mode, the MVME2603/2604 base board uses the sockets provided for SCSI bus terminators on the P2 adapter board used with the MVME712M. If the SCSI bus ends at the adapter board, termination resistors must be installed there. +5V DC power to the SCSI bus TERMPWR signal and termination resistors is supplied through a fuse located on the adapter board.
In MVME761 I/O mode, the P2 adapter board used with the MVME761 has a jumper to enable/disable SCSI bus terminators. +5V DC power for SCSI termination is supplied through a polyswitch located on the adapter board.
Functional Description
Ethernet Interface
The MVME2603/2604 VME module uses Digital Equipment???s DECchip 21140 PCI Fast Ethernet LAN controller to implement an Ethernet interface that supports both AUI (via MVME712M) and 10BaseT/100BaseTX (via MVME761) connections. The balanced differential transceiver lines are coupled via
The MVME2603/2604 routes its AUI and 10BaseT/100BaseTX lines through the P2 connector to the transition module (as illustrated in Figure
Every MVME2603/2604 is assigned an Ethernet station address. The address is $08003E2xxxxx, where xxxxx is the unique
Each MVME2603/2604 displays its Ethernet station address on a label attached to the base board in the PMC connector keepout area just behind the front panel. In addition, the six bytes including the Ethernet station address are stored in an SROM off the DECchip Ethernet controller, that is, the value 08003E2xxxxx is stored in SROM. At an offset of $1F2C, the upper four bytes (08003E2x) can be read. At an offset of $1F30, the lower two bytes (xxxx) can be read. The MVME2603/2604 debugger, PPCBug, has the capability to retrieve or set the Ethernet station address via the CNFG command.
Note The unique Ethernet address is set at the factory and should not be changed. Any attempt to change this address may create node or bus contention and thereby render the board inoperable.
If the data in SROM is lost, use the number on the label in the PMC connector keepout area to restore it.
For the pin assignments of the transition module AUI or 10BaseT/100BaseTX connector, refer to the user???s manual for the MVME712M or MVME761 (listed in Appendix D, Related Documentation) respectively. Refer to the BBRAM/TOD Clock memory
Block Diagram
map description in the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation, for detailed programming information.
3
PCI Mezzanine Interface
A key feature of the MVME2603/2604 family is the PCI (Peripheral Component Interconnect) bus. In addition to the
PMC modules offer a variety of possibilities for I/O expansion through FDDI (Fiber Distributed Data Interface), ATM (Asynchronous Transfer Mode), graphics, Ethernet, or SCSI ports. The base board supports PMC front panel and rear P2 I/O. There is also provision for stacking a PMC carrier board on the base board for additional expansion.
The MVME2603/2604 supports one PMC slot. Four
Mezzanine Type PMC (PCI Mezzanine Card)
Mezzanine Size S1B: Single width, standard depth (75mm x 150mm) with front panel
PMC Connectors J11 and J12
The PMC carrier board connector (J5) is a
Refer to Chapter 4, Connector Pin Assignments for the pin assignments of the PMC connectors. For detailed programming information, refer to the PCI bus descriptions in the MVME2603/2604 Programmer???s Reference Guide, listed in Appendix D, Related Documentation, and to the user documentation for the PMC modules you intend to use.
Functional Description
VMEbus Interface
The VMEbus interface is implemented with the CA91C042 Universe ASIC. The Universe chip interfaces the
The Universe ASIC provides:
???The
???The
???The DMA controller functions of the local VMEbus
The Universe chip includes Universe Control and Status Registers (UCSRs) for interprocessor communications. It can provide the VMEbus system controller functions as well. For detailed programming information, refer to the Universe User???s Manual and to the discussions in the MVME2603/2604 Programmer's Reference Guide,listed in Appendix D, Related Documentation.
ISA Super I/O Device (ISASIO)
The MVME2603/2604 uses a PC87308 ISASIO chip from National Semiconductor to implement certain segments of the P2 and
???Two asynchronous serial ports (COM1 and COM2) via P2 and transition module
???Parallel port via P2 and transition module:
???Centronics printer port in
???IEEE1284 bidirectional parallel port in
???Floppy disk drive support via drive/power connector J4
???Keyboard and mouse interface via circular DIN connectors J6 and J8
Block Diagram
Asynchronous Serial Ports
The two asynchronous ports provided by the ISASIO device employ
Hardware initializes the two serial ports as COM1 and COM2 with ISA I/O base addresses of $3F8 and $2F8 respectively. This default configuration also assigns COM1 to PIB (PCI/ISA Bridge Controller) interrupt request line IRQ4 and COM2 to IRQ3. You can change the default configuration by reprogramming the ISASIO device. For detailed programming information, refer to the PCI and ISA bus discussions in the MVME2603/2604 Programmer???s Reference Guide, listed in Appendix D, Related Documentation, and to the vendor documentation for the ISASIO device.
Parallel Port
The parallel port is a Centronics printer interface in MVME712M- compatible models, and a full IEEE1284 bidirectional parallel port in
Hardware initializes the parallel port as PPT1 with an ISA IO base address of $3BC. This default configuration also assigns the parallel port to PIB (PCI/ISA Bridge Controller) interrupt request line IRQ7. You can change the default configuration by reprogramming the ISASIO device. For detailed programming information, refer to the PCI and ISA bus discussions in the MVME2603/2604 Programmer???s Reference Guide, listed in Appendix D, Related Documentation, and to the vendor documentation for the ISASIO device.
Functional Description
Disk Drive Controller
The ISASIO device incorporates a
The ISASIO disk drive controller is compatible with the DP8473, 765A, and N82077 devices commonly used to implement floppy disk controllers. Software written for those devices may be used without change to operate the ISASIO controller. The ISASIO device may be used to support any of the following devices:
???
???
???Standard 250kbps to 2Mbps tape drive system
Keyboard and Mouse Interface
The National Semiconductor PC87308 ISASIO chip used to implement certain segments of the P2 and
The MVME2603/2604 uses a Winbond W83C553 bridge controller to supply the interface between the PCI local bus and the ISA system I/O bus (diagrammed in Figure
Block Diagram
The PIB controller provides the following functions:
???PCI bus arbitration for:
???ISA (Industry Standard Architecture) bus DMA
???The PHB (PCI Host Bridge) MPU/local bus interface function, implemented by the Raven ASIC
???All
???The PMC (PCI Mezzanine Card) slot
???ISA (Industry Standard Architecture) bus arbitration for DMA devices
???ISA interrupt mapping for four PCI interrupts
???Interrupt controller functionality to support 14 ISA interrupts
???Edge/level control for ISA interrupts
???Seven independently programmable DMA channels
???One
???Three interval counters/timers
Accesses to the configuration space for the PIB (PCI/ISA Bridge) controller are performed by way of the CONADD and CONDAT (Configuration Address and Data) registers in the Raven bridge controller ASIC. The registers are located at offsets $CF8 and $CFC, respectively, from the PCI I/O base address.
The MVME2603/2604 employs an
Functional Description
???A
???A SNAPHAT?? battery housing a crystal along with the battery
The SNAPHAT battery package is mounted on top of the M48T59/T559 device. The battery housing is keyed to prevent reverse insertion.
The clock furnishes seconds, minutes, hours, day, date, month, and year in BCD
Programmable Timers
Among the resources available to the local processor are a number of programmable timers. Timers are incorporated into the PIB controller and the Z8536 CIO device (diagrammed in Figure
Interval Timers
The
???Counter 0 is associated with interrupt request line IRQ0. It can be used for system timing functions, such as a timer interrupt for a
???Counter 1 generates a refresh request signal for ISA memory. This timer is not used in the MVME2603/2604.
Block Diagram
???Counter 2 provides the tone for the speaker output function on the PIB controller (the SPEAKER_OUT signal which can be cabled to an external speaker via the remote reset connector).
The interval timers use the OSC clock input as their clock source. The MVME2603/2604 drives the OSC pin with a 14.31818 MHz clock source.
Four
Serial Communications Interface
The MVME2603/2604 uses a Zilog Z85230 ESCC (Enhanced Serial Communications Controller) to implement the two serial communications interfaces, which are routed through P2. The Z85230 supports synchronous (SDLC/HDLC) and asynchronous protocols. The MVME2603/2604 hardware supports asynchronous serial baud rates of 110B/s to 38.4KB/s.
Each interface supports the CTS, DCD, RTS, and DTR control signals as well as the TxD and RxD transmit/receive data signals, and TxC/RxC synchronous clock signals. Since not all modem control lines are available in the Z85230, a Z8536 CIO is used to provide the missing modem lines.
A PAL device performs decoding of register accesses and pseudo interrupt acknowledge cycles for the Z85230 and the Z8536 in ISA I/O space. The PIB controller supplies DMA support for the Z85230.
The Z85230 receives a 10MHz clock input. The Z85230 supplies an interrupt vector during pseudo interrupt acknowledge cycles. The vector is modified within the Z85230 according to the interrupt source. Interrupt request levels are programmed via the PIB controller. Refer to the Z85230 data sheet and to the MVME2603/ MVME2604 Programmer???s Reference Guide, both listed in Appendix D, Related Documentation, for further information.
Functional Description
Z8536 CIO Device
The Z8536 CIO device complements the Z85230 ESCC by supplying modem control lines not provided by the Z85230 ESCC. In addition, the Z8536 CIO device has three independent
Base Module Feature Register
The Base Module Feature Register contains the details of the MVME2603/2604 single board computer???s configuration. It is an
Base Module Feature Register ??? Offset $0802
SCCP??? Z85230 ESCC present. If set, there is no
PMC2P??? PMC/PMCIX slot 2 present. If set, no PCI mezzanine card (or PCI expansion device) is installed in PMC slot 2. If cleared, PMC/PMCIX slot 2 contains a PCI mezzanine card (or PCI expansion device).
PMC1P??? PMC slot 1 present. If set, no PCI mezzanine card is installed in PMC slot 1. If cleared, PMC slot 1 contains a PCI mezzanine card.
VMEP??? VMEbus present. If set, there is no VMEbus interface. If cleared, the VMEbus interface is supported.
LANP??? Ethernet present. If set, no Ethernet transceiver interface is installed. If cleared, there is
Block Diagram
SCSIP??? SCSI present. If set, there is no
Due to the limited supply of available pins in the P2 backplane connectors of MVME2603/2604 models that are configured for MVME761 I/O mode, certain signals are multiplexed through VMEbus connector P2 for additional I/O capacity.
The signals affected are synchronous I/O control signals that pass between the base board and the MVME761 transition module. The multiplexing is a hardware function that is entirely transparent to software.
Four signals are involved in the P2 multiplexing function: MXDO, MXDI,
MXCLK, and MXSYNC???.
MXDO is a
A
Table
Functional Description
Table
ABORT Switch (S1)
The ABORT switch is located on the LED mezzanine. When activated by software, the ABORT switch can generate an interrupt signal from the base board to the processor. The interrupt is normally used to abort program execution and return control to the debugger firmware located in the MVME2603/2604 EPROM and Flash memory. The interrupt signal reaches the processor module via ISA bus interrupt line IRQ8???. The signal is also available at pin PB7 of the Z8536 CIO device, which handles various status signals, serial I/O lines, and counters.
The interrupter connected to the ABORT switch is an
RESET Switch (S2)
The RESET switch is located on the LED mezzanine. The RESET switch resets all onboard devices; it also drives a SYSRESET??? signal if the MVME2603/2604 is the system controller.
Block Diagram
Front Panel Indicators (DS1 ??? DS6)
There are six LEDs on the MVME2603/2604 front panel: CHS, BFL, CPU,
PCI, FUS, and SYS.
??? CHS (DS1, yellow). Checkstop; driven by the MPC603/604 status lines on the MVME2603/2604. Lights when a halt condition from the processor is detected.
??? BFL (DS2, yellow). Board Failure; lights when the BRDFAIL??? signal line is active.
??? CPU (DS3, green). CPU activity; lights when the DBB??? (Data Bus Busy) signal line on the processor bus is active.
??? PCI (DS4, green). PCI activity; lights when the IRDY??? (Initiator Ready) signal line on the PCI bus is active. This indicates that the PCI mezzanine or carrier board (if installed) is active.
??? FUS (DS5, green). Fuse OK; lights when +5V DC, +12V DC, and
Note Because the FUS LED monitors the status of several voltages on the MVME2603/2604, it does not directly indicate the condition of any single fuse. If the LED flickers or goes out, check all the fuses (polyswitches).
??? SYS (DS6, green). System Controller; lights when the Universe ASIC in the MVME2603/2604 is the VMEbus system controller.
Functional Description
Polyswitches (Resettable Fuses)
The MVME2603/2604 base board draws fused +5V DC, +12V DC, and
Table
I/O Power
The MVME2603/2604 base board furnishes +12V DC and (in MVME761 I/O mode)
In MVME712M I/O mode, the yellow DS1 LED on the MVME712M also signals the availability of +12V DC LAN power, indicating in turn that polyswitch R34 is good. If the Ethernet transceiver fails to operate, check polyswitch R34.
In MVME712M I/O mode, the MVME2603/2604 supplies SCSI terminator power through a 1A fuse (F1) located on the P2 adapter board. If the fuse is blown, the SCSI device(s) may function erratically or not at all. With the P2 adapter board cabled to a transition module and with an SCSI bus connected to the transition module, the green SCSI LED on the
Block Diagram
module illuminates when SCSI terminator power is available. If the SCSI LED on the transition module flickers during SCSI bus operation, check fuse F1 on the P2 adapter board.
Note Because any device on the SCSI bus can provide TERMPWR, and because the FUS LED monitors the status of several voltages, the LED does not directly indicate the condition of any single fuse. If the LED flickers or goes out, check all the fuses (polyswitches).
In MVME761 I/O mode, the MVME2603/2604 supplies SCSI terminator power through a polyswitch (resettable fuse) located on the P2 adapter board.
Speaker Control
The MVME2603/2604 base board supplies a SPEAKER_OUT signal to the
PM603/604 Processor
At present, you have the choice of a PowerPC 603 or a PowerPC 604 processor chip with 16MB to 256MB of ECC DRAM, 256KB of level 2 cache (L2 cache), and up to 9MB of Flash memory. The L2 cache and 1MB of
The PowerPC 603 is a
Functional Description
The Raven bridge controller ASIC provides the bridge between the PowerPC microprocessor bus and the PCI local bus. Electrically, the Raven chip is a
Flash Memory
The MVME2603/2604 base board has provision for 1MB of
The onboard monitor/debugger, PPCBug, resides in the Flash chips. PPCBug provides functionality for:
???Booting the operating system
???Initializing after a reset
???Displaying and modifying configuration variables
???Running
???Updating firmware ROM
Under normal operation, the Flash devices are in
RAM200 Memory Module
The RAM200 is the ECC DRAM memory mezzanine module that (together with an LED mezzanine and an optional PCI mezzanine card) plugs into the base board to make a complete MVME2603 or MVME2604 single board computer. See Figure
Block Diagram
RAM200 modules of 16, 32, 64, 128, or 256MB are available for memory expansion. The ECC DRAM is controlled by the Falcon memory controller chip set. The Falcon ASICs perform
In addition to the ECC DRAM, the RAM200 module supplies 4MB or 8MB of additional
MVME712M Transition Module
The MVME712M transition module (Figure
The features of the MVME712M include:
???A parallel printer port (via P2 adapter)
???An Ethernet interface supporting AUI connections (via P2 adapter)
???Four
???An SCSI interface (via P2 adapter) for connection to both internal and external devices
???
???Provision for modem connection
???Green LED for SCSI terminator power; yellow LED for Ethernet transceiver power
The features of the P2 adapter board include:
???A
???
Functional Description
???Fused SCSI terminator power developed from the +5V DC present at connector P2
???A
MVME761 Transition Module
The MVME761 transition module (Figure
The features of the MVME761 include:
???A parallel printer port (IEEE
???An Ethernet interface supporting 10BaseT/100BaseTX connections
???Two
???Two synchronous serial ports (SERIAL 3 and SERIAL 4 on the front panel), configurable for
???Two
Serial Interface Modules
The synchronous serial ports on the MVME761 are configurable via serial interface modules (SIMs), used in conjunction with the appropriate jumper settings on the transition module and base board. The SIMs are small plug- in printed circuit boards which contain all the circuitry needed to convert
Block Diagram
a
Table
For additional information about the serial interface modules, refer to the MVME761 User???s Manual (listed in Appendix D, Related Documentation) as necessary.
Connector Pin Assignments 4
MVME2603/2604 Connectors
This chapter summarizes the pin assignments for the following groups of interconnect signals for the MVME2603/2604:
???Connectors with pin assignments common to MVME712M, as well as
Connector
LED Mezzanine Connector J1 on page
Debug Connector J2 on page
Floppy/LED Connector J4 on page
PCI Expansion Connector J5 on page
Keyboard and Mouse Connectors J6, J8 on page
DRAM Mezzanine Connector J7 on page
PCI Mezzanine Card Connectors on page
VMEbus Connector P1 on page
???Connectors with pin assignments specific to MVME712M- compatible versions of the base board
Connector
VMEbus Connector P2 on page
Connector Pin Assignments
???Connectors with pin assignments specific to MVME761- compatible versions of the base board
Connector
VMEbus Connector P2 on page
Serial Ports 1 and 2 on page
Serial Ports 3 and 4 on page
Parallel Connector on page
Ethernet 10BaseT/100BaseTX Connector on page
The following tables furnish pin assignments only. For detailed descriptions of the various interconnect signals, consult the support information documentation package for the MVME2603/2604 single board computer or the support information sections of the transition module documentation as necessary.
Common Connectors
Common Connectors
The following tables describe connectors used with the same pin assignments by MVME712M, as well as
A
Removing the LED mezzanine makes the mezzanine connector available for service as a remote status and control connector. In this application, J1 can be connected to a
Table
Connector Pin Assignments
Debug Connector J2
A
Table
Common Connectors
Table
Connector Pin Assignments
Table
Common Connectors
Table
Floppy/LED Connector J4
A
Table
Connector Pin Assignments
Table
PCI Expansion Connector J5
The MVME2603/2604 has provision for stacking a PMC carrier board on the base board for additional PCI expansion. A
Table
Common Connectors
Table
Connector Pin Assignments
Table
Common Connectors
Keyboard and Mouse Connectors J6, J8
The MVME2603/2604 has two
Table
Table
Connector Pin Assignments
DRAM Mezzanine Connector J7
A
Table
Common Connectors
Table
Connector Pin Assignments
Table
Common Connectors
Table
PCI Mezzanine Card Connectors
Four
Table
Connector Pin Assignments
Table
Table
Common Connectors
Table
Connector Pin Assignments
VMEbus Connector P1
Two
Table
Table
The following tables summarize the pin assignments of connectors that are specific to MVME2603/2604 modules configured for use with MVME712M transition modules.
VMEbus Connector P2
Two
Table
Connector Pin Assignments
Table
SCSI Connector
The SCSI connector for the MVME2603/2604 is a
Table
Connector Pin Assignments
Serial Ports
For the MVME2603/2604, the interface for asynchronous ports 1 and 2 and for synchronous/asynchronous ports 3 and 4 is implemented with four
Table
Table
22No Connection
23No Connection
24ETTxC (Port 4 only)
25No Connection
Parallel Connector
Both versions of the base board provide parallel I/O connections. For
Table
Connector Pin Assignments
Table
Ethernet AUI Connector
The MVME2603/2604 provides both AUI and 10BaseT/100BaseTX LAN connections. For
Table
The following tables summarize the pin assignments of connectors that are specific to MVME2603/2604 modules configured for use with MVME761 transition modules.
Two
Table
Connector Pin Assignments
Table
Serial Ports 1 and 2
The MVME2603/2604 provides both asynchronous (ports 1 and 2) and synchronous/asynchronous (ports 3 and 4) serial connections. For the
Table
Table
6 SPnDSR
7 SPnRTS
8 SPnCTS
9 SPnRI
Serial Ports 3 and 4
For
Table
Connector Pin Assignments
Table
Parallel Connector
Both versions of the base board provide parallel I/O connections. For
Table
Table
Ethernet 10BaseT/100BaseTX Connector
The MVME2603/2604 provides both AUI and 10BaseT/100BaseTX LAN connections. For
Table
For detailed descriptions of the various interconnect signals, consult the support information documentation package for the MVME2603/2604 SBC or the support information sections of the transition module documentation as necessary.
PPCBug 5
Overview
The PowerPC debugger, PPCBug, is a powerful evaluation and debugging tool for systems built around Motorola PowerPC microcomputers. Facilities are available for loading and executing user programs under complete operator control for system evaluation.
The PowerPC debugger provides a high degree of functionality and user friendliness, and yet stresses portability and ease of maintenance. It achieves good portability and comprehensibility because it was written entirely in the C programming language, except where necessary to use assembler functions.
PPCBug includes commands for display and modification of memory, breakpoint and tracing capabilities, a powerful assembler and disassembler useful for patching programs, and a
Various PPCBug routines that handle I/O, data conversion, and string functions are available to user programs through the System Call handler.
PPCBug consists of three parts:
???A
???A set of
???A user interface which accepts commands from the system console terminal.
When using PPCBug, you will operate out of either the debugger directory or the diagnostic directory. The debugger prompt
PPCBug
Because PPCBug is
The PPCBug is similar to previous Motorola firmware debugging packages (for example, MVME147Bug, MVME167Bug, MVME187Bug), with differences due to microprocessor architectures. These are primarily reflected in the instruction mnemonics, register displays, addressing modes of the assembler/disassembler, and the passing of arguments to the system calls.
Memory Requirements
PPCBug requires a maximum of 768KB (maybe less) of read/write memory (that is, DRAM). The debugger allocates this space from the top of memory. For example, a system containing 64MB ($04000000) of read/write memory will place the PPCBug memory page at locations $03F80000 to $03FFFFFF.
PPCBug Implementation
PPCBug is written largely in the C programming language, providing benefits of portability and maintainability. Where necessary, assembly language has been used in the form of separately compiled program modules containing only assembler code. No
Physically, PPCBug is contained in two socketed
Using the Debugger
Using the Debugger
PPCBug is
What you key in is stored in an internal buffer. Execution begins only after you press the Return or Enter key. This allows you to correct entry errors, if necessary, with the control characters described in the PPCBug Firmware Package User???s Manual.
After the debugger executes the command, the prompt reappears. However, if the command causes execution of user target code (for example, GO) then control may or may not return to the debugger, depending on what the user program does. For example, if a breakpoint has been specified, then control returns to the debugger when the breakpoint is encountered during execution of the user program. Alternately, the user program could return to the debugger by means of the System Call Handler routine RETURN (described in the PPCBug Firmware Package User???s Manual). For more about this, refer to the GD, GO, and GT command descriptions in the PPCBug Firmware Package User???s Manual .
A debugger command is made up of the following parts:
???The command name, either uppercase or lowercase (for example,
MD or md).
???Any required arguments, as specified by command.
???At least one space before the first argument. Precede all other arguments with either a space or comma.
???One or more options. Precede an option or a string of options with a semicolon (;). If no option is entered, the command???s default option conditions are used.
PPCBug
Debugger Commands
The individual debugger commands are listed in Table
Note You can list all the available debugger commands by entering the Help (HE) command alone. You can view the syntax for a particular command by entering HE and the command mnemonic, as listed below.
Table
Using the Debugger
Table
PPCBug
Table
Using the Debugger
Table
Although a command (PFLASH) to allow the erasing and reprogramming
!of Flash memory is available to you, keep in mind that reprogramming any
Caution portion of Flash memory will erase everything currently contained in Flash, including the PPCBug debugger.
Note Both banks A and B of Flash contain the PPCBug debugger.
PPCBug
Diagnostic Tests
The individual diagnostic test sets are listed in the following table. The diagnostics are described in the PPC1Bug Diagnostics Manual, listed in Appendix D, Related Documentation.
Table
Notes
1.Some diagnostics depend on restart defaults that are set up only in a particular restart mode. Refer to the documentation on a particular diagnostic for the correct mode.
2.Test Sets marked with an asterisk (*) are not available on PPCBug release 3.1 and earlier.
CNFG and ENV Commands 6
Overview
You can use the
???The Board Information Block in NVRAM contains various elements concerning operating parameters of the hardware. Use the PPCBug command CNFG to change those parameters.
???Use the PPCBug command ENV to change configurable PPCBug parameters in NVRAM.
The CNFG and ENV commands are both described in the PPCBug Firmware Package User???s Manual, listed in Appendix D, Related Documentation. Refer to that manual for general information about their use and capabilities.
The following paragraphs present additional information about CNFG and ENV that is specific to the PPCBug debugger, along with the parameters that can be configured with the ENV command.
CNFG and ENV Commands
CNFG ??? Configure Board Information Block
Use this command to display and configure the Board Information Block, which is resident within the NVRAM. The board information block contains various elements detailing specific operational parameters of the PowerPC board. The board structure for the PowerPC board is as shown in the following example for an MVME2600:
The parameters that are quoted are
The Board Information Block is
Refer to the Programmer???s Reference Guide, listed in Appendix D, Related Documentation, for the actual location and other information about the Board Information Block.
Refer to the PPCBug Firmware Package User's Manual for a description of CNFG and examples.
ENV ??? Set Environment
ENV ??? Set Environment
Use the ENV command to view and/or configure interactively all PPCBug operational parameters that are kept in
Refer to the PPCBug Firmware Package User???s Manual for a description of the use of ENV. Additional information on registers in the Universe ASIC that affect these parameters is contained in your PowerPC board programmer???s reference guide.
Listed and described below are the parameters that you can configure using ENV. The default values shown were those in effect when this publication went to print.
Configuring the PPCBug Parameters
The parameters that can be configured using ENV are:
Bug or System environment [B/S] = B?
BBug is the mode where no system type of support is displayed. However,
SSystem is the standard mode of operation, and is the default mode if NVRAM should fail. System mode is defined in the PPCBug Firmware Package User???s Manual.
Field Service Menu Enable [Y/N] = N?
CNFG and ENV Commands
Remote Start Method Switch [G/M/B/N] = B?
The Remote Start Method Switch is used when the MVME2600/MVME3600/MVME4600 is
GUse the Global Control and Status Register to pass and start execution of the
MUse the Multiprocessor Control Register (MPCR) in shared RAM to pass and start execution of the cross- loaded program.
BUse both the GCSR and the MPCR methods to pass and start execution of the
N Do not use any Remote Start Method.
Probe System for Supported I/O Controllers [Y/N] = Y?
YAccesses will be made to the appropriate system buses (for example, VMEbus, local MPU bus) to determine the presence of supported controllers. (Default)
NAccesses will not be made to the VMEbus to determine the presence of supported controllers.
YNVRAM (PReP partition) header space will be initialized automatically during board initialization, but only if the PReP partition fails a sanity check. (Default)
NNVRAM header space will not be initialized automatically during board initialization.
ENV ??? Set Environment
Network
YEnable
Negate VMEbus SYSFAIL* Always [Y/N] = N?
YNegate the VMEbus SYSFAIL??? signal during board initialization.
NNegate the VMEbus SYSFAIL??? signal after successful completion or entrance into the bug command monitor. (Default)
Local SCSI Bus Reset on Debugger Startup [Y/N] = N?
NLocal SCSI bus is not reset on debugger setup. (Default)
Local SCSI Bus Negotiations Type [A/S/N] = A?
Local SCSI Data Bus Width [W/N] = N?
CNFG and ENV Commands
NVRAM Bootlist
YGive boot priority to devices defined in the
NDo not give boot priority to devices listed in the fw-
Note When enabled, the GEV (Global Environment Variable) boot takes priority over all other boots, including Autoboot and Network Boot.
NVRAM Bootlist
YGive boot priority to devices defined in the
NGive
NVRAM Bootlist
The time in seconds that a boot from the NVRAM boot list will delay before starting the boot. The purpose for the delay is to allow you the option of stopping the boot by use of the <Break> key. The time value is from
Auto Boot Enable [Y/N] = N?
Auto Boot at
ENV ??? Set Environment
Auto Boot Scan Enable [Y/N] = Y?
YIf Autoboot is enabled, the Autoboot process attempts to boot from devices specified in the scan list (for example, FDISK/CDROM/TAPE/HDISK). (Default)
NIf Autoboot is enabled, the Autoboot process uses the Controller LUN and Device LUN to boot.
Auto Boot Scan Device Type List = FDISK/CDROM/TAPE/HDISK?
This is the listing of boot devices displayed if the Autoboot Scan option is enabled. If you modify the list, follow the format shown above (uppercase letters, using forward slash as separator).
Auto Boot Controller LUN = 00?
Refer to the PPCBug Firmware Package User???s Manual for a listing of disk/tape controller modules currently supported by PPCBug. (Default = $00)
Refer to the PPCBug Firmware Package User???s Manual for a listing of disk/tape devices currently supported by PPCBug.
(Default = $00)
Auto Boot Partition Number = 00?
Which disk ???partition??? is to be booted, as specified in the PowerPC Reference Platform (PReP) specification. If set to zero, the firmware will search the partitions in order (1, 2, 3, 4) until it finds the first ???bootable??? partition. That is then the partition that will be booted. Other acceptable values are 1, 2, 3, or 4. In these four cases, the partition specified will be booted without searching.
CNFG and ENV Commands
Auto Boot Abort Delay = 7?
The time in seconds that the Autoboot sequence will delay before starting the boot. The purpose for the delay is to allow you the option of stopping the boot by use of the <Break> key. The time value is from
Auto Boot Default String [NULL for an empty string] = ?
You may specify a string (filename) which is passed on to the code being booted. The maximum length of this string is 16 characters. (Default = null string)
ROM Boot Enable [Y/N] = N?
Y The ROMboot function is enabled.
N The ROMboot function is disabled. (Default)
ROM Boot at
ROM Boot Enable search of VMEbus [Y/N] = N?
YVMEbus address space, in addition to the usual areas of memory, will be searched for a ROMboot module.
NVMEbus address space will not be accessed by ROMboot. (Default)
ROM Boot Abort Delay = 5?
The time in seconds that the ROMboot sequence will delay before starting the boot. The purpose for the delay is to allow you the option of stopping the boot by use of the <Break> key. The time value is from
ROM Boot Direct Starting Address = FFF00000?
The first location tested when PPCBug searches for a ROMboot module. (Default = $FFF00000)
ENV ??? Set Environment
ROM Boot Direct Ending Address = FFFFFFFC?
The last location tested when PPCBug searches for a ROMboot module. (Default = $FFFFFFFC)
Network Auto Boot Enable [Y/N] = N?
YThe Network Auto Boot (NETboot) function is enabled.
Network Auto Boot at
Network Auto Boot Controller LUN = 00?
Refer to the PPCBug Firmware Package User???s Manual for a listing of network controller modules currently supported by PPCBug. (Default = $00)
Network Auto Boot Device LUN = 00?
Refer to the PPCBug Firmware Package User???s Manual for a listing of network controller modules currently supported by PPCBug. (Default = $00)
Network Auto Boot Abort Delay = 5?
The time in seconds that the NETboot sequence will delay before starting the boot. The purpose for the delay is to allow you the option of stopping the boot by use of the <Break> key. The time value is from
Network Auto Boot Configuration Parameters Offset (NVRAM) = 00001000?
The address where the network interface configuration parameters are to be saved/retained in NVRAM; these parameters are the necessary parameters to perform an unattended network boot. A typical offset might be $1000, but this value is
(Default = $00001000)
CNFG and ENV Commands
If you use the NIOT debugger command, these parameters need to be
!saved somewhere in the offset range $00001000 through $000016F7. The
Caution NIOT parameters do not exceed 128 bytes in size. The setting of this ENV pointer determines their location. If you have used the same space for your
own program information or commands, they will be overwritten and lost.
You can relocate the network interface configuration parameters in this space by using the ENV command to change the Network Auto Boot Configuration Parameters Offset from its default of $00001000 to the value you need to be clear of your data within NVRAM.
Memory Size Enable [Y/N] = Y?
YMemory will be sized for Self Test diagnostics. (Default)
Memory Size Starting Address = 00000000?
The default Starting Address is $00000000.
Memory Size Ending Address = 02000000?
The default Ending Address is the calculated size of local memory. If the memory start is changed from $00000000, this value will also need to be adjusted.
DRAM Speed in NANO Seconds = 60?
The default setting for this parameter will vary depending on the speed of the DRAM memory parts installed on the board. The default is set to the slowest speed found on the available banks of DRAM memory.
ROM First Access Length (0 - 31) = 10?
This is the value programmed into the MPC105 ???ROMFAL??? field (Memory Control Configuration Register 8: bits
ENV ??? Set Environment
Processor/Memory Mezzanine Module User???s Manual, listed in Appendix D, Related Documentation, for appropriate values. The default value varies according to the system???s bus clock speed.
Note ROM First Access Length is not applicable to the MVME2600/3600/4600. The configured value is ignored by PPCBug.
ROM Next Access Length (0 - 15) = 0?
The value programmed into the MPC105 ???ROMNAL??? field (Memory Control Configuration Register 8: bits
Processor/Memory Mezzanine Module User???s Manual for appropriate values. The default value varies according to the system???s bus clock speed.
Note ROM Next Access Length is not applicable to the MVME2600/MVME3600/MVME4600. The configured value is ignored by PPCBug.
DRAM Parity Enable
Note This parameter (above) also applies to enabling ECC for DRAM.
CNFG and ENV Commands
L2 Cache Parity Enable
PCI Interrupts Route Control Registers (PIRQ0/1/2/3) = 0A0B0E0F?
Initializes the PIRQx (PCI Interrupts) route control registers in the IBC (PCI/ISA bus bridge controller). The ENV parameter is a
MVME2600 Programmer???s Reference Guide, listed in Appendix D, Related Documentation.
Configuring the VMEbus Interface
ENV asks the following series of questions to set up the VMEbus interface for the MVME2300/MVME2600/MVME3600 /MVME4600 series modules. To perform this configuration, you should have a working knowledge of the Universe ASIC as described in the Programmer???s Reference Guide.
VME3PCI Master Master Enable [Y/N] = Y?
PCI Slave Image 0 Control = 00000000?
The configured value is written into the LSI0_CTL register of the
Universe chip.
PCI Slave Image 0 Base Address Register = 00000000?
The configured value is written into the LSI0_BS register of the
Universe chip.
ENV ??? Set Environment
PCI Slave Image 0 Bound Address Register = 00000000?
The configured value is written into the LSI0_BD register of the Universe chip.
PCI Slave Image 0 Translation Offset = 00000000?
The configured value is written into the LSI0_TO register of the Universe chip.
PCI Slave Image 1 Control = C0820000?
The configured value is written into the LSI1_CTL register of the Universe chip.
PCI Slave Image 1 Base Address Register = 01000000?
The configured value is written into the LSI1_BS register of the Universe chip.
PCI Slave Image 1 Bound Address Register = 20000000?
The configured value is written into the LSI1_BD register of the Universe chip.
PCI Slave Image 1 Translation Offset = 00000000?
The configured value is written into the LSI1_TO register of the Universe chip.
PCI Slave Image 2 Control = C0410000?
The configured value is written into the LSI2_CTL register of the Universe chip.
PCI Slave Image 2 Base Address Register = 20000000?
The configured value is written into the LSI2_BS register of the Universe chip.
PCI Slave Image 2 Bound Address Register = 22000000?
The configured value is written into the LSI2_BD register of the Universe chip.
PCI Slave Image 2 Translation Offset = D0000000?
The configured value is written into the LSI2_TO register of the Universe chip.
CNFG and ENV Commands
PCI Slave Image 3 Control = C0400000?
The configured value is written into the LSI3_CTL register of the
Universe chip.
PCI Slave Image 3 Base Address Register = 2FFF0000?
The configured value is written into the LSI3_BS register of the
Universe chip.
PCI Slave Image 3 Bound Address Register = 30000000?
The configured value is written into the LSI3_BD register of the
Universe chip.
PCI Slave Image 3 Translation Offset = D0000000?
The configured value is written into the LSI3_TO register of the
Universe chip.
VMEbus Slave Image 0 Control = E0F20000?
The configured value is written into the VSI0_CTL register of the
Universe chip.
VMEbus Slave Image 0 Base Address Register = 00000000?
The configured value is written into the VSI0_BS register of the
Universe chip.
VMEbus Slave Image 0 Bound Address Register = (Local DRAM Size)?
The configured value is written into the VSI0_BD register of the Universe chip. The value is the same as the Local Memory Found number already displayed.
VMEbus Slave Image 0 Translation Offset = 80000000?
The configured value is written into the VSI0_TO register of the
Universe chip.
VMEbus Slave Image 1 Control = 00000000?
The configured value is written into the VSI1_CTL register of the
Universe chip.
ENV ??? Set Environment
VMEbus Slave Image 1 Base Address Register = 00000000?
The configured value is written into the VSI1_BS register of the Universe chip.
VMEbus Slave Image 1 Bound Address Register = 00000000?
The configured value is written into the VSI1_BD register of the Universe chip.
VMEbus Slave Image 1 Translation Offset = 00000000?
The configured value is written into the VSI1_TO register of the Universe chip.
VMEbus Slave Image 2 Control = 00000000?
The configured value is written into the VSI2_CTL register of the Universe chip.
VMEbus Slave Image 2 Base Address Register = 00000000?
The configured value is written into the VSI2_BS register of the Universe chip.
VMEbus Slave Image 2 Bound Address Register = 00000000?
The configured value is written into the VSI2_BD register of the Universe chip.
VMEbus Slave Image 2 Translation Offset = 00000000?
The configured value is written into the VSI2_TO register of the Universe chip.
VMEbus Slave Image 3 Control = 00000000?
The configured value is written into the VSI3_CTL register of the Universe chip.
VMEbus Slave Image 3 Base Address Register = 00000000?
The configured value is written into the VSI3_BS register of the Universe chip.
VMEbus Slave Image 3 Bound Address Register = 00000000?
The configured value is written into the VSI3_BD register of the Universe chip.
CNFG and ENV Commands
VMEbus Slave Image 3 Translation Offset = 00000000?
The configured value is written into the VSI3_TO register of the
Universe chip.
PCI Miscellaneous Register = 10000000?
The configured value is written into the LMISC register of the
Universe chip.
Special PCI Slave Image Register = 00000000?
The configured value is written into the SLSI register of the Universe chip.
Master Control Register = 80C00000?
The configured value is written into the MAST_CTL register of the Universe chip.
Miscellaneous Control Register = 52060000?
The configured value is written into the MISC_CTL register of the
Universe chip.
User AM Codes = 00000000?
The configured value is written into the USER_AM register of the
Universe chip.
ASpecifications A
Specifications
Table
A complete functional description of the MVME2603/2604 base boards appears in Chapter 3, Functional Description. Specifications for the optional PCI mezzanines can be found in the documentation for those modules.
Table
Cooling Requirements
The Motorola MVME2603/2604 family of single board computers is specified, designed, and tested to operate reliably with an incoming air temperature range from 0?? to 55?? C (32?? to 131?? F) with forced air cooling of the entire assembly (base board and modules) at a velocity typically achievable by using a 100 CFM axial fan. Temperature qualification is performed in a standard Motorola VME system chassis.
While the exact amount of airflow required for cooling depends on the ambient air temperature and the type, number, and location of boards and other heat sources, adequate cooling can usually be achieved with 10 CFM and 490 LFM flowing over the module. Less airflow is required to cool the module in environments having lower maximum ambients. Under more favorable thermal conditions, it may be possible to operate the module reliably at higher than 55?? C with increased airflow. It is important to note that there are several factors, in addition to the rated CFM of the air mover, which determine the actual volume and speed of air flowing over a module.
FCC Compliance
The MVME2603/2604 single board computer was tested in an
FCC compliance was achieved under the following conditions:
???Shielded cables on all external I/O ports.
???Cable shields connected to earth ground via metal shell connectors bonded to a conductive module front panel.
???Conductive chassis rails connected to earth ground. This provides the path for connecting shields to earth ground.
???Front panel screws properly tightened.
For minimum RF emissions, it is essential that the conditions above be implemented. Failure to do so could compromise the FCC compliance of the equipment containing the module.
BSerial Interconnections B
Introduction
As described in previous chapters of this manual, the MVME2603/2604 serial communications interface has four ports. Two of them are combined synchronous/asynchronous ports; the other two are asynchronous only. Both synchronous and asynchronous ports supply an
Asynchronous Serial Ports
The MVME2603/2604 uses a PC87308 ISASIO chip from National Semiconductor to implement the two asynchronous serial ports (in addition to the disk drive controller, parallel I/O, and keyboard/mouse interface).
The asynchronous ports provided by the ISASIO device are routed through P2 and the associated transition module. The
The MVME2603/2604 hardware supports asynchronous serial baud rates of 110B/s to 38.4KB/s. For detailed programming information, refer to the PCI and ISA bus discussions in the MVME2600 Series Single Board Computer Programmer???s Reference Guide, listed in Appendix D, Related Documentation, and to the vendor documentation for the ISASIO device.
Synchronous Serial Ports
The MVME2603/2604 uses a Zilog Z85230 ESCC (Enhanced Serial Communications Controller) with a 10 MHz clock to implement the two synchronous/asynchronous serial communications ports, which are routed through P2 to the transition module. The Z85230 handles both
Serial Interconnections
synchronous (SDLC/HDLC) and asynchronous protocols. The hardware supports asynchronous serial baud rates of 110B/s to 38.4KB/s and synchronous baud rates of up to 2.5MB/s.
Each port supports the CTS, DCD, RTS, and DTR control signals, as well as the TxD and RxD transmit/receive data signals and TxC/RxC synchronous clock signals. Since not all modem control lines are available in the Z85230, a Z8536 CIO device is used to provide the missing modem lines.
The
Table
To interpret the information correctly, remember that the
Table
Serial Interconnections
Table
Notes
1.A high
voltages and is contrary to specifications.
2.The
The
Table
The MVME2603/2604 conforms to
Table
The
Table
Table
In specifying parameters for serial binary data interchange between DTE and DCE devices, the
???The interconnection cable is too long for effective unbalanced operation.
???The interconnection cable is exposed to extraneous noise sources that may cause an unwanted voltage in excess of ??1V measured
differentially between the signal conductor and circuit ground at the load end of the cable, with a 50?? resistor substituted for the transmitter.
???It is necessary to minimize interference with other signals.
???Inversion of signals may be required (for example, plus polarity MARK to minus polarity MARK may be achieved by inverting the cable pair).
MVME2603/2604 are listed in Table
Table
Proper Grounding
Table
Proper Grounding
An important subject to consider is the use of ground pins. There are two pins labeled GND. Pin 7 is the signal ground and must be connected to the distant device to complete the circuit. Pin 1 is the chassis ground, but it must be used with care. The chassis is connected to the power ground through the green wire in the power cord and must be connected to be in compliance with the electrical code.
The problem is that when units are connected to different electrical outlets, there may be several volts of difference in ground potential. If pin 1 of each device is interconnected with the others via cable, several amperes of current could result. This condition may not only be dangerous for the small wires in a typical cable, but may also produce electrical noise that causes errors in data transmission. That is why Table
CTroubleshooting CPU Boards:
Solving Startup Problems C
Introduction
In the event of difficulty with your CPU board, try the simple troubleshooting steps on the following pages before calling for help or sending the board back for repair. Some of the procedures will return the board to the factory debugger environment. (The board was tested under these conditions before it left the factory.) The
Table
Troubleshooting CPU Boards: Solving Startup Problems
Table
Introduction
Table
Troubleshooting CPU Boards: Solving Startup Problems
Table
DRelated Documentation D
Motorola Computer Group Documents
The Motorola publications listed below are referenced in this manual. You can obtain paper or electronic copies of Motorola Computer Group publications by:
???Contacting your local Motorola sales office
???Visiting MCG???s World Wide Web literature site, http://www.motorola.com/computer/literature
To locate and view the most
Related Documentation
Manufacturers??? Documents
For additional information, refer to the following table for manufacturers??? data sheets and user???s manuals. For your convenience, a source for the listed document is also provided.
It is important to note that in many cases, the information shown is preliminary and the revision levels of the documents are subject to change without notice.
Manufacturers??? Documents
Related Documentation
Related Specifications
Related Specifications
For additional information, refer to the following table for related specifications. For your convenience, a source for the listed document is also provided. It is important to note that in many cases, the information is preliminary and the revision levels of the documents are subject to change without notice.
Related Documentation
Index
A
Abort (interrupt) signal
adapter board, P2
adapter, P2
for MVME761
ambient air temperature
B
backplane jumpers
layout
base module feature register
block diagram MVME2603/2604
board
configuration
C
cables
conductive chassis rails
base board
MVME712M transition module
configuration, transition module serial port
configure
PPC1Bug parameters
Configure Board Information Block (CNFG)
connector pin assignments
D
data
data terminal equipment (DTE)
debugger firmware
DECchip 21140 LAN controller
test groups
Index
E
interface characteristics
function of Raven ASIC
ENV command
station address
F
IBC DMA channel assignments
MVME712M transition module
PMC module
installation considerations
Ethernet
serial
interrupt architecture, MVME2603/2604
interrupt signals
ISA bus
J
jumper headers
MVME2603/2604 base board
jumpers
J10 (Flash selection)
J17 (SP4 transmit clock)
J18 (SP3 transmit clock)
J20 (SP4 clock receiver buffer)
J22 (system controller)
J3 (cache mode)
K
keyboard/mouse interface
L
L2 cache
LED mezzanine
M
manufacturers??? documents
PCI local bus
multiplexing function (P2)
N
NETboot enable
Network Auto Boot enable
O
operating parameters
P
P2 adapter
for MVME761
P2 adapter board
P2 multiplexing
P2 multiplexing function
parallel port
PCI bus
PCI expansion
functions
pin assignments, connector
polyswitches (fuses)
PPCBug debugger firmware
R
RAM200 memory module
Raven MPU/PCI bus bridge controller ASIC
remote control/status connector
connector
remote status/control connector
resetting the system
RF emissions
ROMboot enable
ROMNAL
S
SCSI
I
N
D
E
X
Index
serial communications interface
serial interface modules (SIMs)
serial port configuration, base board
serial port configuration, transition module
set environment to bug/operating system (ENV)
SGS- Thomson MK48T559 timekeeper de- vice
shielded cables (see also cables)
speaker output
Symbios 53C825A SCSI controller
system controller function
system startup