Motorola MVME712AM Guide d'installation

Naviguer en ligne ou télécharger Guide d'installation pour Processeurs Motorola MVME712AM. Motorola MVME712AM Installation guide Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 176
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs

Résumé du contenu

Page 1 - Installation Guide

MVME167Single Board ComputerInstallation Guide MVME167IG/D4

Page 2 - Restricted Rights Legend

Starting Up 167Bug 4-6Autoboot 4-6 Autoboot Sequence 4-6ROMboot 4-7ROMboot Sequence 4-7Network Boot 4-8Network Boot Sequence 4-8Restarting the System

Page 3

4-22Debugger General Information4MPCR Status CodesThe status codes stored in the MPCR are of two types: ❏ Status returned (from the 167Bug) ❏ Command

Page 4 - Safety Depends On You

Multiprocessor Support4-2343. As the initialization proceeds, the execution path comes to the "prompt" routine. Before sending the prompt, t

Page 5

4-24Debugger General Information4Global Control and Status Register (GCSR) MethodA remote processor can initiate program execution in the local MVME16

Page 6

Diagnostic Facilities4-254Diagnostic FacilitiesIncluded in the 167Bug package is a complete set of hardware diagnostics intended for testing and troub

Page 7 - Contents

4-26Debugger General Information4NV Non-Verbose ModeSD Switch DirectoriesSE Stop on Error ModeST SelftestZE Clear (Zero) Error CountersZP Zero Pass Co

Page 8

Diagnostic Facilities4-274167Bug Diagnostic Test GroupsRefer to the MVME167Bug Debugging Package User's Manual for complete descriptions of the d

Page 9

4-28Debugger General Information4

Page 10

55-15Using the 167BugDebuggerThis Chapter Covers❏ Entering debugger command lines❏ Entering and debugging programs❏ Calling system utilities from user

Page 11 - Port Numbers 5-9

5-2Using the 167Bug Debugger5Note The presence of the upward caret ( ^ ) before a character indicates that the Control (CTRL) key must be held down w

Page 12

Entering Debugger Command Lines5-35For example, if a breakpoint has been specified, then control returns to the debugger when the breakpoint is encoun

Page 13 - List of Figures

Multiprocessor Address Register (MPAR) 4-22MPCR Powerup sequence 4-22Global Control and Status Register (GCSR) Method 4-24Diagnostic Facilities 4-251

Page 14 - List of Tables

5-4Using the 167Bug Debugger5Syntactic VariablesThe following syntactic variables are encountered in the command descriptions which follow. In additio

Page 15 - 1Introduction to the MVME167

Entering Debugger Command Lines5-55A numeric value may also be expressed as a string literal of up to four characters. The string literal must begin a

Page 16 - Used in this Manual

5-6Using the 167Bug Debugger5Address FormatsTable 5-1 summarizes the address formats that are acceptable for address parameters in debugger command li

Page 17

Entering Debugger Command Lines5-75Note In commands with range specified as addr del addr, and with size option W or L chosen, data at the second (en

Page 18

5-8Using the 167Bug Debugger5Example: A portion of the listing file of an assembled, relocatable module is shown below: The above program was loaded a

Page 19 - Related Documentation

Entering Debugger Command Lines5-95By using one of the offset registers, the disassembled code addresses can be made to match the listing file address

Page 20

5-10Using the 167Bug Debugger5Entering and Debugging ProgramsThere are various ways to enter a user program into system memory for execution:❏ Create

Page 21

Calling System Utilities from User Programs5-115A communication link must exist between the host system and the MVME167 port 1. (Hardware configuratio

Page 22

5-12Using the 167Bug Debugger5167Bug uses certain of the MVME167 onboard resources and may also use offboard system memory to contain temporary variab

Page 23 - Description

Preserving the Debugger Operating Environment5-135Examples❏ If, for example, your program inadvertently wrote over the static variable area containing

Page 24 - SCSI Mass Storage Interface

Disk/Tape Controller Default ConÞgurations B-2IOT Command Parameters for Supported Floppy Types B-4Network Controller Modules Supported C-1Introducti

Page 25 - Parallel (Printer) Port

5-14Using the 167Bug Debugger5Note These depend on what the Vector Base Register (VBR) is set to in the VMEchip2.When the debugger handles one of the

Page 26 - Features

Preserving the Debugger Operating Environment5-155Example: Trace one instruction using debugger. 167Bug>RDPC =00010000 SR =2700=TR:OFF_S._7_...

Page 27

5-16Using the 167Bug Debugger5The start address of this target vector table area is the base address ($00) of the debugger memory. This address is loa

Page 28 - Specifications

Preserving the Debugger Operating Environment5-175**** EXCEPT - Exception handler *****EXCEPT SUBQ.L #4,A7 Save space in stack for a PC value.LINK A

Page 29 - Board Level Overview

5-18Using the 167Bug Debugger5It may turn out that your program uses one or more of the exception vectors that are required for debugger operation. De

Page 30 - Transition Modules

Floating Point Support5-195Valid data types that can be used when modifying a floating point data register or a floating point memory location:When en

Page 31

5-20Using the 167Bug Debugger5Single Precision RealThis format would appear in memory as:A single precision number takes 4 bytes in memory. Double Pre

Page 32 - Functional Description

Floating Point Support5-215Packed Decimal RealThis format would appear in memory as:A packed decimal number takes 12 bytes in memory. Scientific Notati

Page 33 - Front Panel Switches and LEDs

5-22Using the 167Bug Debugger5The 167Bug Debugger Command SetThe 167Bug debugger commands are summarized in Table 5-3. The command syntax is shown usi

Page 34 - MC68040 MPU

The 167Bug Debugger Command Set5-235DC Data Conversion DC exp | addr [; [B][O][A]]DMA DMA Block of Memory MoveDMA range del addr del vdir del am del b

Page 35 - Static RAM

List of Figures MVME167 General Block Diagram 2-7MVME167 Switches, Headers, Connectors, Fuses, and LEDs 3-6Typical Internal SCSI and Serial Port Conn

Page 36

5-24Using the 167Bug Debugger5MAR Load Macros MAR [controller LUN] [del [device LUN][del block #]]MD Memory Display MD [S] addr [:count | del addr] [;

Page 37 - Onboard DRAM

The 167Bug Debugger Command Set5-255RESET Cold/Warm Reset RESETRL Read Loop RL addr; [B|W|L]RM Register Modify RM [reg] [; [S|D]]RS Register Set RS re

Page 38

5-26Using the 167Bug Debugger5

Page 39

AA-1AConfigure and EnvironmentCommandsThis Appendix Covers❏ Configuring the board information block ❏ Setting the environment to Bug/Operating System ❏

Page 40 - I/O Interfaces

A-2Configure and Environment CommandsAExample: to display the current contents of the board information block. 167-Bug>cnfg Board (PWA) Serial Numb

Page 41

Setting Environment to Bug/Operating SystemA-3AOnce modification and update is complete, you can now display the current contents as described earlier

Page 42 - ❏ low-to-high transition

A-4Configure and Environment CommandsAThe parameters to be configured are listed in the following table:Table A-1. ENV Command Parameters ENV Paramet

Page 43

Setting Environment to Bug/Operating SystemA-5AAuto Boot Abort Delay 15 This is the time in seconds that the Auto Boot sequence will delay before star

Page 44

A-6Configure and Environment CommandsANetwork Auto Boot Controller LUN00 LUN of a network controller module currently supported by the Bug. Default is

Page 45 - Local Resources

Setting Environment to Bug/Operating SystemA-7ANetwork Auto Boot ConÞguration Parameters Pointer (NVRAM)00000000 This is the address where the network

Page 46 - Memory Maps

xiv List of Tables MVME167 General SpeciÞcations 2-6Bus Transfers 2-9Front Panel Switches 2-11Front Panel LEDs 2-11Local Bus Memory Map 2-25Local I/O

Page 47

A-8Configure and Environment CommandsAMemory Search Ending Address 02000000 Top limit of the Bug's search for a work page. If a contiguous block

Page 48

Setting Environment to Bug/Operating SystemA-9ABase Address of Local Memory 00000000 Beginning address of Local Memory. It must be a multiple of the L

Page 49

A-10Configure and Environment CommandsASlave Address Translation Select #100000000 This register deÞnes which bits of the Translation Address are sign

Page 50 - VMEbus Memory Map

Setting Environment to Bug/Operating SystemA-11AMaster Enable #1 [Y/N] Y Yes, Setup and enable the Master Address Decoder #1. Master Starting Address

Page 51 - Installation

A-12Configure and Environment CommandsAMaster Enable #4 [Y/N] N Do not set up and enable the Master Address Decoder #4. Master Starting Address #4 000

Page 52 - Overview of Startup Procedure

Setting Environment to Bug/Operating SystemA-13AF-Page (VMEbus A24) Enable [Y/N]Y Yes, Enable the F-Page Address Decoder. F-Page (VMEbus A24) Control

Page 53

A-14Configure and Environment CommandsA

Page 54

BB-1BDisk/Tape ControllerDataDisk/Tape Controller Modules SupportedThe following VMEbus disk/tape controller modules are supported by the 167Bug. The

Page 55 - Preparing the Hardware

B-2Disk/Tape Controller DataBDisk/Tape Controller Default ConfigurationsNote SCSI Common Command Set (CCS) devices are only the ones tested by Motorola

Page 56 - PRIMARY SIDE

Disk/Tape Controller Default ConfigurationsB-3BMVME327A -- 9 DevicesController LUN Address Device LUN Device Type2 $FFFFA600 00102030405060SCSI Common

Page 57 - Jumper Settings

1 1-1 1Introduction to the MVME167Installation Guide This Chapter Covers ❏ Details about this manual ❏ Terminology, conventions, and definitions used

Page 58

B-4Disk/Tape Controller DataBIOT Command Parameters for Supported Floppy TypesThe following table lists the proper IOT command parameters for floppies

Page 59

IOT Command Parameters for Supported Floppy TypesB-5BSingle/DoubleTRACK DensityDDDD DDDSingle/Equal_in_allTrack Zero DensitySEEE EEESlow/Fast Data Rat

Page 60

B-6Disk/Tape Controller DataB

Page 61

CC-1CNetwork ControllerDataNetwork Controller Modules SupportedThe following VMEbus network controller modules supported by MVME167Bug are shown in Ta

Page 62

C-2Network Controller DataCMVME376 $07 $00 $FFFFA400 EthernetMVME374 $10 $00 $FF000000 EthernetMVME374 $11 $00 $FF100000 EthernetMVME374 $12 $00 $FF20

Page 63

DD-1DTroubleshooting the MVME167:Solving Startup Problems❏ Try these simple troubleshooting steps before calling for help or sending your CPU board ba

Page 64 - Preparing the System Chassis

D-2Troubleshooting the MVME167: Solving Startup ProblemsDII. There is a display on the terminal, but input from the keyboard has no effect.A. The keyb

Page 65 - Installing the Hardware

D-3DIII. Debug prompt 167-Bug>does not appear at powerup, and the board does not auto boot.A. Debugger EPROM may be missing.1. Disconnect all power

Page 66

D-4Troubleshooting the MVME167: Solving Startup ProblemsDIV. Debug prompt167-Bug>appears at powerup, but the board does not auto boot.A. The initia

Page 67

D-5D6. You may need to use the cnfg command (see Appendix A) to change clock speed and/or Ethernet Address, and then later return toenv <Return>

Page 68

1-2Introduction to the MVME167 Installation Guide1 Terminology, Conventions, and Definitions Used in this Manual Data and Address Parameter Numeric Fo

Page 69 - Connecting Peripherals

D-6Troubleshooting the MVME167: Solving Startup ProblemsD

Page 70 - ❏ one stop bit per character

EE-1EEIA-232-DInterconnectionsIntroductionThe EIA-232-D standard is the most common terminal/computer and terminal/modem interface, and yet it is not

Page 71

E-2EIA-232-D InterconnectionsETable E-1. EIA-232-D Interconnections Pin NumberSignal MnemonicSignal Name and Description1 CHASSIS GROUND. Not always

Page 72 - SCSI INTERFACE

Levels of ImplementationE-3ELevels of ImplementationThere are several levels of conformance that may be appropriate for typical EIA-232-D interconnect

Page 73 - Starting the System

E-4EIA-232-D InterconnectionsESignal AdaptationsOne set of handshaking signals frequently implemented are RTS and CTS. CTS is used in many systems to

Page 74

Levels of ImplementationE-5EFigure E-1. Middle-of-the-Road EIA-232-D Configuration3TXDRXDRTSCTSDCDTXCRXC-12VTXDRXDRTSCTSDCDTXCRXCOPTIONALHARDWARETRANS

Page 75 - WED May 22 10:37:00.00 1996

E-6EIA-232-D InterconnectionsEFigure E-2 shows a way of wiring an EIA-232-D connector to enable a computer to connect to a basic terminal with only th

Page 76 - System Considerations

Levels of ImplementationE-7EProper GroundingAnother subject to consider is the use of ground pins. There are two pins labeled GND. Pin 7 is the SIGNAL

Page 77

E-8EIA-232-D InterconnectionsE

Page 78

IN-9IndexSymbols+12V LED 2-11Numerics167Bug (see debug monitor andMVME167Bug)command line 5-1command-line interface 2-4debugger command set 5-22firmwa

Page 79 - Information

Terminology, Conventions, and Definitions Used in this Manual1-31 Assertion and Negation Conventions Assertion and negation are used to specify forci

Page 80 - Description of 167Bug

IndexIN-10INDEXboldface strings 5-3booting 167Bug 4-5BOOTP protocol module 4-20Bootstrap and Halt (BH) 4-16Bootstrap Operating System (BO) 4-15braces

Page 81

IN-11INDEXgeneral information 4-1prompt 5-1setup/operation parameters storedin ROM 3-9decimal number 1-2default 167Bug controller and device pa-ramete

Page 82 - 167Bug Implementation

IndexIN-12INDEXFfactory debugger environment D-1FAIL LED 2-11false 1-3features 2-4general description 2-1flexible diskette B-2floating pointinstructio

Page 83 - Booting and Restarting 167Bug

IN-13INDEXjumpers 3-8Kkeyboard control 4-3LLANLED 2-11transceiver 3-27LAN (local area network) (see 82596CAand Ethernet) 2-21LCSR (Local Control and S

Page 84 - Autoboot

IndexIN-14INDEXMVME712X 2-8, 3-16NNCR 53C710 SCSI I/O controller 2-22negation 1-3network boot 4-8network boot control module 4-20network controller da

Page 85

IN-15INDEXRTXC4 (Receive Transmit Clock 4) 3-10,3-13RUN LED 2-11SSanyo CR2430 battery 2-14SBC (see CISC Single Board Comput-er(s)) B-1SCC (Serial Cont

Page 86 - Network Boot

IndexIN-16INDEXstatic variable space 4-5status bit 1-4status pins 2-20storage and the Real-Time Clock 3-28streaming tape drive (see QIC-2 stream-ing t

Page 87 - Restarting the System

1-4Introduction to the MVME167 Installation Guide1 Control and Status Bit Definitions The terms control bit and status bit are used extensively in thi

Page 88

Related Documentation1-51 Related Documentation The MVME167 ships with a startup installation guide (MVME167IG/D, the document you are presently read

Page 89

Notice While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any omissi

Page 90

1-6Introduction to the MVME167 Installation Guide1 Additional Manuals for this Board Also available but not included in the set: Other Applicable Mot

Page 91 - Disk I/O Support

Related Documentation1-71 Non-Motorola Peripheral Controllers Publications Bundle For your convenience, we have collected user's manuals for eac

Page 92 - Device Probe Function

1-8Introduction to the MVME167 Installation Guide1 Applicable Non-Motorola Publications The following non-Motorola publications are also available fr

Page 93 - Disk I/O via 167Bug Commands

22-12Board Level HardwareDescriptionThis Chapter Covers❏ A general description of the MVME167 CISC Single Board Computer❏ Features and specifications❏

Page 94

2-2Board Level Hardware Description2Onboard Memory Mezzanine ModuleThe MVME167 onboard DRAM mezzanine boards are available in different sizes and with

Page 95

General Description2-32Serial PortsThe serial ports support standard baud rates of 110 to 38.4K baud.All four serial ports use EIA-232-D drivers and r

Page 96 - Disk I/O Error Codes

2-4Board Level Hardware Description2167Bug FirmwareThe MVME167Bug debug monitor firmware (167Bug) is provided in two of the four EPROM sockets on the

Page 97 - Network I/O Support

Features2-52❏ RESET and ABORT switches ❏ Four 32-bit tick timers for periodic interrupts ❏ Watchdog timer ❏ Eight software interrupts ❏ I/O Ð SCSI Bus

Page 98 - Network Boot Control Module

2-6Board Level Hardware Description2SpecificationsConformance to RequirementsThese boards are designed to conform to the requirements of the following

Page 99

Board Level Overview2-72Board Level OverviewConnectorsThe MVME167 has two 96-position DIN connectors: P1 and P2. ❏ P1 rows A, B, C, and P2 row B provi

Page 100

Preface This manual provides a general board level hardware description, hardware preparation and installation instructions, debugger general informa

Page 101 - Multiprocessor Support

2-8Board Level Hardware Description2Transition ModulesThe MVME712X transition modules provide configuration headers and provide industry standard conn

Page 102 - GPCSR0 GPCSR1

Board Level Overview2-92VMEchip2 ASICProvides the VMEbus interface. The VMEchip2 includes:❏ Two tick timers❏ A watchdog timer❏ Programmable map decode

Page 103 - Diagnostic Facilities

2-10Board Level Hardware Description2MEMC040 Memory Controller ASICThe MEMC040 memory controller ASIC provides the programmable interface for the pari

Page 104

Functional Description2-112Front Panel Switches and LEDsThere are two switches and eight LEDs on the boardÕs front panel (refer to Table 2-3, Table 2-

Page 105 - 167Bug Diagnostic Test Groups

2-12Board Level Hardware Description2Data Bus StructureThe local data bus on the MVME167 is a 32-bit synchronous bus that is based on the MC68040 bus,

Page 106

Functional Description2-132EPROMFour 44-pin PLCC/CLCC EPROM sockets for 27C102JK or 27C202JK type EPROMs. They are:❏ Organized as two 32-bit wide bank

Page 107 - Debugger

2-14Board Level Hardware Description2Optional SRAM Battery BackupSRAM battery backup is optionally available on the MVME167, but only as a factory bui

Page 108

Functional Description2-152!CautionLithium batteries incorporate inflammable materials such as lithium and organic solvents. If lithium batteries are

Page 109 - Debugger Command Syntax

2-16Board Level Hardware Description2Motorola software does support mixed parity and ECC memory boards on the same main board.The DRAM is four-way int

Page 110 - Syntactic Variables

Functional Description2-172Battery Backed Up RAM and ClockThe MK48T08 RAM and clock chip is a 28-pin package that provides:❏ A time-of-day clock❏ An o

Page 111

Safety SummarySafety Depends On You The following general safety precautions must be observed during all phases of operation, service, andrepair of t

Page 112 - Address Formats

2-18Board Level Hardware Description2VMEbus InterfaceThe VMEchip2 provides:❏ Local bus to VMEbus interface❏ VMEbus to local bus interface❏ Local-VMEbu

Page 113

Functional Description2-192All four serial ports use EIA-232-D drivers and receivers located on the MVME167, and all the signal lines are routed to th

Page 114 - MD 1327C;DI

2-20Board Level Hardware Description2Parallel Port InterfaceThe PCCchip2 provides an 8-bit bidirectional parallel port. This port may be used as a Cen

Page 115 - Port Numbers

Functional Description2-212The PCCchip2 provides an auto-strobe feature similar to that of the MVME147 PCC. ❏ In auto-strobe mode, after a write to th

Page 116

2-22Board Level Hardware Description2Buffer OverrunsBecause the 82596CA has small internal buffers and the VMEbus has an undefined latency period, buf

Page 117 - Environment

Functional Description2-232Local ResourcesThe MVME167 includes many resources for the local processor. These include tick timers, software programmabl

Page 118

2-24Board Level Hardware Description2Memory MapsThere are two points of view for memory maps: 1. Local bus memory mapÐ The mapping of all resources as

Page 119 - Hardware Functions

Memory Maps2-252Table 2-5. Local Bus Memory MapAddress RangeDevices AccessedPort SizeSizeSoftwareCacheInhibitNotes$00000000 - DRAMSIZEUser Programmab

Page 120 - Exception 167Bug Facility

2-26Board Level Hardware Description2The following table focuses on the Local I/O Devices portion of the local bus Main Memory Map.Table 2-6. Local I

Page 121 - ❏ Manually with GO command

Memory Maps2-272$FFFA0000 - $FFFBFFFF reserved -- 128KB 4$FFFC0000 - $FFFCFFFF MK48T08 (BBRAM, TODClock)D32-D8 64KB 1$FFFD0000 - $FFFDFFFF reserved --

Page 122

All Motorola PWBs (printed wiring boards) are manufactured by UL-recognized manufacturers, with a ßammability rating of 94V-0. !WARNING This equipmen

Page 123

2-28Board Level Hardware Description2VMEbus Memory MapThis section describes the mapping of local resources as viewed by VMEbus masters. Default addre

Page 124 - Floating Point Support

33-13Hardware Preparation andInstallationThis Chapter CoversThis chapter provides instructions on:❏ Unpacking the equipment❏ Preparing the hardware ❏

Page 125

3-2Hardware Preparation and Installation3Overview of Startup ProcedureThe following list identifies the things you will need to do before you can use

Page 126 - Extended Precision Real

Overview of Startup Procedure3-334 Install adapter boards and transition modules. Transition Modules and Adapter Boards Overview3-16Installing Transit

Page 127 - Scientific Notation

3-4Hardware Preparation and Installation37 Start up the system. Starting the System3-23Power up the system. Front Panel Switches and LEDs2-11Initializ

Page 128

Preparing the Hardware3-53Preparing the HardwareThis section covers:❏ Modifying hardware configurations before installation❏ Checking the 167Bug EPROM

Page 129 - ; B

3-6Hardware Preparation and Installation3Figure 3-1. MVME167 Switches, Headers, Connectors, Fuses, and LEDsS1 S2P1A1B1C1A32B32C321379 9404MVME167PRIM

Page 130 - Display/Modify

Preparing the Hardware3-73Checking the 167Bug EPROMsBe sure that the two factory installed 128K x 16 167Bug EPROMs are in the proper sockets. EPROM Lo

Page 131

3-8Hardware Preparation and Installation3Optional Jumper SettingsMost of the optional functions on your board can be changed through software control

Page 132

Preparing the Hardware3-93Table 3-2. J1 Bit DescriptionsBit J1 Pins DescriptionBit #0 (GPI0) 1-2 When this bit is a one (high), it instructs the debu

Page 134

3-10Hardware Preparation and Installation3System Controller Header J2The MVME167 can be VMEbus system controller. The system controller function is en

Page 135

Preparing the Hardware3-113The remaining configuration of the clock lines is accomplished using the Serial Port 4 Clock Configuration Select header on

Page 136

3-12Hardware Preparation and Installation3Optional SRAM Backup Power Source Select Header J8Header J8 is an optional header used to select the SRAM ba

Page 137

Preparing the Hardware3-133Preparing the MVME167 for InstallationRefer to the setup procedures in the manuals for your particular chassis or system fo

Page 138

3-14Hardware Preparation and Installation3Preparing the System ChassisNow that the MVME167 is ready for installation, prepare the system chassis and d

Page 139

Installing the Hardware3-153Installing the HardwareThis section covers❏ Installation of the MVME167 into a VME chassis❏ Overview and installation of t

Page 140

3-16Hardware Preparation and Installation3Transition Modules and Adapter Boards OverviewThe MVME167 supports the MVME712-12, MVME712-13, MVME712M, MVM

Page 141

Installing the Hardware3-173Figure 3-2. Typical Internal SCSI and Serial Port ConnectionsP1P2J2J3ENCLOSURE BOUNDARYLC P2 P2TERMINATORJ2, P2, OR J11MV

Page 142

3-18Hardware Preparation and Installation3Equipment ConnectionsSome connection diagrams are in the Single Board Computer Programmer's Reference G

Page 143

Installing the Hardware3-193Installing Transition Modules and Adapter BoardsConnecting PeripheralsThe MVME167 mates with (optional) terminals or other

Page 144

Contents This Chapter Covers 1-1About this Manual 1-1Terminology, Conventions, and DeÞnitions Used in this Manual 1-2Data and Address Parameter Numer

Page 145

3-20Hardware Preparation and Installation3Table 3-12. Peripheral Connection Procedures Step Action... Refer to...1 Connect and install any optional S

Page 146

Installing the Hardware3-213Note In order for high-baud rate serial communication between 167Bug and the terminal to work, the terminal must do some f

Page 147 - BDisk/Tape Controller

3-22Hardware Preparation and Installation3Figure 3-4. Typical Transition Module Peripheral Port ConnectorsPRINTERMVME712A/12/13SERIAL PORT 1 SERIAL P

Page 148

Installing the Hardware3-233Completing the InstallationStarting the SystemAfter completing the preparation and installation procedures, you are ready

Page 149

3-24Hardware Preparation and Installation3Powering Up the SystemThe following table shows what takes place when you turn equipment power ON (depending

Page 150 - Floppy Types

Installing the Hardware3-253Programming the PCCchip2 and VMEchip2See System Considerations below, and refer to Memory Maps on page 2-24, and the Singl

Page 151

3-26Hardware Preparation and Installation3System ConsiderationsBackplane Power ConnectionsThe MVME167 needs to draw power from both P1 and P2 of the V

Page 152 - Disk/Tape Controller Data

System Considerations3-273Multiple Module Cage ConfigurationMultiple MVME167s may be configured into a single VME card cage. In general, hardware multi

Page 153 - CNetwork Controller

3-28Hardware Preparation and Installation3SCSI Bus Termination❏ The MVME167 provides SCSI terminator power through a 1-amp fuse (F1) located on the P2

Page 154

44-14Debugger GeneralInformationThis Chapter Covers❏ An introduction to the MVME167Bug firmware package❏ Booting and restarting 167Bug❏ Disk input/out

Page 155 - Solving Startup Problems

Functional Description 2-10Front Panel Switches and LEDs 2-11Data Bus Structure 2-12Local Bus Arbitration 2-12MC68040 MPU 2-12EPROM 2-13Programmable

Page 156 - CONTROL key and type a ÒQÓ)

4-2Debugger General Information4Description of 167BugThe 167Bug package, MVME167Bug, is a powerful evaluation and debugging tool for systems built aro

Page 157

Introduction to MVME167Bug4-34Debugger or Diagnostic DirectoriesWhen using 167Bug, you operate out of either the debugger directory or the diagnostic

Page 158 - RETURN key

4-4Debugger General Information4Similarity to other Motorola Debugging FirmwareIf you have used one or more of Motorola's other debugging package

Page 159

Booting and Restarting 167Bug4-54Memory RequirementsThe program portion of 167Bug is approximately 512KB of code, consisting of download, debugger, an

Page 160

4-6Debugger General Information4Starting Up 167Bug1. Verify that the MVME167 is properly installed and operating as described in Table 3-1 on page 3-2

Page 161 - Interconnections

Booting and Restarting 167Bug4-744. Following this message there is a delay to allow you an opportunity to abort the Autoboot process if you wish. To

Page 162

4-8Debugger General Information4For a user's ROMboot module to gain control through the ROMboot linkage, four requirements must be met: For compl

Page 163 - Levels of Implementation

Booting and Restarting 167Bug4-943. At powerup, Network Boot is enabled, and providing the drive and controller numbers encountered are valid, the fol

Page 164 - Sample Configurations

4-10Debugger General Information4ResetPressing and releasing the MVME167 front panel RESET switch initiates a system reset. Reset must be used if the

Page 165

Booting and Restarting 167Bug4-114Whenever abort is invoked when executing a user program (running target code), a "snapshot" of the process

Page 166 - EIA-232-D Interconnections

Optional Jumper Settings 3-8General Purpose Software Readable Header J1 3-8System Controller Header J2 3-10Serial Port 4 Clock Configuration Select H

Page 167 - Proper Grounding

4-12Debugger General Information4 Break Sequence1. Removes any breakpoints in your code and keeps the breakpoint table intact. 2. Takes a snapshot of

Page 168

Disk I/O Support4-134Disk I/O Support167Bug can initiate disk input/output by communicating with intelligent disk controller modules over the VMEbus.

Page 169 - Numerics

4-14Debugger General Information4Blocks Versus SectorsThe logical block defines the unit of information for disk devices. A disk is viewed by 167Bug a

Page 170

Disk I/O Support4-154Disk I/O via 167Bug CommandsThese following 167Bug commands are provided for disk I/O. Detailed instructions for their use are fo

Page 171

4-16Debugger General Information4BH (Bootstrap and Halt)BH reads an operating system or control program from a specified device into memory, and then

Page 172

Disk I/O Support4-174A command packet for one type of controller module usually does not have the same format as a command packet for a different type

Page 173

4-18Debugger General Information4There are three ways to change the parameter tables: Disk I/O Error Codes167Bug returns an error code if an attempted

Page 174

Network I/O Support4-194Network I/O SupportThe Network Boot Firmware provides the capability to boot the CPU through the ROM debugger using a network

Page 175

4-20Debugger General Information4RARP/ARP Protocol ModulesThe Reverse Address Resolution Protocol (RARP) basically consists of an identity-less node b

Page 176

Multiprocessor Support4-214Network I/O Error Codes167Bug returns an error code if an attempted network operation is unsuccessful. Multiprocessor Suppo

Commentaires sur ces manuels

Pas de commentaire