ICS TRIPLEX 9300/9852底板模块
通电启动系统重置。重置也可以是通过MVME172LX前面板上的重置开关断言，或通过软件
有关通过软件重置MVME172LX板的详细信息，请参阅MVME172嵌入式控制器程序员参考指南。“冷”和“热”重置模式都可用。默认情况下，172Bug为在“冷”模式下。在冷复位过程中，发生整个系统初始化，就好像MVME172LX刚刚通电一样。所有静态变量（包括磁盘设备和控制器参数）恢复到其默认状态。
ICS TRIPLEX 9300/9852底板模块断点表和偏移寄存器被清除。这个目标寄存器无效。输入和输出字符队列是变明朗。车载设备（计时器、串行端口等）重置，两个串行端口被重新配置为其默认状态。在热重置期间，172Bug变量和表也会保留作为目标状态寄存器和断点。注意，当MVME172LX冷复位时，172Bug运行在电路板模式下。使用环境（ENV）或菜单命令可以
使172Bug在系统模式下运行。有关详细信息，请参阅第3章。如果处理器停止，或者172Bug环境丢失（向量表被破坏，堆栈损坏等）。中止通过按下并释放MVME172LX前面板。当您在执行时调用中止时用户程序（运行目标代码），处理器状态的快照是存储在目标寄存器中。这一特性使中止最为频繁适用于终止正在调试的用户程序。例如，如果程序陷入循环，则应使用中止来重新获得控制。目标PC、寄存器内容等有助于精确定位故障按下并释放中止开关会产生局部电路板条件如果启用，可能会中断处理器。目标寄存器，反映按下中止开关时的机器状态显示在屏幕上。代码中安装的任何断点都是已删除，断点表保持不变。控件返回到调试器。
Powering up the MVME172LX initiates a system reset. Resets can also be
asserted through the RESET switch on the MVME172LX front panel, or by
software.
For details on resetting the MVME172LX board through software, refer to
the MVME172 Embedded Controller Programmer’s Reference Guide.
Both “cold” and “warm” reset modes are available. By default, 172Bug is
in “cold” mode. During cold resets, a total system initialization takes place,
as if the MVME172LX had just been powered up. All static variables
(including disk device and controller parameters) are restored to their
default states. The breakpoint table and offset registers are cleared. The
target registers are invalidated. Input and output character queues are
cleared. Onboard devices (timer, serial ports, etc.) are reset, and the two
serial ports are reconfigured to their default state.
During warm resets, the 172Bug variables and tables are preserved, as well
as the target state registers and breakpoints.
Note that when the MVME172LX comes up in a cold reset, 172Bug runs
in Board mode. Using the Environment (ENV) or MENU commands can
make 172Bug run in System mode. Refer to Chapter 3 for specifics. You will need to reset your system if the processor ever halts, or if the
172Bug environment is ever lost (vector table is destroyed, stack
corrupted, etc.).
Abort
Aborts are invoked by pressing and releasing the ABORT switch on the
MVME172LX front panel. When you invoke an abort while executing a
user program (running target code), a snapshot of the processor state is
stored in the target registers. This characteristic makes aborts most
appropriate for terminating user programs that are being debugged.
If a program gets caught in a loop, for instance, aborts should be used to
regain control. The target PC, register contents, etc., help to pinpoint the
malfunction.
Pressing and releasing the ABORT switch generates a local board condition
which may interrupt the processor if enabled. The target registers,
reflecting the machine state at the time the ABORT switch was pressed, are
displayed on the screen. Any breakpoints installed in your code are
removed and the breakpoint table remains intact. Control is returned to the
debugger.
