Manuals / Motorola / Computer Equipment / Laptop

Motorola MVME177 manual Signal Adaptations, Sample Conﬁgurations

Models: MVME177

1 171

Download 171 pages 43 Kb

Page 76

A

EIA-232-D Interconnections

Signal Adaptations

One set of handshaking signals frequently implemented are RTS and CTS. CTS is used in many systems to inhibit transmission until the signal is high. In the modem application, RTS is turned around and returned as CTS after 150 microseconds. RTS is programmable in some systems to work with the older type 202 modem (half duplex). CTS is used in some systems to provide flow control to avoid buffer overflow. This is not possible if modems are used. It is usually necessary to make CTS high by connecting it to RTS or to some source of +12 volts such as the resistors shown in Figure A-1. CTS is also frequently jumpered to an MC1488 gate which has its inputs grounded (the gate is provided for this purpose).

Another signal used in many systems is DCD. The original purpose of this signal was to inform the system that the carrier tone from the distant modem was being received. This signal is frequently used by the software to display a message like CARRIER NOT PRESENT to help the user to diagnose failure to communicate. Obviously, if the system is designed properly to use this signal and is not connected to a modem, the signal must be provided by a pullup resistor or gate as described above (see Figure A-1).

Many modems expect a DTR high signal and issue a DSR response. These signals are used by software to help prompt the operator about possible causes of trouble. The DTR signal is sometimes used to disconnect the phone circuit in preparation for another automatic call. These signals are necessary in order to communicate with all possible modems (see Figure A-1).

Sample Conﬁgurations

Figure A-1 is a good minimum configuration that almost always works. If the CTS and DCD signals are not received from the modem, the jumpers can be moved to artificially provide the needed signal.

A-4

Image 76

Motorola MVME177 manual Signal Adaptations, Sample Conﬁgurations

Contents

Single Board Computer Installation and Use Manual MVME177Restricted Rights Legend Preface Page This equipment. Use extreme caution when handling, testing AdjustingPage Contents Page Page Flash Fill Test B-48Flash Patterns Test B-49 List of Figures List of Tables Introduction Model DesignationsMVME177 Model Designations Model Number Speed Major DifferencesMVME177 Features FeaturesFeature Description Speciﬁcations Cooling RequirementsCharacteristics SpeciÞcations MVME177 SpeciﬁcationsGeneral Description FCC ComplianceMVME712AM Bbram Equipment Required MVME712M MVME712A MVME712AM MVME712BRelated Documentation System V/68Motorola Document Title NumberSupport Information Manual Terminology Hardware Preparation and Installation Unpacking InstructionsStart-up Overview Overview of Start-up ProcedureWhat you will need to do Refer to Appears You may also wish to obtainInitialize the clock Examine and/or changeHardware Preparation MVME177 Switches, Headers, Connectors, Polyswitches LEDs Conﬁguring MVME177 Headers Header Number Description ConÞguration Jumpers1MB Eprom Header Number Description ConÞguration MVME177 Header NotesDo not remove all jumpers from J2. This may Disable the Sram Setup Instructions Bit J1 Pins Description MVME177 Module Installation Instructions MVME177 Module Installation Instructions Hardware Preparation and Installation System Considerations Hardware Preparation and Installation MVME177 Module Installation Instructions Hardware Preparation and Installation Controls and Indicators Abort Switch S1Reset Switch S2 Front Panel Indicators DS1 DS4 Local Bus Memory Map Memory MapsNormal Address Range Local Bus Memory Map Range Devices Accessed Port Size InhibitSoftware Address Address Range Devices Accessed Port Size Local I/O Devices Memory Map$FFF77000 $FFF77FFF Reserved Software Initialization Local Reset OperationMulti-MPU Programming Considerations Sysreset Operating Instructions MVME177 Functional Description Functional Description IntroductionData Bus Structure MPU Block ScsiFlash Memory and Eprom MC68060 MPUFlash Memory Eprom and Flash Control and Conﬁguration Jumper or Control Bit Control Condition Memory ConÞgurationEprom Sram Do not short circuit Onboard Dram Battery Backed Up RAM and Clock VMEbus Interface InterfacesSerial Port Interface RXD CTS DCD TXD RTS DTRTXD RTS DTR Parallel Port Interface Ethernet Interface Scsi Interface Local ResourcesScsi Termination Watchdog Timer Programmable Tick TimersSoftware-Programmable Hardware Interrupts Module Identiﬁcation Timing PerformanceLocal Bus Time-out Local Bus to Dram Cycle TimesROM Cycle Times Scsi TransfersRemote Status and Control LAN DMA TransfersAEIA-232-D Interconnections Pin Signal Number Mnemonic Signal Name and Description Table A-1. EIA-232-D InterconnectionsLevels of Implementation Number Mnemonic Signal Name and DescriptionPin Signal Adaptations Sample ConﬁgurationsFigure A-1. Middle-of-the-Road EIA-232-D Conﬁguration Figure A-2. Minimum EIA-232-D Connection Proper Grounding EIA-232-D Interconnections Overview of M68000 Firmware Description of 177BugDebugger General Information Autoboot 177Bug ImplementationAutoboot in progress... To abort hit Break ROMboot Network Boot Restarting the System Reset AbortBreak SYSFAIL* Assertion/Negation MPU Clock Speed CalculationMemory Requirements Terminal Input/Output Control Disk I/O Support Blocks Versus SectorsDebugger General Information Device Probe Function IOC IOP IOT MAR MAWDisk I/O via 177Bug Commands IOI Input/Output Inquiry IOP Physical I/O to DiskBO Bootstrap Operating System BH Bootstrap and HaltIOT I/O Teach IOC I/O ControlDskcfig Disk I/O Error Codes Default 177Bug Controller and Device ParametersNetwork I/O Support Intel 82596 LAN Coprocessor Ethernet Driver UDP/IP Protocol ModulesRARP/ARP Protocol Modules Bootp Protocol ModuleTftp Protocol Module Network Boot Control Module Network I/O Error CodesMultiprocessor Support Multiprocessor Control Register Mpcr MethodStatus codes that may be set by the bus master are Gcsr Method Diagnostic Facilities Table B-1. Diagnostic Test Groups Test Group DescriptionUsing the 177Bug Debugger Entering Debugger Command LinesSyntactic Variables Boldface stringsExpression as a Parameter Data Type Base IdentiÞer ExamplesString Numeric Value Literal Expression Result In HexAddress Formats Address as a ParameterTable B-2. Debugger Address Parameter Formats Offset Registers 177BugMD 1327CDI Port Numbers Entering and Debugging Programs IOP177Bug Vector Table and Workspace Hardware Functions Exception Vectors Used by 177BugTable B-3. Exception Vectors Used by 177Bug Vector Offset Exception 177Bug FacilityUsing 177Bug Target Vector Table Creating a New Vector Table Except SUBQ.L 177Bug Generalized Exception Handler 177BugMD A7&30 Integer Data Types Floating Point SupportFloating Point Data Types Single Precision Real This format would appear in memory asExtended Precision Real Double Precision RealPacked Decimal Real Additions to Flash Commands Scientiﬁc NotationFlash Test Conﬁguration Acceptable Entries Erase TestFlash Fill Test Diagflash eraseFlash Patterns Test Diagflash fillDefault Flash Test Conﬁguration Figure B-1. Three Possible Mapping OptionsSflash Command Sflashl Pflash ff800000 ff9fffff ffa00000 177Bug Debugger Command Set Table B-4. Debugger Commands Command Command Line Mnemonic Title SyntaxBI Range B W L Cnfg I MENV D IOI CLNiot H a R n aPA n Nopa nOr SET nC VER EDebugger General Information Disk/Tape Controller Modules Supported First Second Controller TypeDisk/Tape Controller Default Conﬁgurations Controller Address DeviceDevice Type Controller DeviceMVME323 -- Four Devices ControllerMVME328 -- Fourteen Devices Controller LUN Address Device LUN Device TypeIOT Command Parameters for Supported Floppy Types Floppy Types and Formats IOT ParameterOther Commands Conﬁgure Board Information BlockConfigure and Environment Commands Set Environment to Bug/Operating System ENV D= EFFFFFFF? Master Starting Address #2 = 00000000? Table D-1. ENV Command Parameters ENV Parameter and Options Default Meaning of DefaultLUN Network Auto Boot Memory Search Starting Address $02 refer to the Memory Requirements Accessible by the VMEbus. Default is Slave Ending Address #2 Master Ending Address #3 Short I/O VMEbus A16 Control ENetwork Controller Data Network Controller Modules SupportedController Interface Type Clun DlunTable F-1. Basic Troubleshooting Steps Condition Possible Problem Try ThisCTRL-Q Set mmddyyhhmm CR Envd CRSt CR Env CRDe CR Index Index IN-7 IN-8 IN-9 IN-10 XON/XOFF