Motorola MVME187 User Manual
4-6
Debugger General Information
4
Starting Up 187Bug
1. Verify that the MVME187 is properly installed and operating
.
2. Power up the system. 187Bug executes some self-checks and
displays the debugger prompt
187-Bug>
(if 187Bug is in
Board Mode). However, if the ENV command (Appendix A)
has put 187Bug in System Mode, the system performs a
selftest and tries to autoboot. Refer to the ENV and MENU
commands listed in
has put 187Bug in System Mode, the system performs a
selftest and tries to autoboot. Refer to the ENV and MENU
commands listed in
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.
fault is encountered. If possible, an appropriate message is
displayed, and control then returns to the menu.
Autoboot
Autoboot is a software routine that is contained in the 187Bug
EPROMs to provide an independent mechanism for booting an
operating system.
EPROMs to provide an independent mechanism for booting an
operating system.
Autoboot Sequence
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.
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).
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:
displays the following message:
"Autoboot in progress... To abort hit <BREAK>"