Motorola MVME197LE manual Entering Debugger Command Lines

Page 61

USING THE 197Bug

DEBUGGER

4

Entering Debugger Command Lines

197Bug is command-driven and performs its various operations in response to user commands entered at the keyboard. When the debugger prompt (197- Bug>) appears on the terminal screen, then the debugger is ready to accept commands.

As the command line is entered, it is stored in an internal buffer. Execution begins only after the carriage return is entered, thus allowing the user to correct entry errors, if necessary, using the control characters described in the Debugger General Information chapter in this guide.

When a command is entered, the debugger executes the command and the prompt reappears. However, if the command entered causes execution of user target code, for example GO, then control may or may not return to the debugger, depending on what the user program does. For example, if a breakpoint has been specified, then control returns to the debugger when the breakpoint is encountered during execution of the user program. Alternately, the user program could return to the debugger by means of the TRAP #496 function “.RETURN”.

In general, a debugger command is made up of the following parts:

1.The command identifier (i.e., MD or md for the Memory Display command). Note that either upper- or lowercase is allowed.

2.A port number if the command is set up to work with more than one port.

3.At least one intervening space before the first argument.

4.Any required arguments, as specified by command.

5.An option field, set off by a semicolon (;) to specify conditions other than the default conditions of the command.

MVME197LEIG/D14-1

Image 61
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 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 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 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 Address Formats Address as a ParameterOffset Registers 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 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 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