Table of Contents
Advertisement
Debugger General Information
Starting Up 167Bug
4
Autoboot
Autoboot Sequence
4-6
1. Verify that the MVME167 is properly installed and operating
as described in
2. Power up the system. 167Bug executes some self-checks and
displays the debugger prompt
Board Mode). However, if the ENV command (Appendix A)
has put 167Bug in System Mode, the system performs a
selftest and tries to autoboot. Refer to the ENV and MENU
commands listed in Table 5 -1.
If the confidence test fails, the test is aborted when the first
fault is encountered. If possible, an appropriate message is
displayed, and control then returns to the menu.
Autoboot is a software routine that is contained in the 167Bug
EPROMs to provide an independent mechanism for booting an
operating system.
1. The autoboot routine automatically scans for controllers and
devices in a specified sequence until a valid bootable device
containing a boot media is found or the list is exhausted.
2. If a valid bootable device is found, a boot from that device is
started.
The controller scanning sequence goes from the lowest
controller Logical Unit Number (LUN) detected to the
highest LUN detected. (Controllers, devices, and their LUNs
are listed in Appendix B).
3. At powerup, Autoboot is enabled, and if the drive and
controller numbers encountered are valid, the system console
displays the following message:
"Autoboot in progress... To abort hit <BREAK>"
Table 3-1 on page
3-2.
167-Bug>
(if 167Bug is in
Hide quick links:
Advertisement
Table of Contents
