Motorola MVME197LE manual System Considerations

Page 40

Hardware Preparation and Installation

provided in the MVME197LE, MVME197DP, and MVME197SP Single

2Board Computers Programmer’s Reference Guide). Some cable(s) are not provided with the MVME712X module and therefore, are made or provided by the user. (Motorola recommends using shielded cables for all connections to peripherals to minimize radiation). Connect the peripherals to the cable(s).

g.Install any other required VMEmodules in the system.

h.Replace the chassis cover.

i.Connect the power cable to the ac power source and turn the equipment power ON.

System Considerations

The MVME197LE needs to draw power from both connectors P1 and P2 of the VMEbus backplane. Connector P2 is also used for the upper 16 bits of data for 32-bit transfers, and for the upper 8 address lines for the extended addressing mode. The MVME197LE may not operate properly without its main board connected to connectors P1 and P2 of the VMEbus backplane.

Whether the MVME197LE operates as a VMEbus master or as a VMEbus slave, it is configured for 32 bits of address and for 32 bits of data (A32/D32). However, it handles A16 or A24 devices in certain address ranges. D8 and/or D16 devices in the system must be handled by software. Refer to the memory maps in the MVME197LE, MVME197DP, and MVME197SP Single Board Computers Programmer’s Reference Guide.

The MVME197LE contains shared onboard DRAM whose base address is software-selectable. Both the onboard processor and off-board VMEbus devices see this local DRAM at base physical address $00000000, as programmed by the MVME197Bug firmware. This may be changed, by software, to any other base address. Refer to the MVME197LE, MVME197DP, and MVME197SP Single Board Computers Programmer’s Reference Guide for details.

If the MVME197LE tries to access off-board resources in a non-existent location, and is not the system controller, and if the system does not have a global bus timeout, the MVME197LE waits forever for the VMEbus cycle to complete. This would cause the system to hang up. There is only one situation in which the system might lack this global bus timeout: when the MVME197LE is not the system controller and there is no global bus timeout elsewhere in the system.

2-8

Installation Guide

Image 40
Contents MVME197LE Restricted Rights Legend Preface Document TerminologyBIT Related Documentation Document Title Motorola Publication NumberPage Page Safety Summary Safety Depends on YOU Contents Hardware Preparation and Installation Using the 197Bug Debugger Appendix a Configure and Environment Commands List of Figures Xiv List of Tables Xvi Introduction OverviewRequirements Features Block Diagram SpecificationsMVME197LE Specifications Block Diagram Bus Data Bus 256 BusSwitch MC88110 Address Data MUX AddressMezzanine Address Bus Memory ArrayFront Panel Switches and Indicators Functional DescriptionData Bus Structure MC88110 MPUFlash Memory Onboard DramBattery Backup RAM and Clock VMEbus InterfaceInterfaces Serial Port InterfacePrinter Interface Ethernet InterfaceScsi Interface Scsi TerminationPeripheral Resources Connectors Memory MapsInterrupt Sources Processor Bus Memory MapProcessor Bus Memory Map DramsizeAddress Range Devices Accessed Port Size Local Devices Memory MapVMEbus Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Short I/O Memory Map Unpacking Instructions Hardware PreparationHardware Preparation and Installation VMEbus Connector P1 Switch S1 Configuration SwitchesConfiguration Switch S1 General Information S1-1 to S1-8 OFF -- All Ones Factory Configuration Installation Instructions Switch S6MVME197LE Module Installation System Considerations MVME197LEIG/D1 Hardware Preparation and Installation Overview of M88000 Firmware Description of 197BugComparison With M68000-Based Firmware Installation and Start-up197Bug Implementation Terminal to make sure XON/XOFF handshaking is enabled OteAutoboot ROMboot Network BootReset Restarting the SystemAbort BreakSYSFAIL* Assertion/Negation Memory RequirementsMPU Clock Speed Calculation Terminal Input/Output Control DELBlocks Versus Sectors Disk I/O SupportDevice Probe Function Disk I/O via 197Bug Commands Disk I/O via 197Bug System Calls DskcfigDisk I/O Error Codes Default 197Bug Controller and Device ParametersNetwork I/O Support Bootp Protocol Module Physical Layer Manager Ethernet DriverUDP/IP Protocol Modules RARP/ARP Protocol ModulesNetwork Boot Control Module Network I/O Error CodesMultiprocessor Support Multiprocessor Control Register Mpcr MethodMpar Diagnostic Facilities Gcsr MethodDebugger General Information Entering Debugger Command Lines DebuggerSyntactic Variables Expression as a ParameterData Type Base Identifier Examples Address Formats Address as a ParameterOffset Registers Entering and Debugging Programs Port NumbersCalling System Utilities From User Programs Preserving The Debugger Operating Environment197Bug Vector Table and Workspace Hardware FunctionsFloating Point Support CPU/MPU RegistersDouble Precision Real Single Precision RealScientific Notation 197Bug Debugger Command Set Debugger CommandsNocm Noma Name Nioc RL Addrbhw Using the 197Bug Debugger Configure Board Information Block Cnfg MISet Environment to Bug/Operating System ENV DTable A-1. ENV Command Parameters ENV Parameter and Options Default Meaning of DefaultConfigure and Environment Commands Ffbffffc Table A-1. ENV Command Parameters Memory Requirement s 01FFFFFF Table A-1. ENV Command Parameters Efffffff FF7FFFFF Table A-1. ENV Command Parameters Table A-1. ENV Command Parameters Table A-1. ENV Command Parameters DISK/TAPE Controller Data Disk/Tape Controller Modules SupportedDisk/Tape Controller Default Configurations Single Board Computers 7 DevicesMVME320 4 Devices MVME323 4 DevicesMVME327A 9 Devices MVME328 14 DevicesMVME350 1 Device IOT Command Parameters for Supported Floppy Types IOT ParameterDisk/Tape Controller Data Network Controller Data Network Controller Modules SupportedNetwork Controller Data Symbols NumericsIN-2 IN-3 Nvram A-2 XON/XOFF Index
Related manuals
Manual 78 pages 27.46 Kb