Table of Contents
Advertisement
Autoboot is controlled by parameters contained in the ENV command.
These parameters allow the selection of specific boot devices and files, and
allow programming of the Boot delay. Refer to the ENV command in
Appendix A for more details.
!
Although streaming tape can be used to autoboot, the
same power supply must be connected to the streaming
tape drive, controller, and the MVME162LX. At power-
Caution
up, the tape controller will position the streaming tape to
the load point where the volume ID can correctly be read
and used.
If, however, the MVME162LX loses power but the
controller does not, and the tape happens to be at the load
point, the sequences of commands required (attach and
rewind) cannot be given to the controller and autoboot will
not be successful.
ROMboot
As shipped from the factory, the 162Bug occupies an EPROM installed in
socket XU24. This leaves three sockets (XU21 - XU23) and the flash
available for your use. Contact your Motorola sales office for assistance.
This function is configured/enabled by the Environment (ENV) command
(refer to Appendix A) and executed at power-up (optionally also at reset)
or by the RB command assuming there is valid code in the memory devices
(or optionally elsewhere on the controller 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
2. Your routine must be located within the controller's Flash/PROM
http://www.mcg.mot.com/literature
change this to also respond to any reset).
memory map (but the ENV command can change this to any other
portion of the onboard memory, or even offboard VMEbus
memory).
ROMboot
3
3-7
Advertisement
Table of Contents
