ROMboot, Network Boot | Motorola MVME197LE specification

ROMboot

Caution

Although streaming tape can be used to autoboot, the same power supply must be connected to the streaming tape drive, controller, and the MVME197LE. At power-up, the tape controller will position the streaming tape to load point where the volume ID can correctly be read and used.

3

If, however, the MVME197LE loses power but the controller does not, and the tape happens not to be at load point, the sequences of commands required (attach and rewind) cannot be given to the controller and autoboot will not be successful.

ROMboot

This function is configured/enabled by the Environment (ENV) command and executed at power-up (optionally also at reset) or by the RB command assuming there is valid code in the flash memories (or optionally elsewhere on the module or VMEbus) to support it. If ROMboot code is installed, a user- written routine is given control (if the routine meets the format requirements). One use of ROMboot might be resetting SYSFAIL* on an unintelligent controller module. The NORB command disables the function.

For a user’s ROMboot module to gain control through the ROMboot linkage, four requirements must be met:

1.Power must have just been applied (but the ENV command can change this to also respond to any reset).

2.The user’s routine must be located within the MVME197LE ROM memory map (but the ENV command can change this to any other portion of the onboard memory, or even offboard VMEbus memory).

3.The ASCII string “BOOT” must be located within the specified memory range.

4.The user's routine must pass a checksum test, which ensures that this routine was really intended to receive control at power-up.

For complete details on how to use ROMboot, refer to the MVME197BUG 197Bug Debugging Package User’s Manual.

Network Boot

Network Auto Boot is a software routine contained in the 197Bug that provides a mechanism for booting an operating system using a network (local Ethernet interface) as the boot device. The Network Auto Boot routine

MVME197LEIG/D1

3-5

Image 47

Motorola MVME197LE manual ROMboot, Network Boot

Contents

MVME197LE Restricted Rights Legend Document Terminology Preface BIT 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 Introduction Requirements Features MVME197LE Specifications SpecificationsBlock Diagram Block Diagram Memory Array Bus Data Bus 256 BusSwitchMC88110 Address Data MUX Address Mezzanine Address Bus Functional Description Front Panel Switches and Indicators Onboard Dram Data Bus StructureMC88110 MPU Flash Memory Serial Port Interface Battery Backup RAM and ClockVMEbus Interface Interfaces Ethernet Interface Printer Interface Scsi Termination Scsi Interface Peripheral Resources Processor Bus Memory Map ConnectorsMemory Maps Interrupt Sources Dramsize Processor Bus Memory Map Local Devices Memory Map Address Range Devices Accessed Port Size VMEbus Short I/O Memory Map VMEbus Accesses to the Local Peripheral BusVMEbus Memory Map Hardware Preparation Unpacking Instructions Hardware 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 Instructions MVME197LE Module Installation System Considerations MVME197LEIG/D1 Hardware Preparation and Installation Description of 197Bug Overview of M88000 Firmware 197Bug Implementation Installation and Start-upComparison With M68000-Based Firmware Ote Terminal to make sure XON/XOFF handshaking is enabled Autoboot Network Boot ROMboot Restarting the System Reset Break Abort MPU Clock Speed Calculation Memory RequirementsSYSFAIL* Assertion/Negation DEL Terminal Input/Output Control Device Probe Function Disk I/O SupportBlocks Versus Sectors Disk I/O via 197Bug Commands Dskcfig Disk I/O via 197Bug System Calls Network I/O Support Default 197Bug Controller and Device ParametersDisk I/O Error Codes RARP/ARP Protocol Modules Bootp Protocol ModulePhysical Layer Manager Ethernet Driver UDP/IP Protocol Modules Multiprocessor Control Register Mpcr Method Network Boot Control ModuleNetwork I/O Error Codes Multiprocessor Support Mpar Gcsr Method Diagnostic Facilities Debugger General Information Debugger Entering Debugger Command Lines Expression as a Parameter Syntactic Variables Data Type Base Identifier Examples Offset Registers Address as a ParameterAddress Formats Port Numbers Entering and Debugging Programs Hardware Functions Calling System Utilities From User ProgramsPreserving The Debugger Operating Environment 197Bug Vector Table and Workspace CPU/MPU Registers Floating Point Support Scientific Notation Single Precision RealDouble Precision Real Debugger Commands 197Bug Debugger Command Set Nocm Noma Name Nioc RL Addrbhw Using the 197Bug Debugger Cnfg MI Configure Board Information Block ENV D Set Environment to Bug/Operating System ENV Parameter and Options Default Meaning of Default Table A-1. ENV Command Parameters Configure 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 Data MVME323 4 Devices Disk/Tape Controller Default ConfigurationsSingle Board Computers 7 Devices MVME320 4 Devices MVME328 14 Devices MVME327A 9 Devices MVME350 1 Device IOT Parameter IOT Command Parameters for Supported Floppy Types Disk/Tape Controller Data Network Controller Modules Supported Network Controller Data Network Controller Data Numerics Symbols IN-2 IN-3 Nvram A-2 XON/XOFF Index