This manual provides general information, preparation for use and installation
instructions, operating instructions, and functional description for the MVME167
series of Single Board Computers (referred to as the MVME167 throughout this
manual).
Model Designations
The MVME167 is available in several models, which are listed in Table 1-1.
MVME167 Model Designations on page 1-1.
Table 1-1. MVME167 Model Designations
Model NumberSpeedMajor Differences
1
MVME167-001B (was MVME1 67-01 or -001A) 25 MHz4MB Onboard Parity DRAM
MVME167-002B (was MVME1 67-02 or -002A) 25 MHz8MB Onboard Parity DRAM
MVME167-003B (was MVME1 67-03 or -003A) 25 MHz16MB Onboard Parity DRAM
MVME167-004B (was MVME1 67-04 or -004A) 25 MHz32MB Onboard Parity DRAM
MVME167-031B (was MVME1 67-31 or -031A)33 MHz4MB Onboard ECC DRAM
MVME167-032B (was MVME1 67-32 or -032A)33 MHz8MB Onboard ECC DRAM
MVME167-033B (was MVME1 67-33 or -033A)33 MHz16MB Onboard ECC DRAM
MVME167-034B (was MVME1 67-34 or -034A)33 MHz32MB Onboard ECC DRAM
MVME167-035B (was MVME167-03 5A)33 MHz64MB Onboard ECC DRAM
MVME167-036B (was MVME167-03 6A)33 MHz128MB Onboard ECC DRAM
MVME167/D31-1
Page 12
1
Genera l Information
Features
Features of the MVME167 are listed below.
❏MC68040 Microprocessor at 25 MHz (-00X models), or 33 MHz
(-03X models)
❏4/8/16/32/64MB o f 32-b it DRAM with parity protection
or 4/8/16/32/64/128/256MB of DRAM with ECC protection
❏Four 44-pin PLCC ROM sockets (organized as two banks of 32 bits)
❏128KB SRAM (with optional battery backup)
❏Status LEDs for FAIL, STAT, RUN, SCON, LAN, +12V (LAN power), SCSI,
and VME.
❏8K by 8 RAM and time of day clock with battery backup
❏RESET and ABORT switches
❏Four 32-bit tick timers for periodic interrupts
❏Watchdog timer
❏Eight software interrupts
❏I/O
–SCSI Bus interface with DMA
–Four serial ports with EIA-232-D buffers with DMA
–Centronics printer port
–Ethernet transceiver interface with DMA
❏VMEbus interface
–VMEbus system controller functions
–VMEbus interface to local bus (A24/A32,
D8/D16/D32 (D8/D16/D32/D64BLT) (BLT = Block Transfer)
–Local bus to VMEbus interface (A16/A24/A32, D8/D16/D32)
–VMEbus interrupter
–VMEbus interrupt handler
–Global CSR for interprocessor communications
–DMA for fast local memory - VMEbus transfers (A16/A24/A32,
D16/D32 (D16/D32/D64BLT)
1-2MVME167 Single Board Computer User’s Manual
Page 13
Specifications
General specifications for the MVME167 are listed in Table 1-2. MVME167
Specifications on page 1-4.
The following sections detail cooling requirements and FCC compliance.
Cooling Requirements
The Motorola MVME167 VMEmodule 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 at a velocity typ ically achievable by using a 100
CFM axial fan. Temperature qualification is performed in a standard Motorola
VMEsystem chassis. Twenty-five watt load boards are inserted in two card slots, one
on each side, adjacent to the board under test, to simulate a high power den sity system
configuration. An assembly of three axial fans, rated at 100 CFM per fan, is placed
directly under the VME card cage. The incoming air temperature is measured between
the fan assembly and the card cage, where the incoming airstream first encounters the
module under test. Test software is executed as the module is subjected to ambient
temperature variations. Case temperatures of critical, high power density integrated
circuits are monitored to ensure component vendors specifications are not exceeded.
Specifications
1
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 usual ly be achieved with 10 CFM and 4 90 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.
MVME167/D31-3
Page 14
1
Genera l Information
Table 1-2. MVME167 Specifications
CharacteristicsSpecifications
Power requirements
(with all four EPROM
sockets popula te d and
excluding external
LAN transceiver)
Operating temperature (refer to
Cooling Requirements section)
Storage t e mp erature-40° to +85 ° C
Relative humidi ty5% to 90% (non-cond e ns in g)
Physical dimensions
PC board with mezzanine module
only
Height
Depth
Thickness
PC boards with connectors and front
panel
Height
Depth
Thickness
+5 Vdc (± 5%), 3.5 A (typical), 4.5 A (max.)
(at 25 MHz, with 32MB parity DRAM);
5. 0 A ( typical), 6.5 A (ma x.)
(at 33 MHz, with 128MB ECC DRAM)
+12 Vdc (± 5%), 100 mA (max.)
(1.0 A (max.) with offboard LAN
transceiver)
-12 Vdc (± 5%), 100 mA (max.)
0° to 55° C at point of entry of forced ai r
(approximately 490 LFM)
Double-high VMEboard
9.187 inches (233.35 mm)
6.299 inches (160.00 mm)
0.662 inches (16.77 mm)
10.309 inches (261.85 mm)
7.4 inches (188 mm)
0.80 inches (20.32 mm)
FCC Compliance
The MVME167 was tested in an FCC-compliant chassis, and meets the requirements
for Class A equipment. FCC compliance was achieved under the following conditions:
1.Shielded cables on all external I/O ports.
2.Cable shields connected to earth ground via metal shell connectors bonded to a
conductive module front panel.
3.Conductive chassis rails connected to earth ground. This provides the path for
connecting shields to earth ground.
4.Front panel screws pro pe rly tightened.
1-4MVME167 Single Board Computer User’s Manual
Page 15
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.
General Description
The MVME167 is a double-high VMEmodul e based on the MC68040 microprocessor.
The MVME167 has 4/8/16/32/64 MB of parity-protected DRAM or
4/8/16/32/64/1 28/2 56 MB of ECC-p rotect ed DRAM, 8KB o f stati c RAM and time of
day clock (with battery backup), Ethernet transceiver interface, four serial ports with
EIA-232-D interface, four tick timers, watchdog timer, four ROM sockets, SCSI bus
interface with DMA, Centronics printer port, A16/A24/A32/D8/D16/D32/D64
VMEbus master/slave interface, 128KB of static RAM (with optional battery backup),
and VMEbus system controller.
The I/O on the MVME167 is connected to the VMEbus P2 connector. The main board
is connected through a P2 transition board and cables to the transition boards. The
MVME167 supports the transition boards MVME712-12, MVME712-13,
MVME712M, MVME712A, MVME712AM, and MVME712B (referred to in this
manual as MVME712X, unless separately specified). The MVME712X trans ition
boards provide configuration headers and provid e industry standard connectors for the
I/O devices.
General Description
1
The VMEbus interface is provided by an ASIC called the VMEchip2 . The VMEchip2
includes two tick timers, a watchdog timer, pr ogrammable map decoders for the master
and slave interfaces, and a VMEbus to/from local bus DMA controller, a VMEbus
to/from local bus non-DMA programmed access interface, a VMEbus interrupter, a
VMEbus system controller, a VMEbus interrupt handler, and a VMEbus requester.
Processor-to-VMEbus transfers can be D8, D16, or D32. VMEchip2 DMA transfers to
the VMEbus, however, can be D16, D32, D16/BLT, D32/BLT, or D64/MBLT.
The PCCchip2 ASIC provides two tick timers and the inter face to the LAN chip, SCSI
chip, serial port chip, printer port, and BBRAM.
The MEMC040 memory controller ASIC provides the programmable interfac e for the
parity-protected DRAM mezzanine board.
The MCECC memory controller ASIC provides the programmable interface for the
ECC-protected DRAM mezzanine board.
MVME167/D31-5
Page 16
1
Genera l Information
Equipment Required
The following equipment is required to m ake a complete system using the MVME167:
MVME712AM, or MVME712B, and connecting cables and P2 adapter
❏Operating system
The MVME167Bug debug moni t or fi r mware (167Bug) is provided in two of t he f our
EPROM sockets on the MVME167 main module. It provides over 50 debug,
up/downline load, and disk bootstrap load commands, as well as a full set of onboard
diagnostics and a one-line assembler/disassembler. 167Bug includes a user interface
which accepts commands from the system console terminal. 167Bug can also operate
in a System Mode, which includes choices from a service menu. Refer to the
MVME167Bug Debugging Package User’s Manual and the Debugging Package for
Motorola 68K CISC CPUs User’s Manual for details.
The MVME712X series of transition modules provide the interface between the
MVME167 module and peripheral devices. They connect the MVME167 to
EIA-232-D serial devices, Cent ronics-co mpatible para llel devi ces, SCSI devi ces, and
Ethernet devices. The MVME712X series work with cables and a P2 adapter.
Software available for the MVME167 includes SYSTEM V/68 and real-time operating
systems, programm ing languages, an d other tools and applications . Contact your local
Motorola sales office for more details.
1-6MVME167 Single Board Computer User’s Manual
Page 17
Related Documentation
The following publications are applicable to the MVME167 and may provide
additional helpful in formation. If not shipped wi th this product, they may be purchas ed
by contacting your local Motorola sales office. Non-Motorola documents may be
purchased f rom the sources listed.
Document Title
Related Documentation
1
Motorola
Publication
Number
Note
MVME167 Single Board Computer Support Information
(Refer to Support Informat ion on page 1-8)
MVME167Bug Debugging Package User’s ManualMVME167BUG
Debugging Package for Motorola 68K CISC CPUs User’s Manual 68KBUG
Single Board Computers SCSI Software User’s Manual SBCSCSI
MVME166/MVME167/MVME187 Single Board Computers
Manual
MVME712-12, MVME712-13, MVME712A, MVME712AM, and
MVME712B Transition Module and LCP2 Adapter Board User’s
Manual
M68040 Microprocessor User’s ManualM68040UM
SIMVME167
MVME187PG
MVME712M
MVME712A
Although not shown in the above list, each Motorola Computer
Group manual pub lication number is suffixed with ch aracters
which represent the revision level of the document, such as
"/D2" (the second revision of a manual); a supplement bears the
same number as a manual but has a suffix such as "/D2A1" (the
first supplement to the second edition of the manual).
MVME167/D31-7
Page 18
1
Genera l Information
The following publications are available from the sources indicated.
Versatile Backplane Bus: VMEbus, ANSI/IEEE Std 1014-1987, The Institute of
Electrical and Electronics Engi neers, Inc., 345 East 47t h Street, New York, NY 10017
(VMEbus Specification). This is also available as Microprocessor system bus for 1 to 4 byte data, IEC 821 BUS , Bureau Central de la Commission Electrotechnique
Internationale; 3, rue de Varembé, Geneva, Switzerland.
ANSI Small Computer System Interface-2 (SCSI-2), Draft Document X3.131-198X,
Revision 10c; Global Engineering Documents, P.O. Box 19539, Irvine, CA 92714.
CL-CD2400/240 1 Fo ur-Channel Multi-Protocol Communications Controller Data
Sheet, order number542400-003; Cirrus Logic, Inc., 3100 West Warren Ave.,
Fremont, CA 94538.
82596CA Local Area Network Coprocessor Data Sheet, order number 290218; and
82596 User’s Manual, order numb er 296853; Intel C orporatio n, Literatur e Sales, P .O.
Box 58130, Santa Clara, CA 95052-8130.
NCR 53C710 SCSI I/ O Pr oces so r Dat a Ma nual, order nu mber NCR53C710DM; and
NCR 53C710 SCSI I/O Processor Programmer’s Guide, order number
NCR53C710PG; NCR Corporation, Microelectronics Products Division, Colorado
Springs, CO.
MK48T08(B) Timekeeper TM and 8Kx8 Zeropower TM RAM data sheet in Static
RAMs Databook, order number DBSRAM71; SGS-THOMPSON Microelectr onics
Group; North & South American Marketing Headquarters, 1000 East Bell Road,
Phoenix, AZ 85022-2699.
Support Information
The SIMVME167 manual contains the connector interconnect signal information,
parts lists, and the schematics for the MVME167.
This manual may be obtained free of charge by contacting your local Motorola sales
office.
1-8MVME167 Single Board Computer User’s Manual
Page 19
Manual Terminology
Throughout this manual, a convention is used which precedes data and address
parameters by a character identifying the numeric format as follows:
$dollarspecifies a hexad ecimal character
%percentspecifies a binary number
&ersandspecifies a decimal number
Unless otherwise specified, all address references are in hexadecimal.
An asterisk (*) following the signal name for signals which are level significant
denotes that the signal is true or valid when the signal is low.
An asterisk (*) following the signal name for signals which are edge significant
denotes that the actions initiated by that signal occur on high to low transition.
In this manual, assertion and negation are used to specify forcing a signal to a
particular state. In particular, assertion and assert r efer to a signal that is active o r true;
negation an negate indicate a signal that is inactive or false. These terms are used
independently of the voltage level (hi gh or low) that they represent.
Manual Terminology
1
Data and address sizes are defined as follows:
❏A byte is eight bits, numbered 0 through 7, with bit 0 being the least significant.
❏A word is 16 bits, numbered 0 through 15, with bit 0 being the least significant.
❏A longword is 32 bits, numbered 0 through 31, with bit 0 being the least
significant.
MVME167/D31-9
Page 20
1
Genera l Information
1-10MVME167 Single Board Computer User’s Manual
Page 21
HARDWARE PREPARATION
Introduction
This chapter provides unpacking instructions, hardware preparation, and installation
instructions for the MVME167. The MVME712X transition module hardware
preparation is provided in separate manua ls. Refer to Related Documentation in
Chapter 1.
Unpacking Instructions
Note
Unpack equipment from shipping carton. Refer to packing list and verify that all items
are present. Save packing material for storing and reshipping of equipment.
Caution
If the shipping carton is damaged upon receipt, request carrier’ s
agent be present during unpacking and inspection of equipment.
Avoid touching areas of integrated circuitry; static discharge
can damage circuits.
AND INSTALLATION
2
Hardware Preparation
To select the desired configuration and ensure proper operation of the MVME167,
certain option modifications may be necessary before installation. The MVME167
provides so ftware control f or most of these options. Some options can not be done in
software, so are done by jumpers on headers. Most other modifications are done by
setting bits in control registers after the MVME167 has been installed in a system. (The
MVME167 registers are described in Chapter 4, and/or in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide as listed in Related Documentation in Chapter 1.)
The location of the switches, jumper headers, connectors, and LED indicators on the
MVME167 is illustrated in Figure 2-1. The MVME167 has been factory tested and is
shipped with the factory jumper settings de scribed in the following sections. The
MVME167 operates with its required and factory-installed Debug Monitor,
MVME167Bug (167Bug), with these factory jumper settings.
Settings can be made for:
❏General purpose readable register (J1)
MVME167/D32-1
Page 22
2
Hardware Preparation and Installation
❏System controller select (J2)
❏Serial port 4 clock configuration select (J6 and J7)
❏SRAM backup power source select (J8) (optional)
General Purpo se Readable Jumpers on He ader J1
Each MVME167 may be configured with readable jump ers. These jumpers can be read
as a register (at $FFF40088) in the VMEchip2 LCSR. The bit values are read as a one
when the jumper is off, and as a zero when the jumper is on.
J1
2
1
GP10 GP11 GP12 GP13 GP14 GP15 GP16 GP17
All Zeros (Factory Configuration)
System Controller Header J2
The MVME167 can be VMEbus system controller. The system controller function is
enabled/disabled by jumpers on header J2. When the MVME167 is system controller,
the SCON LED is turned on. The VMEchip2 may be configured as a system controller
as follows.
J2
2
1
16
15
J2
2
1
System Controller
(Factory Configurati on)
2-2MVME167 Single Board Computer User’s Manual
Not System Controller
Page 23
MVME
167
HALTFAIL
RUN SCON
LAN
+12V
SCSI VME
Hardware Preparation
2
2
6
40
6
2
39401
7
XU2
17
29
18
28
(OPTIONAL)
4
23
1
J8
DS1
DS2
DS3
DS4
6
2
7
1
15
1
J2
19
20
XU1
J1
17
18
162
2
J3
COMPONENTS ARE REMOVED FOR CLARITY
1
2
6
2
39
39401
29
28
1
7
SKT
17
18
7
XU3
17
29
18
28
SKT
39401
XU4
29
28
A1B1C1
P1
A32
B32
C32
1379 9404
ABORT
RESET
PRIMARY SIDE
S1S2
60
59
J4
2
1
60
59
MEZZANINE BOARD
F2
A1B1C1
P2
J5
2
1
J6J7
A32
B32
C32
11
33
Figure 2-1. MVME167 Switches, Headers, Connectors, Fuses, and LEDs
MVME167/D32-3
Page 24
Hardware Preparation and Installation
2
Serial Port 4 Clock Configuration Select Headers J6 and J7
Serial port 4 can be configured to use clock signals provided by the RTXC4 and
TRXC4 signal lines. Headers J6 and J7 on the MVME167 configure serial port 4 to
drive or receive RTXC4 and TRXC 4, r espectively. Factory configuration is with port
4 set to receive both signals.
The remaining configuration of the clock lines is accomplished using the Serial Port 4
Clock Configuration Select header on the MVME712M transition module. Refer to the
MVME712M Transition Module and MVME147P2 Adapter Board User’s Manual for
configuration of that header
J6
1
3
Receive RTXC4
Receive TRXC4
(Factory Configurations)
J7
1
3
J6
1
3
Drive RTXC4
2-4MVME167 Single Board Computer User’s Manual
J7
1
3
Drive TRXC4
Page 25
Hardware Preparation
SRAM Backup Power Source Select Header J8
Header J8 is an optional header that is used to select the power source used to back up
the SRAM on the MVME167, if the optional battery and circuitry is present.
J8
4
132
Backup Power Disabled
(Factory Config uration, when
Optional Battery Is Present)
4
13
2
VMEbus +5V STBY
2
J8J8
4
132
Optional Battery
Caution
Do not remove all jumpers from J8. This may disable the
SRAM.
If your board contains the optional header J8, but the optional
battery is removed, jumpers must be installed on J8 between
pins 2 and 4, as sh own in the Backup Power Disabled drawing
above.
MVME167/D32-5
Page 26
Hardware Preparation and Installation
2
Installation Instructions
The following sections discuss installation of the MVME167 into a VME chassis, and
system considerations. Ensure that EPROM devices are installed as needed. Factory
configuration is with two EPROMs installed for the MVME167Bug debug monitor, in
sockets XU1 and XU2. Ensure that all header jumpers are configured as desired.
MVME167 Module Insta llation
Now that the MVME167 module is ready for installation, proceed as follows:
1.Turn all equipment power OFF and disconnect power cable from ac power source.
Caution
!
WARNING
Inserting or removing modules while power is applied could
result in damage to module components.
DANGEROUS VOLTAGES, CAPABLE OF CAUSING
DEATH, ARE PRESENT IN THIS EQUIPMENT. USE
EXTREME CAUTION WHEN HANDLING, TESTING, A ND
ADJUSTING.
WARNING
2.Remove chassis cover as instructed in the equipment user’s manual.
3.Remove the filler panel(s) from the appropriate card slot(s) at the front and rear of
the chassis (if the chassis has a rear card cage). The MVME167 module requires
power from both P1 and P2 . It may be in stall ed in any dou ble-he ight un used car d
slot, if it is not configured as system controller. If the MVME167 is configured as
system controller, it must be installed in the leftmost card slot (slot 1) to correctly
initiate the bus-grant daisy-chain and to have proper operation of the
IACK-daisy-chain driver. The MVME167 is to be installed in the front of the
chassis and the MVME712X is to be installed in the front or the rear of the chassis.
Other modules in the system may have to be moved to allow space for the
MVME712M which has a double-wide front panel.
4.Carefully slide the MVME167 modu le into the card slot. Be sure the module is
seated properly into the P1 and P2 connectors on the backplane. Do not damage
or bend connector pins. Fasten the module in the chassis with screws provided,
making good contact with the transverse mounting rails to minimize RFI
emissions.
5.Remove IACK and BG jumpers from the header on the chassis backplane for the
card slot the MVME167 is installed in.
2-6MVME167 Single Board Computer User’s Manual
Page 27
6.Connect the P2 Adapter Board and specified cable(s) to the MVME167 at P2 on
the backplane at the MVME167 slot, to mate with (optional) terminals or other
peripherals at the EIA-232-D serial ports, parallel port, SCSI ports, and LAN
Ethernet port. Refer to the manuals listed in Related Documentation in Chapter 1
for information on installing the P2 Adapter Board and the MVME712X transition
module(s). (Some connection diagrams are in the
MVME166/MVME167/MVME187 Single Board Computers Programmer’s
Reference Guide.) Some cable(s) are not provided with the MVME712X
module(s), and therefore are made or provided by the user. (Motorola
recommends using shielded cables for all connections to peripherals to minimize
radiation.) Connect the peripherals to the cable(s). Detailed information on the
EIA-232-D signals supported is found in Appendix A.
7.Install any other required VMEmodules in the system.
8.Replace the chassis cover.
9.Connect power cable to ac power source and turn equipment power ON.
System Considerations
Installation Instructions
2
The MVME167 needs to draw power from both P1 and P2 of the VMEbus backplane.
P2 is also used for the upper 16 bits of data for 32-bit transfers, and for the upper 8
address lines for extended addressing mode. The MVME167 m ay not operate properly
without its main board connected to P1 and P2 of the VMEbus backplane.
Whether the MVME167 operates as a VMEbus master or as a VMEbus slave, it is
configured for 32 bits of address and for 32 bits of data (A32/D32). However, it
handles A16 or A24 devices in the address ranges indicated in Chapter 3. D8 and/or
D16 devices in the system must be handled by the MC68040 software. Refer to the
memory maps in Chapte r 3.
The MVME167 contains shared onboard DRAM whose base address is
software-selectable. Both the onboard processor and offboard VMEbus devices see
this local DRAM at base physical address $00000000, as programmed by the
MVME167Bug firmware. This may be changed, by software, to any other base
address. Refer to the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for details.
If the MVME167 tries to access offbo ard resources in a nonexistent location, and is not
system controller, and if the system d oes not have a global bus timeo ut, the MVME167
waits forever for the VMEbus cycle to complete. This would cause the system to hang
up. There is only one situation in which the system might lack this glo bal bus timeout:
the MVME167 is not the system controller, and there is n o global bus timeout
elsewhere in the system.
MVME167/D32-7
Page 28
2
Hardware Preparation and Installation
Multiple MVME167 modules may be configured into a single VME card cage. 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 set includes four
bits which func tion as location monitors to allow one MVME167 pr ocessor to
broadcast a signal to other MVME167 processors, if any. All eight registers are
accessible from any local processor as well as from the VMEbus.
The MVME167 provides +12 Vdc power to the Ethernet LAN transceiver interface
through a 1 amp fuse F2 located on the MVME167 module. The +12V LED lights
when +12 Vdc is available. The fuse is socketed, and located near diode CR1. If the
Ethernet transceiver fails to operate, check the fuse. When using the MVME712M
module, the yellow LED (DS1) on the MVME712M front panel lights when LAN
power is available, indicating that the fuse is good.
The MVME167 provides SCSI terminator power through a 1 amp fuse F1 located on
the P2 Adapter Board. The fuse is socketed. If the fuse is blown, the SCSI devices may
not operate or may function erratically. When the P2 Adapter Board is used with an
MVME712M and the SCSI bus is connected to the MVME712M, the green LED
(DS2) on the MVME712M front panel ligh ts when th ere is SCSI termi nator power. If
the LED flickers during SCSI bus operation, the fuse should be checked.
2-8MVME167 Single Board Computer User’s Manual
Page 29
OPERATING
Introduction
This chapter provides necessary information to use the MVME167 module in a system
configuration. This includes controls and indicators, memory maps, and software
initialization of the module.
Controls and Indicators
The MVME167 module has ABORT and RESET switches; and FAIL, STAT, RUN,
SCON, LAN,+12V (LAN power), SCSI, and VME indicators; all located on the fro nt
panel of the module.
ABORT Switch S1
When enabled by software, the front panel ABORT switch generates an interrupt at a
user-programmable level. It is normally used to abort p rogram execution and return to
the 167Bug debugger firmware located in the MVME167 EPROMs.
The ABORT switch interrupter in the VMEchip2 is an edge-sensitive interrupter
connected to the ABORT switch. This interrupter is filtered to remove switch bounce.
INSTRUCTIONS
3
RESET Switch S2
The front panel RESET switch resets all onboard devices, and drives SYSRESET* if
the board is system controller. The RESET switch may be disabled by software.
The VMEchip2 includes both a global and a local reset driver. When the chip operates
as the VMEbus system controller, the reset driver provides a global system reset by
asserting the VMEbus signal SYSRESET*. A SYSRESET* may be generated by the
RESET switch, a power up res et, a watchdog t imeout, or by a control bi t in the LCSR.
SYSRESET* remains asserted for at least 200 msec, as required by the VMEbus
specification.
Similarly, the VMEchip2 provides 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 VMEchip2 is not the system controller. A local reset
may be generated by the RESET switch, a power up reset, a watchdog timeout, a
VMEbus SYSRESET*, or a control bit in the GCSR.
Front Panel Indicators (DS1 - DS4)
There are eight LEDs on the MVME167 front panel: FAIL, STAT, RUN, SCON,
LAN, +12V (LAN power), SCSI, and VME.
MVME167/D33-1
Page 30
3
Operating Instructions
❏The red FAIL LED (part of DS1) lights when the BRDFAIL signal line is active.
❏The MC68040 status lines are decoded, on the MVME167, to drive the yellow
STAT (status) LED (part of DS1). In this case, a halt condition from the processor
lights the LED.
❏The green RUN LED (part of DS2) lights when the local bus TIP* signal line is
low. This indicates one of the local bus masters is executing a local bus cycle.
❏The green SCON LED (part of DS2) lights when the VMEchip2 in the MVME167
is the VMEbus system controller.
❏The green LAN LED (part of DS3) lights when the LAN chip is local bus master.
❏The MVME167 supplies +12V power to the Ethernet transceiver interface
through a fuse. The green +12V (LAN power) LED (part of DS3) lights when
power is available to the transceiver interface.
❏The green SCSI LED (part of DS4) lights when the SC SI chip is local bus master.
❏The green VME LED (part of DS4) lights when the board is using the VMEbus
(VMEbus AS* is asserted by the VMEchip2) or when the board is accessed by the
VMEbus (VMEchip2 is the local bus master).
3-2MVME167 Single Board Computer User’s Manual
Page 31
Memory Maps
There are two points of view for memory maps: 1) the mapping of all resources as
viewed by local bus m ast ers ( lo cal bu s memo ry map), and 2) the mapp i ng of onboard
resources as viewed by VMEbus Masters (VMEbus memory map).
Local Bus Memory Map
The local bus memory map is split into different address spaces by the transfer type
(TT) signals. The local resources respond to the normal access and interrupt
acknowledge codes.
Normal Address Range
The memory map of devices that r e spond to the n ormal address range is shown in the
following tables. The normal address range is defined by the Transfer Type (TT)
signals on the local bus. On the MVME167, Transfer Types 0, 1, and 2 define the
normal address range.
Table 3-1. Local Bus Memory Map, is the entire map from $00000000 to $FFFFFFFF.
Many areas of the map are user-programmable, and suggested uses are shown in the
table. The cache inhibit function is programmable in the MMUs. The onboard I/O
space must be marked cache inhibit and serialized in its page table.
Memory Maps
3
Table 3-2. Local I/O Devices Memory Map on page 3-5 further defines the map fo r the
local I/O devices.
(Refer to next table)
$FFFF0000 - $FF FFFFFFUser Program mable
(VMEbus A16)
D32DRAMSIZEN1, 2
D32/D1 63GB?3, 4
D32-D81MBY3
D32/D1664KB?2, 4
Cache
Inhibit
NOTES: 1. Onboard EPROM appears at $00000000 - $003FFFFF f ollowing a local bus
reset. The EPROM appears at 0 until the ROM0 bit is cleare d in the VMEchip2.
The ROM0 bit is located at address $FFF40030 bit 20. The EPROM must be
disabled at 0 before the DRA M i s enabled. The VMEchip2 and DRAM map
decoders are disabled by a local bus reset.
2. Thi s area is user-programmable. The suggested use is shown in the table. The
DRAM decoder is programmed in the MEMC040 or MCECC chip, and the
local-to-VMEbus decoders are programmed in the VMEchip2.
3. Size is approximate.
4. Cache inhibit depends on devices in area mapped.
5. This area is not decoded. If these locations are accessed and the local bus timer
is enabled, the cycle times out and is terminated by a TEA signal .
Notes
3-4MVME167 Single Board Computer User’s Manual
Page 33
Memory Maps
The following table focuses on the Local I/O Devices portion of the local bus Main
Memory Map.9.
NOTES: 1. For a complete description of the register bits, refer to the data sheet for the
specific chip. For a more detailed memory map refer to the following deta iled
peripheral device memory maps.
2. On t he MVME167 this area does not return an acknowledge signal. If the local
bus timer is enabled, the access times out and is terminated by a TEA signal.
MVME167/D33-5
Page 34
Operating Instructions
3. Byte reads should be used to read the interrupt vector. These locations do not
respond when an interrupt is not pending. If the local bus timer is enabled, the
access times out and is terminated by a TEA signal.
3
4. Writes to the LCSR in the VMEchip2 must be 32 bits. LCSR writes of 8 or 16
bits terminate with a TEA signal. Writes to the GCSR may be 8, 16 or 32 bits.
Reads to the LC SR and GCSR may be 8, 1 6 or 32 bits.
5. This area does not return an acknowledge signal. If the local bus timer is enabled,
the access times out and is terminated by a TEA signal.
6. This area does return an acknowledge signal.
7. Size is approximate.
8. Port commands to the 82596CA must be written as two 16-bit writes: upper word
first and lower word second.
9. The CD2401 appears repeatedly from $FFF45200 to $FFF45FFF on the
MVME167. If the local bus timer is enabled, the access times out and is
terminated by a TEA signal.
Detailed I/O Memory Maps
Tables 3-3 through 3-13 give the detailed memory maps for:
3-3VM Echip23-982596CA Eth e rnet chip
3-4PCCchip23-10 53C710 SCSI ch ip
3-5Printer3-11 MK48T08 BBRAM/TOD clock
3-6MEMC040 memory controller chip3-12 BBRAM configuration area
3-7MCECC memory controller chip3-13 TOD clock
3-8CD2401 serial chip
Note: Manufacturers’ errata sheets for the various chips are available by contacting
your local Motorola sales representative. A no n-disclosure agreement may be requir ed.
GENERAL PURPOSE CONTROL AND STATUS REGISTER 0
GENERAL PURPOSE CONTROL AND STATUS REGISTER 1
GENERAL PURPOSE CONTROL AND STATUS REGISTER 2
GENERAL PURPOSE CONTROL AND STATUS REGISTER 3
GENERAL PURPOSE CONTROL AND STATUS REGISTER 4
GENERAL PURPOSE CONTROL AND STATUS REGISTER 5
Table 3-8. Cirrus Logic CD2401 Serial Port Memory Map
Base Address = $FFF45000
Register Description
Global Registers
Global Firmware Revision Code RegisterGFRCR81BR
Channel Access RegisterCAREEBR/W
Option Registers
Channel Mode RegisterCMR1BBR/W
Channel Option Register 1COR110BR/W
Channel Option Register 2COR217BR/W
Channel Option Register 3COR316BR/W
Channel Option Register 4COR415BR/W
Channel Option Register 5COR514BR/W
Channel Option Register 6COR618BR/W
Channel Option Register 7COR707BR/W
Special Character Register 1SCHR11FBR/W Async
Special Character Register 2SCHR21EBR/W Async
Special Character Register 3SCHR31DBR/W Async
Special Character Register 4SCHR41CBR/W Async
Special Character Range lowSCRl23BR/W Async
Special Character Range highSCRh22BR/W Async
LNext CharacterLNXT 2EBR/W Async
Table 3-8. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
3
Register Description
Channel Command and Status Registers
Channel Command RegisterCCR13BR/W
Special Transmit Command RegisterSTCR12BR/W
Channel Status RegisterCSR1ABR
Modem Signal Value RegistersMSVR-RTSDEBR/W
Interrupt Registers
Local Interrupt Vector RegisterLIVR09BR/W
Interrupt Enable RegisterIER11BR/W
Local Interrupting Channel RegisterLICR26BR/W
Stack Regis terSTKE2BR
Receive Interrupt Registers
Receive Priority Interrupt Level RegisterRPILRE1BR/W
Receive Interrupt RegisterRIREDBR
Receive Interrupt Statu s RegisterRISR88W
Receive Interrupt Status Regist er l owRISRl89BR
Receive Interrupt Statu s Register highRISRh88BR
Receive FIFO Output CountR FOC3 0BR
Receive Data RegisterRDRF8BR
Receive End Of Interrupt RegisterREOIR84BW
Register
Name
MSVR-DTRDFBR/W
OffsetsSizeAccess
R/W
(NOTE)
Transmit Priority Interrupt Level RegisterTPILRE0BR/W
Transmit Interrupt RegisterTIRECBR
Transmit Interrupt Status RegisterTISR8ABR
Transmit FIFO Transfer CountTFTC80BR
Transmit Data RegisterTDRF8BW
Transmit End Of Interrupt Registe rTEOIR85BW
3-20MVME167 Single Board Computer User’s Manual
Transmit Interrupt Registers
Page 49
Table 3-8. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
Memory Maps
Register Description
Modem Interrupt Registers
Modem Priority Interrupt Level RegisterMPILRE3BR/W
Modem Interrupt RegisterM IREFBR
Modem (/Timer) Interrupt Status RegisterMISR8BBR
Modem End Of Interrupt RegisterMEOIR86BW
A Receive Buffer Address LowerARBADRL42WR/W
A Receive Buffer Address UpperARBADRU40WR/W
B Receive Buffer Address LowerBRBADRL46WR/W
B Receive Buffer Address UpperBRBADRU44WR/W
A Receive Buffer Byte CountARBCNT4AWR/W
B Receive Buffer Byte CountBRBCNT48WR/W
A Receive Buffer StatusARBSTS4FBR/W
B Receive Buffer StatusBRBSTS4EBR/W
Receive Current Buffer Address LowerRCBADRL3EWR
Receive Current Buffer Address UpperRCBADRU3CWR
DMA T ransmit Registers
A Transmit Buffer Address LowerATBADRL52WR/W
A Transmit Buffer Address UpperATBADRU50WR/W
B Transmit Buffer Address LowerBTBADRL56WR/W
B Transmit Buffer Address UpperBTBADRU54WR/W
A Transmit Buffer Byte CountATBCNT5AWR/W
B Transmit Buffer Byte CountBTBCNT58WR/W
A Transmit Buffer StatusATBSTS5FBR/W
B Transmit Buffer StatusBTBSTS5EBR/W
Transmit Current Buffer Address LowerTCBADRL3AWR
Transmit Current Buffer Address UpperT CBADRU38WR
Register
Name
OffsetsSizeAccess
3
MVME167/D33-21
Page 50
Operating Instructions
Table 3-8. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
3
Register Description
Timer Registers
Timer Period RegisterTPRDABR/W
Receive Time-out Period RegisterRTPR24WR/W Async
Receive Time-out Period Regis lowRTPRl25BR/W As ync
Receive Time-out Period Register highRTPRh24BR/W Async
General Timer 1GT12AWR Sync
General Timer 1 lowGT1l2BBR Sync
General Timer 1 highGT1h2ABR Sync
General Timer 2 GT229BR Sync
Transmit T imer RegisterTT R29BR Async
Register
Name
OffsetsSizeAccess
NOTE: This is a 16-bit register.
3-22MVME167 Single Board Computer User’s Manual
Page 51
Table 3-9. 82596CA Ethernet LAN Memory Map
Memory Maps
82596CA Ethernet LAN Directly Accessible Registers
Data Bits
AddressD31D16D15D0
$FFF46000Upper Command WordLower Command Word
$FFF46004MPU Channel Attention (CA)
NOTES: 1. Refer to the MPU Port and MPU Channel Attention registers in the
MVME166/MVME167/MVME187 Single Board Computers Programmer’s
Reference Guide.
2. After resetting, you must write the System Configuration Po inter to the command
registers before writing to the MPU Channel Attention register. Writes to the
System Configuration Pointer must be upper word first, lower word second.
NOTES: W = Write BitR = Read Bi tS = Signbit
ST = Stop BitFT = Frequency Testx = Unused
BBRAM,TOD Clock Memory Map
The MK48T08 BBRAM (also called Non-Volatile RAM or NVRAM) is divided into
six areas as shown in Table 3-11. MK48T08 BBRAM,TOD Clock Memory Map on page
3-25. The first five areas are def ined by soft ware, while the sixth area, the time-of-day
(TOD) clock, is defined by the chip hardware. The first area is re serv ed fo r us er data.
The second area is used by Motorola networking software. The third area is used by
the SYSTEM V/68 operating system. The fou rth area is used by the MVME167 board
debugger (MVME167Bug). The fifth area, detailed in Table 3-12. BBRAM Configuration Area Memory Map on page 3-25, is the configuration area. The sixth
area, the T OD clock, det ailed in Table 3-13. TOD Clock Memory Map on page 3-26,
is defined by the chip hardware.
The data structure of the configuration bytes starts at $FFFC1EF8 and is as follows.
1.Four bytes are reserved for the revi sion or version of this structure. This revis i on
is stored in ASCII format, with the first two bytes being the major version
numbers and the last two bytes being the minor version numbers. For exam ple, if
the version of this structure is 1.0, this field contains:
0100
2.T welve bytes are reserved for the serial number of the board in ASCII format. For
example, this field could contain:
000000470476
3.Sixteen bytes are reserved for the board ID in ASCII format. For example, for a
16 MB, 25 MHz MVME167 board, this field contains:
3
MVME167-003B
(The 12 characters are followed by four blanks.)
4.Sixteen bytes are reserved for the printed wiring assembly (PWA) number
assigned to this board in ASCII format. This includes the
01-W prefix. This is for
the main logic board if more than one board is required for a set. Additional boards
in a set are defined by a structure for that set. For example, for a 16 MB, 25 MHz
MVME167 board at revision A, the PWA field contains:
01-W3899B03A
(The 12 characters are followed by four blanks.)
5.Four bytes contain the speed of the board in MHz. The first two bytes are the
whole number of MHz and the second two bytes are fractions of MHz. For
example, for a 25.00 MHz board, this field contains:
2500
6.Six bytes are reserved for the Ethernet address. The address is stored in
hexadecimal format. (Refer to the detailed description in Chapter 4.) If the board
does not support Ethernet, this field is filled with zeros.
7.These two bytes are reserved.
8.Two bytes are reserved for the local SCSI ID. The SCSI ID is stored in ASCII
format.
9.Eight bytes are reserved for the systems serial ID, for boards 1used in a system.
MVME167/D33-27
Page 56
Operating Instructions
10. Eight bytes are reserved for the printed wiring board (PWB) number assigned to
the first mezzanine board in ASCII format. This does not include the
For example, for a 16MB par ity mezzanine at revision E, the PWB field contains:
01-W prefix.
3
3690B03E
11. Eight bytes are reserved for the serial number assigned to the first mezzanine
board in ASCII format.
12. Eight bytes are reserved for the printed wiring board (PWB) number assigned to
the optional second mezzanine board in ASCII format.
13. Eight bytes are reserved for the serial number assigned to the optional second
mezzanine board in ASCII format.
14. Growth space (153 bytes) is reserved. This pads the structure to an even 256 bytes.
System-specific items, such as size of system side, and systems side version, may
go here.
15. The final one byte of the area is reserved for a checksum (as defined in the
MVME167Bug Debugging Package User’s Manual and the Debugging Package
for Motorola 68K CISC CPUs User’s Manual) for security and data integrity of
the configuration area of the NVRAM. This data is stored in hexadecimal format.
Interrupt Acknowledge Map
The local bus disti nguishes interr upt acknowledg e cycles from other cycles by placin g
the binary value %11 on TT1-TT0. It also specifies the level that is being
acknowledged using TM2-TM0 . The interrupt handler selects which device within that
level is being acknowledged.
On the MVME187, a read anywhere from location $FFFE0004 through $FFFE001C
causes an interrupt acknowledge cycle at the specified level. This does not do so on the
MVME167. Refer to the PCCchip2 information in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for information on reading the current interrupt lev e l and setting the interrupt
mask.
VMEbus Memory Map
This section describes the mapping of local resources as viewed by VMEbus masters.
VMEbus Accesses to the Local Bus
The VMEchip2 includes a user-programmable map decoder for the VMEbus to local
bus interface. The map decoder allows yo u to progr am the starting and end ing addr ess
and the modifiers the MVME167 responds to.
3-28MVME167 Single Board Computer User’s Manual
Page 57
VMEbus Short I/O Memory Map
The VMEchip2 includes a user-programmable map decoder for th e GCSR. The GCSR
map decoder allows you to program the star ting ad dress of the GCSR in the VMEbus
short I/O space.
Memory Maps
3
MVME167/D33-29
Page 58
3
Operating Instructions
Software Initia li za tion
Most functions that have been done with switches or jumpers on other modules are
done by setting control regis ters on the MVME167. At powerup or reset, the EPROMs
that contain the 167Bu g debuggin g package set up th e default valu es of many of th ese
registers.
Specific programming details may be determined by study of the MC68040 Microprocessor User’s Manual . Then check the details of all the MVME167 onbo ard
registers as given in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide.
Multi-MPU Programming Considerations
Good programming practice dictates that only one MPU at a time have control of the
MVME167 control registers.
Of particular note are:
registers that modify the address map;
registers that require two cycles to access; and
VMEbus interrupt request registers.
Local Reset Operation
Local reset (LRST) is a subset of system reset (SRST). Local reset can be generated
five ways: expiration of t he watchdog timer, pressing t he front panel RESET switch (if
the system controller function is disabled), by asserting a bit in the board control
register in the GCSR, by SYSRESET*, or by powerup reset.
Note
Any VMEbus access to the MVME167 while it is in the reset state is ignored. If a
global bus timer is enabled, a bus error is generated.
The GCSR allows a VMEbus master to reset the local bus. This
feature is very dangerous and should be used with caution. The
local reset feature is a partial system reset, not a complete
system reset such as powerup reset or SYSRESET*. When the
local bus reset signal is asserted, a local bus cycle may be
aborted. The VMEchip2 is connected to both the local b us and
the VMEbus and if the aborted cycle is bound for the VMEbus,
erratic operation may result. Communications between the local
processor and a VMEbus master should use interrupts or
mailbox locations; reset should not be used in normal
communications. Reset should be used only when the local
processor is halted or the local bus is hung and res et is the last
resort.
3-30MVME167 Single Board Computer User’s Manual
Page 59
FUNCTIONAL
DESCRIPTION
Introduction
This chapter provides a block diagram level description for the MVME167 module.
The functional description pr ovides an o verview of the module, fol lowed by a det ailed
description of several blocks of the module. The block diagram of the MVME167 is
shown in Figure 4-1. MVME167 Main Modu le Block Diagram on page 4-10. The block
diagram of the parity DRAM mezzanine module of the MVME167 is shown as Figure
4-2. Parity DRAM Mezzanine Module Block Diagram on page 4-11. The block
diagram of the ECC DRAM mezzanine module of the MVME167 is shown as Figure
4-2. Parity DRAM Mezzanine Module Block Diagram on page 4-11.
Descriptions of the other b locks of t he MVME167, inclu ding prog rammabl e register s
in the ASICs and peripheral chips, are given in the MVME166/MVME167/MVME187 Single Board Computer s Programmer’s Reference Guide. Refer to it for the rest of the
functional description of the MVME167 module.
MVME167 Functional Description
4
The MVME167 is a high functionality VMEbus single b oard computer designed
around the MC68040 chip. It has 4/8 /16/3 2/64/1 28/2 56MB of d ynamic RAM, a SC SI
mass storage interface, four serial ports, a printer port, and an Ethernet transceiver
interface.
Data Bus Structure
The local data bus on the MVME167 is a 32-bit synchronous bus that is based on the
MC68040 bus, and su pports burst transf ers and snooping. The various local bus master
and slave devices use the local bus to communicate. The local bus is arbitrated by
priority type arbiter and the priority of the local bus masters from highest to lowest is:
82596CA LAN, CD2401 serial (t hrough the PCCch ip2), 53C710 SCSI, VMEbus, and
MPU. In the general case, any master can access any slave; however, not all
combinations pass the common sense test. Refer to the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide and to the user’s guide for each device to determine its port size, data bus
connection, and any restrictions that apply when accessing the device.
MVME167/D34-1
Page 60
Functional Description
MC68040 MPU
The MC68040 processor is used on the MVME167. The MC68040 has on-chip
instruction and data caches and a floating point proce ssor. Refer to the MC68040 user’s
manual for more information.
EPROM
4
There are four 44-pin PLCC/CLCC EP ROM sockets for 27C102JK or 2 7C202JK type
EPROMs. They are organized as two 3 2-bit wide banks that sup port 8-, 16-, and 32-b it
read accesses. The EPROMs are mapped to local bus address 0 following a local bus
reset. This allows the MC68040 to access the stack pointer and execution address
following a reset. The EPROMs are controlled by the VMEchip2. The map decoder,
access time, and when they appear at address 0 is p rogrammable. For more detail, refer
to the VMEchip2 in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide.
SRAM
The boards include 128KB o f 32-bit wi de static RAM t hat supports 8-, 16-, and 32 -bit
wide accesses. The SRAM allows the debugger to operate and limited diagnostics to
be executed without the DRAM mezzanine. The SRAM is controlled by the
VMEchip2, and the access time is programmable. Refer to the VMEchip2 in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for more detail. The boards are populated with 100 ns SRAMs .
SRAM battery backup is optionally available on the MVME167. The battery backup
function is pr ovided by a Dallas DS1 210S. Only one backup po wer source is suppo rted
on the MVME167.
Each time the MVME167 is powered, the DS1210S checks power source and if the
voltage of the backup source is less than two volts, the second memory cycle is
blocked. This allows software to pr ovide an early warning to avo id data loss. Because
the DS1210S may block the second access, the software should do at least two accesses
before relying on the data.
Optionally, the MVME167 provides jumpers that allow the power source of the
DS1210S to be connected to the VMEbus +5 V STDBY pin or the onboard battery.
The optional power source SRAM is a socketed Sanyo CR2430 battery. A small
capacitor is provided to allow the battery to be quickly replaced without data loss.
The lifetime of the battery is very depe nd ent on the ambient temper ature of the bo ard
and the power-on duty cycle. The FB1225 and CR2430 lithium batteries should
provide at least two years of back up time with the board po wered off and the board at
4-2MVME167 Single Board Computer User’s Manual
Page 61
MVME167 Functional Description
40° C. If the power-on duty cycle is 50% (the board is powered on half of the time),
the battery lifetime is four years. At lower ambient temperatures the backup time is
greatly extended and may approach the shelf life of the battery.
When a board is stored, if the battery is present, it should be disconnected to prolong
battery life. This is especially important at high ambient temperatures. MVME167
boards with battery backup are shipped with the batteries disconnected.
The power leads from the battery ar e exposed on the solder sid e of the board, therefor e
the board should not be placed on a conductive surface or stored in a conductive bag
unless the battery is removed.
!
WARNING
❏Do not short circuit.
❏Do not disassemble, deform, or apply excessive pressure.
❏Do not heat or incinerate.
❏Do not apply solder directly.
❏Do not use different models, or new and old batteries together.
❏Do not charge.
4
Lithium batteries incorporate inflammable materials such as
lithium and organic solvents. If lithium batteries are mistreated
or handled incorrectly, they may burst open and ignite, possibly
resulting in injury and/or fire. When dealing with lithium
batteries, carefully follow the precautions listed below in order
to prevent accidents.
❏Always check proper polarity.
To remove the battery from the module, carefully pull the battery from the socket.
Onboard DRAM
The MVME167 onboard DRAM is located on a mezzanine board. The mezzanine
boards are available in different sizes and with parity protection or ECC protection.
Mezzanine board sizes are 4, 8, 16, or 32MB (parity), or 4, 8, 16, 32, 64, or 128MB
(ECC); two mezzanine boards may be stacked to provide 256MB of onboard RAM.
The main board and a single mezzanine board together take one slot. The stacked
configuration requires two VMEboard slots. Motorola software does support mixed
parity and ECC memory boards on the same main board. The DRAM is four-way
interleaved to efficiently support cache burst cycles. The parity mezzanines are only
supported on 25 MHz main boards.
MVME167/D34-3
Page 62
4
Functional Description
The DRAM map decoder can be programmed to accommodate different base
address(es) and sizes of mezzanine boards. The onboard DRAM is disabled by a local
bus reset and must be programmed before the DRAM can be accessed. Refer to the
MEMC040 or the MCECC in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for detailed programming information.
Most DRAM devices require some number of access cycles before the DRAMs are
fully operational. Normally this requirement is met by the onboard refresh circuitry
and normal DRAM initialization. Ho wever, software should insure a minimum of 10
initialization cycles are performed to each bank of RAM.
Battery Backed Up RAM and Clock
The MK48T08 RAM and clock chip is used on the MVME167. This chip provides a
time of day clock, oscillator, crystal, power fail detection, memory write protection,
8KB of RAM, and a battery in one 28-pin package. The clock provides seconds,
minutes, hours, day, date, month, and year in BCD 24-hour format. Corrections for
28-, 29- (leap year), and 30-day months are automatically made. No interrupts are
generated by the clock. The MK48T08 is an 8 bit device; however, the interface
provided by the PCCchip2 supports 8-, 16-, and 32-bit accesses to the MK48T08.
Refer to the PCCchip2 in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide and to the MK48T08 data sheet for
detailed programming information.
VMEbus Interface
The local bus to VMEbus interface, the VMEbus to local bus interface, and the
local-VMEbus DMA controller functions on the MVME167 are provided by the
VMEchip2. The VMEchip2 can also provide the VMEbus system controller functions .
Refer to the VMEchip2 in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for detailed programming information.
I/O Interfaces
The MVME167 provides onbo ard I/O for many system ap plications. The I/O functions
include serial ports, printer port, Ethernet transceiver interface, and SCSI mass storage
interface.
Serial Port Interface
The CD2401 serial controller chip (SCC) is used to implement the four serial ports.
The serial ports support the standard baud rates (110 to 38.4K baud). The four serial
ports are different functionally because of the limited number of pins on the P2 I/O
connector. Serial port 1 is a minimum function asynchronous port. It uses RXD, CTS,
TXD, and RTS. Serial ports 2 and 3 are full function asynchronous ports. They use
RXD, CTS, DCD, TXD, RTS, and DTR. Serial port 4 is a full function asynchron ous
4-4MVME167 Single Board Computer User’s Manual
Page 63
Note
MVME167 Functional Description
or synchronous por t. It can operat e at synchronou s bit rate s up to 64 k bits per seco nd.
It uses RXD, CTS, DCD, TXD, RTS, and DTR. It also interfaces to the synchronous
clock signal lines. Refer to the MVME166/MVME167/MVME1 87 Si ngle Boar d Computers Programmer’s Reference Guide for drawings of the serial port interface
connections.
All four serial ports use EIA-232-D drivers and receivers located on the main board,
and all the signal lines are routed to the I/O connector. The configuration headers are
located on the main board and the MVME712X transition board. An external I/O
transition board such as the MVME712X should be used to convert the I/O connector
pinout to industry-standard connectors.
The MVME167 board hardware ties the DTR signal from the
CD2401 to the pin labeled RTS at connector P2. Likewise, RTS
from the CD2401 is tied to DTR on P2. Therefore, when
programming the CD2401, assert DTR when you want RTS,
and RTS when you want DTR.
4
The interface provided by the PCCchip2 allows the 16-bit CD2401 to appear at
contiguous addresses; however, accesses to the CD2401 must be 8 or 16 bits. 32-bit
accesses are not permitted. Refer to the CD2401 data sheet and to the PCCchip2 in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for detailed programming information.
The CD2401 supports DMA operations to local memory. Because the CD2401 does
not support a retry operation necessary to break VMEbus lockup condition s, the
CD2401 DMA controllers should not be programmed to access the VMEbus. The
hardware does not restrict the CD2401 to onboard DRAM.
Parallel Port Interface
The PCCchip2 provides an 8-bit bidirectional parallel port. All eight bits of the port
must be either inputs or outputs (no individual selection). In addition to the 8 bits of
data, there are two control pins and five status pins. Each of the status pins can generate
an interrupt to the MPU in any of the following programmable conditions: high level,
low level, high-to-low transition, or low-to-high transition. This port may be used as a
Centronics-compatible parallel printer port or as a general parallel I/O port.
When used as a parallel printer port, the five status pins function as: Printer
Acknowledge (ACK), Printer Fault (FAULT*), Printer Busy (BSY), Printer Select
(SELECT), and Printer Paper Error (PE); while the control pins act as Printer Strobe
(STROBE*), and Input Prime (INP*).
MVME167/D34-5
Page 64
4
Functional Description
The PCCchip2 provides an auto-strobe featu re similar to that of the MVME147 PCC.
In auto-strobe mode, after a write to the Printer Data Register, the PCC chip2
automatically asserts the STROBE* pin for a selected time specified by the Printer Fast
Strobe control bit. In manual mode, the Printer Strobe control bit directly controls the
state of the STROBE* pin.
Refer to the MVME166/MVME16 7/M VME1 87 Si ng le Boar d Comp ut ers Programmer’s Reference Guide for drawings of the printer port inter face connections.
Ethernet Interface
The 82596CA is used to implement the Ethernet transceiver interface. The 82596CA
accesses local RAM using DMA operations to perform its normal function s. Because
the 82596CA has small internal buffers and the VMEbus has an undefined latency
period, buffer overrun may occur if the DMA is programmed to access the VMEbus.
Therefore, the 82596CA should not be programmed to access the VMEbus.
Every MVME167 is assigned an Ethernet Station Address. The address is
$08003E2XXXXX where XXXXX is the unique 5-nibble number assigned to the
board (i.e., every MVME167 has a different value for XXXXX).
Each module has an Ethernet Station Address displayed on a label attached to the
VMEbus P2 connector. In addition, the six by tes including the Ethernet address are
stored in the configuration area of the BBRAM. That is, 080 03E2XXXXX is stored in
the BBRAM. At an address of $FFFC1F2C, the upper four bytes (08003E2X) can be
read. At an address of $FFFC1F30, the lower two bytes (XXXX) can be read. Refer to
the BBRAM, TOD Clock memory map description in Chapter 3. The MVME167
debugger has the capability to retrieve or set the Ethernet address.
If the data in the BBRAM is lost, the user should us e the number on the VMEbus P2
connector label to restore it.
The Ethernet transceiver interface is located on the MVME1 67 main mo dule, and the
industry standard connector is located on the MVME712X transition module.
Support functions for the 82596CA are provided by the PCCchip2. Refer to the
82596CA user’s guide and to the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for detailed programming information.
SCSI Interface
The MVME167 provides for mass storage subsystems through the industry-standard
SCSI bus. These subsyst ems may i nclu de h ard and floppy disk dri ves, streaming tape
drives, and other mass storage devices. The SCSI interface is implemented using the
NCR 53C710 SCSI I/O controller.
4-6MVME167 Single Board Computer User’s Manual
Page 65
Support functi ons for t he 53C710 are provid ed by th e PCCchip2. R efer to t he 53C710
user’s guide and to the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for detailed programming information.
SCSI Termination
The system configurer must ensure that the SCSI bus is properly terminated at both
ends. On the MVME167, sockets are provided for the terminators on the P2 transition
board. If the SCSI bus ends at the P2 transition board, then termination resistors must
be installed on the P2 transition board. +5V power to the SCSI bus TERM power line
and termination resistors is provided through a fuse located on the P2 transition board.
Local Resources
The MVME167 includes many resources for the local processor. These include tick
timers, software programmable hardware interrupts, watchdog timer, and local bus
timeout.
Programmable Tick Timers
MVME167 Functional Description
4
Four 32-bit programmable tick timers with 1 µs resolution are provided, two in the
VMEchip2 and two in the PCCchip2. The tick timers can be pro grammed to gen erate
periodic interrupts to the processor. Refer to the VMEchip2 and PCCchip2 in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for detailed programming information.
Watchdog Timer
A watchdog timer function is provided in the VMEchip2. When the watchdog timer is
enabled, it must be reset by software within the programmed time or it times out. The
watchdog timer can be programmed to generate a SYSRESET signal, local reset
signal, or board fail signal if it times out. R e fer to the VMEchip 2 in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for detailed programming information.
Software-Programmable Hardware Interrupts
Eight software-programmable hardware interrupts are provided by the VMEchip2.
These interrupts allow software to create a hardware interrupt. Refer to the VMEchip2
in the MVME166/MVME167/MVME187 Single Board Computers Programmer’s Reference Guide for detailed programming information.
Local Bus Timeout
The MVME167 provides a timeout function for the lo cal bus. When the timer is
enabled and a local bus access times out, a Transfer Error Acknowledg e (TEA) signal
is sent to the local bus master. The timeout value is selectable by software for 8 µsec,
64 µsec, 256 µsec, or infinite. The local bus timer does not operate during VMEbus
MVME167/D34-7
Page 66
Functional Description
bound cycles. VMEbus bound cycles are timed by the VMEbus access timer and the
VMEbus global timer. Refer to the VMEchip2 in the
MVME166/MVME167/M VME187 Sing le Boa rd Comput ers Pr ogrammer’s Reference
Guide for detailed programming information.
Timing Performance
4
This section provides the performance information for the MVME167. Various
MVME167s are designed to operate at 25 MHz or 33 MHz.
Local Bus to DRAM Cycle Times
The PCCchip2 and VMEchip2 have the same local bus interface timing as the
MC68040, therefore the following cycle times also apply to the PCCchip2 and the
VMEchip2. Read accesses to onboard DRAM require 4 bus clock cycles with parity
checking off. With parity checking on and the bus error reported in the current cycle,
5 bus clock cycles are required. Write accesses to onboard DRAM require 2 bus clock
cycles.
Burst read accesses require 7 (4-1-1-1) bus clock cycles with parity check off. With
parity checking on and the bu s error reported in the curren t cycle, 8 (5-1-1-1) bus clock
cycles are required. Burst write cycles require 5 (2-1-1-1) bus clock cycles.
The parity DRAM is organized as fou r banks; thi s requires t he use of 256K by 4 chip s
for the data portion of the RAM and 256K by 4 chips with the write-per-bit option for
the parity bits. The use of four banks allows X-1-1-1 b ursts with parity on.
ROM Cycle Times
The ROM cycle time is programmable from 4 to 11 bus clock cycles. The data
transfers are 32 bits wide. Refer to the MVME166/MVME167/MVME1 87 Single Board Computers Programmer’s Reference Guide.
SCSI Transfers
The MVME167 includes a SCSI mass storage bus interface with DMA controller. The
SCSI DMA controller uses a FIFO buffer to interface the 8-bit SCSI bus to the 32-bit
local bus. The FIFO buffer allows the SCSI DMA controller to efficiently transfer data
to the local bus in four longword bursts. This reduces local bus usage by the SCSI
device.
The first longword transfer of a burst, with snooping disabled, takes four bus clocks
with parity off a nd five bus clocks with parity on. Each of the remai ning three transfer s
requires one bus clock.
The transfer rate of the DMA controller is 44 MB/sec at 25 MHz with parity off.
Assuming a continuous transfer rate of 5 MB/sec on the SCSI bus, 12% of the local
bus bandwidth is used by transfers from the SCSI bus.
4-8MVME167 Single Board Computer User’s Manual
Page 67
LAN DMA Transfers
The MVME167 includes a LAN interface with DMA controller. The LAN DMA
controller uses a FIFO buffer to interface the serial LAN bus to the 32-bit local bus.
The FIFO buffer allows the LAN DMA controller to efficiently transfer data to the
local bus.
The 82596CA does not execute MC68040 compatible burst cycles, therefor e the LAN
DMA controller does not use burst transfers. Parity DRAM write cycles require 3
clock cycles, and read cycles r equire 5 clock cycles with parity off and 6 clock cycles
with parity on.
The transfer rate of the LAN DMA controller is 20 MB/sec at 25 MHz with parity off.
Assuming a continuo us transfer rat e of 1 MB/s ec on the LAN bus, 5% o f the local bus
bandwidth is used by transfers from the LAN bus.
Remote Status and Control
The remote status and control connector, J3, is a 20-pin connector located behind the
front panel of the MVME167. It provides system designers the flexibility to access
critical indicator and reset functions. This allows a sy stem designer to construct a
RESET/LED panel that can be located remotely from the MVME167.
MVME167 Functional Description
4
In addition to the LED and RESET switch access, this connector also includes two
general purpose TTL-level I/O pins and one general purpose interrupt pin which can
also function as a trigger input. This interrupt pin is level programmable.
MVME167/D34-9
Page 68
Functional Description
4
MEZZANINE
P4, P5
SHEET 8
SHEET 20
J3
J4, J5
SHEET 7
MC68040 MPU
SHEET 27
IPL COMBINER
SHEET 28
CLOCKS
GENERATOR
SHEET 10
BBRAM AND TOD
SHEET 23
PCCCHIP2
SHEET 21
SCSI INTERFACE
SHEET 18
LANCE
SHEET 19
VMECHIP2
SHEET 12
SERIAL PORT
SHEETS 24-26
PRINTER PORTS
SHEET 22
SIA
SHEET 20
VME BUFFERS
SHEETS 13-15
P2
SHEET 6
P1
SHEET 5
SERIAL
PRINTER
SCSI
LAN
VME
LEDS AND
SWITCHES
REMOTE
RESET/ABORT/LEDS
SHEET 9
Figure 4-1. MVME167 Main Module Block Diagram
4-10MVME167 Single Board Computer User’s Manual
SRAMS AND
EPROMS
SHEETS 16-17
BATTERY/BACKUP
SHEET 28
VME
1473 9405
Page 69
MVME167 Functional Description
4
CONNECTOR
SHEET 5
CONNECTORS
SHEET 4
ADDRESS BUS
DATA BUS
ADDRESS MUX
SHEET 7
DATA MUX
SHEET 13, 14
TIMING CONTROL
SHEET 6
MULTIPLEXED ADDRESS
RDA BUS
RDB BUS
RDC BUS
RDD BUS
PARITY DATA
DRAM STROBES
MEMORY ARRAY
BANK A
SHEET 8
MEMORY ARRAY
BANK B
SHEET 9
MEMORY ARRAY
BANK C
SHEET 10
MEMORY ARRAY
BANK D
SHEET 11
PARITY MEMORY
SHEET 12
Figure 4-2. Parity DRAM Mezzanine Module Block Diagram
MVME167/D34-11
ACKNOWLEDGE
CONTROL
SHEET 15
10887.00 9401
Page 70
Functional Description
10885.00 9401
4
SHEET 11 , 12
BLOCKS 0 AN D 1
LOWER DRAM ARRAY
DRAM ADDR, CNTRL, LOWER DATA
SHEET 7
ADDDRESS MUX,
LOWER DATA MUX
TIMING_CONTROL,
SHEET 6
BOARD DEFAULTS
SHEET 13,14
BLOCKS 0 AN D 1
UPPER DRAM ARRAY
DRAM ADDR, CNTRL, UPPER DATA040 ADDR, CNTRL, U DATA
SHEET 8
ADDRESS MUX,
UPPER DATA MUX
TIMING_CONTROL,
Figure 4-3. ECC DRAM Mezzanine Module Block Diagram
4-12MVME167 Single Board Computer User’s Manual
040 ADDR, CNTRL, L DATA
040 LOCAL BUS
SHEET 4, 5
CONNECTORS
Page 71
EIA-232-D
Introduction
The EIA-232-D standard is the most widely used terminal/computer and
terminal/modem interface, and yet it is not fully understood. This may be because not
all the lines are clearly defined, and many users do not see the need to follow the
standard in their applications. Many times designers think only of their own
equipment, but the state of the art is computer-to-computer or computer-to-modem
operation. A system should easily connect to any other.
The EIA-232-D standard was originally developed by the Bell System to connect
terminals via modems. Several handshaking lines were included for that purpose.
Although handshaking is unnecessary in many applications, the lines themselves
remain part of many designs because they facilitate troubleshooting.
Table A-1 lists the standard EIA-232-D interconnections. To interpret this information
correctly, remember that EIA-232-D was intended to connect a terminal to a modem.
When computers are connected to each other without modems, one of them must be
configured as a terminal (data terminal equipment: DTE) and the other as a modem
(data circuit-terminating equipment: DCE). Since computers are normally configured
to work with terminals, they are said to be configured as a modem in most cases.
INTERCONNECTIONS
A
Signal levels must lie between +3 and +15 volts for a high level, and between
-3 and -15 volts for a low level. Connecting units in parallel may produce out-of-range
voltages and is contrary to EIA-232-D specifications.
MVME167/D3A-1
Page 72
A
EIA-232-D Interconnections
Table A-1. EIA-232-D Interconnections
Pin NumberSignal Mnem oni cSignal Name and Desc ription
01Not used.
02TxDTRANSMIT DATA. Data to be transmitted; input to the modem from the
terminal.
03RxDRECEIVE DATA. Data which is demodulated from the receive line; output
from the modem to t h e t erm inal.
04RTSREQUEST TO SEND. Input to the modem from the terminal when required
to transmit a message. With RTS off, the modem carrier remains off. When
RTS is turned on, the modem immediat e ly turns on the carrier.
05CTSCLEAR TO SEND. Output from the modem to the terminal to indicate that
message transmission ca n begin. When a modem is used, CTS foll ows the
off-to-on transition of RTS after a time delay.
06DSRDATA SET READY. Output from the modem to the terminal to indicate that
the modem is ready to transmit data.
07SIG-GNDSIGNAL GROUND. Common return line for all signals at the modem
interface.
08DCDDATA CARRIER DETECT. Output from the modem to the terminal to
indicate that a valid carrier is being received.
09-14Not used.
15TxCTRANSMIT CLOCK (DCE). Output from the modem to the terminal; clocks
data from the te rm inal to the modem .
16Not used.
17RxCRECEIVE CL OCK. Output from the modem to the terminal; clocks data
from the modem to t h e t erm inal.
18, 19Not used.
20DTRDATA TERMINAL READY. Input to the modem from the term ina l;
indicates that the terminal is re ady to send or receiv e data.
21 Not used.
22RIRING INDICATOR. Output from the modem to the terminal; indicates to the
terminal tha t a n incoming call is pr es e n t. The terminal caus e s the modem to
answer the phone by carrying DTR true while RI is active.
23Not used.
24TxCTRANSMIT CLOCK (DTE). Input to modem fro m termina l; same fu ncti on
as TxC on pin 15.
25BSYBUSY. Input to modem from terminal. A positive EIA signal applied to this
pin causes the modem to go off-hook and make the associated phone busy.
NOTES: 1. A high EIA-232-D signal level is +3 to +15 volts. A low level is -3 to -15 volts.
Connecting units in parallel may produce out-of-range voltages and is contrary
to specifications.
A-2MVME167 Single Board Computer User’s Manual
Page 73
2. The EIA-232-D interface is intended to connect a terminal to a modem. When
computers are connect ed without modems, one must be configured as a modem
and the other as a terminal.
Levels of Implementation
There are several levels of conformance that may be appropriate for typical EIA-232D interconnections. The bare minimu m requirement is the two data lines and a ground.
The full implementation of EIA-232-D requires 12 lines; it accommodates automatic
dialing, automatic answering, and sync hronous transmission. A middle-of-the-road
approach is illustrated in Figure A-1.
Signal Adaptations
One set of handshaking signals frequently implemented are RTS and CTS. CTS is used
in many systems to inhibit trans mission until the signal is high. In th e modem
application, RTS is turned around and returned as CTS after 150 microseconds. RTS
is programmable in some systems to work with the older type 202 modem (half
duplex). CTS is used in some systems to provi de flow control to avoid b uffer overflow.
This is not possible if modems are used. It is usually necessary to make CTS high by
connecting it to RTS or to some source of +12 volts such as the resistors shown in
Figure A-1. CTS is also frequently jumpered to an MC1488 gate which has its inputs
grounded (the gate is provided for this purpose).
Levels of Implementation
A
Another signal used in many systems is DCD. The origin al purpos e of this signal was
to tell the system that the carrier tone from the distant modem was being received. This
signal is frequently used by the software to displ ay a message like
PRESENT
is designed prop erly to use this signal and i s not connected t o a modem, the sign al must
be provided by a pullup resistor or gate as described above (see Figure A- 1).
Many modems expect a DTR high signal and issue a DSR. These signals are used by
software to help prompt th e operator about poss ible causes of troubl e. The DTR signal
is sometimes used to disconnect the phone circu it in preparation for another auto matic
call. It is necessary to provide these signals in order to talk to all possible modems (see
Figure A-1).
to help the user to diagnose failure to communicate. Obviou sly, if the system
CARRIER NOT
MVME167/D3A-3
Page 74
A
EIA-232-D Interconnections
Sample Configurations
Figure A-1 is a good minimum configur ation that almost al ways works. If the CTS and
DCD signals are not received from the modem, the jumpers can be moved to
artificially provide the needed signal.
Figure A-2 shows a way of wiring an EIA-232-D connector to enable a computer to
connect to a basic terminal with only three lines. This is feasible because most
terminals have a DTR signal that is ON, and which can be used to pull up the CTS,
DCD and DSR signals. Two of these connectors wired back-to-back can be used. In
this implementation, however, di agnostic messages th at might oth erwise be ge nerated
do not occur because all the handshaking is bypassed. In addition, the TX and RX lines
may have to be crossed since TX from a terminal is outgoing but the TX line on a
modem is an incoming signal.
EIA-232-D CONNECTOR
GND1
TxD2
RxD3
RTS4
CTS5
A
DSR6
GND7
DCD8
DTR20
....
Figure A-2. Minimum EIA-232-D Connection
MVME167/D3A-5
Page 76
A
EIA-232-D Interconnections
Proper Grounding
Another subject to consider is t he 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 the chassis 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 ma y
also produce electrical noise that causes errors in data transmission. That is why Figure
A-1 shows no connection for pin 1. Normally, pin 7 should only be connected to the
CHASSIS GROUND at one point; if several terminals are used with one computer, the
logical place for that point is at the computer. The terminals should not have a
connection between the logic ground return and the chassis.
A-6MVME167 Single Board Computer User’s Manual
Page 77
Index
When using this index, keep in mind that a page number indicates only where
referenced material begins. It may extend to the page or pages following the page
referenced.
Numerics
167Bug (see debug monitor and
MVME167Bug) 1-6, 2-2, 2-6, 3-1,
3-30
53C710 (see SCSI Controller) 4-7
53C710 SC SI memory map 3-24
82596CA (see Ethernet and LAN) 4-6
82596CA Ethernet LAN memory map
LAN (see 82596CA and Ethernet) 4-6
LAN DMA transfers 4-9
LAN FIFO buffer 4-9
LAN transceiver 2-8
LCSR (Local Control and Status Regis-
ters) (see VMEchip2 LCSR) 2-2
LEDs 3-2
levels of implementation A-3
LFM (linear feet per minute) 1-3
linear feet per minute (LFM) 1-3
little endian mode 3-24
Local Area Network (see LAN) 4-6
local bus 4-8
local bus access 4-8
local bus memory map 3-3, 3- 4
local bus timeout 4-8
local bus to DRAM cycle times 4-8
Local Control and Status Registers
(LCSR) (see VMEchip2 LCSR)
2-2
local I/O devices memory map 3-5
local reset (LRST) 3-1, 3-30
local reset operation 3-30
local resources 4-7
local SCSI ID 3-28
location monitors 2-8
longword 1-9
LRST (local reset) 3-1, 3-30
er J8 2-5
SRAM battery backup 4-2
SRST (system reset) 3-1, 3-30
static RAM (SRAM) 4-2
support information 1 -8
SYSRESET* (see system reset) 3-1, 3-30
system considerations 2-7
system console terminal 1-6
system controller 2-2
system controller function 2-2, 3-30
system controller header J2 2-2
system mode 1-6
system reset (SRST) 3-30
system reset (SRST) (see SYSRESET*) 3-1
SYSTEM V/68 1-6
systems serial ID 3-28
VMEbus 3-29
VMEbus accesses to the local bus 3-29
VMEbus interface 4-4
VMEbus memory map 3-29
VMEbus short I/O me mory map 3-29
VMEbus specification 1-8
VMEchip2 1-5
VMEchip2 GCSR (Global Control and
local bus 4-8
timers 4-7
timing performance 4-8
TOD clock memory map 3-26
transfer type (T T ) signals 3-3
transition modules 1-5, 4-5
transparent mode A-4
MVME167/D3IN-5
I
N
D
E
X
Page 82
Index
I
N
D
E
X
IN-6MVME167 Single Board Computer User’s Manual
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.