Ote | Motorola MVME162 specification

Installation and Startup

4.Jumpers on headers J11 and J12 configure serial ports 1 and 2 to drive or receive clock signals provided by the TXC and RXC signal lines. The factory configures the module for asynchronous communication, that is, installs no jumpers. Refer to Chapter 2 if your application requires configuring ports 1 and 2 for synchronous communication.

5.If using a PROM version of the 162Bug, install the PROM device in socket U47. Be sure that the physical chip orientation is correct, that is, with the flatted corner of the PROM aligned with the corresponding portion of the PROM socket on the MVME162 module.

3

Check the jumper installation on header J21 for correct size. Connect pins 1 and 2 on J21 for 27C080 devices, or pins 2 and 3 for 27C040 devices. The factory default is 2 and 3.

Remove the jumper on J22 pins 9 and 10.

6.Refer to the set-up procedure for your particular chassis or system for details concerning the installation of the MVME162.

7.Connect the terminal that is to be used as the 162Bug system console to the default debug EIA-232-D port at serial port 1 on the front panel of the MVME162 module. Refer to Chapter 2 for other connection options. Set up the terminal as follows:

–eight bits per character

–one stop bit per character

–parity disabled (no parity)

–baud rate 9600 baud (default baud rate of MVME162 ports at power- up)

After power-up, the baud rate of the debug port can be reconfigured by using the Port Format (PF) command of the 162Bug debugger.

			In order for high-baud rate serial communication between
N
	ote
	ote		162Bug and the terminal to work, the terminal must do some
			162Bug and the terminal to work, the terminal must do some
			form of handshaking. If the terminal being used does not do
			hardware handshaking via the CTS line, then it must do
			XON/XOFF handshaking. If you get garbled messages and
			missing characters, then you should check the terminal to
			make sure XON/XOFF handshaking is enabled.

8.If you want to connect devices (such as a host computer system and/or a serial printer) to the other EIA-232-D port connectors (marked SERIAL PORTS 2, 3, and 4 on the MVME712X transition module), connect the

MVME162IG/D2

3-5

Image 67

Motorola MVME162 manual Ote

Contents

MVME162IG/D2 MVME162 Restricted Rights Legend Preface Page Safety Summary Safety Depends On You Page Overview Introduction Document Title Motorola Publication Number Related Documentation Introduction MVME162 Embedded Controller Installation Guide Requirements Features MVME162 Specifications SpecificationsCharacteristics Specifications Special Considerations for Elevated Temperature Operation Manual Terminology MVME162 Block Diagram Block Diagram Functional Description Front Panel Switches and Indicators MC68xx040 Cache Data Bus StructureMC68040 or MC68LC040 MPU No-VMEbus-Interface Option Dram Options Memory OptionsSram Options About the Battery Eprom and Flash Battery Backed Up RAM and Clock MVME162 Serial Port VMEbus Interface and VMEchip2Interfaces Serial Communications Interface MVME162 Serial Port Optional LAN Ethernet Interface IndustryPack IP Interfaces Scsi Termination Optional Scsi Interface Local Resources Programmable Tick TimersWatchdog Timer Local Bus Timeout Local Bus Arbitration Priority ConnectorsMemory Maps Local Bus Arbiter Normal Address Range Local Bus Memory MapLocal Bus Memory Map MVME162 Embedded Controller Installation Guide Address Range Device Port Width Size Local Bus I/O Devices Memory Map MVME162 Embedded Controller Installation Guide VMEbus Memory Map VMEbus Accesses to the Local BusVMEbus Short I/O Memory Map Board Level Hardware Description Hardware Preparation Unpacking Instructions SIM Selection Hardware Preparation Serial Interface Module Part Numbers Configuration Part Number Model Standard System Controller Select Header J1 Installation of New SIM J12 Clock Select Header J12 for Serial Port Eprom Size Select Header J21 Sram Battery Backup Source Select Header J20 J22 General Purpose Readable Jumpers Header J22 IP Installation on the MVME162 Installation Instructions MVME162 Module Installation System Considerations MVME162 Embedded Controller Installation Guide MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 1 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 3 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 4 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 5 MVME162 EIA-232-D Connection Diagram, MVME712M Sheet 6 SIM07 MVME162 EIA-530 Connection Diagram Sheet 1 Hardware Preparation and Installation MVME162 EIA-530 Connection Diagram Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 1 MVME162 EIA-23-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 2 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 3 MVME162 EIA-232-D Connection Diagram, MVME712A/AM/-12/-13 Sheet 4 Hardware Preparation and Installation Description of 162Bug Overview of M68000 Firmware MVME162 Embedded Controller Installation Guide 162Bug Implementation Installation and Startup Debugger General Information Bit J22 Pins Description Ote Autoboot ROMboot Restarting the System Network Boot Abort ResetBreak SYSFAIL* Assertion/Negation Memory RequirementsMPU Clock Speed Calculation Terminal Input/Output Control DEL Blocks Versus Sectors Disk I/O Support IOP Physical I/O to Disk Disk I/O via 162Bug CommandsDevice Probe Function IOI Input/Output Inquiry IOC I/O Control BO Bootstrap Operating SystemBH Bootstrap and Halt Disk I/O via 162Bug System Calls Default 162Bug Controller and Device Parameters UDP/IP Protocol Modules Disk I/O Error CodesNetwork I/O Support Intel 82596 LAN Coprocessor Ethernet Driver RARP/ARP Protocol Modules Bootp Protocol ModuleNetwork Boot Control Module Network I/O Error Codes Multiprocessor Control Register Mpcr Method Multiprocessor Support Mpar Gcsr Method Diagnostic Facilities Manufacturing Test Process Debugger Entering Debugger Command Lines Italic strings Syntactic Variables Data Type Base Identifier Examples Expression as a ParameterString Numeric Value Literal Hexadecimal Address Formats Address as a ParameterExpression Result In Hex Format Example Description Debugger Address Parameter Formats Relative addresses are limited to 1MB 5 digits, regardless Offset RegistersRange of the closest offset register 162BugMD 1327CDI Port Numbers Calling System Utilities from User Programs Entering and Debugging ProgramsPreserving the Debugger Operating Environment Hardware Functions 162Bug Vector Table and Workspace Exception Vectors Used by 162Bug Exception Vectors Used by 162BugVector Exception 162Bug Facility Offset Using 162Bug Target Vector Table Creating a New Vector Table Buildx MOVEC.L VBR,A0 162Bug Generalized Exception Handler 162BugMD A7&30 Integer Data Types Floating Point SupportFloating Point Data Types Double Precision Real Single Precision RealExtended Precision Real Scientific Notation Packed Decimal Real Debugger Commands 162Bug Debugger Command Set 162Bug Debugger Command Set Norb Cnfg IM Configure Board Information Block Configure and Environment Commands ENV D Set Environment to Bug/Operating System ENV Parameter and Options Default Meaning of Default Table A-1. ENV Command Parameters Ffdffffc Nvram Memory Requirements section Base Address of Dynamic Memory Slave Ending Address #1 Master Starting Address #1 Master Starting Address #3 Table A-1. ENV Command Parameters Bits Register Address Configuring the IndustryPacks FFFBC016 First Second Controller Type Disk/Tape Controller Modules SupportedAddress Controller LUN Address Device LUN Device Type Disk/Tape Controller Default ConfigurationsCisc Embedded Controllers -- 7 Devices MVME320 -- 4 Devices MVME327A -- 9 Devices MVME323 -- 4 Devices MVME350 -- 1 Device MVME328 -- 14 Devices IOT Command Parameters for Supported Floppy Types Disk/Tape Controller Data Controller Interface Type Network Controller Modules SupportedAddress Type Network Controller Data Numerics Symbols IN-2 IN-3 IN-4 IN-5 IN-6 Scsi LED Sysfail