Motorola MVME197LE manual Entering and Debugging Programs, Port Numbers

Page 65

Entering and Debugging Programs

Note

Relative addresses are limited to 1MB (5 digits), regardless of the range of the closest offset register.

Port Numbers

Some 197Bug commands give the user the option to choose the port to be used to input or output. Valid port numbers which may be used for these commands are:

1.MVME197LE EIA-232-D Debug (Terminal Port 0 or 00) (PORT 1 on the MVME197LE P2 connector). Sometimes known as the “console port”, it is used for interactive user input/output by default.

4

2.MVME197LE EIA-232-D (Terminal Port 1 or 01) (PORT 2 on the MVME197LE P2 connector). Sometimes known as the “host port”, this is the default for downloading, uploading, concurrent mode, and transparent modes.

Note

These logical port numbers (0 and 1) are shown in the pinouts of the MVME197 module as “SERIAL PORT 1” and “SERIAL PORT 2”, respectively. Physically, they are all part of connector P2.

Entering and Debugging Programs

There are various ways to enter a user program into system memory for execution. One way is to create the program using the Memory Modify (MM) command with the assembler/disassembler option. The program is entered by the user one source line at a time. After each source line is entered, it is assembled and the object code is loaded to memory. Refer to the MVME197BUG 197Bug Debugging Package User’s Manual for complete details of the 197Bug Assembler/Disassembler.

Another way to enter a program is to download an object file from a host system. The program must be in S-record format (described in the MVME197BUG 197Bug Debugging Package User’s Manual) and may have been assembled or compiled on the host system. Alternately, the program may have been previously created using the 197Bug MM command as outlined above and stored to the host using the Dump (DU) command. A communication link must exist between the host system and the MVME197 port 1. (Hardware configuration details are in the Installation and Start-upsection in the Debugger General Information chapter of this guide). The file is downloaded from the host to MVME197LE memory by the Load (LO) command.

MVME197LEIG/D1

4-5

Image 65
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 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 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 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 Offset Registers Address as a ParameterAddress Formats 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 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 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