and the Motorola logo are registered trademarks of Motorola, Inc.
MC68040™ and MC68060™ are trademarks of Motorola, Inc.
IndustryPack™ and IP™ are trademarks of GreenSpring Computers, Inc.
All other products ment io ned i n this document are trademarks or re gi stered trademarks of
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, precede pote ntia lly da nger ous pro cedu res th rough out th is manual . In struc tion 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 equipment in y our operating environment.
To prevent serious injury or death from dangerous voltages, use extreme
caution when handling, testing, and adjusting this equipment and its
All Motorola PWBs (printed wiring boards) are manufactu red 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
may cause or be susceptible to electromagnetic interference (EMI) if not
installed and used with adequate EMI protection.
Lithium Battery Caution
This product contains a lithium battery to power the clock and calendar circuitry.
Danger of explosion if battery is re placed incorrect ly. Replace battery only
!
Caution
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 Batt er ie . Ers at z nur
durch denselben ode r einen vom Herstel ler empfohle nen Typ. Entsorgu ng
gebrauchter Batterien nach Angaben des Herstellers.
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 re serves the right to revise this
document and to ma ke c hanges from time to time in the content hereof witho ut obligation
of Motorola to notify any person of such revision or changes.
Electronic versions of this material may be read online, downloaded for personal use, or
referenced in another document as a URL to the Motorola Computer Group website. The
text itself may not 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 ref er ence to or information 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.
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 at 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
MVME172P4 VME Embedded Controller Installation and Use provides
instructions for hardware preparation and installation; a board-level
hardware overview ; and firmwa re-rel ated genera l inform ation and st artup
instructions for the MVME172P-644 series of embedded controllers,
known collectively as the ‘‘MVME172P4’’ because they are equipped
with the “Petra” chip and accommodate up to four IP modules.
The “Petra” chip that dist inguishes MVME172P4 embe dded control lers is
an application-specific integrated circuit (ASIC) which combines the
functions previously covered by the MC2 chip, the IP2 chip, and the
MCECC chip in a single ASIC. As of the publica tion date, the informati on
presented in this manual applies to the following MVME172P4 models:
If the part number of your board includes a "PA" (for example:
MVME172PA-644L), your board is equipped with a second-generation
Petra ASIC. All other particulars of the board remain the sa me.
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 the Related Documentation secti on
in Appendix E.
This is the second edition of MVME172P4 Installation and Use. It
supersedes the September 2000 edition and incorporates the following
updates.
DateDescription of Change
October 2000 In the description of the snoop control switch on page 1-18, entries in the table
concerning boards equipped with the MC68060 processor have been corrected.
October 2000 Several jumper drawings and configuration descriptions in Chapters 1 and 2
have been updated to reflect the current board layout and shipping
configuration.
October 2000 In the descriptions of the MC2 and MCECC DRAM size switches on pages
1-15 and 1-21, the importance of executing env;d after modifying switch
settings has been emphasized.
Overview of Contents
Chapter 1, Hardware Preparation and Installation, provides unpacking
instructions, hardware preparation guidelines, and installation instructions
for the MVME172P4 VME Embedded Controller.
xvi
Chapter 2, Startup and Operation, provides information on powering up
the MVME172P4 VME Embedded Controller after its installation in a
system and describes the functionality of the switches, status indicators,
and I/O ports.
Chapter 3, 172Bug Firmware, describes the basics of 172Bug and its
architecture, describes the monitor (interactive command portion of the
firmware) in detail, and gives information on using the debugger and
special commands.
Chapter 4, Functional Description, describes the MVME172P4 VME
Embedded Controller on a block diagram level.
Chapter 5, Pin Assignments, summarizes the pin assignments for the
various groups of interconnect signals on the MVME172P4.
Appendix A, Specifications, lists the general specifications for the
MVME172P4 Embedded Controller. Subsequent sections of the appendix
detail cooling requirements and EMC regulatory compliance.
Appendix B, Troubleshooting, includes simple troubleshooting steps to
follow in the event t hat you hav e diffic ulty with your MVME172P4 VME
Embedded Controller.
Appendix C, Network Controller Data, describes the VMEbus network
controller modules that are supported by the 172Bug firmware.
Appendix D, Disk/Tape Controll er Data, de scribes th e VMEbus disk/t ape
controller modules that are supported by the 172Bug firmware.
Appendix E, Related Documentation, provides all documentation related
to the MVME172P4.
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
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.
The following typographical conventions are used in this document:
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
xviii
represents the Control key. Execute control characters by pressing the
Ctrl key and the letter simultaneously, for example, Ctrl-d.
A character precedes a data or address parameter to specify the numeric
format, as follows:
$Specifies a hexadecimal character
0xSpecifies a hexadecimal number
%Specifies a binary number
&Specifies a decimal number
An asterisk (∗) following a signal name for si gnals that are level sig nificant
denotes that the signal is true or valid when the signal is low. An asterisk
(∗) following a signal name for signals that are edge significant denotes
that the actions initiated by that signal occur on high to low transition.
This chapter provides unpacking instructions, hardware preparation
guidelines, and installation instructions for the MVME172P4 VME
Embedded Controller. Hardware preparation of the MVME712 series
transition modules compatible with this board is described in separate
manuals.
Getting Started
This section supplies an overview of startup procedures applicable to the
MVME172P4. Equipment requirements, directions for unpacking, and
ESD precautions that you should take complete the section.
Overview of Installation Procedure
The following table lists the things you will need to do to use this board
and tells where to find the info rmat io n you need to perform each step. Be
sure to read this entire chapter, including all Cautions and Warnings,
before you begin.
Installation
1
Table 1-1. Startup Overview
What you need to do...Refer to...
Unpack the hardware. Guidelines for Unpacking on page 1-3.
Reconfigure jumpers or swit ches
on the MVME172P 4 board as
necessary.
Ensure that IP modules are
properly installed on the
MVME172P4 boar d.
Install the MVM E172P4 board in
a chassis.
Connect a display terminal.Serial Connections on page 1-28.
Note If the shipping carton is damaged upon receipt, request that the
carrier’s agent be presen t during the unpa cking and in spection of
the equipment.
Unpack the equipment from the shipping carton. Refer to the packing list
and verify that al l items are present. Sa ve t h e pac king material for storing
and reshipping of equipment.
Getting Started
1
!
Caution
Avoid touching areas of integrated circuitry; static discharge can damage
circuits.
ESD Precautions
This section applies to all hardware installations you may perform that
involve the MVME172P4 board.
Motorola strongly recommends the use of an antistatic wrist strap and a
conductive foam pad when you install or upgrade the board. Electronic
components can be extremely sensi tive to ESD. After removi ng the board
from the chassis or from its protective wrapper, place the board flat on a
grounded, static-free surface, component side up. Do not slide the board
over any surface.
If no ESD station is available, you can av oid dama ge re sul ti ng fr om ESD
by wearing an antistatic wrist strap (available at electronics stores). Place
the strap around your wrist and attach the grounding end (usually a piece
of copper foil or an alligator clip) to an electrical ground. An electrical
ground can be a piece of metal that literally runs into the ground (such as
an unpainted met al pipe) or a metal part of a grounded electric al appliance.
An appliance is grou nded if it has a thr ee-pro ng plug and i s plugged i nto a
three-prong grounde d outlet . You can not use th e chassi s in which you are
installing the MVME172P4 itself as a ground, because the enclosure is
unplugged while you work on it.
Turn the system’s powe r off be fore you perform t hese proc edures. Fail ure
!
Warning
to turn the power off before opening the enclosure can result in personal
injury or damage to the equipment. Hazardous voltage, current, and ene rgy
levels are present in the chassis. Hazardous voltages may be present on
power switch terminals even when the powe r switc h is off. Neve r opera te
the system with the cover removed. Always replace the cover before
powering up the system.
Preparing the Board
To produce the desired configuration and ensure proper operation of the
MVME172P4, you may need to reconfigure hardware to some extent
before installing the module.
Most options on the MVME172P4 are under software control: By setting
bits in control registers after installing the module in a system, you can
modify its configuration. (The MVME172P4 registers are described in
Chapter 3 under ENV – Set Environme nt, and/or in the MVME1x2P4 VME Embedded Controller Progr ammer's Reference Guide as listed in “Relate d
Documentation” in Appendix E.)
Some options, though, are not software-programmable. Such options are
either set by configuration switches or are controlled through physical
installation or removal of head er jumpers o r interface modules on th e base
board.
Figure 1-1 illustrates the placement of the jumper headers, connectors,
configuration switches, and various other components on the
MVME172P4. Manually configurable jumper headers and configuration
switches on the MVME172P4 are listed in the following table.
NoteJumper J3is not listed, as it is provided for manufacturing
purposes only and cannot be configured.
Table 1-2. MVME172P4 Configuration Settings
FunctionFactory Default
VME System Controller (J1)2-3
IP Bus Clock (J14)1-2
SIM Selection for Serial Port B (J15)SIMM06
Serial Port 1/Console Clock (J16)No jumpers
Serial Port 2 Cloc k (J 17 )No jumpers
IP Bus Strobe (J19)No jumper
Preparing the Board
1
SRAM Backup Power Source (J22)1-3, 2-4
EPROM Size (J23)2-3
Flash Write Protection (J24)Jumper on
MC2 DRAM Size (S3)Off-Off-Off
If you modify the switch settings, you will need to execute env;d
<CR> so that the firmware recognizes the new memory
defaults.
IP DMA Snoop Cont rol (S5 Pins 1/2)On-On
IP Reset Mode (S5 Pin 3)On
Flash Write Enable Mode (S5 Pin 4)On
MCECC DRAM Size (S6)On-Off-On
The MVME172P4 board is factory-configured in "automatic" system
controller mode with a jumper across J1 pins 2 -3. In this confi guration, the
MVME172P4 determines whe ther it is the system cont roller by its positi on
on the bus. If the bo ard is located i n the first sl ot from the lef t, it configure s
itself as the system controller. When the board is operating as system
controller, the
If you want the MVME172P4 to fu nction as syste m controlle r in all cases,
move the jumper to pins 1-2. If the MVME172P4 is not to be system
controller under any circumstances, remove the jumper from J1.
NoteOn MVME172P4 boards without the option al VMEbus interface
SCON LED is turned on.
(i.e., with no VMEchip2 ASIC), the jumper may be installed or
removed with no effect on normal operation.
Header J14 selects the speed of the IP bus clock. The IP bus clock speed
may be 8MHz or it may be set to the speed of the local bus clock (i.e.,
30MHz for the 60MHz MC68060 or 32MHz for the 64MHz
MC68LC060). The default f actory conf iguration has a jumper installed on
pins 1-2, denoting an 8MHz clock.
If the jumper is installed on J14 pins 2-3, the IP bus clock speed matches
that of the proce ssor l ocal bu s cl ock (3 0/32MHz ), all owin g the I P modul e
to pace the MPU. Whether the setting is 8MHz or the local bus clock
speed, all IP ports operate at the same speed.
The setting of the IP32 bit in t he Control/St atus regist ers (Petra IP2 sector ,
!
Caution
register at offs et $1 D, bit 0) must co rresp ond to tha t of th e jumper. Th e bit
is cleared (0) for 8MHz, or set (1) t o match the proce ssor bus clock spe ed.
If the jumper and the CSR bi t a re not configured the same, the boa rd ma y
not run properly.
Port B of the MVME172P4 Z85230 serial communications controller is
configurable via a serial interface module (SIM) that is installed at
connector J15 on the board. Five serial interface modules are available:
❏ EIA-232-D (DCE and DTE)
❏ EIA-530 (DCE and DTE)
❏ EIA-485/EIA-422 (DCE or DTE)
You can change Port B from an EIA-232-D to an EIA-530 interface or to
an EIA-485/EIA-42 2 interface (or vice -versa) by mounting the appropriate
serial interface module. Port B i s rout ed (vi a the SIM at J 15) to the 25- pin
DB25 front panel connector marked
For the location of SI M connector J15 on the MVME172 P4, refer to Figur e
1-1. Figure 1-2 illustrates the sec ondary s ide (b ott om) of a seria l in ter face
module, showing the J1 connecto r which plugs int o SIM connector J15 on
the MVME172P4. Figure 1-3 (sheets 3-6), Figu re 1-4, and Figure 1-5
illustrate the seven configurations available for Port B.
Preparing the Board
1
SERIAL PORT 2.
391
402
SECONDARY SIDE
J1
1568 9502
Figure 1-2. Serial Interface Module, Connector Side
For the part numbers of the serial interf ace modules, refer to Table 1-2. The
part numbers are ord ina ri ly printed on the primary s id e ( to p) of the SIMs,
but may be found on the secondary side in some versions.
If you need to replace an existing serial interface module with a SIM of
another type, go to Removal of Existing SIM below. If there is no SIM on
the main board, skip to Installation of New SIM.
Table 1-2. Serial Interface Module Part Numbers
EIA StandardConfigurationPart Num ber
EIA-232-DDTE01-W3846BSIMM05
EIA-530DTE01-W3868BSIMM07
EIA-485-or EIA-422DTE or DCE
Removal of Existing SIM
1. Each serial interface module is retained by two 4-40 x
Phillips-head screws in opposite corners. (Exception: SIMM09 is
retained by one Phillips-head screw in the center of the module.)
Remove the screw(s) and store them in a safe place for later use.
2. Grasp opposite sides of the SIM and gently lift straight up.
Avoid lifting the SIM by one side only, as the connector can be damaged
!
Caution
on the SIM or the main board.
3. Place the SIM in a static-safe container for possible reuse.
1. Observe the orientati on of the connect or keys on SIM connec tor J1
and MVME172P4 connector J15. Turn th e SIM so that the keys line
up and place it gently on connector J15, aligning the mounting
hole(s) at the SIM c orners (or center) wi th the mat ching stand off(s)
on the MVME172P4.
2. Gently press the top of the SIM to seat it on the connector. If the
SIM does not seat with gentle pressure, recheck the orientation. If
the SIM connector is oriente d incorrectly, the mounti ng hole(s) will
not line up with the standoff(s).
Do not attemp t to force the SIM into place if it is oriented incorrectly.
!
Caution
3. Place the one or two 4-40 x
previously removed (or that were supplied with the new SIM) into
the one center or two opposite-corner mounting hole(s). Turn the
screw(s) into the standoff(s) but do not overtighten.
The signal relationships and signal connections in the various serial
configurations available for ports A and B are illustrated in Figures 1-3
through 1-5.
The MVME172P4 is shipped from the factory with the SERIAL PORT
1/CONSOLE header configured for asynchronous communications (i.e.,
jumpers removed). To selec t synchronous c ommunications f or
PORT 1/CONSOLE connection, install jumpers acr oss pins 1- 2 and pins 3-4.
J16J16
3434
1212
External ClockInternal Clock
(Factory configuration)
the SERIAL
Serial Port 2 Clock (J17)
The MVME172P4 is shipped from the factory with the SERIAL PORT 2
header configured for asynchronous communications (i.e., jumpers
removed). To select sync hronous communica tions for t he
connection, install jumpers across pins 1-2 and pins 3-4.
Some IP bus implementations make use of the Strobe∗ signal (pin AA19
on the Petra ASIC) a s an input to the IP mod ules from t he Petra IP 2 sector.
Other IP interfaces require that the strobe be disconnected.
With a jumper installed between J19 pin s 1-2, a programmable fr equency
source is connecte d to the Strobe ∗ signal on the IP bus (for details, refer to
the Petra/IP2 chip programming mod el in the Programmer’s Reference Guide).
If the jumper is removed from J19, the strobe line is available for a
sideband type of mes saging between I P modules. The Strobe∗ signal is not
connected to any active d evices on th e board, but i t may be connect ed to a
pull-up resistor.
Preparing the Board
1
J19
2
1
IP Strobe disconnected
(Factory configuration)
SRAM Backup Power Source (J22)
Header J22 determines th e sourc e fo r onboar d stati c RAM backu p power.
The MVME172P4 is factory-configured to use VMEbus +5V standby
voltage as a backup power source for the SRAM (i.e., j umpers are installed
across pins 1-3 and 2-4). To select the onboard battery as the backup
power source, install the jumpers across pins 3-5 and 4-6.
NoteFor MVME172P4s without the opt i onal VMEbus interface (i.e.,
without the VMEchip2 ASIC), you must select the onboard
battery as the backup power source.
When the Flash write-enable jumper is installed (factory configuration),
Flash memory can be written to via the normal software routines. When
the jumper is removed, Flash memory is not wr itable.
Preparing the Board
1
J24
2
1
Flash Write-Protected
MC2 DRAM Size (S3)
MVME1x2P4 boards use SDRAM (Synchronous DRAM) in place of
DRAM. The MVME172P4’s 16MB shared SDRAM is configurable to
emulate either of the following memory models:
❏ 1MB, 4MB, 8MB, or 16MB shared parity-protected DRAM
❏ 4MB, 8MB, or 16MB ECC-protected DRAM
The two memory controllers modeled in the Petra ASIC duplicate the
functionality of the “parity memory controller” found in MC2 ASICs as
well as that of the “single-bit error correcting/double-bit error detecting”
memory controller found in MCECC ASICs. Board firmware will
initialize the memory controller as appropriate.
J24
2
1
Flash Write-Enabled
(Factory configuration)
If the Petra ASIC is supporting MVME1x2P4 functionality, firmware will
enable the parity (MC2) memory cont roller model. If the Petr a ASIC is
supporting MVME1x2P2 functionality, firmware will enable either the
parity or the MCECC memory controller model, depending on the board
configuration. Board configuration is a function of switch settings and
resistor population options.
S3 comes into play in the MC2 memory controller model. S3 is a foursegment slide switc h whose lower th ree seg ment s estab lish t he si ze of t he
parity DRAM (segment 4 is not used.) Refer to the illustration and table
below for specifics.
Notes As shown in the preceding table, the Petra/MC2 interface
supports parity DRAM emulations up to 16MB. For sizes
beyond 16MB, it is necesary to use the MCECC memory
model.
For access to the MCECC registers, you must first disabl e the
MC2 interface by setting S3 to 001 (Off/Off/On). Further
details on selecting the MCECC emulation can be found
under MCECC DRAM Size (S6).
If you modify the swit ch setting s, you will ne ed to execute env;d
<CR> so that the f irmware recogniz es the new memory default s.
Switch S4 is similar in function to the general-purpose re adable jumper
headers found on earlier MVME162/172 ser ie s boards. S4 provides eight
software-readable switch segments. These switches can be read as bits in
a register (at address $FFF4202C) in the MC2 General-Purpose Inputs
register in the Petra ASIC (refer to the Programmer’s Reference Guide for
details). Bit GPI7 is associated with switch segment 1; bit GPI0 is
associated with switch segme nt 8. Th e bit values are read as a 0 when the
switch is on, and as a 1 when the switch is off. The MVME172P4 is
shipped from the factory with S4 set to all 0s (all switches set to
diagrammed below.
If the MVME172Bug firmware is installed, four bits are user-definable
(i.e., switch segments 1-4). If the MVME172Bug fir mware is not instal led,
seven bits are user-definable (i.e., segments 1-4 and segments 6-8).
NoteSwitch segment 5 (GPI3) is reserved to s elect either the Fl ash
Segments 1 and 2 of switch S5 define the state of the snoop control bus
when an IP DMA controller is local bus master . As shown in Table 1-4, S5
segment 1 controls Snoop Contr ol signal 1 on the MC68 0x0 processor. S5
segment 2 controls Snoop Control signal 0. Setting a segment to
produces a logical 0; setting it to
ONOFF
4
1
OFF produces a logical 1.
S5
Snoop inhibited
(factory configuration)
2736 0004 (1-3)
S5 varies in function according to the type of processor installed. For
MVME162P4 boards with an MC68040 pro cessor, settin g segments 1 and
2 of switch S5 to
OFF or leaving both segments set to ON (the factory
configuration) inhibits snooping. Enabling snooping requires one of two
possible
ON/OFF combinations, according to the operation desired.
MVME172P4 boards with an MC68060 processor have different snoop
functionality.
ON
The following table lists the snoop operations represented by the settings
of S5 with both types of processor. For further details, refer to the
MC68040 or MC68060 microprocessor user’s manuals listed in the
Related Documentation appendix.
Segment 3 of switch S5 defi nes the IP controller model (IP1 or IP2) to be
emulated when the board comes up. With S5 segment 3 set to
factory configuration), the board initializes in IP2 mode. With S5 segment
3 set to
In IP2 mode, IP resets occur only in response to a direct software write or
to a power-up reset; the IP reset control bit is not self-clearing.
In IP1 mode, the IP reset control bit clears itself after after a 1msec
interval. IP resets may occur in response to a software write, a power-up
reset, or a local b us reset. For details, r efer to the Programmer’s Reference
Guide listed in “Related Documentation” in Appendix E.
Segment 4 of switch S5 define s the Flash memor y controlle r model (MC1
or MC2) to be emulated when enabling or disabling Flash memory
accesses on the MVME172P4 board. With S5 segment 4 set to
factory configuration), the board initializes in MC2 mod e. With S5
segment 4 set to
In MC2 mode, writes to Flash memory are enabled or inhibited by a
control bit at memory location $FFF42042. With the control bit set to
Flash memory is write-enabled.
ON (the
2736 0004 (3-3)
1,
In MC1 mode, writes to Flash memo ry are enabled by a me mory access to
any location in the range $FFFCC000-$FFFCFFF. Writes to Flash
memory are disabled by a memory access to any location in the range
$FFFC8000-$FFFCBFFF. For details, refer to the Programmer’s
Reference Guide listed in “Related Documentation” in Appendix E.
MVME1x2P4 boards use SDRAM (Synchronous DRAM) in place of
DRAM. The MVME172P4’s 16MB shared SDRAM is configurable to
emulate either of the following memory models:
❏ 1MB, 4MB, 8MB, or 16MB shared parity-protected DRAM
❏ 4MB, 8MB, or 16MB ECC-protected DRAM
The two memory controllers modeled in the Petra ASIC duplicate the
functionality of the “parity memory controller” found in MC2 ASICs as
well as that of the “single-bit error correcting/double-bit error detecting”
memory controller found in MCECC ASICs. Board firmware will
initialize the memory controller as appropriate.
If the Petra ASIC is supporting MVME1x2P4 functionality, firmware will
enable the parity (MC2) memory cont roller model. If the Petr a ASIC is
supporting MVME1x2P2 functionality, firmware will enable either the
parity or the MCECC memory controller model, depending on the board
configuration. Board configuration is a function of switch settings and
resistor population options.
Preparing the Board
1
S6 comes into pla y in th e MCECC me mory contr oller model . S6 is a f oursegment slide switc h whose lower th ree seg ment s estab lish t he si ze of t he
ECC DRAM (segment 4 is not used.) Refer to the illustration and table
below for specifics.
NoteFor the MCECC memory model to be enabled, the MC2
emulation must be disabled. You disable the MC2 memory
model by setting the MC2 DRAM size select switch (S3) to
110 (Off/Off/On). Refe r to MC2 DRAM Size (S3 ) for further
details.
The factory default setting for S6 is 16MB (On/Off/On). If you
modify the switch settings, you will need to execute env;d <CR>
so that the firmware recognizes the new memory defaults.
Installation Instructions
S6
Segment 3
MCECC
DRAM Size
This section covers:
❏ Installation of IndustryPacks (IPs) on the MVME172P4
❏ Installation of the MVME172P4 in a VME chassis
❏ System considerations relevant to the installation. Ensure that an
EPROM device is installed as needed. Before installing
IndustryPacks, ensure that the serial ports and all header jumpers
and configuration switches are set as appropriate.
The MVME172P4 accommodates up to four IndustryPack (IP) modules.
Install the IP modules on the MVME172P4 as follows:
1. Each IP module has two 50-pin connectors that plug into two
corresponding 50-pin connectors on the MVME172P4: J4/J5,
J10/J11, J20/J21, J29/J30. See Figure 2-1 for the MVME172P4
connector locations.
– Orient the IP module(s) so that the tapered connector shells mate
properly. Plug IP_a into co nnectors J4 and J5; plug IP _b into J10
and J11. Plug IP_c into J20 and J21; pl ug IP_d into J29 and J30.
If a double-sized IP is us ed, plug I P_ab in to J4, J5, J10, a nd J11;
plug IP_cd into J20, J21, J29, and J30.
2. Four additional 50-pin connectors (J7, J8, J26, and J27) are
provided behind the MVME172P4 front panel for external cabling
connections to the IP modules. There is a one-to-one
correspondence between the signals on the cabling connectors and
the signals on the associated IP connectors (i.e., J8 has the same
IP_a signals as J4; J7 ha s the same IP_b signals as J10; J27 has the
same IP_c signals as J20; and J2 6 has the same I P_d signal s as J29).
Installation Instructions
1
– Connect user-supplied 50-pin cables to J7, J8, J26, and J27 as
needed. (Because of th e vary ing re qui rements fo r eac h diff erent
kind of IP, Motorola does not supply these cables.)
– Bring the IP cables out the narrow slots in the MVME172P4
front panel and attach them to the appropriate external
equipment, depending on the nature of the particular IP(s).
MVME172P4 Installation
With EPROM, SIM, and IP modules installed and headers or switches
properly configured, proceed as follows to install the MVME172P4 in a
VME chassi s:
1. Turn all equipment power OFF and disconnect the power cable
from the AC power source.
Inserting or removing modules while power is applied could result in
!
!
damage to module components.
Dangerous voltages, capable of causing death, are present in this
equipment. Use extreme caution when handling, testing, and adjusting.
2. Remove the chassis cover as instructed in the user’s manual f or t he
equipment.
3. Remove the filler panel from the card slot where you are going to
install the MVME172P4.
– If you intend to use the MVME172P4 as system controller, it
must occupy the leftmost card slot (slot 1). The system controller
must be in slot 1 to correctly initiate the bus-grant daisy-chain
and to ensure proper operation of the IACK daisy-chain driver.
– If you do not intend to use the MVME172P4 as system
controller, it can occupy any unused double-height card slot.
4. Slide the MVME172P4 into the selected card slot. Be sure the
module is seated properly in the P1 and P2 connectors on the
backplane. Do not damage or bend connector pins.
5. Secure the MVME172P4 in the chassis with the screws provided,
making good contact wi th the transverse mou nting rails to minimize
RF emissions.
6. Install the MVME712 series transition module in the front or the
rear of the VME chassis. (To install an MVME712M, which has a
double-wide front pan el, you may need to shif t other modules in the
chassis.)
7. On the chassis backplane, remove the
(IACK) and
slot occupied by the MVME172P4.
1-24Computer Group Literature Center Web Site
BUS GRANT (BG) jumpers from the header for t he card
NoteSome VME backplanes (e.g., those used in Motorola "Modular
Chassis" systems) have an autojumpering feature for automatic
propagation of the IACK and BG signals. Step 7 does not apply
to such backplane designs.
8. Connect the P2 Adapter Boar d or LCP2 Adapter Board and cable(s)
to MVME172P4 backplane connector P2. This provides a
connection point for terminals or other peripherals at the EIA-232D serial ports, SCSI por ts, and LAN Ethern et por t. For i nform ation
on installing the P2 or LCP2 Adapter Board and the MVME712
series transition module(s), refer to the corresponding user’s
manuals (the Programmer’s Reference Guide provides some
connection diagrams).
NoteIf you intend to use the MVME172P4 with Por t B in an EIA-
530 configuration or an EIA-4 85/EIA- 422 conf igura tion, d o
not install the P2 or LCP2 Adapt er Board and the MVME712
series transition module. They are incompatible with the
EIA-530 interface and the EIA-485/EIA-422 interface.
1
9. Connect the appropriate cable(s) to the panel connectors for the
serial ports, SCSI port, and LAN Ethernet port.
– Note that some cables are not provided with the MVME712
series transition module and must be made or purchased by the
user. (Motorola recommends shielded cable for all peripheral
connections to minimize radiation.)
10. Connect the peripheral(s) to the cable(s).
11. Install any other required VMEmodules in the system.
12. Replace the chassis cover.
13. Connect the power cable to the AC power source and turn the
equipment power ON.
The MVME172P4 draws power from VMEbus backplane connectors P1
and P2. P2 is also used for the upper 16 bits of data in 3 2-bit tr ansfers, an d
for the upper 8 address lines in extended addressing mode. The
MVME172P4 may not operate pr operly wi thout it s main boar d connecte d
to VMEbus backplane connectors P1 and P2.
Whether the MVME172P4 operates as a VMEbus master or VMEbus
slave, it is c onfigured for 3 2 bits of address and 32 bits o f data (A32/D32).
However, it handles A1 6 or A24 devi ces in the address ran ges indicated in
the VMEchip2 chapter of th e P rogrammer’s Reference Guide. D8 and/or
D16 devices in the syste m must be handled by the MC680x0/MC68L C0x0
software. For specifics, refer to the memory maps in the Programmer’s Reference Guide.
The MVME172P4 contains shar ed onboard DRAM whose base address is
software-selectable. Both the onboard processor and offboard VMEbus
devices see this local DRAM at base physical address $00000000, as
programmed by the MVME172Bug firmware. This may be changed via
software to any other base address. Refer to the Programmer’s Reference Guide for more information.
If the MVME172P4 tries to access offboard resources in a nonexistent
location and is not system controller, and if the system does not have a
global bus timeout, the MVME17 2P4 waits forever f or the VMEbus cycle
to complete. This will cause the system to lock up. There is only one
situation in which th e syste m might lack th is gl obal bus timeou t: when t he
MVME172P4 is not the system controller and there is no global bus
timeout el sewhere in the system.
Multiple MVME172P4s may be installed in a single VME chassis. In
general, hardware multiprocessor features are supported.
Note If you are installing multiple MVME172P4s in an MVME945
chassis, do not install an MVME172P4 in slot 12. The height of
the IP modules may cause clearance difficulties in that slot
position.
Other MPUs on the VMEbus can interrupt, disable, communicate with,
and determine the opera tional status of the proc essor(s). One registe r of the
GCSR (global control/s tatus regi ster) s et in the VMEchip2 ASIC i ncludes
four bits that function as location monitors to allow one MVME172P4
processor to broadcas t a si gnal to any othe r MVME172P4 p rocess ors. Al l
eight registers of the GCSR set are acc essib le from any loc al process or as
well as from the VMEbus.
The following circuits are protected by solid-state fuses that open during
overload conditions and reset themselves once the overload is removed:
FUSE LED illuminates to indi cate that +1 2 Vdc is avai lable. W hen an
The
MVME712M module is used, the yellow DS1 LED on the MVME712M
illuminates on availabili ty of LAN power, signify ing that the fuse is good.
If the Ethernet transceiver fails to operate, check fuse F3.
1
The MVME172P4 provides SCSI terminato r power through a 1A fuse (F1)
located on the P2 Adapter Board or LCP2 Adapter Board. If the fuse is
blown, the SCSI device( s) may f uncti on err atic ally or not at a ll. When the
P2 Adapter Board is used with an MVME712M and the SCSI bus is
connected to the MVME712M, the green DS2 LED on the MVME712M
front panel illuminates on availability of SCSI terminator power. If the
green DS2 LED flickers during SCSI bus operation, check P2 Adapter
Board fuse F1.
If a solid-state fuse opens, you will need to remove power for several
minutes to let the fuse reset to a closed or shorted condition.
The MVME172P4 uses a Zilog Z85230 serial port cont roller to implement
the two serial communications interfaces. Each interface supports:
❏ CTS, DCD, RTS, and DTR control signals
❏ TXD and RXD transmit/receive data signals
❏ TXC and RXC synchronous clock signals
The Z85230 supports synchronous (SDLC/HDLC) and asynchronous
protocols. The MVME172P4 hardwa re supports async hronous serial ba ud
rates of 110b/s to 38.4Kb/s.
For additional information on the MVME172P4 serial communications
interface, refer to the Z85230 Serial Communications Controller Product
Brief listed under Manufacturer’s Documents in the Related
Documentation appendix. For additional information on the EIA-232-D
interface, refer to the EIA-232-D Standard.
The following figures illustrate the signal relationships and signal
connections in the various serial configurations available for ports A and
B.
This chapter provide s information on poweri ng up the MVME172P4 VME
Embedded Controller after its installation in a system, and describes the
functionality of the switches, status indicators, and I/O ports.
For programming infor mation, cons ult the MVME1X2P 4 VME Embedded
Controller Programmer’s Reference Guide.
Front Panel Switches and Indicators
There are two switches (ABORT and RESET) and eight LEDs (FAIL, STAT,
RUN, SCON, LAN, FUSE, SCSI, and VME ) located on th e MVME172P4 front
panel.
Table 2-1. MVME172P4 Front Panel Controls
2
Control/IndicatorFunction
Abort Switch (
Reset Switch (
FAIL LED (DS1, red)Board failure. Lights if a fault occurs on the MVME172P4 board.
STAT LED (DS2, amber) CPU status. Lights if the processor enters a halt condition.
RUN LED (DS3, green)CPU activity. Indicates that one of the local bus masters is executing
ABORT)Sends an interrupt signal to the processor. The interrupt is normally
used to abort program execution and return control to the debugger
firmware located in the MVME172P4 Flash memory.
The interrupter connected to the Abort switch is an edge-sensitive
circuit, filtered to remove switch bounce.
RESET)Resets all onboard devices. Also drives a SYSRESET∗ signal if the
MVME172P4 is system controller. SYSRESET∗ signals may be
generated by the Reset switch, a power-up reset, a watchdog timeout,
or by a control bit in the Local Control/Status Register (LCSR) in the
VMEchip2 ASIC. For further details, refer to Chapter 4, Functional Description.
SCON LED (DS4, green) System controller. Lights when the VMEchip2 ASIC is functioning
as VMEbus system controller.
LAN LED (DS5, green)LAN activity. Lights when the LAN controller is functioning as local
bus master.
FUSE LED (DS6, green)Fuse OK. Indicates that +5Vdc, +12Vdc, and –12Vdc power is
available to the LAN and SCSI interfaces and IP connectors.
SCSI LED (DS7, green)SCSI activity. Lights when the SCSI controller is functioning as local
bus master.
VME LED (DS8, green)VME activity. Lights when the board is using the VMEbus or being
accessed from the VMEbus.
Initial Conditions
After you have verified that all necessary hardware preparation has been
done, that all connections have been made correctly, and that the
installation is compl ete, yo u can power up the sys tem. Apply ing power to
the system (a s well as resetting it) triggers an initialization of the
MVME172P4’s MPU, hardware, and firmware along with the rest of the
system.
The Flash-resident firmware initializes the devices on the MVME172P4
board in preparation for booting the operating system. The firmware is
shipped from the factory with a set of defaul ts appropr iate to the boa rd. In
most cases there is no need to modify the firmware configuration before
you boot the operating sys tem. For specifics in this regard, refer to Chapter
3 and to the user documentation for the MVME172Bug firmware.
When you power up ( or when you re set) the sys tem, the firmwar e executes
some self- checks and proceeds to the hardware in itialization. The sy stem
startup flows in a predetermined sequence, following the hierarchy
inherent in the processor and the MVME172P4 hardware. The figure
below charts the flow of the basic initialization sequence that takes place
during system startup.
STARTUP
INITIALIZATION
POST
Power-up/reset initialization
Initialization of devices on the MVME172P4
module/system
Power-On Self-Test diagnostics
2
BOOTING
MONITOR
Firmware-configured boot mechanism,
if so configured. Default is no boot.
Interactive, command-driven on-line
debugger, when terminal connected.
Before you power up the MVME172P4 sy stem, be sure that the fol lowing
conditions exist:
1. Jumpers and/or configuration switches on the MVME172P4 VME
Embedded Controller and associated equipment are set as required
for your particular application.
2. The MVME172P4 board is installed and cabled up as appropriate
for your particular chassis or system, as outlined in Chapter 1.
3. The terminal that you plan to use as the system cons ole is connecte d
to the console port (serial port 1) on the MVME172P4 module.
4. The terminal is set up as follows:
– Eight bits per character
– One stop bit per character
– Parity disabled (no parity protect ion)
– Baud rate 9600 baud (the default baud rate of many serial ports
at power-up)
5. Any other device that you wish to use, such as a host computer
system and/or peripheral equipment, is cabled to the appropriate
connectors.
After you comple te the ch ecks lis ted above, you are ready to power up th e
system.
The MVME172P4 comes with MVME172Bug fi rmware installed. For the
firmware to operate properly with the board, you must follow the steps
below.
!
Caution
Inserting or removing boards with power applied may damage board
components.
Turn all equipment power OFF. Refer to MVME172P4 Configuration on
page 1-5 and verify that jumpers and switches are configured as necessary
for your particular application.
1. Configuration switch S4 on the MVME172P4 contains eight
segments, which all affect the operation of the firmware. They are
read as a regist er ( at l ocati on $FFF4 202C) i n the Petr a MC2 sect or.
(The MVME1X2P4 VME Embedded Controller Programmer’s Reference Guide has additional information on the Petra MC2
emulation.) The bit values are read as a 0 when the corresponding
switch segment is set to
OFF.
The defaul t configuration for S4 has S4 set to all 0s (all switch
segments set to
ON). The 172Bug firmware reser ves/defines the four
lower order bits (GPI0 to GPI3, switch segments 5-8). Table 2-2
describes the bit assignments on S4.
2
ON, or as a 1 when that segm ent is set to
2. Configure header J1 as appropria te for the des ired system controller
functionality (alwa ys system contro ller, neve r system cont roller , or
self-regulating) on the MVME172P4.
3. Header J14 configures the IP bus clock for either 8MHz or the
processor bus clock speed ( 60MHz for the MC68060 or 64MHz f or
the MC68LC060). The factory c onfigurati on has a jumpe r instal led
on J14 pins 1-2, denot ing a n 8MHz clock . Verif y tha t thi s set ting is
appropriate for your application.
GPI08When set to 1 (high) , i ns t ructs th e debugger to use local static RAM fo r
GPI17When set to 1 (high), instructs the de bugger to use the default
GPI26Reserved for future use.
GPI35When set to 0 (low), informs the debugger that it is executing out of
GPI44Open to your application.
GPI53Open to your application.
GPI62Open to your application.
GPI71Open to your application.
Table 2-2. Software-Readable Switches
its work page (variables, stack, vector tables, etc.).
setup/operation parameters in ROM instead of the user se tup/operation
parameters in NVRAM. The effect is the same as pressing the
ABORT switches simultaneously.
and
This feature can be helpful in the event the user setup is corrupted or
does not meet a sanity check. Refer to the ENV command description
for the Flash/ROM defaults.
Flash memory. When set to 1 (high), it informs the debugger that it is
executing out of the PROM.
RESET
4. You may configure Port B of the Z85230 serial communications
controller with a ser ial interfac e module (SIM), which you install a t
connector J15 on the MVME172P4 board. Five serial interface
modules are available:
– EIA-232- D DTE (SIMM05)
– EIA-232-D DCE (SIMM06)
– EIA-530 D TE (SIMM07)
– EIA-530 DCE (SIMM08)
– EIA-485, or EIA-422 DTE or DCE (all with SIMM09)
For information on removing and/or installing a SIM, refer to
5. Headers J16 and J17 configure serial ports 1 and 2 to drive or
receive clock signals provided by the TXC and RXC signal lines.
The MVME172P4 is factory-configured for asynchronous
communication: it comes with no jumpers on J16 or J17. Refer to
the instruct ions in Chapter 1 if your a pplication req uires config uring
ports 1 and 2 for synchronous communication.
6. Header J19 enables or disables the IP bus strobe function on the
MVME172P4. The factory configuration puts no jumper on J19,
disabling the Strobe∗ signal to the Petra/IP2 chip disconnected.
Verify that this setting is appropriate for your application.
7. The jumpers on header J22 establish the SRAM backup power
source on the MVME172P4. The factory configuration uses
VMEbus +5V standby voltage as the primary and s econdary powe r
source (the onboard battery is disconnected). Verify that this
configuration is appropriate for your application.
8. The EPROM size select header, J23, should be jumpered between
pins 2-3. This sets i t up for a 4Mbit x 8 EPROM density, t he factory
default.
9. Header J24 defines the s tate of Fl ash memory write protecti on. The
factory configuration has the jumper installed, allowing writes to
Flash. Verify that this setting is appropriate for your application.
2
10. Verify that the se tt ing s of configuration switche s S3 (MC2 DRAM
size), S5 (IP DMA snoop control, IP Reset mode, and Flash Write
Enable mode), and S6 (MCECC DRAM size) are appropriate for
your memory controller emulation.
11. Refer to the setup p rocedure for your parti cular chassis or syst em for
details concerning the installation of the MVME172P4.
12. Connect the termin al to be used a s the 172Bug system co nsole to the
default EIA-232-D port at Serial Port 1 on the front panel of the
MVME172P4, or Serial Por t 2 on the MVME712 x series transition
module. (For other connection options, refer to Serial Connections
in Chapter 1.) Set the terminal up as follows:
– Eight bits per character
– One stop bit per character
– Parity disabled (no parity)
– Baud rate 9600 baud (the power-up default)
After power-up, you can reconf igure the baud rate of the de bug port
by using the 172Bug Port Format (PF) command.
Note Whatever the b aud rate, some form of h ardware handshaking —
either XON/XOFF or via the RTS/CST line — is desirable if the
system supports it. If you get garbled messages and missing
characters, you should check the terminal to make sure that
handshaking is enabled.
13. If you have equipment (such as a host computer system and/or a
serial printer) to connect to the other EIA-232-D port connectors
(marked
connect the appropri ate ca ble s and conf igure t he port (s) as deta iled
in Step 12 above. After power-up, you can reconfigure the port(s)
by programming the MVME172P4 Z85230 Serial Communicati ons
Controller (SCC) or by using the 172Bug PF command.
SERIAL PORT on the MVME712x transition module),
14. Power up the system. 172Bug executes some self-checks and
displays the debugger prompt
172-Bug> if the firmware is in Board
mode.
However, if the ENV command has placed 172Bug in System
mode, the system performs a self-test and tries to aut oboot. Refe r to
the ENV and MENU commands (Table 3-2).
If the confidence test fails, the test is aborted when the first fault is
encountered. If possible, an appropriate message is displayed, and
control then returns to the menu.
15. Before using the MVME172P4 after the initial installation, set the
date and time using the following command line structure:
172-Bug> SET [mmddyyhhmm]|[<+/-CAL>;C]
For example, the followi ng command line starts the real -time clock
and sets the date and time to 10:37 a.m., November 7, 2000:
The board’s self-tests and operating systems require that the realtime clock be running.
Note If you wish to execute the debugger out of Flash and Flash
does not contain 172 Bug, you may copy the EPROM version
of 172Bug to Flash memory. To c opy the EPROM version of
172Bug to Flash memory, first ve rify that a jumper is in place
on J24 to enable Fl ash writes, set switch S4 seg ment 5 to
and make sure that 172Bug is in Bug mode. Then copy the
EPROM contents to Flash memory with the PFLASH
command as follows:
172-Bug> PFLASH FF800000:80000 FFA00000
Then remove the jumper from J24 (if you wish to disable
subsequent Flash writes) and slide switch S4 segment 5 back to
OFF. (172Bug always executes f rom memory location FF800000;
the setting of S4 determines wheth er that location is in EPROM
or Flash.)
ON,
2
Autoboot
Autoboot is a software routine included in the 172Bug Flash/EPROM to
provide an independent mechanism for booting operating systems. The
autoboot routine automatically scans for controllers and devices in a
specified sequen ce until a val id bootable devi ce containing a boot media is
found or the list is exhausted. If a valid bootable device is found, a boot
from that device is started. The control ler scanning sequence goes from the
lowest controller Logical Unit Number (LUN) d etected to the highest LUN
detected. Controllers, devices, and their LUNs are listed in Appendix D.
At power-up, Autoboot is enabled and (provided that the drive and
controller numbers encountered are valid) the following message is
displayed upon the system console:
you wish. Then the actual I/O begins: the program designated within the
volume ID of the media specified is loaded into RAM and control passes
to it. If you want to gain control without Autoboot during this time,
A delay follows this message so that you can abort the Autoboot proces s if
however, you can press the <BREAK> key or use the
ABORT or RESET
switches on the front panel.
The Autoboot process is controlled by parameters contained in the ENV
command. These parameters allow the selection of specific boot devices
and files, and allow programming of the Boot delay. Refer to the ENV
command description in Chapter 3 for more details.
Although you can use streaming tape to autoboot, the same power supply
!
Caution
must be connected to the ta pe drive, t he control ler, and the MVME17 2P4.
At power-up, the tape controller will position the streaming tape to the load
point where the volume ID can correctly be read and used.
However, if the MVME172P4 loses powe r but the controller does not, and
the tape happens to be at load point, the necessary command sequences
(Attach and Rewind) cannot be given to the controller and the autoboot
will not succeed.
ROMboot
As shipped from the factory, 172Bug occupies the first quarter of Flash
memory. This leaves the remainder of the Fla sh memory a nd the EPROM
socket (XU1) available for your use.
NoteYou may wish to contact your Motorola sales office for
assistance in using these resources.
The ROMboot function is configured/enabled via the ENV command
(refer to Chapter 3) and is executed at power-up (optionally also at reset).
You can also execute the ROMboot function via the RB command,
assuming there is valid code in the memory devices (or optionally
elsewhere on the board or VMEbus) to support it. If ROMboot code is
installed, a user-written routine is given control (if the routine meets the
format requi rements).
One use of ROMboot might be resetting the SYSFAIL∗ line on an
unintelligent controller module. The NORB command disables the
function.
For a user’s ROMboot module to gain control through the ROMboot
linkage, four conditions must exist:
❏ Power has just been applied (but the ENV command can change this
to also respond to any reset).
❏ Your routine is located within the MVME172P4 Flash/PROM
memory map (but the ENV command can change this to any other
portion of the onboard memory, or even offboard VMEbus
memory).
❏ The ASCII string "BOOT" is f ound i n the speci fied me mory ra nge.
❏ Your routine pass es a checksum tes t, which ensu res that this routine
was really intended to receive control at powerup.
2
For complete details on using the ROMboot function, refer to the
Debugging Package for Motorola 68K CISC CPUs User’s Manual.
Network Boot
Network Auto Boot is a software routine in the 172Bug Flash/EPROM
which provides a mechanism for booting an operating system using a
network (local Ethernet interface) as the boot device. The Network Auto
Boot routine automa tically scans for contr ollers and device s in a spec ified
sequence until a valid bootable device containing boot media is found or
until the list is exhausted. If a valid bootable device is found, a boot from
that device is started. The controller scanning sequence goes from the
lowest controller Logical Unit Number (LUN) d etected to the highest LUN
detected. (Refer to Appendix C for default LUNs.)
At power-up, Network Boot is enabled and (provided that the drive and
controller numbers encountered are valid) the following message is
displayed upon the system console:
Network Boot in progress... To abort hit <BREAK>
After this mess age, there is a delay to let you abort th e Aut o Boot pr ocess
if you wish. Then the actual I/O is begun: the program designated within
the volume I D of the media specified is loaded into RAM and control
passes to it. If you wa nt t o ga in control without Network Boot d uri ng this
time, however, you can press the <BREAK> key or use the software
ABORT or RESET switches.
Network Auto Boot is controlled by parameters contained in the NIOT
and ENV commands. These parameters allow the selection of specific
boot devices, systems, and files, and allow programmin g of the Boot delay.
Refer to the ENV command description in Chapter 3 for more details.
Restarting the System
You can initialize the system to a known state in three different ways:
Reset, Abort, and Break. Each method has characteristics which make it
more suitable than the others in certain situations.
A special debugger function is accessible during resets. This feature
instructs the debugger to use the default setup/operation parameters in
ROM instead of your own setup/operation parameters in NVRAM. To
activate this function, you press the
same time. This feature can be helpful in the event that your
setup/operation parameters are corrupted or do not meet a sanity check.
Refer to the ENV command description in Chapter 3 for the ROM
defaults.
RESET and ABORT switches at the
Reset
Powering up the MVME172P4 initiates a system reset. You can also
initiate a reset by pressing and quickly releasing the
MVME172P4 front panel, or reset the board in software.
For details on resett ing the MVME172 P4 board thr ough software, r efer to
the MVME1X2P4 Embedded Controller Programmer’s Reference Guide.
Both “cold” and “warm” r eset modes are a vaila ble. By defaul t, 172Bug is
in “cold” mode. During cold resets, a tot al system initiali zation takes place,
as if the MVME172P4 had just been powered up. All static variables
(including disk device and controller parameters) are restored to their
default states. The breakpoint table and offset registers are cleared. The
target registers are invalidated. Input and output character queues are
cleared. Onboard devices (timer, serial ports, etc.) are reset, and the two
serial ports are reconfigured to their default state.
During warm resets, the 172 Bug variables and tables are pres erved, as well
as the target state registers and breakpoints.
Note that when the MVME172P4 comes up in a cold reset, 172Bug runs
in Board mode. Using the Environment ( ENV) or MENU commands can
make 172Bug run in System mode. Refer to Chapter 3 for specifics.
You will need to reset your system if the processor ever halts, or if the
172Bug environment is ever lost (vector table is destroyed, stack
corrupted, etc.).
2
Aborts are invoked by pressing and releasing the ABORT switch on the
MVME172P4 front panel. When you invoke an abort while executing a
user program (running target code), a snapshot of the processor state is
stored in the target registers. This characteristic makes aborts most
appropriate for terminating user programs that are being debugged.
If a program gets caught in a loop, for instance, aborts should be used to
regain control. The target PC, register contents, etc., help to pinpoint the
malfunction.
Pressing and releasi ng the
ABORT switch generates a local board condition
which may interrupt the processor if enabled. The target registers,
reflecting the mac hine state at the time the
displayed on the screen. Any breakpoints installed in your code are
removed and the breakpoint table remains intact. Control returns to the
debugger.
Break
Pressing and releasing the <BREAK> key on the terminal keyboard
generates a ‘‘power break’’. Breaks do not produce interrupts. The only
time that breaks are recognized is while characters are being sent or
received by the console port. A break removes any breakpoints in your
code and keeps the breakpoint table intact. If the function was entered
using SYSCALL, Break also takes a snapshot of the machine state. This
machine state is then accessible to you for diagnostic purposes.
In many cases, you may wish to ter minate a de bugger command before i ts
completion (for example , during the display of a large b loc k of memory) .
Break allows you to terminate the command.
Diagnostic Facilities
The 172Bug package includes a set of hardware diagnostics for testing and
troubleshooting the MVME172P4. To use the diagnostics, switch
directories to the diagnostic directory.
If you are in the debugger directory, you can switch to the diagnostic
directory with the debugger command Switch Directories (SD). The
diagnostic prompt
for Motorola 68K CISC CPUs User’s Manual for complete descriptions of
the diagnostic routines available and instructions on how to invoke them.
Note that some diagnostics depend on restart defaults that are set up only
in a particular restart mode. The documentation for such diagnostics
includes restart information.
The 172Bug firmware i s the layer of software just above the hardware . The
firmware supplies the appropriate initialization for devices on the
MVME172P4 board upon power-up or reset.
This chapter descri bes the basic s of 172Bug and its a rchitectur e, describes
the monitor (interactive command portion of the firmware) in detail, and
gives information on using the debugger and special commands. A list of
172Bug commands appears at the end of the chapter.
For complete user information about 172Bug, refer to the Debugging
Package for Motorola 68K CISC CPUs User’s Manual and to the
MVME172Bug Diagnostics User’s Manual, listed under Related
Documentation.
3172Bug Firmware
3
172Bug Overview
The firmware for the M68000-based (68K) series of board and system
level products has a c ommon ge nealogy, deriving from the Bug fi rmwar e
currently used on all Motorola M68000-based CPUs. The M68000
firmware version implemented on the MVME172P4 MC68040- or
MC68LC040-based embedded contro ll er is known as MVME172Bug, or
172Bug. It includes diagnostics for testing and configuring IndustryPack
modules.
172Bug is a powerful evaluation and debugging tool for systems built
around MVME172P4 CISC-based microcomputers. Facilities are
available for loading and executing user programs under complete
operator control for system evaluation. The 172Bug firmware provides a
high degree of functionality, user friendliness, portability, and ease of
maintenance.
❏ Breakpoint and tracing capabilities
❏ A powerful assembler/disassembler useful for patching programs
❏ A “self-test at po wer- up” feature which verifies th e in tegrity of the
system
In addition, the TRAP #15 syst em calls make various 172Bug rou tines that
handle I/O, data conversion, and string functions available to user
programs.
172Bug consists of three parts:
❏ A command-driven user-interactive software debugger, described
in this chapter . It is re fe rred to her e as “ th e debugg er” or “172Bug ”.
❏ A command-driven diagnostic package for the MVME172P4
hardware, referred to here as “the diagnostics”.
❏ A user interface or debug/diagnostics monitor that accepts
commands from the system console terminal.
When using 172Bug, you operate out of either the debugger directory or
the diagnostic directory.
❏ If you are in the deb ugger director y, the debugger prompt 172-Bug>
is displayed and you have all of the debugger commands at your
disposal.
❏ If you are in the diagnostic directory, the diagnostic prompt 172-
Diag> is displayed and you have all of the diagnost ic commands at
your disposal as well as all of the debugger commands.
Because 172Bug is command-driven, it performs its vari ous operati ons in
response to user commands entered at the keyboard. When you enter a
command, 172Bug executes the command and the prompt reappears.
However, if you enter a command that causes executi on of user target code
(for example, GO), then control may or may not return to 172Bug,
depending on the outcome of the user program.
If you have used one or more of Motorol a’s other debugging packages, you
will find the CISC 172Bug very similar. Some effort has also been made
to improve th e consistency of interactive commands. For e xample,
delimiters between commands and arguments may be commas or spaces
interchangeably.
172Bug Implementation
Physically, 172Bug is contained in a 28F160S5 Flash memory chip,
providing 512KB (128K longwords) of storage. Optionally, the 172Bug
firmware can be loaded and executed in a single 27C040 DIP EPROM
installed in socket XU1. The executable code is checksummed at every
power-on or reset firmware entry, and the result (which includes a
precalculated chec ksum cont ained in the memory de vices) is t ested for a n
expected zero. Users are cautioned against modification of the memory
devices unless precautions for re-checksumming are taken.
172Bug Implementation
3
Note MVME172P4 boa rds ordered without the VMEbus interface
are shipped with Flash memory blank (the factory uses the
VMEbus to program the Flash memory wit h debugger code).
To use the 172Bug package, be sure that switch S4 segment
5 is configured to select the EPROM memory map.
If you subsequently wish to run the debugger from Flash
memory, you must first initialize Flash memory with the
PFLASH command, then reconfigure S4. Refer to Step 15
(Note) under Bringing up the Board on page 2 - 5 for further
details.
The program portion of 172Bug is approximately 512KB of code,
3
.
consisting of download, debugger, and diagnostic packages contained
entirely in Flash memory or in EPROM.
The 172Bug firmware ex ecutes from address $FF800000 whether i n Flash
or EPROM. If you set switch S4 segment 5 to
ON, the address spaces of the
Flash and EPROM are swapped. For MVME172P-644 series boards
(MVME172P4), the factory ship configuration except in the no-VMEbus
case has switch S4 segment 5 set to
OFF (172Bug operating out of Flash).
The 172Bug initial stack completely changes 8KB of SRAM memory at
addresses $FFE0C000 through $FFE0DFFF, at power-up or reset.
Table 3-1. Memory Offsets with 172Bug
Type of Memory PresentDefault DRAM
4/8/16/32MB synchron ous DRAM (SDR AM). Appears
as parity memory at 1/8/16MB, ECC at 32MB.
The synchronous DRAM can be modeled as ECC or parity type, as
indicated above.
The 172Bug firmware requires 2KB of NVRAM for storage of board
configuration, commun ic ati on, and booting parameters. This st ora ge a re a
begins at $FFFC16F8 and ends at $FFFC1EF7.
172Bug requires a minimum of 6 4KB of contiguous rea d/write memory to
operate. The ENV command controls where this block of memory is
located. Regardless of where the onboard RAM is located, the first 64KB
is used for 172Bug stack and static variable space and the rest is reserved
as user space. Whenever the MVME172P4 is reset, the target PC is
initialized to the address correspon ding to t he beginni ng of th e user sp ace,
and the target stack pointers are initialized to addresses within the user
space, with the targ et Interrupt Stack Pointer (ISP) set to the to p of the user
space.
172Bug is command-driven; it perfor ms its various o perations i n response
to commands that you enter a t the k eyboard. Whe n the
appears on the terminal screen, the debugger is ready to accept debugger
commands. When the
debugger is ready to accept diagnostics commands.
To switch from one mode to the other, enter SD (Switch Directories). To
examine the commands in the directory that you are currently in, use the
Help command (HE).
What you key in is stored in an internal buff er. Execution begi ns only after
the carriage return is entered. This allows you to correct entry errors, if
necessary, with the control characters de scribed in the Debugging Package for Motorola 68K CISC CPUs User’s Manual, Chapter 1 .
After the debugger executes the command you have entered, the prompt
reappears. However, if the command ca uses exe cution of user targ et code
(for example GO), then control may or may not return to the debugger,
depending on what the user program does.
Using 172Bug
172-Bug> prompt
172-Diag> promptappears on the screen, the
3
For example, if a bre akpoint has bee n specified, t hen contro l returns to t he
debugger when the br eakpoint is enc ountered during e xecution of the user
program. Alternatively, the user program could return to the debugger by
means of the System Call Handler routine RETURN (described in the
Debugging Package for Motorola 68K CISC CPUs User’s Manual,
Chapter 5).
A debugger command is made up of the following parts:
❏ The command name, either uppercase or lowercase (e.g., MD or
md).
❏ A port number (if the c ommand is set up to work with more than one
port).
❏ Any required arguments, as specified by the command.
❏ At least one space before the first argument. Precede all other
❏ One or more options. Precede an option or a string of options with
a semicolon (;). If no option is entered, the command’s default
option conditions are used.
3
Debugger Commands
The 172Bug debugger commands are summarized in the following table.
The commands are described in detail in the Debugging Package for Motorola 68K CISC CPUs User’s Manual.
Table 3-2. Debugger Commands
CommandDescription
ABAutomatic Bootstrap Operating System
NOABNo Autoboot
ASOne Line Assembler
BCBlock of Memory Compare
BFBlock of Memor y Fill
BHBootstrap Operating System and Halt
BIBlock of Memory Initialize
BMBlock of Memory Move
BOBootstrap Operating System
BRBre akpoint Insert
NOBRBreakpoint Delete
BSBlock of Memory Search
BVBlock of Memory Verify
CMC oncu rren t Mode
NOCMNo Concurrent Mode
CNFGConfigure Board Information Block
CSChecksum
DCData Conversion
DMADMA Block of Memory Move
DSOne Line Disassembler
DUDump S-records
ECHOEcho String
ENVSet Environment to Bug/Operating System
NOPAPrinter Detach
PFPort Format
NOPFPort Detach
PFLASHProgram FLASH Memory
PSPut RTC Into Power Save Mode for Storage
RBROMboot Enable
NORBROMboot Disable
RDRegister Display
REMOTEConnect the Remote Modem to CSO
RESETCold/Warm Reset
RLRead Loop
RMRegister Modify
RSRegister Set
SDSwitch Directories
SETSet Time and Date
SYMSymbol Table Attach
NOSYMSymbol Table Detach
SYMSSymbol Table Display/Search
TTrace
TATerminal Attach
TCTrace on Change of Control Flow
TIMEDisplay Time and Date
TMTransparent Mode
TTTrace to Temporary Breakpoint
VEVerify S-Records Against Memory
VERDisplay Revision/Version
WLWrite Loop
Modifying the Environment
You can use the factory-installed debug monitor, 172Bug, to modify
certain parameters contained in the MVME172P4’s Non-Volatile RAM
(NVRAM), also known as Battery Backed-Up RAM (BBRAM).
❏ The Board Information Block in NVRAM contains various entries
that define operating parameters of the board hardware. Use the
172Bug command CNFG to change those para meters.
❏ Use the 172Bug command ENV to change configurable 172Bug
parameters in NVRAM.
The CNFG and ENV commands are both described in the Debugging Package for Motorola 68K CISC CPUs User’s Manual. Refer to that
manual for general information about their use and capabilities.
The following paragraphs present supplementary information on CNFG
and ENV that is specific to the 172Bug firmwa re, along with the
parameters that you can modify with the ENV command.
CNFG - Configure Board Information Block
Use this command to display and configure the Board Information Block
which resides within th e NVRAM. The board information block contai ns
various elements tha t correspo nd to speci fic opera tional par ameters of the
MVME172P4 board. (Note that a lthough no memory mezzanine is present
on MVME1X2P4 series boards, the o n-b oard me mory is modele d as s uch
for backward compatibility.)
The board structure for the MVME172P4 is as follows:
Serial Port 2 Personality Artwork (PWA) Identifier = " "
Serial Port 2 Personality Module (PWA) Serial Number = " "
IndustryPack A Board Identifier = " "
3
IndustryPack A (PWA) Serial Number = " "
IndustryPack A Artwork (PWA) Identifier = " "
IndustryPack B Board Identifier = " "
IndustryPack B (PWA) Serial Number = " "
IndustryPack B Artwork (PWA) Identifier = " "
IndustryPack C Board Identifier = " "
IndustryPack C (PWA) Serial Number = " "
IndustryPack C Artwork (PWA) Identifier = " "
IndustryPack D Board Identifier = " "
IndustryPack D (PWA) Serial Number = " "
IndustryPack D Artwork (PWA) Identifier = " "
172-Bug>
The parameters that ar e quoted ar e left -just ifi ed chara cter ( ASCII) stri ngs
padded with space characters, and the quotes (") are displayed to indicate
the size of the string. Parameters that are not quoted are considered data
strings, and data strings are right-justified. The data strings are padded
with zeros if the length is not met.
The Board Information Block is factory-configured before shipment.
There is no need to modify block parameters unless the NVRAM is
corrupted.
Refer to the MVME1X2P4 VME Embedded Controller Programmer’s Reference Guide for the actual location and other information about the
Board Information Block. Refer to the Debugging Package for Motorola 68K CISC CPUs User's Manual for a CNFG description and examples .
Use the ENV command to view and/ or config ure inte ractivel y all 172 Bug
operational parameters that are kept in Non-Volatile RAM (NVRAM).
Refer to the Debugging Package for Motorola 68K CISC CPUs User’s Manual for a description of the use of ENV. Additional information on
registers in the MV ME172P4 t hat aff ect th ese p aramet ers appe ars in yo ur
Listed and described below are the parameters that you can configure
using ENV. The default values shown are those that were in effect when
this document was published.
NoteIn the event of difficulty with the MVME172P4, you may wish
to use env;d <CR> to restore the factory defaults as a
troubleshooting aid (see Appendix B).
Configuring the 172Bug Parameters
Modifying the Environment
3
The parameters that can be configured using ENV are:
Table 3-3. ENV Command Parameters
ENV Parameter and OptionsDefaultMeaning of Default
Bug or System environment [B/S]BBug mode
Field Service Menu Enable [Y/N]NDo not display field service menu.
Remote Start Method Switch
[G/M/B/N]
Probe System for Support e d I/O
Controllers [Y/N]
Negate VMEbus SYSFAIL∗
Always [Y/N]
http://www.motorola.com/computer/literature3-11
BUse both methods [Global Control and Status
Register (GCSR) in the VMEchip2, and
Multiprocessor Control Register (MPCR) in
shared RAM] to pass and execute cross-loaded
programs.
YAccesses will be made to the appropriate
system buses (e.g., VMEbus, local MPU bus)
to determine presence of supported co ntrollers.
NNegate VMEbus SYSFAIL∗ after successful
completion or entrance into the bug command
monitor.
ENV Parameter and OptionsDefaultMeaning of Default
3
Local SCSI Bus Reset on
Debugger Startup [Y/N]
Local SCSI Bus Negotiations
Type [A/S/N]
Industry Pack Reset on Debugger
Startup [Y/N]
Ignore CFGA Block on a Hard
Disk Boot [Y/N]
Auto Boot Enable [Y/N]NAuto Boot function is disabled.
Auto Boot at power-up only [Y/N]YAuto Boot is attempted at power-up reset only.
Auto Boot Controller LUN00Specifies LUN of disk/tape controller module
Auto Boot Device LUN00Specifies LUN of disk/tape device currently
Auto Boot Abort Delay15The time in seconds that the Auto Boot
Auto Boot Default String
[Y(NULL String)/(String)]
ROM Boot Enable [Y/N]NROMboot function is disabled.
ROM Boot at power-up only
[Y/N]
ROM Boot Enable search of
VMEbus [Y/N]
ROM Boot Abort Delay00The time in seconds that the ROMboot
ROM Boot Direct Starting
Address
NNo local SCSI bus reset on debugger startup.
AAsynchronous negotiations.
YIP modules are reset on debugger startup.
YConfiguration Area (CFGA) Block contents
are disregarded at boot (hard disk only).
currently supported by the Bug. Default is $0.
supported by the Bug. Default is $0.
sequence will delay before starting th e boot.
The delay gives you the option of stopping the
boot by use of the Break key. The time span is
0-255 seconds.
You may specify a string (filename) to pass on
to the code being booted. Maximum length is
16 characters. Default is the null string.
YROMboot is attempted at power-up only.
NVMEbus address space will not be accessed by
ROMboot.
sequence will delay before starting th e boot.
The delay gives you the option of stopping the
boot by use of the Break key. The time span is
0-255 seconds.
FF800000First location tested when the Bug searches for
ENV Parameter and OptionsDefaultMeaning of Default
3
Memory Search Increment Size00010000Multi-CPU feature used to offset the location
of the Bug work page. This must be a multiple
of the debugger work page, modulo $10000
(64KB). Typically, Memory Search Increment
Size is the product of CPU number and size of
the Bug work page. Example: first CPU $0 (0 x
$10000), second CPU $10000 (1 x $10000),
etc.
Memory Search Delay Enable
[Y/N]
Memory Search Delay AddressFFFFD20F Default address is $FFFFD20F. This is the
Memory Size Enable [Y/N]YMemory is sized for Self-Test diagnostics.
Memory Size Starting Address00000000Default Starting Address is $0.
Memory Size Ending Address00100000Default Ending Address is the calculated size
NNo delay before the Bug begins it s s earch fo r a
work page.
MVME172P4 GCSR GPCSR0 as accessed
through VMEbus A16 space; it assumes the
MVME172P4 GRPAD (group address) and
BDAD (board address within group) switches
are set to "on". This byte-wide value is
initialized to $FF by MVME172P4 hardware
after a System or Power-On reset. In a multi172P4 environment, where the work pages of
several Bugs reside in the memory of the
primary (first) MVME172P4, the non-primary
CPUs will wait for the data at the Memory
Search Delay Address to be set to $00, $01, or
$02 (refer to the Memory Requirements section
in Chapter 3 for the definition of these values)
before attempting to locate their work page in
the memory of the primary CPU.
ENV Parameter and OptionsDefaultMeaning of Default
Note
Memory Configuration Defaults.
The default configuration for Dynamic RAM mezzanine boards will position the mezzanine with
the largest memory size to start at the address selected with the ENV parameter "Base Address of
Dynamic Memory". The Base Address parameter defaults to 0. The smaller sized mezzanine will
follow immediately above the larger in the memory map. If mezzanines of the same size and type
are present, the first (closest to the board) is mapped to the selected base ad dress. If mezzan ines of
the same size but different type (parity and ECC) are present, the parity type will be mapped to the
selected base address and the ECC type mezzanine will follow. The SRAM does not default to a
location in the memory map that is contiguous with Dynamic RAM.
Base Address of Dynamic
Memory
Size of Parity Memory 00100000 The size of the Parity type dynamic RAM
Size of ECC Memory Board 000000000 The size of the first ECC type memory
Size of ECC Memory Board 100000000 The size of the second ECC type memory
Base Address of Static MemoryFFE00000The beginning address of SRAM. The default
Size of Static Memory00080000The size of the SRAM type memory present.
ENV Parameter and OptionsDefaultMeaning of Default
3
ENV asks the following series of questions to set up the VMEbus interface for the MVME172P
series modules. You should have a working knowledge of the VMEchip2 as given in the
MVME1X2P4 VME Embedded Controller Programmer’s Reference Guide in order to perform
this configuration. Also included in this series are questions for setting ROM and Flash access
time.
The slave address decoders are used to allow another VMEbus master to access a local resource of
the MVME172P4. There are two slave address decoders set. They are set up as follows:
Slave Enable #1 [Y/N]YYes, set up and enable Slave Address Decoder
#1.
Slave Starting Address #100000000Base address of the local resource that is
accessible by the VMEbus. Default is the base
of local memory, $0.
Slave Ending Address #1000FFFFFEnding address of the local resource that is
accessible by the VMEbus. Default is the end
of calculated memory.
Slave Address Translation
Address #1
Slave Address Translation Select #100000000This register defines which bits of the address
Slave Control #103FFDefines the access restriction for the address
Slave Enable #2 [Y/N]NDo not set up and enable Slave Address
Slave Starting Address #200000000Base address of the local resource that is
Slave Ending Address #200000000Ending address of the local resource that is
Slave Address Translation
Address #2
00000000This register allows the VMEbus address and
the local address to differ. The value in this
register is the base address of the local resource
that is associated with the starting and ending
address selection from the previous questions.
Default is 0.
are significant. A logical "1" indicates
significant address bits, logical "0" is nonsignificant. Default is 0.
space defined with this slave address decoder.
Default is $03FF.
Decoder #2.
accessible by the VMEbus. Default is 0.
accessible by the VMEbus. Default is 0.
00000000Works the same as Slave Address Translation
ENV Parameter and OptionsDefaultMeaning of Default
3
Master Starting Address #300000000Base address of the VMEbus resource that is
accessible from the local bus. If enabled, the
value is calculated as one more than the
calculated size of memory. If not enabled, the
default is $00000000.
Master Ending Address #300000000Ending address of the VMEbus resource that is
accessible from the local bus. If enabled, the
default is $00FFFFFF, otherwise $00000000.
Master Control #300Defines the access characteristics for the
address space defined with this master address
decoder. If enabled, the default is $3D,
otherwise $00.
Master Enable #4 [Y/N]NDo not set up and enable Master Address
Decoder #4.
Master Starting Address #400000000Base address of the VMEbus resource that is
accessible from the local bus. Default is $0.
Master Ending Address #400000000Ending address of the VMEbus resource that is
accessible from the local bus. Default is $0.
Master Address Translation
Address #4
Master Address Translation Select #400000000This register defines which bits of the address
Master Control #400Defines the access characteristics for the
Short I/O (VMEbus A16) Enable
[Y/N]
Short I/O (VMEbus A16) Control01Defines the access characteristics for the
00000000This register allows the VMEbus address and
the local address to differ. The value in this
register is the base address of the VMEbus
resource that is associated with the starting and
ending address selection from the previous
questions. Default is 0.
are significant. A logical "1" indicates
significant address bits, logical "0" is nonsignificant. Default is 0.
address space defined with this master address
decoder. Default is $00.
YYes, Enable the Short I/O Address Decoder.
address space defined with the Short I/O
address decoder. Default is $01.
If you have specified environmental parameters that will
cause an overlap condition, a warning message will appear
before the environmental parameters are saved in NVRAM.
The important informa tion about each configurable ele ment in
the memory map is displayed, showing where any overlap
conditions exist. This allows you to quickly identify and
correct an undesirable configuration before it is saved.
3
If an undesirable configura tion alrea dy exist s, you may wis h to res tore the
factory defaults with env;d <CR>.
This chapter describes the MVME172P4 VME embedded controller on a
block diagram level. The Summary of Features provides an overview of
the MVME172P4, followed by a d eta il ed description of several bloc ks o f
circuitry. Figure 4-1 shows a block diagram of the overall board
architecture.
Detailed descriptions of other MVME172P4 blocks, including
programmable registe rs in the ASICs and peripheral c hips, can be f ound in
the MVME1X2P4 VME Embedded Controller Programmer’s Reference Guide (part number V1X2P4A/PG). Refer to that manual for a functional
description of the MVME172P4 in greater depth.
Summary of Features
4
The following table summarizes the features of the MVME172P4 VME
embedded controller.
Table 4-1. MVME172P4 Features
FeatureDescription
MicroprocessorMVME172P4: 60MHz MC68060 or 64MHZ MC68LC060 processor
Form factor6U VMEbus
16MB synchronous DRAM (SDRAM), configurable to emulate
Memory
Flash memory
EPROMOne 32-pin JEDEC stand ard PLCC EPROM socket with 512Kb x 8 density
Real-time clock
1/4/8/16MB parity-protected DRAM or 4/8/16MB ECC-protected DRAM
512KB SRAM with battery backup
MVME172P4: One Intel 28F160S5 2MB 8-bit Flash device with optional
write protection
8KB NVRAM with RTC, battery backup, and watchdog function (SGSThomson M48T58)
InterruptsEight software interrupts (on versions with VMEchip2 ASIC)
VME I/OVMEbus P2 connector
Serial I/O
Ethernet I/O
IP interfaceFour IndustryPack interface channels v ia 3M connectors behin d front panel
SCSI I/OOptional SCSI interface with DMA via P2 or LCP2 adapte r board
VMEbus interface
Controller (
Activity
Four 32-bit tick timers and watchdog timer in Petra ASIC
Two 32-bit tick timers and watchdog timer in VMEchip2 ASIC
Two EIA-232-D, EIA-530, EIA-422, or EIA-425 configurable serial ports
via front panel and transition module
Optional Ethernet transceiver interface via DB15 connector on transition
module
VMEbus system contro ller functions
VMEbus-to-local-bus interface (A24/A32, D8/D16/D32/block transfer
[D8/D16/D32/D64])
Local-bus-to-VMEbus interface (A16/A24/A32, D8/D16/D32)
VMEbus interrupter
VMEbus interrupt handler
Global Control/Status Register (GCSR) for interprocesso r communications
DMA for fast local memory/VMEbus transfers (A16/A24/A32,
D16/D32/D64)
(SCSI), VME Activity (VME)
(FAIL), CPU Status (STAT), CPU Ac tivity (RUN), Sy st e m
SCON), LAN Activity (LAN), Fuse Status (FUSE), SCSI
Processor and Memory
The MVME172P4 is based on the MC68060/MC68LC060
microprocessor. The boards are built with 16MB synchronous DRAM
(SDRAM). Various versions of the MVME1 72P4 may have the SDRAM
configured to model 1MB, 4MB, 8MB, or 16MB of parity-protected
DRAM or 4MB, 8MB, or 16MB of ECC-protected DRAM.
All boards are available with 512KB of SRAM (with battery backup);
time-of-day clock (with batte ry bac kup) ; an opt io nal Ether net tra nsc ei ver
interface; two serial ports with EIA-232-D or EIA-530 or EIA-485/-422
interface; six ti ck timers with watchdo g timer(s); an EPROM soc ket; 2MB
Flash memory (one Flash device); four IndustryPack (IP) interfaces with
DMA; optional SCSI bus interface with DMA; and a VMEbus interface
(local bus to VMEbus/VMEbus to local bus, with A16/A24/A32,
D8/D16/D32 bus widths and a VMEbus system controller).
I/O Implementation
Input/Output (I/O) s ignals on the MVME172P4 are routed to the VMEbus
P2 connector. The main board is connected through a P2 adapter board and
cables to the transition boards. The MVME172P4 supports the
MVME712M and MVME712B series of transition boards (referred to in
this manual as MVME712x, unless separately specified).
The MVME712x transition boards provide configuration headers, serial
port drivers, and industry-standard connectors for various I/O devices.
Although the MVME712x series transition boards were originally
designed to support MVME167 boar ds, they lend themselves readily to the
MVME172P4 application a s long as you keep a few spec ial considerat ions
in mind (refer to th e section o n the Ser ial Communi cations I nterfac e, later
in this chapter, for details).
Summary of Features
4
The I/O connection for the serial ports on the MVME172P4 is also
implemented with two DB25 co nnectors on the front panel. In addition, the
panel has cutouts for routing of flat cables to the optional IndustryPack
modules.
❏ VMEchip2 ASIC (VMEbus interface). Provi des two ti ck timers, a
watchdog timer, programmable map decoders for the master and
4
slave interfaces, and a VMEbus to/from local bus DMA controller
as well as a VMEbus to/from local bus non-DMA programmed
access interface, a VMEbus interrupter, a VMEbus system
controller, a VMEbus interrupt handler, and a VMEbus requester.
Processor-to-VMEbus transfers are D8, D16, or D32. VMEchip2
DMA transfers to the VMEbus, however, are D16, D32, D16/BLT,
D32/BLT, or D64/MBLT.
❏ Petra ASIC. Combines the functions previously covered by the
MC2 chip, the MCECC chip, and the IP2 chip in a single ASIC.
– MC2 function. Provides a parity DRAM emulation. Also
supplies four tick timers and interfaces to the LAN chip, SCSI
chip, serial port chip, BBRAM, EPROM/Flash, and SRAM.
– MCECC function. Provides an ECC DRAM emulation.
– IP2 function. Provides control and status information for up to
four single-wide or two double- wide Indus tryPack mod ules that
can be plugged into the MVME172P4 main board.
Block Diagram
The block diagram in Figure 4-1 on page 4-5 illustr ates the
MVME172P4’s overall architecture.
Functional Description
This section contains a functional description of the major blocks on the
MVME172P4.
The local bus on the MVME172P4 is a 32-bit synchronous bus that is
based on the MC68060 bus, and which supports burst transfers and
snooping. The various local bus mast er and sl ave devices us e the local bu s
to communicate. The local bus is arbitrated by pri ority type; the prio rity of
4
the local bus masters from highest to lowest is: 82596CA LAN, 53C710
SCSI, VMEbus, and MPU. As a general rule, any master can access any
slave; not all combinat ions pass the common sense test , however. Refer to
the MVME1X2P4 VME Embedded Controller Programmer’s Reference Guide and to the u ser’s guide for eac h device to determ ine its port s ize, data
bus connection, and any restr ictions that appl y when accessing the device.
Microprocessor
MVME172P4 models may be ordered wi th an MC680 60 o r MC68LC060
microprocessor.
The MC68060 has on-chip instruction and dat a caches and a float ing-point
processor. (A floating-point coprocessor is the major difference between
the MC68060 and MC68LC060.) Refer to the MC68060 use r’s manual for
more information.
xx
MC68
4-6Computer Group Literature Center Web Site
060 Cache
The MVME172P4 local bus masters (VMEchip2, processor, 53C710
SCSI controller, and 82596CA Ethernet controller) have programmable
control of the snoop/ caching mode. Th e IP DMA local bus master’s snoo p
control function is govern ed by the settings of switc h S5 segments 1 and 2
(refer to IP DMA Snoop Control (S5 Pins 1/2)on page 1-18). S5
determines the val ue of t he snoop co ntrol signal fo r all IP DMA t ransf ers.
This includes the IP DMA whi ch executes when the DMA control r egisters
are updated while the IP DMA is operating in command chaining mode.
The MVME172P4 local bus slaves that support the snoop/caching mode
are defined in the “Lo cal Bus M emory Ma p” sect ion o f the MVME1X2P4
NoteAs outlined in Table 1-4, the snoop capabilities of the
MC68xx060 processor differ f rom those of the MC68xx040 used
on MVME162P4 series boards. Application software must take
these differences into account.
No-VMEbus-Interface Option
In support of possible future configurations in which the MVME172P4
might be offered as an e mbedded controller witho ut the VMEbus interface,
certain logic in the VMEchip2 has been duplicated in the Petra chip. (For
the location of the overlapping logic, refer to Chapter 1 in the
MVME1X2P4 VME Embedded Controller Programmer’s Reference
Guide.) As long as th e VMEchi p2 ASI C is pr ese nt , th e r edundant logic is
inhibited in the Petra chip. The enabling signals for these functions are
controlled by software and Petra chip hardware initiali zation.
Memory Options
The following memory options are available on the different versions of
MVME172P4 boards.
DRAM
MVME172P4 boards are built with 16MB synchronous DRAM
(SDRAM). Depending on build opt ions chosen at the time of manufacture,
various versions of the MVME172P4 have the SDRAM configured to
model 1MB, 4MB, 8MB, or 16MB of parity-protected DRAM or 4MB,
8MB, or 16MB of ECC-protected DRAM.
4
The SDRAM memory array itself is always a single-bit error correcting
and multi-bit error detection memory, irrespective of which interface
model you use to access the SDRAM. When the MC2 (parity) memory
controller interface is used to access the SDRAM, single-bit errors are
undetectable to users and multi-bit errors are defined to be parity errors.
Firmware will initialize the memory controller to maintain backward
compatibility with MVME172FX or -LX products. If the Petra ASIC is
supporting MVME172FX functionality, the parity memory controller
model will be enabled by default. If the Petra ASIC is supporting