HIMA Z7127線纜，Z7127使用產品
每當MVME187復位時，目標IP初始化為對應于用戶空間開頭的地址，以及目標堆棧指針初始化為用戶內的地址空間，目標偽堆棧指針（R31）設置為用戶空間。
通電或重置時，地址為$FFE0C000的所有8KB內存通過$FFE0DFFF，187Bug首字母完全改變了堆棧啟動和重新啟動187Bug
本節涵蓋以下任務：
? 啟動187Bug? 自動腳印? 羅姆布特
? 網絡引導? 重新啟動系統
驗證MVME187是否正確安裝和運行如第3-2頁表3-1所述。
HIMA Z7127線纜2、接通系統電源。187Bug執行一些自檢并顯示調試器提示187 Bug>（如果187Bug在電路板模式）。但是，如果ENV命令（附錄A）將187Bug置于系統模式，系統執行自檢并嘗試自動啟動。參考環境和菜單表5-1中列出的命令。
如果置信度測試失敗，當第一個遇到故障。如果可能，請發送適當的消息顯示，然后控件返回菜單。自動腳印Autoboot是187Bug中包含的一個軟件例程EPROM提供了一種獨立的啟動機制操作系統。自動啟動序列1.autoboot例程自動掃描控制器和在指定序列中的設備，直到有效的可引導設備找到包含啟動介質或列表已用盡。
起動。控制器掃描順序從最低開始檢測到的控制器邏輯單元號（LUN）檢測到最高的LUN。（控制器、設備及其LUN）見附錄B）。
3.通電時，Autoboot啟用，如果驅動器遇到的控制器編號有效，系統控制臺顯示以下消息：
Whenever the MVME187 is reset, the target IP is initialized to the
address corresponding to the beginning of the user space, and the
target stack pointers are initialized to addresses within the user
space, with the target Pseudo Stack Pointer (R31) set to the top of
the user space.
At power up or reset, all 8KB of memory at addresses $FFE0C000
through $FFE0DFFF is completely changed by the 187Bug initial
stack.
Booting and Restarting 187Bug
This section covers the following tasks:
? Starting up 187Bug
? Autoboot
? ROMboot
? Network boot
? Restarting the systemStarting Up 187Bug
1. Verify that the MVME187 is properly installed and operating
as described in Table 3-1 on page 3-2.
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 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
Autoboot is a software routine that is contained in the 187Bug
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.
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:
