and the Motorola logo are registered t r ademarks of Motorola, Inc.
MC68040™ and MC68060™ are trademarks of Motorola, Inc.
All other products ment io ned i n this document are trade marks or registered trade marks 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, shoul d foll ow these warni ngs and al l other sa fety pr ecauti ons nece ssary fo r the safe ope ration 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 su pplied wi th a three-c onductor A C power ca ble, the po wer cable m ust be plug ged into an a pproved
three-contact electrical outlet, with the grounding wire (green/yellow) reliably connected to an electrical ground
(safety ground) at the power outlet. The power jack and mating plug of the power cable meet International
Electrotechnical Commission (IEC) safety standards and local electrical regulatory codes.
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 adjust ment. Service pe rsonnel should n ot replace compon ents with power c able connected. Under certain
conditions, dangero us voltages may exist even with the power cable remo ved. T o avoid inju ries, such pers onnel should
always disconnect power and discharge circuits before touching components.
Use Caution When Exposing or Handling a CRT.
Breakage of a Cathode-Ray Tube (CRT) causes a high-velocity scattering of glass fragments (implosion). To prevent
CRT implosion, do not handl e the CRT and avoid rough handling o r jarring of t he equipment . Handling o f a CRT
should be done only by qualified service personnel using approved safety mask and gloves.
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.
W arn ings , such as th e exa mple be low, prece de po tent ially danger ous p roce dures th roug hout th is manu al . Instr uction s
contained in the warnings m ust be follow ed. You should also employ all ot her safety precautions w hich you dee m
necessary for the operation of the equi pment 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 94V-0 by UL-recognized manufacturers.
EMI Caution
This equipment ge ner ates, uses a nd can radi ate el ectro magne tic energy . It
!
Caution
This product contains a lithium battery to power the clock and calendar circuitry.
!
Caution
may cause or be susceptible to electromagnetic interference (EMI) if not
installed and used with adequate EMI protection.
Lithium Battery Caution
Danger of explosion if battery is re placed incorrect ly. Replace battery only
with the same or equivalent type recommended by the equipment
manufacturer. Dispose of used batteries according to the manufacturer’s
instructions.
!
Attention
!
Vorsicht
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
é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 ode r einen vom Herstel ler empfohle nen Typ. Entsorgu ng
gebrauchter Batterien nach Angaben des Herstellers.
CE Notice (European Community)
Motorola Compute r Group pro ducts wi th the CE mar king co mply with the EMC Dir ective
(89/336/EEC). Compliance with this directive implies conformity to the following
European Norms:
EN55022 “Limits and Methods of Meas urement of Radio Int erferen ce Chara cteri stic s
of Information Technology Equipment”; this product tested to Equipment Class B
EN50082-1:1997 “Electromag netic Compatibi lit y—Gener ic Im munity St andard , Part
1. Residential, Commercial and Light Industry”
System products al so fulf ill EN60950 ( product saf ety) which i s essenti ally the r equirement
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 CE-marked system will maintain the
required EMC /safety performance.
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. a ssumes n o lia bility r esulti ng from any omissio ns in this docu ment, or from
the use of the information obtained therein. Motorola reserves the right to revise this
document and to ma ke c hanges from time to time in the conten t he reof without obliga ti on
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 b e published commerci ally in print o r electronic for m, edited, transla ted,
or otherwise altered without the permission of Motorola, Inc.
It is possible th at t hi s publication may contain reference to or infor m at ion about Motorola
products (machines and pr ograms), progra mming, or services that are not av ailable 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 t he Rig hts i n Technical Data clause a t DFARS 252.227-7013 (Nov.
1995) and of the Rights in Noncommerc ial Computer Software and Docume ntation c lause
at DFARS 252.227-7014 (Jun. 1995).
Motorola, Inc.
Computer Group
2900 South Diablo Way
Tempe, Arizona 85282
Contents
About This Manual
Overview of Contents...............................................................................................xxii
Comments and Suggestions......................................................................................xxii
Conventions Used in This Manual...........................................................................xxiii
Table C-3. Related Specifications ............................................................................C-3
xix
xx
About This Manual
This manual provides board-level information and detailed ASIC
information, including register bit descriptions, for the MVME167PAxxSE and MVME177PA-xxSE series of VME single-board computers,
known collectively as the ‘‘MVME1X7P’’.
The “Petra” chip that distinguishes MVME167P and MVME177P single-
board computers is an application-specific integrated circuit (ASIC) used
on various Motorola VME boards which combines a va riety of functions
previously implemented in other ASICs (among them the MC2 chip, the
IP2 chip, and the MCECC chip) in a single ASIC. On the MVME1X7P,
the “Petra” chip repl aces the MCECC ASIC. As of the public ation date, the
information presented in this manual applies to the following
MVME1X7P models:
Model NumberCharacteristics
MVME167PA-24SE25MHz MC68040, 16MB SDRAM, SCSI and Ethernet
MVME167PA-25SE25MHz MC68040, 32MB SDRAM, SCSI and Ethernet
MVME167PA-34SE33MHz MC68040, 16MB SDRAM, SCSI and Ethernet
MVME167PA-35SE33MHz MC68040, 32MB SDRAM, SCSI and Ethernet
MVME167PA-36SE33MHz MC68040, 64MB SDRAM, SCSI and Ethernet
MVME177PA-54SE50MHz MC68060, 16MB SDRAM, SCSI and Ethernet
MVME177PA-55SE50MHz MC68060, 32MB SDRAM, SCSI and Ethernet
MVME177PA-56SE50MHz MC68060, 64MB SDRAM, SCSI and Ethernet
MVME177PA-64SE60MHz MC68060, 16MB SDRAM, SCSI and Ethernet
MVME177PA-65SE60MHz MC68060, 32MB SDRAM, SCSI and Ethernet
MVME177PA-66SE60MHz MC68060, 64MB SDRAM, SCSI and Ethernet
MVME177PA-67SE60MHz MC68060, 128MB SDRAM, SCSI and Ethernet
This manual is intended for anyone who designs OEM systems, adds
capability to an existing compatible system, or works in a lab environment
for experimental purposes. A basic knowledge of computers and digital
logic is assumed. To use this manual, you may also wish to become
familiar with the publications listed in Appendix C, Related
Documentation.
xxi
Overview of Contents
Chapter 1, Programming Issues, describes the board-level hardware
features of MVME1X7P single-board computers. It includes memory
maps and a discussion of some general software considerations such as
cache coherency, interrupts, and bus errors.
Chapter 2, VMEchip2, describes the VMEchip2 ASIC, the local
bus/VMEbus interface chip on MVME1X7P boards.
Chapter 3, PCCchip2, describes the PCCchip2 ASIC. The PCChip2 is a
peripheral channel controller designed to interface an MC680x0compatible local bus to va rious on -board periph eral de vices s uch as SCSI
and LAN controllers.
Chapter 4, MCECC Functions, desc ribes the ECC DRAM controlle r ASIC
(MCECC). On the MVME1X7P boa rds, i t sup plies th e interf ace t o a 144 bit wide DRAM memory system.
Appendix A, Summary of Changes, lists the modifications that
accompanied the introduction of the Petra ASIC on the MVME167P and
MVME177P.
Appendix B, Printer and Serial Port Connections, contains drawings of
the printer and serial port interface connections available with the
MVME167P/MVME177P and MVME712 series transition board.
Appendix C, Related Documenta tion, lists all documentation related to the
MVME167P and MVME177P.
Comments and Suggestions
Motorola welcomes and appreciates your comments on its doc umentation.
We want to know what y ou 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
xxii
You can also submit comments to the following e-mail address:
reader-comments@mcg.mot.com
In all your corres pondence , plea se li st your name, po siti on, and c ompan y.
Be sure to include the title and par t 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.
Conventions Used in This Manual
The following typographical conventions are used in this document:
$dollarspecifies a hexadecimal number
%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 deno tes that the a ctions init iated by th at signal occu r on high to
low transitio n.
xxiii
bold
is used for user inpu t that you t ype just as i t appears ; it is al so 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 dis plays 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 character s by pressing the
Ctrl key and the letter simultaneously, for example, Ctrl-d.
In this manual, assertion and negation are used to specify forcing a signal
to a particular stat e. In parti cular, a ssertion and asser t refe r to a signal tha t
is active or true; negation and negate indicate a signal that is inactive or
false. These terms ar e used independently of the vo ltage level (high or l ow)
that they represent.
xxiv
Data and address sizes are defined as follows:
❏ A byte i s eight bits, numb ered 0 through 7, wit h bit 0 being the leas t
significant.
❏ A word is 16 bits, numbered 0 th rough 15, wit h bit 0 bei ng the le ast
significant.
❏ A longword is 32 bi ts, numbered 0 through 31, with bit 0 being the
least significant.
The terms control bit, status bit, true, and false are used ext ensively in this
document. The term control bit is used to describe a bit in a register that
can be set and cleared under software control. The term true is use d to
indicate that a bit is in the state that enables the function it controls. The
term false is used to indicate that the bit is in the state that disables the
function it controls. In all tables, the terms 0 and 1 are used to describe the
actual value that sh ould be written to the bit, or the value that it yields when
read. The term status bit is used to describe a bit in a regi ster that reflects
a specific condition. The status bit can be read by software to determine
operational or exception conditions.
xxv
xxvi
Introduction
The MVME167P and MVME177P single-board computers are complex
boards that interface both to the VMEbus and the SCSI bus. From a
programming standpoint, their multiple-bus interfaces raise issues of
cache coherency and support of indivisible cycles. There are also various
potential sources of bus error.
This chapter discusses those topics in addition to interrupt handling, the
use of bus timers, and the programming interface to each device on the
board. Programmable regist ers that reside in ASICs (Applicati on-Specific
Integrated Circuit s) on the MVME1X7P boards are covered in the chapters
devoted to those devices.
NoteThe MVME1X7P’s new ’‘Petra’’ ASIC performs the functions
1Programming Issues
1
previously implemented in the MCECC chip. For ease of use in
conjunction with programming models and documentation
developed for earlier boards, however, the structure of this
manual preserves the functional distinctions that formerly
characterized the MCECC ASIC.
The Petra ASIC and Second-Generation MVME1X7 Boards
Due to rapid changes in tec hnology, the productio n of certain ASI Cs used
on various Motorola first- and second-generation VME embedded
controllers and single-board computers has ended. The Petra chip was
developed to replace these discontinued ASICs. In the case of
MVME167/177 series boards, the di scontinue d ASIC is the MCECC chip.
The Petra chip now suppl ies the functi ons formerly implemented in the
MCECC chip.
1-1
1
Programming Issues
The Petra ASIC is functionally compatible with each of the components
that it replaces. In cases where functionality between ASICs is exclusive,
configuration switches or jumpers are provided to let you select the
desired functionality.
In several areas of functionality, the configuration switches provide
backward compatibilit y with earl ier MVME167/17 7 implement ations, but
you can override their settings in software if you wish. A “R/W” by the
corresponding regi ster table entry in this manual denotes inst ances where
this override capability is present.
Where the older technology supported “fast page” or “EDO” DRAM
chips, the Petra memory controllers support SDRAM devices. The two
memory controllers modeled in Petra duplicate the functionality of the
“parity” memory control ler f ound i n the MC ASICs used o n cert ain ot her
boards as well as th at of the “single-bit error correcting/double-bit er ror
detecting” memory controller found in the MCECC ASICs used on the
MVME167/177.
This Programmer’s Reference Guide describes the MCECC model (in
Chapter 4). In the MVME167/177 application, there is logic on the Petra
chip to prevent you from in advertently enabling the MC memory controller
model.
The same SDRAM memory array serves both controller models. The
SDRAM array is 32 data bits wi de with 7 checkbits. Th e array architecture
is a non-interleaved single bank for sizes below 32MB. For array sizes
above 32MB, additional physical memory banks are added but the
architecture remains non-interleaved.
A final note on the SDRAM implementation: The bandwidth between the
SDRAM and local bus is greater than it was wit h the earlier DRAM array.
As a result, software takes less time to execute. Applicatio ns that
incorporate elapsed-time functions which are dependent on code
execution may have problems.
For readers who need to know the ASIC-specific differences between the
previous MCECC and Petra/MCECC programming models in detail,
certain areas of the text in this manual are printed in italics and marked
with change bars (as is done her e). Readers should compare those sections
to the corresp onding se ctions o f the first - and s econd-g eneration manuals.
1-2Computer Group Literature Center Web Site
Introduction
Features
The “Petra” ASIC supplants the MCECC memory controller ASIC on
MVME1X7P boards, performin g the memory control func tions previously
carried out by the MCECC chip: It supplies the programmable int erface for
the ECC-protected 16/32/64/128MB DRAM emulation.
The following table summarizes the features of the MVME167P and
MVME177P single-board computers.
Table 1-1. MVME1X7P Features Summary
FeatureMVME167PMVME177P
Processor25/33MHz 32-bit MC68040
microprocessor
DRAM16/32/64/128MB synchro nous DRAM (SDRAM). Configu rable to emulate
4/8/16/32/64/128MB ECC-protected DRAM
MVME1X7P boards use SDRAM (Synchr onous DRAM ) in place of DRAM.
Up to 64MB SDRAM is available on MVME167P boards; up to 128MB is
available on MVME177P boards.
SRAM128KB SRAM with battery backup
EPROMFour 44-pin JEDEC standard PLCC
TimersFour 32-bit tick timers and watchd og timer in Petra ASIC
Software
Interrupts
I/O Four EIA-232-D configurable serial ports via P2 and transition module
8K by 8 Non-Volatile RAM (NVRAM) and Real-Time Clock (RTC) with
battery backup and watchdog function (SGS-Thomson M48T58)
Two 32-bit tick timers and watchdog timer in VMEchip2 ASIC
Eight software interrupts (including those in the VMEchip2 ASIC)
Parallel (printer) interface via P2 and transition module
SCSI interface with DMA via P2 or LCP2 adapter board
Ethernet transceiver interface via DB15 connector on transition module
50/60MHz 32-bit MC68060
microprocessor
Two 44-pin JEDEC standard PLCC
EPROM sockets
devices with optional write protection
1
http://www.motorola.com/computer/literature1-3
1
Programming Issues
Table 1-1. MVME1X7P Features Summary (Continued)
FeatureMVME167PMVME177P
VMEbus
interface
Switches Two pushbutton switches
Status IndicatorsEight LEDs: Board Fail (FAIL), CPU Status (STAT), CPU Activity (RUN),
VMEbus system controller functions
VMEbus-to-local-bus interface (A32/A24, D32/D16/D8)
Local-bus-to-VMEbus interface (A16/A24/A32, D8/D16/D32)
Programmable interrupter and interrupt handler
Global Control/Status register for interprocessor communications
DMA capability for fast local-memory/VMEbus trans f ers (A16/A24/A32,
D16/D32 (D16/D32/D64 BLT)
(ABORT and RESET)
System Controller (
Activity
(SCSI), VME Activity (VME)
SCON), LAN Activity (LAN), LAN Pow er ( +12V), SCSI
Applicable Industry Standards
These boards conform to the requirements of the following documents:
Figure 1-1 and Figure 1- 2 ar e ge neral block diagrams of the MVME167P
and MVME177P single-board computers.
1-4Computer Group Literature Center Web Site
Introduction
1
Memory Array
ECC SDRAM
16-64MB
Up to 128MB ECC DRAM
Battery Optio n
MPU
SRAM
MC68040
PETRA
Connectors
Mezzanine
VMEchip 2
Interface
128KB
25/33MHZ
PCCCHIP 2
VMEbus
4 44-pin
PLCC
Controller
Ethernet
Compressor
SCSI
I/O Controller
Quad Serial
EPROM
i82696CA
53C710
CD2401
P1
P2
8KB RAM/Clock
Battery Backed
M48T58
Compatible
Parallel I/O
Centronics
Port
2816 0800
Figure 1-1. MVME167P Block Diagram
http://www.motorola.com/computer/literature1-5
1
Programming Issues
Memory Array
ECC SDRAM
16-128MB
Up to 128MB ECC DRAM
Battery Optio n
MPU
SRAM
4MB FLASHPETRA
MC68040
Connectors
Mezzanine
VMEchip 2
Interface
128KB
50/60MHZ
PCCCHIP 2
VMEbus
2 44-pin
PLCC
Controller
Ethernet
Compressor
SCSI
I/O Controller
Quad Serial
EPROM
i82696CA
53C710
CD2401
P1
P2
8KB RAM/Clock
Battery Backed
M48T58
Compatible
Parallel I/O
Centronics
Port
2816 0800
Figure 1-2. MVME177P Block Diagram
1-6Computer Group Literature Center Web Site
Programming Interfaces
The following sections describe the programming interface to devices on
the MVME167P and MVME177P single-board computers. Unless the
section specifies a particular board type, the discussion applies to both
models.
MC680X0 MPU
The MVME167P is based on the MC68040 microprocessor. The
MVME177P is based on the MC68060 microprocessor. Both processors
have on-chip instruction and data caches and a floating-point processor
(refer to the MC68040 and MC68060 user’s manuals for more
information).
Both models are available in various versions with the features listed in
Table 1-1 on page 1-3.
Data Bus Structure
Programming Interfaces
1
The local bus for all si ngl e-board computers described in this manual is a
32-bit synchronous bus, which is based on an MC68040-compatible bus
and which supports burst transfers. Throughout this manual this bus is
referred to as the Local Bus. The various Local Bus master and slave
devices use the Local Bus to c ommunicate. Th e Local Bus is arbi trated b y
priority type a rbiter. The pr iority o f the Loca l Bus ma sters fr om highe st to
lowest is:
Highest priority82596CA LAN
CD2401 serial (through the PCCchip2)
53C710 SCSI
VMEbus
Lowest priorityMPU
http://www.motorola.com/computer/literature1-7
1
Programming Issues
As a general rule, any master can access any slave; not all combinations
pass the common sense test, h owever. Refer to the device- specific sectio ns
of this manual and t o the us er’s guide for eac h de vice t o deter min e its port
size, data bus connection, and any restrictions that apply when accessing
the device.
EEPROMs on the MVME1X7P
Both boards include 44-pin PLCC/CLCC sockets for EEPROMs,
organized as follows:
ModelSocketsBanks
MVME16742
MVME17721
The MVME167P boards use 27C102JK or 27C202JK type EEPROMs.
The MVME177 boards use SGS-Thompson M27C4002 (256K x 16) or
AMD 27C4096 type EEPROMs.
The EEPROMs are organized as 32-bit wide banks that support 8-, 16-,
and 32-bit read accesses. (The MVME177 has Flash memory in addition
to EEPROM.)
MVME167
The EEPROMs are mapped to Local Bus addres s 0 following a Local Bus
reset. This allows t he MC6 8040 to access the stack pointer and exec uti on
address following a reset. The EEPROMs are contr olled by the VMEchip2
ASIC. The map decoder, the access time, and the time they appear at
address 0 are programmable parameters. Refer to Chapter 2, VMEchip2 for
more detail.
1-8Computer Group Literature Center Web Site
MVME177
The EEPROMs on the MVME177 share 2MB of memory with the first
2MB of Flash memory. The EEPROM can co-exist with 2MB of Flash, or
you may wish to program all 4MB as Flash memory. The Flash and
EEPROM configuration is jointly controlled by a configuration switch
(S4) as described in Chapters 1 and 4 of MVME177P Single Board ComputerInstallation and Use, and by control bit GPIO2 in the
VMEchip2 ASIC, as described in Chapter 2, VMEchip2.
The EPROMs are mapped to Local Bus address 0 following a Local Bus
reset.This allows the MC68060 processor to access the reset vector and
execution address following a reset.
Flash Memory on the MVME177
The MVME177 includes four 28F008SA Flash memory devices. The 32bit wide Flash can support 8-, 16-, and 32-bit accesses. The Flash can be
used for the onboard debugger firmware, which can be downloaded from
I/O resources such as Ether net, SCSI, serial port, or VMEbus . Flash writeprotection is programmable by setting a control bit (GPIO bit 1) in the
VMEchip2 GPIO register after downloading.
Programming Interfaces
1
When the Flash memory is used with EEPROM, only the top or bottom
2MB of Flash memory is visible at any one time. For access to the
shadowed area of Flash, the 177Bug firmware provides the SFLASH
command.
The MVME177 is shipped with the top 2MB of Flash memory and
EEPROM mapped as illustrated by Map 2 in Figure 1-3.
The 177Bug is shipped in EEPROM. To map all 4MB of Flash and retain
access to the 177Bug, perform the following steps:
1. Map Flash and EEPROM as shown in Map 3 in Figure 1-3.
2. Copy the 177Bug into the bottom 2MB of Flash memory.
3. Remap Flash memory as shown in Map 1 in Figure 1-3.
http://www.motorola.com/computer/literature1-9
1
Programming Issues
MAP 1
FFBFFFFF
FLASH
MEMORY
4MB
FF800000
NO EPROM
IN MAP
MAP 2
(as shipped)
FLASH
TOP 2MB
1MB EPROM
DUPLICATED:
READABLE
NOT WRITABLE
1MB EPROM
(BUG)
MAP 3
FLASH
BOTTOM
2MB
1MB EPROM
DUPLICATED:
READABLE
NOT WRITABLE
1MB EPROM
FFBFFFFF
FFA00000
FF900000
FF800000
1534 9408
Figure 1-3. MVME177 Flash and EPROM Memory Mapping Schem es
SRAM
The MVME167P and MVME177P single-board computers include
128KB of 32-bit wide 100ns static RAM (SRAM) that supports 8-, 16-,
and 32-bit wide accesses. The SRAM allows the debugger to operate and
limited diagnostics to execute without using the on-board SDRAM or
mezzanines. The SRAM is under t he cont rol o f the VMEchip2 ASI C, and
the access time is progr ammable. Refer to Chapter 2, VMEchip2 for more
detail.
The MVME177P provides for SRAM battery bac kup. The battery backup
function is supplied by a Dallas DS1210S nonvolatile controller chip and
Panasonic 2032 (or equivalent) battery.
1-10Computer Group Literature Center Web Site
The MVME177P implements primary a nd secondary backup sources. You
can select from +5V standby power, the onboard battery, or both.
The jumpers and configuration switches for the MVME167P and
MVME177P are described in Chapter 1 of the Installation and Use manual
for the respective boards.
Onboard SDRAM
MVME167P boards are built with 16MB-64MB synchronous DRAM
(SDRAM). MVME177P boards are built with 16MB-128MB SDRAM.
The MVME1X7P may have the SDRAM configured to model 4MB, 8MB,
16MB, 32MB, 64MB, or 128MB of ECC-protected DRAM.
In addition to the onboard SDRAM, an additional mezzanine (of the type
used on previous MVME1X7 boards) can be plugged in to provide up to
128MB of additional DRAM. All DRAM has ECC protection.
The SDRAM map decoder can be pr ogrammed to acc ommodate di ffer ent
base address(es) and sizes of mezzanine boards. The onboard SDRAM is
disabled by a Local Bus reset; it must be programmed in order for you to
access it.
Programming Interfaces
1
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. However,
software should insure a minimum of 10 initialization cycles are
performed to each bank of RAM.
Detailed pro gramming informa tion is availab le in the chapte rs on the
memory options.
http://www.motorola.com/computer/literature1-11
1
Programming Issues
Battery-Backed-Up RAM and Clock
Although the M48T58-70 RAM and clock chip is an 8-bit device, the
interface provided by the PCCchip2 supports 8-, 16-, and 32-bit accesses
to the M48T58. No interrupts are generated by the clock. Refer to Chapter
3, PCCchip2 and to the M48T58 data sheet for detailed programming
guidance and battery life information.
VMEbus Interface
The VMEbus interface is implemented with an ASIC called the
VMEchip2. The VMEchip2 includes:
❏ Two tick timers
❏ A watchdog timer
❏ Programmable map decoders for the master and slave interfaces
❏ 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 tra nsfers can be D8, D16, or D32. VMEchip2 DMA
transfers to the VMEbus, however, can be D16, D32, D16/BLT, D32/BLT,
or D64/MBLT.
Refer to Chapter 2, VMEchip2 for detailed programming information.
I/O Interfaces
The MVME167P and MVME177P single-board computers provide
onboard I/O for many syst em applications. The I/O func tions include serial
ports, parallel (printer) port , Ethernet trans ceiver interf ace, and SCSI mass
storage interface.
1-12Computer Group Literature Center Web Site
Serial Port Interface
The CD2401 serial controller chip (SCC) is used to implement the four
serial ports. The ser ial port s support th e standar d baud rate s (110 to 3 8.4K
baud). The four serial ports differ in function because of the limited
number of pins on the P2 I/O connector:
❏ Serial port 1 is a minimum-function asynchronous port. It uses
❏ Serial ports 2 and 3 are full-function asynchronous ports. They use
❏ Serial port 4 is a ful l-functio n asynchron ous or synch ronous port . It
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 may be on some
transition boar ds. An external I/O transition board is nec ess ary to convert
the I/O connector pinout to industry-standard connectors.
Programming Interfaces
1
RXD, CTS, TXD, and RTS.
RXD, CTS, DCD, TXD, RTS, and DTR.
can operate at synchronous bit rates up to 64 k bits per second. It
uses RXD, CTS, DCD, TXD, RTS, and DTR. It also interfaces to
the synchronous clock signal lines. Refer to Appendix C, Related
Documentation for drawings of the serial port interface
connections.
Note The MVME1X7P 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.
On both MVME167P and MVME177P boards, the interface provided by
the PCCchip2 allows t he 16-b it CD2401 ser ial cont roll er chip t o appear at
contiguous addresses. Acce ss es to the CD2401, howeve r, must be 8 or 16
bits. 32-bit acces ses are not permitted. Ref er to the CD24 01 data sheet and
to Chapter 3, PCCchip2 for detailed pro gramming information.
http://www.motorola.com/computer/literature1-13
1
Programming Issues
The CD2401 supports DMA operations to local memory. Because the
CD2401 does not support a retry operation necessary to break VMEbus
lockup conditions, the CD2401 DMA controllers should not be
programmed to access the VMEbus. The hardware does not restrict the
CD2401 to onboard DRAM.
Parallel (Printer) Interface
The PCCchip2 ASIC provides an 8-bit bidirectional parall el 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 transit ion, or low-to-h igh transi tion. This po rt may be used as
a Centronics-compatible parallel printer port or as a general parallel I/O
port.
When used as a para llel printer por t, the five stat us 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 P rinter Strobe (STROBE∗), and Input Prime (INP∗).
The PCCchip2 provides an auto-strobe feature similar to that of the
MVME147 PCC. In auto-strobe mode, after a write to the Printer Data
Register, the PCCchip2 automatically asserts the STROBE∗ pin for a
selected time specified by the Printer Fast Strobe control bit. I n manual
mode, the Printer Strobe control bit directly controls the state of the
STROBE∗ pin.
Refer to Chapter 3, PCCchip2for detailed programming information.
Refer to Appendix C, Relate d Documenta tion for drawings of the printer
port interface connections.
1-14Computer Group Literature Center Web Site
Ethernet Interface
The MVME1X7P uses the Intel 82596CA LAN co processor to implement
the Ethernet transceiver interface. The 82596CA accesses local RAM
using DMA operations to perform its normal functions. 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 MVME1X7P that is built with an Ethernet interface is assigned an
Ethernet Station Addre ss. The add ress i s $0001AFxxxxxx where x xxx xx is
the unique 6-nibble n umber assigned to the board (i.e., every MVME1X7P
has a different value for xxxxxx).
Each board has an Ethernet Station Address displa yed on a label attached
to the VMEbus P2 connector. In addition, the six bytes including the
Ethernet address are s tored in the co nfigurat ion area of the BBRAM. That
is, 0001AFxxxxxx is stored in the BBRAM. At an addre ss of $FFFC1F2 C,
the upper four bytes (0001AFxx) 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 this chapter under
Battery-Backed-Up RAM and Clock for specifics.)
Programming Interfaces
1
The MVME1X7P debugger firmware has the capability to retrieve or set
the Ethernet address. If the data in the BBRAM is lost , use the number on
the VMEbus P2 connector label to restore it.
The Ethernet transceiver interface is located on the MVME1X7P main
board, and the industry-standard DB15 connector is located on the
MVME712B transition board.
Support functions fo r the 82596CA LAN co proc essor are p rovide d by th e
PCCchip2 ASIC. Refer to the 82596CA user’s guide and to Chapter 3,
PCCchip2 for detailed programming information.
http://www.motorola.com/computer/literature1-15
1
Programming Issues
SCSI Interface
The MVME167P and MVME177P single-board computers provide for
mass storage subsystems through the industry-standard SCSI bus. These
subsystems may include hard and floppy disk drives, streaming tape
drives, and othe r mass storage devices. The SCSI interface is implemented
using the NCR 53C710 SCSI I/O controller.
Support functions for the 53C710 are provided by the PCCchip2 ASIC.
Refer to the 53C710 user’s guide and to Chapter 3, PCCchip2 for detailed
programming information.
SCSI Termination
It is important that the SCSI bus be properly terminated at both ends.
Sockets for terminators are provided on the P2 or LCP2 adapter board. If
the SCSI bus ends at the adapter board, termination resistors must be
installed on the adapter board. +5V power to the SCSI bus TERM power
line and termination resistors is supplied through a fuse located on the
adapter board (in the case of the MVME167P) or through a fuse on the
MVME712 series transition module and a diode on the adapter board (in
the case of the MVME177P).
Local Resources
The MVME167P and MVME177P single-board computers incl ude many
resources for the local processor. These include tick timers, softwareprogrammable hardware interrupts, a watchdog timer, and a local bus
timeout.
Programmable Tick Timers
Four 32-bit programmable tick timers with 1µs resolution are available:
two in the VMEchip2 ASIC and two in the PCCchip2 ASIC. The tick
timers may be programmed to generate periodic interrupts to the
processor. Refer to Chapter 2, VMEchip2 and Chapter 3, PCCchip2
respectively for detailed programming information.
1-16Computer Group Literature Center Web Site
Watchdog Timer
The VMEchip2 ASIC supplies a watchdog timer fu nction. When enab led,
the watchdog timer must be reset by software within the programmed
interval or it times out. The watchdog timer can be programmed to
generate a SYSRESET∗ signal, a local re set signal , or a board f ail signal if
it times out. Refer to Chapter 2, VMEchip2 for detailed programming
information.
Software-Programmable Hardware Interr upts
The VMEchip2 ASIC supplies eight software-programmable hardware
interrupts. These interrupts allow software to create a ha rdware interrupt.
Refer to Chapter 2, VMEchip2 for detailed programming information.
Local Bus Timeout
The MVME167P and MVME177P single-board computers provide a
timeout function in the VMEchip2 ASIC for the Local Bus. When the
timer is enabled and a Local Bus access times out, a Transfer Error
Acknowledge (TEA) signal is sent to the Local Bu s master. The time -out
value is selectable by software for 8 µsec, 64 µsec, 256 µsec, or infinite.
The Local Bus timer does not operate during VMEbus bound cycles.
Functional Description
1
VMEbus bound cycles are timed by the VMEbus access timer and the
VMEbus global timer. Refer to Chapter 2, VMEchip2 for detailed
programming information.
Functional Description
This section highlights a few specific features of the MVME1X7P singleboard computers. For a complete functional description of the major
blocks of the MVME1X7P, refer to the Installation and Use manual.
http://www.motorola.com/computer/literature1-17
1
Programming Issues
VMEbus Interface and VMEchip2
The local-bus-to-VMEbus interface and the VMEbus-to-local-bus
interface are provided by the VMEchip2 ASIC. The VMEchip2 can also
provide the VMEbus system cont roll er func tions . Refer t o the VMEchi p2
description in Chapter 2 for detailed programming information.
VMEchip2 General-Purpose I/O
The MVME1X7P single-board computers, both MVME167P and
MVME177P, follow the previous MVME177 in their routing of GPIO
signals:
❏ GPIO1 controls Flash memory w rite protection.
❏ GPIO3 selects between shared EPROM/Flash mode or Flash-only
mode.
❏ GPIO2 controls whether the upper or lower Flash addres ses are used
in shared EPROM/Flash mode.
❏ GPIO0’s function as +12V power status signal is unchanged.
Petra/VMEchip2 Redundant Logic
In support of possible future configurations in which the MVME1X7P
might be offered as a single-board computer without the VMEbus
interface, certain logic in the VMEchip2 has been duplicated in the Petra
chip. Table 1-2 shows the location of the overla pping logic. As long as the
VMEchip2 ASIC is present, the redundant logic is inhibited in the Petra
chip.
Note that the
ABORT switch logic in the VMEchip2 is not used. Likewise
unused are the GPI inputs to the VMEchip2, which are located at
$FFF40088 bits 7-0. Ins tead, the
ABORT switch interrupt is integrated into
the Petra ASIC at l ocat ion $FFF 42043. Th e GPI inpu ts ar e int egrat ed i nto
the Petra ASIC at location $FFF4202C bits 23-16.
1-18Computer Group Literature Center Web Site
Functional Description
Table 1-2. Functions Duplicated in VMEchip2 and Petra ASICs
5. Bit numbering for the VMEchip2 and Pet ra ASICs has a one-to-one
correspondence.
ABORT switch interrupt control. Implemented also in the
6.
VMEchip2, but with a different bit organization (refer to the
VMEchip2 description in Chapter 2). In the MVME1X7P, the
ABORT switch is wired to the Petra chip, not the VMEchip2.
7. The SRAM and EPROM decoder in the VMEchip2 (ve rsion 2) must
be disabled by software before any accesses are made to these
address spaces.
http://www.motorola.com/computer/literature1-19
1
Programming Issues
8. 32-bit prescaler. The prescaler can also be accessed at $FFF40064
when the optional VMEbus is not enabled.
Memory Maps
There are two points of view for memory maps:
1. The mapping of all resources as viewed by local bus masters (local
bus memory map)
2. The mapping of onboard resources as viewed by VMEbus masters
(VMEbus memory map)
The memory maps and I/O maps described in the following tables are
correct for all l ocal bus masters. Some add ress translati on capability exi sts
in the VMEch ip2. This capab ility makes it pos sible to have multiple
MVME1X7P modules on the same VMEbus with different virtual local
bus maps as viewed by different VMEbus masters.
Local Bus Memory Map
The local b us memory map is split into different addr ess spaces by the
transfer type (TT) signals. The local resources respond to the normal
access and interrupt acknowledge codes.
Normal Address Range
The following tables show t he memory maps of devices that res pond to the
normal address range . The normal addr ess range is def ined by the Tra nsfer
Type (TT) signals on the local bus. On the MVME1X7P, Transfer Types
0, 1, and 2 define the normal address range.
Table 1-3 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 in hibit funct ion is prog rammable in the MC680 x0 MMU.
1-20Computer Group Literature Center Web Site
Memory Maps
The onboard I/O space must be marked cache-inhibit and serialized in its
page table. Table 1-4 on page 1-22 furth er defines the map for the local I/O
devices on the MVME1X7P.
Table 1-3. Local Bus Memory Map
1
Address
Range
$00000000 DRAMSIZE
DRAMSIZE $FF7FFFFF
$FF800000 $FFBFFFFF
$FFC00000 $FFDFFFFF
$FFE00000 $FFE1FFFF
$FFE20000 $FFEFFFFF
$FFF00000 $FFFEFFFF
$FFFF0000 $FFFFFFFF
Software
Devices AccessedPort SizeSize
User Programmable
(Onboard SDRAM)
User Programmable
(VMEbus)
ROM (167P)D324MBN1
EPROM/Flash (177P)D32
Reserved--2MB--5
SRAMD32128KBN--
SRAM (repeated)D32896KBN--
Local I/O Devices
(Refer to next table)
User Programmable
(VMEbus A16)
D32
D32/D163GB?3, 4
D32-D81MBY3
D32/D1664KB?2, 4
DRAMSIZE
2MB
EPROM,
4MB Flash
Cache
Inhibit
N1, 2
N1,6
Notes
Notes
1. ROM on MVME167P, ROM/Flash on MVME177P. Flash/EPROM
devices appear at $FF800000 - $FFBFFFFF, and also appear at
$00000000 - $003FFFFF if the ROM0 bit in the VMEchip2
EPROM control register is high (ROM0 = 1).
The ROM0 bit is located at address $FFF40 030 bit 20. ROM0 is set
to 1 after each reset. The ROM0 bit must be cleared before other
resources (DRAM or SRAM) can be mapped in this range
http://www.motorola.com/computer/literature1-21
1
Programming Issues
($00000000 - $003FFFFF). The VMEchip2 and DRAM map
decoders are disabled by a local bus reset.
On the MVME177P, the Flash/EPROM memory is mapped at
$00000000 - $003FFFFF by hardware default through the
VMEchip2.
2. This area is user-pro gram mable. The sugges ted u se is shown i n the
table. The DRAM decoder is progr ammed in the MCECC chi p, 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.
6. The Flash and EEPROM configuration is jointly controlled by a
configuration switch (S4) as described in Chapters 1 and 4 of
MVME177P Single Board ComputerInstallation and Use, and by
control bit GPIO2 in the VMEchip 2 ASIC, as de scrib ed in Chapt er
2, VMEchip2. Depending on the setting of S4, this address space
may reference 2MB EPROM, 1MB EPROM and 2MB Flash, or
4MB Flash.
Table 1-4 focuses on the Local I/O Devices portion of the local bus Main
1. For a complete desc ription of the r egister bits, r efer to the data s heet
for the specific chip. For a more detailed memory map refer to the
following detailed peripheral device memory maps.
2. On the MVME1X7P, this area does not return an acknowledge
signal. If the local bus timer is enabled, the access times out and is
terminated b y a TEA signal.
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, th e access times out and is ter minated by
a TEA signal.
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 LCSR and GCSR may be 8, 16 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 MVME1X7P. If the local bus timer is enabled, the access
times out and is terminated by a TEA signal.
1-24Computer Group Literature Center Web Site
Detailed I/O Memory Maps
Tables 1-5 through 1-14 give the detailed memory maps for: 7
VMEchip2Table 1-5
PCCchip 2Table 1 -7
PrinterTable 1-6
MCECC Internal RegisterTable 1-8
Cirrus Logic CD2401 Serial PortTable 1-9
82596CA Ethernet LAN chipTable 1-10
53C710 SCSI chipTable 1-11
M48T58 BBRAM, TOD ClockTable 1-12
BBRAM Configuration AreaTable 1-13
TOD Clock Table 1-14
You can obtain manufacturers’ errata sheets for the various chips listed
above by contacting your local Motorola sales representative. A nondisclosure agreement may be necessary.
Memory Maps
1
http://www.motorola.com/computer/literature1-25
1
Programming Issues
Table 1-5. VMEchip2 Memory Map (Sheet 1 of 3)
VMEchip2 LCSR Base Address = $FFF40000
OFFSET:
16171819202122232425262728293031
0
SLAVE ENDING ADDRESS 1
10
14
18
1C
20
24
28
2C
30
34
38
4
8
C
ADDER
2
SLAVE ENDING ADDRESS 2
SLAVE ADDRESS TRANSLATION ADDRESS 1
SLAVE ADDRESS TRANSLATION ADDRESS 2
SNP
2
WP2SUP2USR2A322A24
BLK
BLK2PRGM2DATA
D64
2
2
2
16171819202122232425262728293031
MASTER ENDING ADDRESS 1
MASTER ENDING ADDRESS 2
MASTER ENDING ADDRESS 3
MASTER ENDING ADDRESS 4
MASTER ADDRESS TRANSLATION ADDRESS 4
MAST
D16
EN
MAST
WP
EN
GCSR GROUP SELECT
MAST
MAST
D16
WP
EN
EN
BOARD SELECT
GCSR
MASTER AM 3MASTER AM 4
MAST
MAST
MAST
4
3
EN
EN
MAST
2
1
EN
EN
16171819202122232425262728293031
WAIT
RMW
ROM
ZERO
DMA TB
SNP MODE
SRAM
SPEED
DMA CONTROLLER
3C
40
44
48
TICK
2/1
TICK
IRQ 1
EN
CLR
IRQ
IRQ
STAT
VMEBUS
INTERRUPT
LEVEL
VMEBUS INTERRUPT VECTOR
DMA CONTROLLER
DMA CONTROLLER
DMA CONTROLLER
This sheet continues on facing page.
1-26Computer Group Literature Center Web Site
ADDER
MAST
MAST
WP
D16
EN
IO2ENIO2
ARB
ROBN
DMA
TBL
INT
EN
WP
EN
MAST
DHB
DMA LB
SNP MODE
IO2
S/U
MAST
DWB
MASTER AM 2MASTER AM 1
IO2
IO1ENIO1
P/D
MST
FAIR
DMA
INC
VME
LOCAL BUS ADDRESS COUNTER
SLAVE STARTING ADDRESS 1
SLAVE STARTING ADDRESS 2
SLAVE ADDRESS TRANSLATION SELECT 1
SLAVE ADDRESS TRANSLATION SELECT 2
SNP
1
1
WP1SUP1USR1A321A24
MASTER STARTING ADDRESS 1
MASTER STARTING ADDRESS 2
MASTER STARTING ADDRESS 3
MASTER STARTING ADDRESS 4
MASTER ADDRESS TRANSLATION SELECT 4
MAST
MAST
WP
D16
EN
D16
EN
MST
RWD
DMA
INC
LB
IO1
WP
EN
MASTER
VMEBUS
DMA
WRT
IO1
S/U
DMA
D16
EN
DMA
HALT
DMA
D64
BLK
ROM
SIZE
DMAENDMA
DMA
BLK
ROM BANK B
TBL
DMA
AM
5
1
SPEED
DMA
FAIR
DMA
AM
4
BLK
BLK1PRGM1DATA
D64
1
DM
RELM
DMA
DMA
AM
AM
3
Memory Maps
ROM BANK A
SPEED
DMA
VMEBUS
DMA
AM
2
1
DMA
AM
1
0123456789101112131415
1
0123456789101112131415
0123456789101112131415
0
VMEBUS ADDRESS COUNTER
BYTE COUNTER
TABLE ADDRESS COUNTER
MPU
MPU
MPU
MPU
MPU
DMA
DMA
DMA
DMA
DMA
DMA
DMA TABLE
INTERRUPT COUNT
CLR
STAT
LBE
ERR
LPE
ERR
LOB
ERR
LTO
ERR
LBE
ERR
LPE
ERR
LOB
ERR
LTO
ERR
TBL
ERR
VME
ERR
DMA
DONE
1360 9403
This sheet begins on facing page.
http://www.motorola.com/computer/literature1-27
1
Programming Issues
Table 1-5. VMEchip2 Memory Map (Sheet 2 of 3)
VMEchip2 LCSR Base Address = $FFF40000
OFFSET:
4C
50
ARB
BGTO
EN
DMA
TIME OFF
DMA
TIME ON
TICK TIMER 1
VME
GLOBAL
TIMER
16171819202122232425262728293031
54
58
5C
60
64
68
6C
70
74
78
7C
80
84
88
8C
SCONBRD
AC
AB
FAIL
IRQ
IRQ
EN
EN
IRQ
IRQ
31
30
CLR
CLR
IRQ
IRQ
31
30
VECTOR BASE
REGISTER 0
SYS
FAIL
SYS
FAIL
IRQ
EN
IRQ
29
CLR
IRQ
29
AC FAIL
IRQ LEVEL
VME IACK
IRQ LEVEL
SW7
IRQ LEVEL
SPARE
IRQ LEVEL
FAIL
STAT
MWP
BERR
IRQ
EN
IRQ
28
CLR
IRQ
28
PURS
STAT
PE
IRQ
EN
IRQ
27
CLR
IRQ
27
CLR
BRD
PURS
FAIL
STAT
OUT
IRQ1E
TIC2
IRQ
IRQ
EN
EN
IRQ
IRQ
26
25
CLR
CLR
IRQ
IRQ
26
25
ABORT
IRQ LEVEL
DMA
IRQ LEVEL
SW6
IRQ LEVEL
VME IRQ 7
IRQ LEVEL
VECTOR BASE
REGISTER 1
RST
SW
TIC1
IRQ
IRQ
CLR
IRQ
EN
EN
24
24
SYS
RSTWDCLR
VME
IACK
IRQ
EN
IRQ
23
CLR
IRQ
23
MST
IRQ
EN
LEVEL
TO
DMA
IRQ
EN
IRQ
CLR
IRQ
SYS
FAIL
22
22
WD
CLR
CNT
SIG3
IRQ
EN
IRQ
21
CLR
IRQ
21
SYS FAIL
IRQ LEVEL
SIG 3
IRQ LEVEL
SW5
IRQ LEVEL
VME IRQ 6
IRQ LEVEL
AC
FAIL
LEVEL
WD
TO
STAT
SIG2
IRQ
EN
IRQ
20
CLR
IRQ
20
ABORT
LEVEL
TO
BF
EN
SIG1
IRQ
EN
IRQ
19
CLR
IRQ
19
TICK TIMER 1
TICK TIMER 2
TICK TIMER 2
WD
SRST
RST
LRST
SIG0
IRQ
EN
IRQ
18
CLR
IRQ
18
MST WP ERROR
IRQ LEVEL
SIG 2
IRQ LEVEL
SW4
IRQ LEVEL
VME IRQ 5
IRQ LEVEL
GPIOEN
WD
ENWDEN
LM1
IRQ
EN
IRQ
17
CLR
IRQ
17
PRE
16171819202122232425262728293031
LM0
IRQ
EN
IRQ
16
CLR
IRQ
16
This sheet continues on facing page.
1-28Computer Group Literature Center Web Site
Memory Maps
1
VME
ACCESS
TIMER
LOCAL
BUS
TIMER
COMPARE REGISTER
COUNTER
COMPARE REGISTER
COUNTER
OVERFLOW
COUNTER 2
SCALER
SW7
SW6
IRQ
EN
IRQ
SET
IRQ
CLR
IRQ
14
14
14
P ERROR
IRQ LEVEL
IRQ LEVEL
IRQ LEVEL
VME IRQ 4
IRQ LEVEL
GPIOO
SW5
IRQ
EN
IRQ
13
SET
IRQ
13
CLR
IRQ
13
SIG 1
SW3
IRQ
EN
IRQ
SET
IRQ
CLR
IRQ
15
15
15
SW4
IRQ
IRQ
SET
IRQ
CLR
IRQ
0123456789101112131415
TIME OUT
SELECT
CLR
OVF
2
WD
COC
EN
TIC
EN
2
2
OVERFLOW
COUNTER 1
PRESCALER
CLOCK ADJUST
CLR
OVF
TIC
COC
EN
EN
1
1
1
0123456789101112131415
SW3
SW2
SW1
SW0
IRQ
IRQ
IRQ
EN
EN
EN
IRQ
12
11
SET
IRQ
12
11
CLR
IRQ
12
11
EN
IRQ
IRQ
10
9
SET
SET
IRQ
IRQ
10
9
CLR
CLR
IRQ
IRQ
10
9
IRQ1E
IRQ LEVEL
SIG 0
IRQ LEVEL
SW2
IRQ LEVEL
VMEB IRQ 3
IRQ LEVEL
GPIOIGPI
IRQ
IRQ
SET
IRQ
CLR
IRQ
EN
8
8
8
SPARE VME
EN
IRQ
7
MP
IRQ
EN
IRQ7
EN
IRQ
6
REV
EROM
VME
IRQ6
EN
IRQ
5
TIC TIMER 2
IRQ LEVEL
LM 1
IRQ LEVEL
SW1
IRQ LEVEL
VME IRQ 2
IRQ LEVEL
DIS
SRAM
VME
IRQ5
EN
IRQ
DIS
MST
VME
VME
VME
IRQ4
IRQ3
EN
EN
IRQ
3
NO
EL
BBSY
IRQ
2
TIC TIMER 1
DIS
BSYTENINT
4
IRQ2
EN
IRQ
1
IRQ LEVEL
LM 0
IRQ LEVEL
SW0
IRQ LEVEL
VME IRQ 1
IRQ LEVEL
VME
IRQ1
EN
IRQ
DIS
BGN
0
1361 9403
This sheet begins on facing page.
http://www.motorola.com/computer/literature1-29
1
Programming Issues
Table 1-5. VMEchip2 Memory Map (Sheet 3 of 3)
VMEchip2 GCSR Base Address = $FFF40100
OffsetsBit Numbers
VME
-bus
Local
Bus
1514131211109876543210
00Chip RevisionChip ID
L
L
L
L
S
S
S
S
R
I
24
M
M
M
M
I
I
I
I
3
2
1
0
G
G
3
G
2
1
S
G
T
0
S
F
BFS
C
O
N
48General Purpose Control and Status register 0
6CGeneral Purpose Control and Status register 1
810General Purpose Control and Status register 2
A14General Purpose Control and Status register 3
C1 8General Purpose Control and Status register 4
E1CGeneral Purpose Control and Status register 5
SYS
XXX
FL
1-30Computer Group Literature Center Web Site
Memory Maps
Table 1-6. Printer Memory Map
Printer ACK Interrupt Control Register $FFF42030
BIT3130292827262524
NAMEPLTYE/L*INTIENICLRIL2IL1IL0
Printer FAULT Interrupt Control Register $FFF42031
BIT2322212019181716
NAMEPLTYE/L*INTIENICLRIL2IL1IL0
Printer SEL Interrupt Control Register $FFF42032
BIT151413121110 9 8
NAMEPLTYE/L*INTIENICLRIL2IL1IL0
Printer PE Interrupt Control Register $FFF42033
BIT76543210
NAMEPLTYE/L*INTIENICLRIL2IL1IL0
Printer BUSY Interrupt Control Register $FFF42034
BIT3130292827262524
NAMEPLTYE/L*INTIENICLRIL2IL1IL0
1
Printer Input Status Register $FFF42036
BIT151413121110 9 8
NAMEPLTYACKFLTSELPEBSY
Printer Port Control Register $FFF42037
BIT76543210
NAMEDOENINPSTBFASTMAN
Printer Data Register 16 bi ts $FFF4203A
BIT15-0
NAMEPD15 - PD0
http://www.motorola.com/computer/literature1-31
1
Programming Issues
Table 1-7. PCCchip2 Memory Map
PCCchip2 Base Address = $FFF42000
OFFSET:
D16D23D24D31
00
CHIP IDCHIP REVISION
04
08
0C
10
14
18
1C
20
24
28
2C
30
34
38
3C
GPI
PLTY
PRTR
ACK
PLTY
PRTR
BSY
PLTY
PRESCALER COUNT REGISTERPRESCALER CLOCK ADJUST
GPI
GPI
GPI
E/L*
INT
IEN
SCC
RTRY
ERR
GPI
ICLR
SCC
PAR
ERR
SCC
EXT
ERR
GPI
IRQ LEVEL
SCC
LTO
ERR
SCC
SCLR
SCC
MDM
ERR
SCC
MDM
IEN
MDM
AVEC
SCC TRANSMIT PIACK
LAN
LAN
LAN
LTO
ERR
SCSI
LTO
ERR
PRTR ACK
IRQ LEVEL
PRTR BSY
IRQ LEVEL
LAN
SCLR
SCSI
SCLR
PRTR
FLT
PLTY
PRTR
FLT
E/L*
PRTR
FLT
INT
PRTR
FLT
IEN
PRTR
ACK
E/L*
PRTR
BSY
E/L*
PRTR
ACK
INT
PRTR
BSY
INT
PRTR
ACK
IEN
PRTR
BSY
IEN
PAR
ERR
SCSI
PAR
ERR
PRTR
ACK
ICLR
PRTR
BSY
ICLR
EXT
ERR
SCSI
EXT
ERR
CHIP SPEED
GPIGPOE GPO
SCC
PRTR
FLT
ICLR
TIC TIMER 1
TIC TIMER 1
TIC TIMER 2
TIC TIMER 2
SCC MODEM
IRQ LEVEL
PRTR FAULT
IRQ LEVEL
SCC PROVIDES ITS OWN VECTORS
This sheet continues on facing page.
1-32Computer Group Literature Center Web Site
Memory Maps
1
D15D7D8D0
CPU
MSTR
DRO
040
FAST
INT
BRAM
EN
VECTOR BASE REGISTER
COMPARE REGISTER
COUNTER REGISTER
COMPARE REGISTER
COUNTER REGISTER
CLR
OVERFLOW
COUNTER 2
TIC2
INT
SCC
TX
IRQ
TIC2
IEN
SCC
TX
IEN
TIC2
ICLR
SCC
TX
AVEC
CLR
OVF
2
TIC TIMER 2
IRQ LEVEL
SCC TRANSMIT
IRQ LEVEL
COC
EN
TIC
EN
2
2
SCC
SC1
OVERFLOW
COUNTER 1
TIC1
INT
SCC
SCC
RX
SC0
IRQ
TIC1
IEN
SCC
RX
IEN
TIC1
ICLR
SCC
RX
AVEC
OVF
1
TIC TIMER 1
IRQ LEVEL
SCC RECEIVE
IRQ LEVEL
COC
EN
1
SCC MODEM PIACK
SCC RECEIVE PIACK
LAN
LAN
LAN
INT
PLTY
PRTR
SEL
PLTY
PRTR
ANY
INT
LAN
INT
E/L*
PRTR
SEL
E/L*
LAN
INT
PRTR
SEL
INT
LAN
IEN
PRTR
SEL
IEN
PRTR
ACK
LAN
ICLR
PRTR
SEL
ICLR
PRTR
FLT
PRTR
SEL
LAN INT
IRQ LEVEL
PRTR SEL
IRQ LEVEL
PRTRPEPRTR
BSY
LAN
SC1
PRTR
PE
PLTY
LAN
SC0
PRTR
PE
E/L*
ERR
INT
SCSI
IRQ
PRTR
PE
INT
ERR
IEN
SCSI
IEN
PRTR
PE
IEN
PRTR
DAT
ENBL
LAN
ERR
ICLR
PRTR
PE
ICLR
PRTR
INP
PRTR
STB
LAN ERR
IRQ LEVEL
SCSI INT
IRQ LEVEL
PRTR PE
IRQ LEVEL
PRTR
FAST
ASTB
PRINTER DATA
INTERRUPT
IPL LEVEL
INTERRUPT
MASK LEVEL
TIC
EN
PRTR
MAN
STB
1
1362 9403
This sheet begins on facing page.
http://www.motorola.com/computer/literature1-33
1
Programming Issues
Table 1-8. MCECC Internal Register Memory Map
MCECC Base Address = $FFF43000 (1st); $FFF43100 (2nd)
Table 1-9. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
Register DescriptionRegister
Name
Receive Interrupt Status Register lowRISRl89BR
Receive Interrupt Status Register highRISRh88BR
Receive FIFO Output CountRFOC30BR
Receive Data RegisterRDRF8BR
Receive End Of Interrupt RegisterREOIR84BW
Transmit Interrupt Registers
Transmit Priority Interrupt Level RegisterTPILRE0BR/W
Transm i t Inte rrupt Registe rTIRECBR
Transmit Interrupt Status RegisterTISR8ABR
Transmit FIFO Transfer CountTFTC80BR
Transmit Data RegisterTDRF8BW
Transmit End Of Interrupt RegisterTEOIR85BW
Modem Interrupt Registers
Modem Priority Interrupt Level RegisterMPILRE3BR/W
Modem Interrupt RegisterMIREFBR
Modem (/Timer) Interrupt Status RegisterMISR8BBR
Modem End Of Interrupt RegisterMEOIR86BW
DMA Registers
DMA Mode Register (write only)DMRF6BW
Bus Error Retry CountBERCNT8EBR/W
DMA Buffer Status
DMA Receive Registers
A Receive Buffer Address Lower
A Receive Buffer Address Upper
B Receive Buffer Address Lower
B Receive Buffer Address Upper
A Receive Buffer Byte CountARBCNT4AWR/W
DMABSTS
ARBADRL
ARBADRU
BRBADRL
BRBADRU
OffsetsSizeAccess
19BR
42WR/W
40WR/W
46WR/W
44WR/W
1-38Computer Group Literature Center Web Site
Memory Maps
Table 1-9. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
Register DescriptionRegister
Name
B Receive Buffer Byte CountBRBCNT48WR/W
A Receive Buffer StatusARBSTS4FBR/W
B Receive Buffer StatusBRBSTS4EBR/W
Receive Current Buffer Address Lower
Receive Current Buffer Address Upper
RCBADRL
RCBADRU
DMA Transmit Registers
A Transmit Buffer Address Lower
A Transmit Buffer Address Upper
B Transmit Buffer Address Lower
B Transmit Buffer Address Upper
ATBADRL
ATBADRU
BTBADRL
BTBADRU
A Transmit Buffer Byte Cou ntATBCNT5AWR/W
B Transmit Buffer Byte CountBTBCNT58WR/W
A Transmit Buffer StatusATBSTS5FBR/W
B Transmit Buffer StatusBTBSTS5EBR/W
Transmit Current Buffer Address Lower
Transmit Current Buffer Address UpperTCBADRU38WR
TCBADRL
Timer Registers
Timer Period RegisterTPRDABR/W
Receive Time-out Period RegisterRTPR24WR/W
Receive Time-out Period Regis lowRTPRl25BR/W
Receive Time-out Period Register highRTPRh24BR/W
General Timer 1GT12AWR Sync
OffsetsSizeAccess
3EWR
3CWR
52WR/W
50WR/W
56WR/W
54WR/W
3AWR
Async
Async
Async
1
http://www.motorola.com/computer/literature1-39
1
Programming Issues
Table 1-9. Cirrus Logic CD2401 Serial Port Memory Map (Continued)
Base Address = $FFF45000
Register DescriptionRegister
Name
General Timer 1 lowGT1l2BBR Sync
General Timer 1 highGT1h2ABR Sync
General Timer 2 GT229BR Sync
Transmit Timer RegisterTTR29BR Async
NoteThis is a 16-bit register
Table 1-10. 82596CA Ethernet LAN Memory Map
82596CA Ethernet LAN Directly Accessible Registers
Data Bits
AddressD31D16D15D0
$FFF46000Upper Command WordLower Command Word
$FFF46004MPU Channel Atten tion (CA)
OffsetsSizeAccess
Notes
1. Refer to the MPU Port and MPU Channel Atte ntion registe r entrie s.
2. After resetting, you must write the System Configura tion Pointer to
the command registers befor e writing to the MPU Channel
Attention register . Writes to the System Config uration Pointer must
be upper word first, lower word second.
NoteAccesses may be 8-bit or 32-bit, but not 16-bit.
BBRAM/TOD Clock Memory Map
The M48T58 BBRAM (also called Non-Vola tile RAM or NVRAM) is divided into
six areas as shown in Table 1-12. The first five areas are defined by software, while
the sixth area, the time-of-day (TOD) clock, is defined by the chip hardware. The
first area is re served for u ser data. The sec ond area is used by Motorola ne tworking
software. The third area may be used by an operating system. The fourth area is
http://www.motorola.com/computer/literature1-41
1
Programming Issues
used by the MVME1X7P board debugger (MVME1X7Bug). The fifth area,
detailed in Table 1-13, is the configuration area. The sixth area, the TOD clock,
detailed in Table 1-14, is defined by the chip hardware.
Table 1-12. M48T58 BBRAM,TOD Clock Memory Map
Address RangeDescriptionSize
(Bytes)
$FFFC0000 - $FFFC0FFFUser Area4096
$FFFC1000 - $FFFC10FFNetwork i ng Area256
$FFFC1100 - $FFFC16F7Operating System Area1528
$FFFC16F8 - $FFFC1EF7Debugger Area2048
$FFFC1EF8 - $F FFC1FF7Configuration Area256
$FFFC1FF8 - $FFFC1FFFTOD Clock8
1. Four bytes are r eserved for the r evi si on or version of t his structure.
This revision 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. Fo r example, if the version o f this struct ure
is 1.0, this field contains:
0100
2. Twelve 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:
MVME167P-24SE
(The 13 characters are fo llowed by three blanks.)
4. Sixteen bytes are reserved for the pr inted wiring assembly (PWA)
number assigned to this board in ASCI I 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
1-44Computer Group Literature Center Web Site
Memory Maps
structure for that set. For example, for a 64MB, 33MHz
MVME167P board at revision C, the PWA field contains:
01-W3620F35C
(The 13 characters are fo llowed by three 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 f or the Ethernet address. The addre ss is stored
in hexadecimal format. (Refer to the detailed description earlier in
this chapter. )
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 t he systems se rial ID, fo r boards used i n
a system.
1
10. Eight bytes are r eserved for the printed wiring boar d (PWB) number
assigned to the first mezzanine board in ASCII format. This does not
include the
01-W prefix. For example, for a 16MB parity mezzanine
at revision E, the PWB field contains:
3690B03E
11. Eight bytes are reserved for the serial number assigned to the first
mezzanine board in ASCII format.
12. Eight bytes are r eserved for the pr inted wiring boar d (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 reser ved . This pads the structure to an
even 256 bytes. Syst em-s pec if ic it ems, such as si ze of s yst em side,
and systems side version, may go here.
http://www.motorola.com/computer/literature1-45
1
Programming Issues
15. The final byte of the area i s res er ved for a checksum (as defined in
the Debugging Package User’s Manual for MVME167Bug and
MVME177Bug, and the Debugging Package for Motorola 68K CISC CPUs User’s Manual) for security and data integrity of t he
configuration area of the NVRAM. This data is stored in
hexadecimal format.
Interrupt Acknowledge Map
The local bus distinguishes interrupt acknowledge cycles from other
cycles by placing 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.
VMEbus Memory Map
This section describes the mapping of local resources as viewed by
VMEbus masters. Default addresses for the slave, master, and GCSR
address decoders are provided by the ENV command.
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 you to program
the starting and ending address and the modifiers to which the
MVME1X 7P respond s.
VMEbus Short I/O Memory Map
The VMEchip2 includes a user -programmable map decoder for the GCSR.
The GCSR map decoder allows you to prog ram the star ting address of the
GCSR in the VMEbus short I/O space.
1-46Computer Group Literature Center Web Site
Interrupt Handling
M68000-based systems use hardware-vectored interrupts. Board MPUs
from the M68000 family require that the C040 bit in the PCCc hip2 General
Control register (address $FFF42002) be set. For more information, refer
to the General Control Register section in Chapter 3, PCCchip2.
Most interrupt sour ces are level and base vector programmable. Interrupt
vectors from the PCCchip2 and VMEchip2 ASICs have two sections:
Base valueCan be set by the processor, usually the upper four
Lower bitsSet according to the particular interrupt source
There is a hierarchy of interrupt sources, prioritized as follows:
Highest priorityInterrupts from the PCCchip2
Lowest priorityInterrupt sources from the VMEchip2
The MC68040 and MC68060 proce ssors employ a seven- level priori tized,
hardware-vectore d interrupt sc heme that is standard in th e M68000 family.
Interrupt Handling
1
bits
The Local Bus distinguishes interrupt acknowledge cycles from other
cycles by placing 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.
Example: VMEchip2 Tick Timer 1 Periodic Interrupt
This section describes the use of interrupts on MVME167P and
MVME177P single-board computers. The following example illustrates
how to generate and handle a VMEchip2 Tick Timer 1 interrupt on
M68000-based single-b oard computers such as the MVME1X7P. Specif ic
values are given for the register writes. It is advisable to read this entire
section before you perform any of these procedures.
http://www.motorola.com/computer/literature1-47
1
Programming Issues
1. Set up Tick Timer:
StepRegister and AddressAction and Reference
1Prescaler Control register
$FFF4004C
2Tick Timer 1
Compare register
$FFF40050
3Tick Timer 1
Counter register
$FFF40054
4Tick Timer 1
Control register
$FFF40060 (8 bits)
If not already initialized by the debugger, initialize as
follows: Prescaler register = 256–Bclock (MHz). This
gives a 1 MHz clock to the tick timers. Bclock is the bus
clock rate, such as 25MHz.
256–25 = $E7.
For periodic interrupts, set the Compare Register value =
Period (s). For example, if you want an interrupt every
millisecond, set the register value to 1000 ($3E8). Refer
to the Tick Timer 1 Compare Register description in
Chapter 2 .
Write a zero to clear the register.
Write $07 to this register (set bits 0, 1, and 2). This
enables the Tick Timer 1 counter to increment, resets the
count to zero on compare, and clears the overflow
counter.
2. Set up local bus interrupter:
StepRegist er and AddressAction and Reference
5Vector Base register
$FFF40088 (8 of 32 bits)
6Interrupt Level register 1
(bits 0-7)
$FFF40078 (8 of 32 bits)
7Local Bus Interrupter
Enable register
$FFF4006C (8 of 32 bits)
8I/O Control Register 1
$FFF40088 (8 of 32 bits)
1-48Computer Group Literature Center Web Site
If not already initialized by the debugger, set Interrupt
Base register 0 by writing to bits 28-31. Refer to the
Vector Base Register description a nd to Table 2-4, Local
Bus Interrupter Summary , in Chapter 2.
Write desired level of Tick Tim e r 1 interrupt to bits 0-2.
Set bit 24 (ETIC1) to 1 to enable Tick Timer 1 interrupts.
Write a 1 to bit 23 to enable interrupts from the
VMEchip2. A 0 masks all interrupts from the VMEchip2.
Cache Coherency (MVME167P)
Periodic Tick Timer 1 interrupts now occur, so you need an interrupt
handler. Section 3 gives the details, as follows.
Set up an interrupt handler routine:
3.
StepAction and Reference
Your interru pt ha ndler should include the following features.
1Be sure the MC680x0 Vector Base register is set up. Set the proper MC680x0
exception vector location so the processor vectors to your interrupt handler location.
You can determine the proper exception vector location to set from the MC680x0
Vector Base register, the VMEchip2 Base register, and Table 2-4, Local Bus Interrupter Summary in Chapter 2, from which you can determine the actual interrupt
vector given on a Tick Timer 1 interrupt. Lower the MC680x0 mask so the interrupt
level you programmed is accepted. The interrupt handler itself should include the
following (steps 2 through 5).
2Confirm that the Tick Timer 1 interrupt occurred, by reading the status of bit 24 in the
Interrupter Status register at $FFF40068. A high indicates an interrupt present.
3Clear the Tick Timer 1 interrupt by writing a 1 to bit 24 of the Interrup t Clear register at
$FFF40074.
4Increment a software counter to keep track of the number of interrupts, if desired.
Output a character or some other action (such as toggling the
appropriate count, such as 1000.
5Return from exception.
FAIL LED) on an
1
Cache Coherency (MVME167P)
The MVME167P’s MC68040 process or has the ability to wat ch Local Bus
cycles executed by other Local Bus masters such as the SCSI DMA
controller, the LAN controller, the VMEchip2 DMA controller, and the
VMEbus-to-Local-Bus controller. This bus snooping capability is
described in the M68040 Microprocessors User’s Manual sections on
Cache Coherency and Bus Snooping Operation.
When snooping is enabled, the MC68040 MPU can source da ta and
invalidate cache entries a s require d by the curr ent cycle. Th e MPU canno t
watch VMEbus cycles that do not access the Local Bus. Software must
http://www.motorola.com/computer/literature1-49
1
Programming Issues
ensure that data shared by multiple processors is kept in un-cached
memory. The software must also mark all onboard I/O areas as cache
inhibited and serialized.
Cache Coherency (MVME177P)
The MVME177P’s MC68060 processor has the ability to watch the
external bus during acce sses by other bus masters, mainta ining coh erency
between the MC68060’s caches and external memory systems.To
maintain cache coherency, the MC68060 provides automatic snoopinvalidation when it is not the bus master. When an external cycle is
marked as snoopable, the bus snooper checks the caches and invalidates
the matching data.
Unlike the MC68040, the MC68060 cannot source or sink cache data
during alternate bus master accesses. Therefore, the MVME177 uses a
single snoop control line – SC1. Snoop co ntrol bits for SC0 must be set to
0.
MC68060 cache coherency and bus sno oping capa bilities a re describe d in
the M68060 Microprocessors User’s Manual, in the sections on Cache
Coherency and Bus Snooping Operation.
1-50Computer Group Literature Center Web Site
Using Bus Timers
This section illu strate s the use o f bus timer s by des cribing the sequen ce of
events when the MPU on one single-board computer accesses the Local
Bus memory on another single-board computer using the VMEbus. This
scenario involves three bus timers, which normally should be set to quite
different values:
Local bus timerMeasures the time an access to an onboard resource
Using Bus Timers
1
takes
VMEbus access
timer
Global VMEbus
timer
Measures the time from when the VMEbus request has
been initiated to when a VMEbus grant h a s been
obtained
Measures the time from when a VMEbus cycle beg ins to
when it completes
The sequence begins when the MPU asserts a request for the Local Bus.
The MPU must wait until the Local Bus is released by the current bus
master before its cycle c an begin. When the MPU is grante d the Local Bus,
it begins its cycle and the Local Bus timer starts counting. It continues to
count until an address decode o f the VMEbus addr ess space is de tected and
then the timer stops. This is normally a very short period of time. In fact,
all Local Bus non-error bus accesses are normally very short, such as the
time to access onboard memory. Therefore, it is recommended this timer
be set to a small value, such as 8 µsec.
The next timer to take over when one single-board computer accesses
another is the VMEbus access timer. This measures the time from when
the VMEbus has been address -decoded ( and hence a VMEbus requ est has
been made) to when VMEbus mastership has been granted. Because
experience has shown that some VME systems can become very bus y, we
recommend this time-out be set to a large value, such as 32 msec. For
debug purposes this value can also be set to infinity.
Once the VMEbus has been granted, a third timer takes over. This is the
global VMEbus timer. This timer starts when a transfer actually begins
(DS0 or DS1 goes active) and ends when that transfer completes (DS0 or
http://www.motorola.com/computer/literature1-51
1
Programming Issues
DS1 goes inactive). This time should be longer than any expected
legitimate transfer time on the bus. We normally set it to 256 µsec. This
timer can also be disabled for debug purposes.
Before a single-board computer access to another single-board computer
can complete, however, t he VMEchip2 on the accessed bo ard must decode
a slave access and request the Local Bus of the second board. When the
Local Bus is granted (any in-process onboard transfers have completed),
then the Local Bus time r of the accessed board s tarts. Normally, this is also
set to 8 µsec. When the memory has the data available, a transfer
acknowledge signal ( TA) is given. This transla tes into a DTACK sig nal on
the VMEbus which is then t ranslated into a TA si gnal to the first r equesting
processor, and the transfer is complete.
If the VMEbus global timer expires on a legi timate trans fer, the VMEbus
to Local Bus controller in the VMEchip2 may become confused and the
VMEchip2 may misbehave. Therefore the bus timer values must be set
correctly. The correct settings may depend on the system configuration.
Indivisible Cycles
The MVME167P and MVME177P single-board computers perform
operations that require indivisible read-modify-write (RMW) memory
accesses. These RMW sequences occur when the MMU modifies table
entries or when the MPU executes one of the single-cycle instructions
listed in Ta ble 1-15.
Table 1-15. Single-Cycle Instructions
MPUInstructions
MC68040CAS, CAS2, TAS
MC68060CAS
CAS2 and misaligned CAS instructions are emulated
by software (see NOTE)
1-52Computer Group Literature Center Web Site
Supervisor Stack Pointer (MC68060)
NoteSoftware emulation of CAS2 and misaligned CAS instructions is
performed by the MC6 8060 Software Packag e, which is incl uded
in all Motorola-supplied operating systems for the MVME177P.
Contact your sales office for information about obtaining the
MC68060 Software Package for use with other operating
systems.
The single-board c omputers do not ful ly support all RMW operations in al l
possible cases. The modules mak e the foll owing a ssump tions and s upport
a limited subset of RMW instructions:
❏ The single-board computers support single-address RMW cycles.
❏ Multiple-address RMW cycles are not guaranteed indivisible and
may cause illegal VMEbus cycles.
❏ Lock cycles caused by MMU table walks on the VMEbus do not
cause illegal VMEbus cycles but they are not guaranteed do be
indivisible.
On M68000-based systems, aligned CAS and all TAS cycles are always
single-address RMW operations, while misaligned CAS and CAS2
operations and operations in the MMU can be multiple-address RMW
cycles. The VMEbus does not suppor t mult iple- addre ss RMW cycl es and
there is no defined protocol for supporti ng mu lt ipl e- add re ss RMW cycles
that start onboard and then access offboard resources. Because it is not
possible to tell if the processor is executing a single- or multiple-address
read-modify-write cycle, software should only execute single-address
RMW instructions. For efficien cy, all CAS instru ctions should be ali gned.
1
Supervisor Stack Pointer (MC68060)
On the MC68060, use of the supervis or stack pointer is reserve d for system
programming functions. All applicatio n software must be writ ten to run in
user mode. Such software will migrate to any M68000 platform without
modification.
Programs written for platforms like the MC68040, which do use the
supervisor stack pointer, must be recompiled before you can run them on
a MC68060-based single-board computer such as the MVME177.
http://www.motorola.com/computer/literature1-53
1
Programming Issues
Sources of Local Bus Errors
A TEA* signal (indicating a bus error ) is returned to the Local Bus mast er
when a Local Bus time-out oc curs, a DRAM parity error occurs and parity
checking is enabled, or a VME bus e rror occurs duri ng a VMEbus access .
The sources of Local Bus errors on the Single Board Computers are
described in the next subsections.
Local Bus Timeout
A Local Bus Timeout occurs whenever a Local Bus cycle does not
complete within the programmed time (VMEbus bound cycles are not
timed by the Lo cal Bus timer). If the system is configured properly, this
should only happe n if s oftware accesses a no n-existe nt loca tion within t he
onboard address range.
VMEbus Access Timeout
A VMEbus Access Timeout occurs whenever a VMEbus bound transfer
does not receive a VMEbus bus g rant within the progra mmed time. Thi s is
usually caused by another bus master holding the bus for an excessive
period of time.
VMEbus BERR*
A VMEbus BERR∗ occurs when the BERR∗ signal line is asserted on the
VMEbus while a Local Bus master is accessing the VMEbus. VMEbus
BERR∗ should occur only if one of the following events is detected:
❏ An initializati on routi ne samp les to see if a devic e is pres ent o n the
VMEbus and it is not.
❏ Software accesses a nonexistent device within the VMEbus range.
❏ Erroneous configuration data causes the VMEchip2 to incorrectly
access a device on the VMEbus (such as driving LWORD∗ low to
a 16-bit board).
1-54Computer Group Literature Center Web Site
❏ A hardware error occurs on the VMEbus.
❏ A VMEbus slave reports an access error (such as parity error).
VMEchip2
An 8- or 16-bit write to the LCSR in the VMEchip2 ASIC causes a local
BERR∗.
Bus Error Processing
Because different cond it ions can cause bus error exceptions, the sof tware
must be able to distinguish the source. To aid in this, status registers are
provided for every Local Bus master. The next section describes the
various causes of bus error and the associated status registers.
Generally, the bus error handl er can inter rogate the s tatus bits and procee d
with the result. However, an interrupt may occur during the execution of
the bus error hand ler (before an ins tr uct ion can write to th e st at us register
to raise the interrupt mask). If the interrupt service routine causes a second
bus error, the status that indicates the source of the first bus error may be
lost. Application software must take this possibility into account.
Error Conditions
1
Error Conditions
This section lists the various error conditions that are reported by the
single-board computer hardware. A subheading identifies each error
condition; a standard format provides the following information:
❏ Description of the error
❏ How notification of the error is made
❏ Status register(s) containing information about the error
❏ Comments pertaining to the error
http://www.motorola.com/computer/literature1-55
1
Programming Issues
MPU Parity Error
Description:A DRAM parity error.
MPU Notification:TEA is asserted during an MPU DRAM access.
Status:Bit 9 of the MPU Status and DMA Interrup t Count register
in the VMEchip2 at address $FFF40048.
Comments:After memory has been initialized, this error normally
indicates a hardware problem.
MPU Offboard Error
Description:An error occurred while the MPU was attempting to access
an offboard resource.
MPU Notification:TEA is asserted during offboard access.
Status:Bit 8 of the MPU Status and DMA In terru pt Count
register.
Address $FFF40048
Comments:This can be caused by a VMEbus timeout, a VMEbus
BERR∗, or a single-board computer VMEbus access
timeout. The latter is the time from when the VMEbus has
been requested to when it is granted.
MPU TEA - Cause Unidentified
Description:An error occurred while the MPU was attempting an
access.
MPU Notification:TEA is asserted during an MPU access.
Status:Bit 10 of the MPU Status and DMA Interrupt Count
register.
Address $FFF40048
Comments:No status was given as to the cause of the TEA assertion.
1-56Computer Group Literature Center Web Site
MPU Local Bus Time-out
Description:An error occurred while the MPU was attempting to access
a local resource.
MPU Notification:TEA is asserted during the MPU access.
Status:Bit 7 of the MPU Status and DMA Interrup t Count register
(actually in the DMAC Status register).
Address
$FFF40048
Comments:The Local Bus timer timed out. This usually indicates the
MPU tried to read or write an address at which there was
no resource. Otherwise, it indicates a hardware problem.
DMAC VMEbus Error
Description:The DMAC experienced a VMEbus error during an
Status:The VME bit is set in the DMAC Status register (address
$FFF40048 bit 1).
Comments:This indicates the DMAC attempted to access a VMEbus
address at which there was no resource or the VMEbus
slave returned a BERR∗ signal.
DMAC Parity Error
Description:Parity error while the DMAC was reading DRAM.
MPU Notification:DMAC interrupt (when enabled)
Status:The DLPE bit is set in the DMAC Status register (address
$FFF40048 bit 5).
Comments:If the TBL bit is set (address $FFF40048 bit 2), the error
occurred during a command table access; otherwise the
error occurred during a data access.
http://www.motorola.com/computer/literature1-57
1
Programming Issues
DMAC Offboard Error
Description:Error encountered while the Local Bus side of the DMAC
was attempting to go to the VMEbus.
MPU Notification:DMAC interrupt (when enabled)
Status:The DLOB bit is set in the DMAC Status register (address
$FFF40048 bit 4).
Comments:This is normally caused by a programming error. The
Local Bus address of the DMAC should not be
programmed with a Local Bus address that maps to the
VMEbus. If the TBL bit is set (address $FFF40048 bit 2),
the error occurred during a command table access;
otherwise the error occurred during a data access.
DMAC LTO Error
Description:A Local Bus time-out (LTO) occurred while the DMAC
was Local Bus master.
MPU Notification:DMAC interrupt (when enabled)
Status:The DLTO bit is set in the DMAC Status register (address
$FFF40048 bit 3).
Comments:This indicates the DMAC attempted to access a Local Bus
address at which there was no resource. If the TBL bit is
set (address $FFF40048 bit 2), the error occurred during a
command table access; otherwise the error occurred during
a data access.
1-58Computer Group Literature Center Web Site
DMAC TEA - Cause Unidentified
Description:An error occurred while the DMAC was Local Bus master
and additional status was not provided.
MPU Notification:DMAC interrupt (when enabled)
Status:The DLBE bit is set in the DMAC Status register (address
$FFF40048 bit 6).
Comments:An 8- or 16-bit write to the LCSR in the VMEchip2 causes
this error. If the TBL bit is set (address $FFF40048 bit 2),
the error occurred during a command table access;
otherwise the error occurred during a data access.
SCC Retry Error
Description:Local Bus Retry occurred due to VMEbus Dual Port Lock
or LAN-wanted-Bus while the SCC was Local Bus master.
MPU Notification:SCC Transmit Interrupt or SCC Receive Interrupt
Status:SCC Transmit Interrupt Status register
SCC Transmit Current Buffer Address register
SCC Receive Interrupt Status register High
SCC Receive Current Buffer Address register PCCchip2
SCC Error Status register ($FFF4201C)
Error Conditions
1
Comments:The DMA controllers in the SCC should not be
programmed to access the VMEbus. Refer to the Serial
Port Interface section in this chapter. SCC Transmit and
Receive interrupt enables are controlled in the SCC and in
the PCCchip2.
http://www.motorola.com/computer/literature1-59
1
Programming Issues
SCC Parity Error
Description:Parity Error detected while the SCC was reading DRAM.
MPU Notification:SCC Transmit Interrupt or SCC Receive Interrupt
Status:SCC Transmit Interrupt Status register
SCC Transmit Current Buffer Address register
SCC Receive Interrupt Status register High
SCC Receive Current Buffer Address register PCCchip2
SCC Error Status register ($FFF4201C)
Comments:SCC Transmit and Receive interrupt enables are controlled
in the SCC and in the PCCchip2.
SCC Offboard Error
Description:Error encountered while the SCC was attempting to go to
the VMEbus.
MPU Notification:SCC Transmit Interrupt or SCC Receive Interrupt
Status:SCC Transmit Interrupt Status register
SCC Transmit Current Buffer Address register
SCC Receive Interrupt Status register High
SCC Receive Current Buffer Address register PCCchip2
SCC Error Status register ($FFF4201C)
Comments:SCC Transmit and Receive interrupt enables are controlled
in the SCC and in the PCCchip2.
1-60Computer Group Literature Center Web Site
SCC LTO Error
Description:Local Bus Time-out occurred while the SCC was Local
MPU Notification:SCC Transmit Interrupt or SCC Receive Interrupt
Status:SCC Transmit Interrupt Status register
Comments:SCC Transmit and Receive interrupt enables are controlled
LAN Parity Error
Description:Parity error while the LANCE was reading DRAM
MPU Notification:PCCchip2 Interrupt (LAN ERROR IRQ)
Status:PCCchip2 LAN Error Status register ($FFF42028)
Error Conditions
1
Bus master.
SCC Transmit Current Buffer Address register
SCC Receive Interrupt Status register High
SCC Receive Current Buffer Address register PCCchip2
SCC Error Status register ($FFF4201C)
in the SCC and in the PCCchip2.
Comments:The LANCE has no ability to respond to TEA so the error
interrupt and status are provided in the PCCchip2. Co ntro l
for the interrupt is in the PCCchip2 LAN Error Interrupt
Control register ($FFF4202B).
LAN Offboard Error
Description:Error encountered while the LANCE was attempting to go
to the VMEbus.
MPU Notification:PCCchip2 Interrupt (LAN ERROR IRQ)
Status:PCCchip2 LAN Error Status register ($FFF42028)
Comments:The LANCE has no ability to respond to TEA so the error
interrupt and status are provided in the PCCchip2. Co ntro l
for the interrupt is in the PCCchip2 LAN Error Interrupt
Control register ($FFF4202B).
http://www.motorola.com/computer/literature1-61
1
Programming Issues
LAN LTO Error
Description:Local Bus Time-out occurred while the LANCE was Local
Bus master.
MPU Notification:PCCchip2 Interrupt (LAN ERROR IRQ)
Status:PCCchip2 LAN Error Status register ($FFF42028)
Comments:The LANCE has no ability to respond to TEA so the error
interrupt and status are provided in the PCCchip2. Co ntro l
for the interrupt is in the PCCchip2 LAN Error Interrupt
Control register ($FFF4202B).
SCSI Parity Error
Description:Parity error detected while the 53C710 was reading
DRAM.
MPU Notification:5 3C 710 Interrupt
Status:53C710 DMA Status register
53C710 DMA Inte rrupt Status register
PCCchip2 SCSI Error Status register ($FFF4202C)
Comments:53C710 interrupt enables are controlled in the 53 C710 and
in the PCCchip2.
SCSI Offboard Error
Description:Error encountered while the 53C710 was attempting to go
to the VMEbus.
MPU Notification:5 3C 710 Interrupt
Status:53C710 DMA Status register
53C710 DMA Inte rrupt Status register
PCCchip2 SCSI Error Status register ($FFF4202C)
Comments:53C710 interrupt enables are controlled in the 53 C710 and
in the PCCchip2.
1-62Computer Group Literature Center Web Site
SCSI LTO Error
Description: Local Bus Time-ou t occurred while the 53C 710 was Local
MPU Notification:5 3C 710 Interrupt
Status:53C710 DMA Status register
Comments:53C710 interrupt enables are controlled in the 53 C710 and
Error Conditions
1
Bus master.
53C710 DMA Inte rrupt Status register
PCCchip2 SCSI Error Status register ($FFF4202C)
in the PCCchip2.
http://www.motorola.com/computer/literature1-63
1
Programming Issues
1-64Computer Group Literature Center Web Site
Introduction
This chapter describes the VMEchip2 ASIC, the local-bus/VMEbus
interface chip.
The VMEchip2 interfaces the local bus to the VMEbus. In addition to its
VMEbus-defined functions, the VMEchip2 includes a local-bus-toVMEbus DMA controller, VME board support features, and Global
Control and Status Registers (GCSRs) for int erprocessor communications .
The following table summarizes the characteristics of the VMEchip2
ASIC.
Table 2-1. Features of the VMEchip2 ASIC
FunctionFeatures
Local-Bus-toVMEbus Interface
2VMEchip2
Programmable local bus map decoder
Programmable short, standard, and extended VMEbus addressing
Programmable AM codes
Programmable 16-bit and 32-bit VMEbus data width
Software-enabled write posting mode
Write post buffer (one cache line or one four-byte)
Automatically performs dynamic bus sizing for VMEbus cycles
Software-configured VMEbus access timers
Local-bus-to-VMEbus Requester with:
Programmable VMEbus map decoder
Programmable AM decoder
Programmable local bus snoop enable
Simple VMEbus-to-local-bus address translation
8-bit, 16-bit and 32-bit VMEbus data width
8-bit, 16-bit and 32-bit block transfer
Standard and extended VMEbus addressing
Software-enabled write posting mode
Write post buffer (17 four-bytes in BLT mode, two four-bytes in non-
BLT mode)
An eight four-byte read ahead buffer (BLT mode only)
Programmable 16-bit, 32-bit, and 64-bit VMEbus data width
Programmable short, standard, and extended VMEbus addressing
Programmable AM code
Programmable local bus snoop enable
16 four-byte FIFO data buffer
Up to 4 GB of data per DMA request
Automatically adjustment of transfer size to optimize bus utilization
DMA comple t e interru pt
DMAC command chaining supported by a singly-linked list of DMA
Programmable arbitration timer
IACK daisy-chain driver
Programmable bus timer
SYSRESET logic
Four location monitors
Global control of locally detected failures
Global control of local reset
Four global attention interrupt bits
A chip ID and revision register
Four 16-bit dual-ported general purpose registers
All interr upts maskab l e
All interrupts providing a unique vector
Software and external interrupts
2
http://www.motorola.com/computer/literature2-3
VMEchip2
2
Functional Blocks
The following sections pr ovide an overvie w of the functions implemented
by the VMEchip2 ASIC. See Figure 2-1 for a block diagram of the
VMEchip2. Detailed programmin g models for t he local c ontrol an d status
registers (LCSRs) and the global control and status registers (GCSRs)
appear in subsequent sections.
Local-Bus-to-VMEbus Interface
The local-bus-to-VMEbus interface allows local bus masters access to
global resources on the VMEbus. This interface incl udes a local bus slave ,
a write post bu ffer, and a VMEbus master.
Using programmable map decoders with progr ammable att ribute bit s, the
local-bus-to-VMEbus interface can be c onfigured to provide the following
VMEbus capa bilities:
Addressing capabilities:A16, A24, A32
Data transfer capabilities:D08, D16, D32
The local bus slave includes six local bus map decoders for accessing the
VMEbus. The first four map decoders are general purpose pro gramma ble
decoders, while the other two are fixed and are dedicated for I/ O decoding.
The first four map de code rs compare local bus address lines A31 through
A16 with a 16-bit s tart addre ss an d a 16 -bit end a ddress . When an a ddress
in the selec t ed range is detected, a VM Ebus select is generated to the
VMEbus master. Each map decoder also has eight attribute bits and an
enable bit. The attribut e bits are for VMEbus AM (ad dress modifie r)
codes, D16 enable, and write post (WP) enable.
The fourth map decoder also includes a 16-bit alternate address register
and a 16-bit alternate address select register. This allows any or all of the
upper 16 address bits from the local bus to be replaced by bits from the
alternate address register. The f eature allows th e local bus mas ter to access
any VMEbus address.
2-4Computer Group Literature Center Web Site
Functional Blocks
2
DATA
CONTROL
ADDRESS
1344 9403
VMEBUS TO LOCAL BUS INTERFACE
VMEBUS MASTER
FIFO
LOCAL BUS MASTER
DATA
DATA
DATA
DATA
DATA
DATA
ADDRESS
CONTROL
DATA
CONTROL
CONTROL
DATA
16 ENTRY BY 4 BYTES
DMA CONTROL
GCSR
DATA
DMA CONTROLLER
CONTROL
CONTROL
CONTROL
ADDRESS
ADDRESS
ADDRESS
GLOBAL CONTROL / STATUS REGISTER
CONTROLCONTROL
CONTROLCONTROL
CONTROL
CONTROL
DATA
CONTROL
ADDRESS
CONTROL
ADDRESS
VMEBUS SL AVE
FIFO
DATA
DATA
DATA
ADDRESS
CONTROL
CONTROL
ADDRESS
CONTROL
ADDRESS
CONTROL
16 ENTRY BY 4 BYTES
DATA
DATADATA
ADDRESS
CONTROL
DATA
CONTROL
ADDRESS
CONTROL
CONTROL
ADDRESS
4 ENTRY BY 4 BYTES
LOCAL BUS TO VMEBUS INTERFACE
CONTROLCONTROL
DATA
DATA
CONTROL
CONTROL
ADDRESS
ADDRESS
CONTROL
DATA
CONTROLCONTROL
DATA
LOCAL BUS MASTER
DATA
CONTROL
CONTROL
ADDRESS
ADDRESS
CONTROL
DATA
LOCAL BUSLOCAL BUS SLAVEFIFOVMEBUS MASTERVMEBUS
CONTROL
ADDRESS
Figure 2-1. VMEchip2 Block Diagram
http://www.motorola.com/computer/literature2-5
VMEchip2
2
Using the four programmable map decoders, separate VMEbus maps can
be created, each with its own attributes. For example, one map can be
configured as A32, D32 with write posting enabled while a second map
can be A24, D16 with write posting disabled.
The first I/O map dec oder decodes local bu s addresses $FFFF0000 throug h
$FFFFFFFF as the short I/O A16/D16 or A16/D32 area. The other
provides an A24/D16 s pace at $F0000000 t o $F0FFFFFF and an A32 /D16
space at $F1000000 to $FF7FFFFF.
Supervisor/non-privileged and program/data space is determined by
attribute bits. Write posting may be enabled or disabled for each decoder
I/O space and this map decoder may be enabled or disabled.
When write pos ting is enab led, the VMEchip 2 stores the local bus addre ss
and data and then acknowledges the loca l bus maste r. The loca l bus is then
free to perform other operations while the VMEbus master requests the
VMEbus and performs the requested operation.
The write post buffer stores data in sin gle-byte, doubl e-byte, quad-byte , or
one-cache-line (four quad-bytes) form. Write posting should only be
enabled when bus errors are not expected. If a bus error is returned on a
write posted cycle and the interrupt is enabled, the local processor is
interrupted. The address of the error is not saved. Normal memory never
returns a bus error on a write cycle. However, some VMEbus ECC
memory cards perform a read-modify-write operation and therefore may
return a bus error if there is an error on the read portion of a read-modifywrite. Write posting shoul d not be enabled when thi s type of memory card
is used. Also, memory should not be sized using write operations if write
posting is enabled. I/O areas that have holes should not be write posted if
software may access non-e xiste nt memory. Usi ng the pr ogrammabl e map
decoders, write posting can be enabled for “safe” areas and disabled for
areas which are not “safe”.
Block transfer is not supported because the MC680x0 block transfer
capability is not compatibl e with the VMEbu s.
The VMEbus master supports dynamic bus sizing. When a local device
initiates a quad-byte a ccess t o a VMEbus slave that on ly has t he D16 dat a
transfer capability, the chip executes two double-byte cycles on the
VMEbus, acknowledging the local device after all requested four-bytes
2-6Computer Group Literature Center Web Site
Functional Blocks
have been accessed. This enhances the portability of software because it
allows software to run on the system regardless of the physical
organization of global memory.
Using the local bus map decoder attribute register, the AM code that the
master places on the VMEbus can be pr ogrammed under software co ntrol.
The VMEchip2 includes a software-controlled VMEbus access timer. It
starts ticking when the chip is requested to do a VMEbus data transfer or
an interrupt acknowledge cycle. The timer stops ti cking on ce the chi p has
started the data transfer on t he VMEbus. If the data trans fer does not be gin
before the timer times out, the timer drives the local bus error signal, and
sets the appropriate status bit in the Local Control and Status Register
(LCSR). Using control bits in the LCSR, the timer can be disa bled, or it
can be enab led to drive the local bus er ror signal aft er 64 µs, 1 ms, or 32
ms.
The VMEchip2 includes a software-controlled VMEbus write post timer.
It starts ticking when a data transfer to the VMEbus is write posted. The
timer stops ticking once the chip has started the data transfer on the
VMEbus. If this does not happen before the t imer times out, the chi p aborts
the write posted cycle and sends an interr upt to the local bus interrupter . If
the write post bus error interrupt is enabled in the local bus interrupter, the
local processor is interrupted to indicat e a write post time-out ha s occurred.
The write post timer has the same timing as the VMEbus access timer.
2
Local-Bus-to-VMEbus Requester
The requester provides all the signals necessary to allow the local-bus-toVMEbus master to request and be granted use of the VMEbus. The chip
connects to all signals that a VMEbus requester is required to drive and
monitor.
Requiring no external j umpers, the chip provides th e means for software to
program the reque ster to re quest the bu s on any o ne of the f our bus reque st
levels, automatically establishing the bus grant daisy-chains for the three
inactive levels.
http://www.motorola.com/computer/literature2-7
VMEchip2
2
The requester requests the bus if any of the following conditions occur:
1. The local bus master initiates either a data transfer cycle or an
interrupt acknowledge cycle to the VMEbus.
2. The chip is requested to acquir e control of the VMEbus as signale d
by the DWB input signal pin.
3. The chip is requested to acquir e control of the VMEbus as signale d
by the DWB control bit in the LCSR.
The local-bus-to-VMEbus requester in the VMEchip2 implements a fair
mode. By setting the LVFAIR bit, the requester refrains from requesting
the VMEbus until it detects its assigned request line in its negated state.
The local-bus-to- VMEbus requester attemp ts to release the VMEbus when
the requested data transfer op eration is co mplete, the DWB pin is negate d,
the DWB bit in the LCSR i s negated and t he bus is not being held by a lock
cycle. The requester releases the bus as follows:
1. When the chip is configured in release-when-done (RWD) mode,
the requester releases the bus when the above conditions are
satisfied.
2. When the chip is configured i n release- on-request (ROR) mode, the
requester releases the bus when the above conditions are satisfied
and there is a bus request pending on one of the VMEbus request
lines.
To minimize the timing over head of the arbitration pro ces s, t he local-busto-VMEbus requester in the VMEchip2 executes an early release of the
VMEbus. If it is about to release the bus and it is executing a VMEbus
cycle, the requester release s BBSY before its associ ated master completes
the cycle. This allows the arbiter to arbitrate any pending requests, and
grant the bus to the next r eque st er, at the same time that the a cti ve maste r
completes its cycle.
2-8Computer Group Literature Center Web Site
Functional Blocks
VMEbus-to-Local-Bus Interface
The VMEbus-to-local-bus interface allows an off-board VMEbus master
access to onboard reso urces. The VM Ebus-to-loca l-bus int erface i ncludes
the VMEbus slave, write post buffer, and local bus master.
Adhering to the IEEE 1014-87 VMEbus standard , the sl ave can withstand
address-only cycles, as well as address pipelining, and respond to
unaligned transfers. Using programmable map decoders, it can be
configured to provide the following VMEbus capabilities:
Addressing capabilities:A24, A32
Data transfer capabilities: D08(EO), D16, D32, D 8/BLT,
The slave can be programmed to perform write po st in g operations. When
in this mode , the chip latches incoming data and addressing information
into a staging FIFO an d the n ackn owledges the VMEbus write tr ansfe r by
asserting DTACK∗. The chip then requests control of the local bus and
independently acce sses the local resourc e after it has been grant ed the local
bus. The write-posting pip eline is two deep in non-block transf er mode and
16 deep in block transfer mode.
2
D16/BLT, D32/BLT, D64/BLT
(BLT = block transfer)
To significantly improve the access time of the slave when it responds to
a VMEbus block read cycle, the VMEchip2 contains a 16 four-byte deep
read-ahead pipeline. When responding to a block read cycle, the chip
performs block read cycles on the local bus to keep the FIFO buffer full.
Data for subs equent transfe rs is then retrieved from the on-chip buffer,
significantly improving the response time of the slave in block transfer
mode.
The VMEchip2 includes an on-chip map decoder that allows software to
configure the global addressing range of onboard resources. The decoder
allows the local address range to be partitioned into two separate banks,
each with its own start and end address (in increments of 64KB), as well
as setting each bank’s address modifier codes, write post enable, and sn oop
enable.
http://www.motorola.com/computer/literature2-9
VMEchip2
2
Each map decoder includes an alternate address register and an alternate
address select register. These registers allow any or all of the upper 16
VMEbus address lines to be replaced by s ignals fr om the altern ate address
register. This allows the address of local resources to differ from their
VMEbus address.
The alternate a ddress regist er also provi des the upper eight bits of the local
address when the VMEbus sl ave cycle is A24.
The local bus master requests the local bus and executes cycles as
required. To reduce local bus loading and impr ove per formance it always
attempts to transfer data usi ng a burs t trans fer as d efined by the MC680x0.
When snooping is enabled, the local bus master requests the cache
controller in the MC680x0 to monitor the local bus addresses.
Local-Bus-to-VMEbus DMA Controller
The DMA Controller (DMAC) op erates in conjunction with the local bus
master, the VMEbus master, and a 16 four-byte FIFO buffer. The DMA
controller has a 32-bit local address counter, 32-bit table addr ess counter,
a 32-bit VMEbus address counter, a 32-bit byte counter, and control and
status registers. The Local Control and Status register (LCSR) provides
software with the ability to control the operational modes of the DMAC.
Software can program the DMAC to transfer up to 4GB of data in the
course of a single DMA oper ation. The DMAC supports transf ers from any
local bus address to any VMEbus address. The transfers may be from 1
byte to 4GB in length.
To optimize local bus use, the DMAC automatically adjusts the size of
individual data transfers until 32-bit transfers can be executed. Based on
the address of the first byte, the DMAC transfers a single-byte, a
double-byte, or a mixture of both, and then conti nues to execute quad-byt e
block transfer cycles. When the DMAC is set for 64-bit transfers, the
octal-byte transfers takes place. Based on the address of the last byte, the
DMAC transfers a single byte, a double byte, or a mixture of both to end
the transfer.
2-10Computer Group Literature Center Web Site
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.