Motorola MVME197LE Calling System Utilities From User Programs, 197Bug Vector Table and Workspace

Page 66

Using the 197Bug Debugger

Other ways are by reading in the program from disk, using one of the disk commands (BO, BH, IOP), or by reading the program as a file from a remote computer on a network, using one of the network commands, such as NIOP. Once the object code has been loaded into memory, the user can set breakpoints if desired and run the code or trace through it.

Calling System Utilities From User Programs

4

A convenient way of doing character input/output and many other useful operations has been provided so that the user does not have to write these routines into the target code. The user has access to various 197Bug routines via one of the MC88110 TRAP instructions, using vector #496. Refer to the MVME197BUG 197Bug Debugging Package User’s Manual for details on the various TRAP #496 utilities available and how to invoke them from within a user program.

Preserving The Debugger Operating Environment

This section explains how to avoid contaminating the operating environment of the debugger. 197Bug uses certain of the MVME197LE onboard resources and also off-board system memory to contain temporary variables, exception vectors, etc. If the user disturbs resources upon which 197Bug depends, then the debugger may function unreliably or not at all.

197Bug Vector Table and Workspace

The debugger and diagnostic firmware resides in the FLASH memory. The first 64KB of RAM is also used by the debugger for storage of the Vector Table, executable code, variables, and stack.

Hardware Functions

The only hardware resources used by the debugger are the EIA-232-D ports, which are initialized to interface to the debug terminal. If these ports are reprogrammed, the terminal characteristics must be modified to suit, or the ports should be restored to the debugger-set characteristics prior to reinvoking the debugger.

Exception Vectors Used by 197Bug

The top 16 MC88110 exception vectors (i.e., #496 to 511 inclusive) are reserved for use by the debugger.

4-6	Installation Guide

Image 66

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 Specifications Block DiagramMVME197LE Specifications Block Diagram Mezzanine Address Bus Bus Data Bus 256 BusSwitchMC88110 Address Data MUX Address Memory ArrayFront Panel Switches and Indicators Functional DescriptionFlash Memory Data Bus StructureMC88110 MPU Onboard DramInterfaces Battery Backup RAM and ClockVMEbus Interface Serial Port InterfacePrinter Interface Ethernet InterfaceScsi Interface Scsi TerminationPeripheral Resources Interrupt Sources ConnectorsMemory Maps Processor Bus Memory MapProcessor Bus Memory Map DramsizeAddress Range Devices Accessed Port Size Local Devices Memory MapVMEbus Accesses to the Local Peripheral Bus VMEbus Memory MapVMEbus Short I/O Memory Map Unpacking Instructions Hardware PreparationHardware Preparation and Installation VMEbus Connector P1 Configuration Switches Switch S1Configuration 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 197BugInstallation and Start-up Comparison With M68000-Based Firmware197Bug Implementation Terminal to make sure XON/XOFF handshaking is enabled OteAutoboot ROMboot Network BootReset Restarting the SystemAbort BreakMemory Requirements SYSFAIL* Assertion/NegationMPU Clock Speed Calculation Terminal Input/Output Control DELDisk I/O Support Blocks Versus SectorsDevice Probe Function Disk I/O via 197Bug Commands Disk I/O via 197Bug System Calls DskcfigDefault 197Bug Controller and Device Parameters Disk I/O Error CodesNetwork I/O Support UDP/IP Protocol Modules Bootp Protocol ModulePhysical Layer Manager Ethernet Driver RARP/ARP Protocol ModulesMultiprocessor Support Network Boot Control ModuleNetwork I/O Error Codes 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 as a Parameter Address FormatsOffset Registers Entering and Debugging Programs Port Numbers197Bug Vector Table and Workspace Calling System Utilities From User ProgramsPreserving The Debugger Operating Environment Hardware FunctionsFloating Point Support CPU/MPU RegistersSingle Precision Real Double 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 SupportedMVME320 4 Devices Disk/Tape Controller Default ConfigurationsSingle Board Computers 7 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