Motorola MVME197LE manual Diagnostic Facilities, Gcsr Method

Page 59

Diagnostic Facilities

GCSR Method

A remote processor can initiate program execution in the local MVME197LE dual-port RAM by issuing a remote GO command using the VMEchip2 Global Control and Status Register (GCSR). The remote processor places the MVME197LE execution address in general purpose registers 0 and 1 (GPCSR0 and GPCSR1). The remote processor then sets bit 8 (SIG0) of the VMEchip2 LM/SIG register. This causes the MVME197LE to install breakpoints and begin execution. The result is identical to the MPCR method (with status code B) described in the previous section.

The GCSR registers are accessed in the VMEbus short I/O space. Each general purpose register is two bytes wide, occurring at an even address. The general purpose register number 0 is at an offset of $8 (local peripheral bus) or $4 (VMEbus) from the start of the GCSR registers. The local peripheral bus base address for the GCSR is $FFF40100. The VMEbus base address for the GCSR depends on the group select value and the board select value programmed in the Local Control and Status Registers (LCSR) of the MVME197LE. The execution address is formed by reading the GCSR general purpose registers in the following manner:

GPCSR0

used as the upper 16 bits of the address

GPCSR1

used as the lower 16 bits of the address

The address appears as:

3

GPCVSR0

GPCSR1

Diagnostic Facilities

Included in the 197Bug package is a complete set of hardware diagnostics intended for testing and troubleshooting of the MVME197LE (refer to the MVME197 Single Board Computer Diagnostic Firmware User’s Manual). In order to use the diagnostics, the user must switch directories to the diagnostic directory. If in the debugger directory, the user can switch to the diagnostic directory by entering the debugger command Switch Directories (SD). The diagnostic prompt (“197-Diag>”) should appear. Refer to the MVME197 Single Board Computer Diagnostic Firmware User’s Manual for complete descriptions of the diagnostic routines available and instructions on how to invoke them. Note that some diagnostics depend on restart defaults that are set up only in a particular restart mode. Refer to the documentation on a particular diagnostic for the correct mode.

MVME197LEIG/D1

3-17

Image 59
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 Memory Array Bus Data Bus 256 BusSwitchMC88110 Address Data MUX Address Mezzanine Address BusFunctional Description Front Panel Switches and IndicatorsOnboard Dram Data Bus StructureMC88110 MPU Flash MemorySerial Port Interface Battery Backup RAM and ClockVMEbus Interface InterfacesEthernet Interface Printer InterfaceScsi Termination Scsi InterfacePeripheral Resources Processor Bus Memory Map ConnectorsMemory Maps Interrupt SourcesDramsize 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 RARP/ARP Protocol Modules Bootp Protocol ModulePhysical Layer Manager Ethernet Driver UDP/IP Protocol ModulesMultiprocessor Control Register Mpcr Method Network Boot Control ModuleNetwork I/O Error Codes Multiprocessor SupportMpar 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 ProgramsHardware Functions Calling System Utilities From User ProgramsPreserving The Debugger Operating Environment 197Bug Vector Table and WorkspaceCPU/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 DataMVME323 4 Devices Disk/Tape Controller Default ConfigurationsSingle Board Computers 7 Devices MVME320 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