FBM223模擬量輸出模塊,FOXBORO說明書在線閱讀
自動按指定順序掃描控制器和設(shè)備，直到找到包含引導(dǎo)媒體的有效可引導(dǎo)設(shè)備或列表已用盡。
如果找到有效的可引導(dǎo)設(shè)備，則啟動該設(shè)備的引導(dǎo)。這個控制器掃描順序從最低的控制器邏輯單元開始檢測到的數(shù)量（LUN）為檢測到的最高LUN。（參考附錄C對于默認(rèn)LUN）。
通電時，啟用網(wǎng)絡(luò)引導(dǎo)，并提供驅(qū)動器和控制器遇到的數(shù)字有效，將在系統(tǒng)控制臺：“正在進(jìn)行網(wǎng)絡(luò)引導(dǎo)…要中止hit<BREAK>”在該消息之后，
FBM223模擬量輸出模塊當(dāng)調(diào)試固件等待各種控制器和驅(qū)動器達(dá)到速度然后開始實際的輸入/輸出：程序指向指定媒體的卷ID加載到RAM中，并將控制傳遞給它。
但是，如果在此期間您希望在不啟動網(wǎng)絡(luò)的情況下獲得控制權(quán)，您可以按<BREAK>鍵或軟件中止或重置開關(guān)。網(wǎng)絡(luò)自動引導(dǎo)由NIOT和ENV命令。這些參數(shù)允許選擇特定的引導(dǎo)設(shè)備，并允許對引導(dǎo)延遲進(jìn)行編程。參考ENV有關(guān)更多詳細(xì)信息，請參閱附錄A中的命令。
重新啟動系統(tǒng)用戶可以通過三種不同的方式將系統(tǒng)初始化為已知狀態(tài)：重置、中止和中斷。每一個都有其特點，使其更在某些情況下比其他人更合適。
調(diào)試器在重置條件下具有特殊功能。此功能是通過同時按下重置和中止開關(guān)激活。此功能指示調(diào)試器使用默認(rèn)設(shè)置/操作ROM中的參數(shù)與NVRAM中用戶的設(shè)置/操作參數(shù)。
如果用戶的設(shè)置/操作參數(shù)已損壞或不符合健全性檢查。請參閱ENV命令（附錄A）適用于ROM默認(rèn)值。重置按下并釋放MVME197LE前面板重置開關(guān)啟動系統(tǒng)重置。冷復(fù)位和熱復(fù)位模式可用，并由使用重置命令。默認(rèn)情況下，197Bug處于冷模式。在期間冷復(fù)位時，將進(jìn)行整個系統(tǒng)初始化，就像MVME197LE剛剛通電一樣。所有靜態(tài)變量（包括磁盤設(shè)備和控制器參數(shù)）恢復(fù)到其默認(rèn)狀態(tài)。斷點表和偏移量寄存器被清除。目標(biāo)寄存器無效。輸入和輸出字符隊列已清除。車載設(shè)備（計時器、串行端口等）包括重置，前兩個串行端口重新配置為其默認(rèn)狀態(tài)。
在熱復(fù)位過程中，197Bug變量和表格被保留，以及目標(biāo)狀態(tài)寄存器和斷點。
如果處理器曾經(jīng)停止，或者如果197Bug環(huán)境曾經(jīng)丟失（向量表被破壞、堆棧損壞等）。
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.
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. (Refer to Appendix C
for default LUNs).
At power-up, Network Boot is enabled, and providing the drive and controller
numbers encountered are valid, the following message is displayed upon the
system console:
“Network Boot in progress... To abort hit <BREAK>”
Following this message there is approximately a thirty-second delay while the
debug firmware waits for the various controllers and drives to come up to
speed. Then the actual I/O is begun: the program pointed to within the
volume ID of the media specified is loaded into RAM and control passed to it.
If, however, during this time you want to gain control without Network Boot,
you can press the <BREAK> key or the software ABORT or RESET switches.
Network Auto Boot is controlled by parameters contained in the NIOT and
ENV commands. These parameters allow the selection of specific boot devices,
systems, and files, and allow programming of the Boot delay. Refer to the ENV
command in Appendix A for more details.
Restarting the System
The user can initialize the system to a known state in three different ways:
reset, abort, and break. Each has characteristics which make it more
appropriate than the others in certain situations.
The debugger has a special feature upon a reset condition. This feature is
activated by depressing the RESET and ABORT switches at the same time.
This feature instructs the debugger to use the default setup/operation
parameters in ROM versus the user’s setup/operation parameters in NVRAM.
This feature can be used in the event the user’s setup/operation parameters
are corrupted or do not meet a sanity check. Refer to the ENV command
(Appendix A) for the ROM defaults.
Reset
Pressing and releasing the MVME197LE front panel RESET switch initiates a
system reset. COLD and WARM reset modes are available and are selected by
using the RESET command. By default, 197Bug is in COLD mode. During
COLD reset, a total system initialization takes place, as if the MVME197LE 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 first two serial ports are reconfigured to their default state.
During WARM reset, the 197Bug variables and tables are preserved, as well as
the target state registers and breakpoints.
Reset must be used if the processor ever halts, or if the 197Bug environment is
ever lost (vector table is destroyed, stack corrupted, etc.).
