Motorola MVME197LE manual Default 197Bug Controller and Device Parameters, Disk I/O Error Codes

Page 55

Disk I/O Support

Default 197Bug Controller and Device Parameters

197Bug initializes the parameter tables for a default configuration of controllers and devices (refer to Appendix B). If the system needs to be configured differently than this default configuration (for example, to use a 70MB Winchester drive where the default is a 40MB Winchester drive), then these tables must be changed.

3

There are three ways to change the parameter tables:

Using BO or BH. When the user invokes one of these commands, the configuration area of the disk is read and the parameters corresponding to that device are rewritten according to the parameter information contained in the configuration area. This is a temporary change. If a cold- start reset occurs, then the default parameter information is written back into the tables.

Using IOT. The user can use this command to manually reconfigure the parameter table for any controller and/or device that is different from the default. This is also a temporary change and is overwritten if a cold-start reset occurs.

Obtain the source. The user may change the configuration files and rebuild 197Bug so that it has different defaults. Changes made to the defaults are permanent until changed again.

Disk I/O Error Codes

197Bug returns an error code if an attempted disk operation is unsuccessful.

Network I/O Support

The Network Boot Firmware provides the capability to boot the CPU through the ROM debugger using a network (local Ethernet interface) as the boot device.

The booting process is executed in two distinct phases.

The first phase allows the diskless remote node to discover its network identity and the name of the file to be booted.

The second phase has the diskless remote node reading the boot file across the network into its memory.

The various modules (capabilities) and the dependencies of these modules that support the overall network boot function are described in the following paragraphs.

MVME197LEIG/D1

3-13

Image 55
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