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:
