Motorola MVME197LE manual Overview of M88000 Firmware, Description of 197Bug

Page 43

DEBUGGER GENERAL INFORMATION

3

Overview of M88000 Firmware

The firmware for the M88000-based (88K) series of board and system level products has a common genealogy, deriving from the BUG firmware currently used on all Motorola M68000-based (68K) CPU modules. The M88000 firmware family provides a high degree of functionality and user friendliness, and yet stresses portability and ease of maintenance. This member of the M88000 firmware family is implemented on the MVME197LE Single Board Computer, and is known as the MVME197BUG, or just 197Bug.

Description of 197Bug

The 197Bug package, MVME197BUG, is a powerful evaluation and debugging tool for systems built around the MVME197 series of RISC-based microcomputers. Facilities are available for loading and executing user programs under complete operator control for system evaluation. 197Bug includes commands for display and modification of memory, breakpoint and tracing capabilities, a powerful assembler/disassembler useful for patching programs, and a self-test at power-up feature which verifies the integrity of the system. Various 197Bug routines that handle I/O, data conversion, and string functions are available to user programs through the TRAP #496 handler. The TRAP #496 handler is accessible through any of the trap exception commands TB0, TB1, TBND, and TCND, with trap vector #496.

197Bug consists of three parts:

❏A command-driven user-interactive software debugger, described in a later chapter (Using the 197Bug Debugger) and hereafter referred to as “the debugger”.

❏A command-driven diagnostic package for the MVME197LE hardware, described in the MVME197BUG 197Bug Diagnostic Firmware User’s Manual and hereafter referred to as “the diagnostics”.

❏A user interface which accepts commands from the system console terminal.

When using 197Bug, the user operates out of either the debugger directory or the diagnostic directory. If the user is in the debugger directory, then the debugger prompt “197-Bug>” is displayed and the user has all of the debugger commands at his or her disposal. If in the diagnostic directory, then

MVME197LEIG/D13-1

Image 43

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 Block Diagram SpecificationsMVME197LE Specifications 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 Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Short I/O Memory Map Hardware Preparation Unpacking InstructionsHardware Preparation and Installation VMEbus Connector P1 Switch S1 Configuration SwitchesConfiguration Switch S1 General Information 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 FirmwareComparison With M68000-Based Firmware Installation and Start-up197Bug Implementation Ote Terminal to make sure XON/XOFF handshaking is enabledAutoboot Network Boot ROMbootRestarting the System ResetBreak AbortSYSFAIL* Assertion/Negation Memory RequirementsMPU Clock Speed Calculation DEL Terminal Input/Output ControlBlocks Versus Sectors Disk I/O SupportDevice Probe Function Disk I/O via 197Bug Commands Dskcfig Disk I/O via 197Bug System CallsDisk I/O Error Codes Default 197Bug Controller and Device ParametersNetwork I/O Support 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 Address Formats Address as a ParameterOffset Registers 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 SupportDouble Precision Real Single Precision RealScientific Notation 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