ICS TRIPLEX 9300/9852底板模塊
通電啟動(dòng)系統重置。重置也可以是通過(guò)MVME172LX前面板上的重置開(kāi)關(guān)斷言，或通過(guò)軟件
有關(guān)通過(guò)軟件重置MVME172LX板的詳細信息，請參閱MVME172嵌入式控制器程序員參考指南?！袄洹焙汀盁帷敝刂媚Ｊ蕉伎捎?。默認情況下，172Bug為在“冷”模式下。在冷復位過(guò)程中，發(fā)生整個(gè)系統初始化，就好像MVME172LX剛剛通電一樣。所有靜態(tài)變量（包括磁盤(pán)設備和控制器參數）恢復到其默認狀態(tài)。
ICS TRIPLEX 9300/9852底板模塊斷點(diǎn)表和偏移寄存器被清除。這個(gè)目標寄存器無(wú)效。輸入和輸出字符隊列是變明朗。車(chē)載設備（計時(shí)器、串行端口等）重置，兩個(gè)串行端口被重新配置為其默認狀態(tài)。在熱重置期間，172Bug變量和表也會(huì )保留作為目標狀態(tài)寄存器和斷點(diǎn)。注意，當MVME172LX冷復位時(shí)，172Bug運行在電路板模式下。使用環(huán)境（ENV）或菜單命令可以
使172Bug在系統模式下運行。有關(guān)詳細信息，請參閱第3章。如果處理器停止，或者172Bug環(huán)境丟失（向量表被破壞，堆棧損壞等）。中止通過(guò)按下并釋放MVME172LX前面板。當您在執行時(shí)調用中止時(shí)用戶(hù)程序（運行目標代碼），處理器狀態(tài)的快照是存儲在目標寄存器中。這一特性使中止最為頻繁適用于終止正在調試的用戶(hù)程序。例如，如果程序陷入循環(huán)，則應使用中止來(lái)重新獲得控制。目標PC、寄存器內容等有助于精確定位故障按下并釋放中止開(kāi)關(guān)會(huì )產(chǎn)生局部電路板條件如果啟用，可能會(huì )中斷處理器。目標寄存器，反映按下中止開(kāi)關(guān)時(shí)的機器狀態(tài)顯示在屏幕上。代碼中安裝的任何斷點(diǎn)都是已刪除，斷點(diǎn)表保持不變?？丶祷氐秸{試器。
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.
