Memory Requirements | Motorola MVME197LE manual

Debugger General Information

SYSFAIL* Assertion/Negation

		Upon a reset/power up condition the debugger asserts the VMEbus SYSFAIL*
		line (refer to the VMEbus specification). SYSFAIL* stays asserted if any of the
	3
		following has occurred:
		❏	confidence test failure

		❏	NVRAM checksum error

❏ NVRAM low battery condition ❏ local memory configuration status

❏ self test (if system mode) has completed with error ❏ MPU clock speed calculation failure

After debugger initialization is done and any of the above situations has not occurred, the SYSFAIL* line is negated. This indicates to the user or VMEbus masters the state of the debugger. In a multi-computer configuration, other VMEbus masters could view the pertinent control and status registers to determine which CPU is asserting SYSFAIL*. SYSFAIL* assertion/negation is also affected by the ENV command. Refer to Appendix A.

MPU Clock Speed Calculation

The clock speed of the microprocessor is calculated and checked against a user definable parameter housed in NVRAM (refer to the ENV command). If the check fails, a warning message is displayed. The calculated clock speed is also checked against known clock speeds and tolerances.

Memory Requirements

The program portion of 197Bug is approximately 1 megabyte of code, consisting of download, debugger, and diagnostic packages and contained entirely in the flash memory. The flash memory on the MVME197LE is mapped starting at location $FF800000.

197Bug requires a minimum of 64KB of contiguous read/write memory to operate.

The ENV command controls where this block of memory is located. Regardless of where the onboard RAM is located, the first 64KB is used for 197Bug stack and static variable space and the rest is reserved as user space. Whenever the MVME197LE is reset, the target IP is initialized to the address corresponding to the beginning of the user space, and the target stack pointers are initialized to addresses within the user space, with the target Pseudo Stack Pointer (R31) set to the top of the user space.

3-8	Installation Guide

Image 50

Motorola MVME197LE manual Memory Requirements, SYSFAIL* Assertion/Negation, MPU Clock Speed Calculation

Contents

MVME197LE Restricted Rights Legend Preface Document Terminology BIT 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 Overview Requirements Features MVME197LE Specifications SpecificationsBlock Diagram Block Diagram Mezzanine Address Bus Bus Data Bus 256 BusSwitchMC88110 Address Data MUX Address Memory Array Front Panel Switches and Indicators Functional Description Flash Memory Data Bus StructureMC88110 MPU Onboard Dram Interfaces Battery Backup RAM and ClockVMEbus Interface Serial Port Interface Printer Interface Ethernet Interface Scsi Interface Scsi Termination Peripheral Resources Interrupt Sources ConnectorsMemory Maps Processor Bus Memory Map Processor Bus Memory Map Dramsize Address Range Devices Accessed Port Size Local Devices Memory Map VMEbus Short I/O Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Memory Map Unpacking Instructions Hardware Preparation Hardware Preparation and Installation VMEbus Connector P1 Configuration Switch S1 General Information Configuration SwitchesSwitch S1 S1-1 to S1-8 OFF -- All Ones Factory Configuration Installation Instructions Switch S6 MVME197LE Module Installation System Considerations MVME197LEIG/D1 Hardware Preparation and Installation Overview of M88000 Firmware Description of 197Bug 197Bug Implementation Installation and Start-upComparison With M68000-Based Firmware Terminal to make sure XON/XOFF handshaking is enabled Ote Autoboot ROMboot Network Boot Reset Restarting the System Abort Break MPU Clock Speed Calculation Memory RequirementsSYSFAIL* Assertion/Negation Terminal Input/Output Control DEL Device Probe Function Disk I/O SupportBlocks Versus Sectors Disk I/O via 197Bug Commands Disk I/O via 197Bug System Calls Dskcfig Network I/O Support Default 197Bug Controller and Device ParametersDisk I/O Error Codes UDP/IP Protocol Modules Bootp Protocol ModulePhysical Layer Manager Ethernet Driver RARP/ARP Protocol Modules Multiprocessor Support Network Boot Control ModuleNetwork I/O Error Codes Multiprocessor Control Register Mpcr Method Mpar Diagnostic Facilities Gcsr Method Debugger General Information Entering Debugger Command Lines Debugger Syntactic Variables Expression as a Parameter Data Type Base Identifier Examples Offset Registers Address as a ParameterAddress Formats Entering and Debugging Programs Port Numbers 197Bug Vector Table and Workspace Calling System Utilities From User ProgramsPreserving The Debugger Operating Environment Hardware Functions Floating Point Support CPU/MPU Registers Scientific Notation Single Precision RealDouble Precision Real 197Bug Debugger Command Set Debugger Commands Nocm Noma Name Nioc RL Addrbhw Using the 197Bug Debugger Configure Board Information Block Cnfg MI Set Environment to Bug/Operating System ENV D Table A-1. ENV Command Parameters ENV Parameter and Options Default Meaning of Default Configure 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 Supported MVME320 4 Devices Disk/Tape Controller Default ConfigurationsSingle Board Computers 7 Devices MVME323 4 Devices MVME327A 9 Devices MVME328 14 Devices MVME350 1 Device IOT Command Parameters for Supported Floppy Types IOT Parameter Disk/Tape Controller Data Network Controller Data Network Controller Modules Supported Network Controller Data Symbols Numerics IN-2 IN-3 Nvram A-2 XON/XOFF Index