Motorola MVME197LE manual Memory Maps, Interrupt Sources, Connectors, Processor Bus Memory Map

Page 29

Memory Maps

μsec, 64 μsec, 256 μsec, or infinite for the local peripheral bus. The local peripheral bus timer does not operate during VMEbus bound cycles. VMEbus bound cycles are timed by the VMEbus access timer and the VMEbus global timer.

1

Interrupt Sources

MVME197LE MPU interrupts are channeled through the BusSwitch. They may come from internal BusSwitch sources as well as from the PCCchip2 (IPL inputs to the BusSwitch), the VMEchip2 (XIPL inputs to the BusSwitch), and other external sources (PALINT and IRQ). The BusSwitch may also generate the non-maskable interrupt (NMI) signal to the MPU from the ABORT push- button switch. Refer to the BusSwitch, PCCchip2, and VMEchip2 chapters in the MVME197LE, MVME197DP, and MVME197SP Single Board Computers Programmer’s Reference Guide for more detailed information.

Connectors

The MVME197LE has two 64-position DIN connectors: P1 and P2. Connector P1 rows A, B, C, and connector P2 row B provide the VMEbus interconnection. Connector P2 rows A and C provide the interconnect to the SCSI bus, the serial ports, the Ethernet interface, and the Centronics printer. There is a 249-pin mezzanine connector (J2) with the MC88110 bus interface. This mezzanine connector is for other MVME197 module expansion. On the MVME197LE there is also a 20-pin general purpose connector (J1) which provides the interconnect to the LEDs and the reset and abort signals. This connector is different for the other modules in the MVME197 series. Refer to the board specific SIMVME197 Single Board Computer Support Information manual for detailed connector signal descriptions.

Memory Maps

There are three points of view for the memory maps: 1) the mapping of all resources as viewed by the Processor Bus (MC88110 bus), 2) the mapping of onboard/off-board resources as viewed from the Local Peripheral Bus (MC68040 compatible bus), and 3) the mapping of onboard resources as viewed by VMEbus Masters (VMEbus memory map).

Processor Bus Memory Map

Care should be taken, since all three maps are programmable. It is recommended that direct mapping from the Processor Bus to the Local Peripheral Bus be used.

MVME197LEIG/D1

1-13

Image 29
Contents MVME197LE Restricted Rights Legend Document Terminology PrefaceBIT Document Title Motorola Publication Number Related DocumentationPage 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 Overview IntroductionRequirements Features MVME197LE Specifications SpecificationsBlock Diagram Block Diagram MC88110 Address Data MUX Address Bus Data Bus 256 BusSwitchMezzanine Address Bus Memory ArrayFunctional Description Front Panel Switches and IndicatorsMC88110 MPU Data Bus StructureFlash Memory Onboard DramVMEbus Interface Battery Backup RAM and ClockInterfaces Serial Port InterfaceEthernet Interface Printer InterfaceScsi Termination Scsi InterfacePeripheral Resources Memory Maps ConnectorsInterrupt Sources Processor Bus Memory MapDramsize Processor Bus Memory MapLocal Devices Memory Map Address Range Devices Accessed Port SizeVMEbus Short I/O Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Memory Map Hardware Preparation Unpacking InstructionsHardware Preparation and Installation VMEbus Connector P1 Configuration Switch S1 General Information Configuration SwitchesSwitch S1 S1-1 to S1-8 OFF -- All Ones Factory Configuration Switch S6 Installation InstructionsMVME197LE Module Installation System Considerations MVME197LEIG/D1 Hardware Preparation and Installation Description of 197Bug Overview of M88000 Firmware197Bug Implementation Installation and Start-upComparison With M68000-Based Firmware Ote Terminal to make sure XON/XOFF handshaking is enabledAutoboot Network Boot ROMbootRestarting the System ResetBreak AbortMPU Clock Speed Calculation Memory RequirementsSYSFAIL* Assertion/Negation DEL Terminal Input/Output ControlDevice Probe Function Disk I/O SupportBlocks Versus Sectors Disk I/O via 197Bug Commands Dskcfig Disk I/O via 197Bug System CallsNetwork I/O Support Default 197Bug Controller and Device ParametersDisk I/O Error Codes Physical Layer Manager Ethernet Driver Bootp Protocol ModuleUDP/IP Protocol Modules RARP/ARP Protocol ModulesNetwork I/O Error Codes Network Boot Control ModuleMultiprocessor Support Multiprocessor Control Register Mpcr MethodMpar Gcsr Method Diagnostic FacilitiesDebugger General Information Debugger Entering Debugger Command LinesExpression as a Parameter Syntactic VariablesData Type Base Identifier Examples Offset Registers Address as a ParameterAddress Formats Port Numbers Entering and Debugging ProgramsPreserving The Debugger Operating Environment Calling System Utilities From User Programs197Bug Vector Table and Workspace Hardware FunctionsCPU/MPU Registers Floating Point SupportScientific Notation Single Precision RealDouble Precision Real Debugger Commands 197Bug Debugger Command SetNocm Noma Name Nioc RL Addrbhw Using the 197Bug Debugger Cnfg MI Configure Board Information BlockENV D Set Environment to Bug/Operating SystemENV Parameter and Options Default Meaning of Default Table A-1. ENV Command ParametersConfigure 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 Modules Supported DISK/TAPE Controller DataSingle Board Computers 7 Devices Disk/Tape Controller Default ConfigurationsMVME320 4 Devices MVME323 4 DevicesMVME328 14 Devices MVME327A 9 DevicesMVME350 1 Device IOT Parameter IOT Command Parameters for Supported Floppy TypesDisk/Tape Controller Data Network Controller Modules Supported Network Controller DataNetwork Controller Data Numerics SymbolsIN-2 IN-3 Nvram A-2 XON/XOFF Index
Related manuals
Manual 78 pages 27.46 Kb