GE燃机 DS200IPCDG1ABA机械设备卡件
字符串“BOOT”必须位于指定的内存范围内。❏ 您的例程必须通过校验和测试，以确保此例程在通电时确实要接收控制。有关如何使用ROMboot的完整详细信息，请参阅Motorola 68K CISC CPU用户手册的调试包。网络引导网络自动引导是包含在162Bug Flash/PROM中的软件例程，它提供了一种使用网络（本地以太网接口）作为引导设备来引导操作系统的机制。Network Auto Boot（网络自动引导）例程会按指定的顺序自动扫描控制器和设备，直到找到包含引导介质的有效可引导设备或列表用尽。如果找到有效的可引导设备，则启动该设备的引导。控制器扫描顺序从检测到的最低控制器逻辑单元号（LUN）到检测到的最高LUN。（有关默认LUN，请参阅附录C。）通电时，网络引导已启用，并且如果遇到的驱动器和控制器编号有效，系统控制台上会显示以下消息：“Network Boot in progress…to abort hit”（网络引导正在进行中…要中止命中）。此消息后会出现延迟，允许您根据需要中止自动引导过程。然后开始实际的I/O：在指定介质的卷ID内指向的程序被加载到RAM中，并将控制权传递给它。但是，如果在此期间您想在没有网络引导的情况下获得控制权，您可以按键或软件ABORT或RESET开关。3-12计算机组文献中心网站调试器一般信息3网络自动启动由NIOT和ENV命令中包含的参数控制。这些参数允许选择特定的引导设备、系统和文件，并允许对引导延迟进行编程。有关更多信息，请参阅第5章中的ENV命令。重新启动系统您可以通过三种不同的方式将系统初始化为已知状态：重置、中止和中断。在某些情况下，每种语言都具有比其他语言更合适的特点。调试器在重置条件下具有特殊功能。同时按下RESET（复位）和ABORT（中止）开关可激活此功能。此功能指示调试器使用ROM中的默认设置/操作参数，而不是NVRAM中的设置/操作。如果您的设置/操作参数损坏或不符合健全性检查，则可以使用此功能。有关ROM默认值，请参阅ENV命令（第5章）。重新启动系统http://www.mcg.mot.com/literature3-13 3重置按下并快速释放MVME162FX控制器的前面板重置按钮可启动系统重置。COLD（冷）和WARM（暖）复位模式可用。默认情况下，162Bug处于COLD模式。在COLD重置过程中，系统将进行完全初始化，就像控制器刚刚通电一样。所有静态变量（包括磁盘设备和控制器参数）都恢复到其默认状态。断点表和偏移寄存器被清除。目标寄存器无效。清除输入和输出字符队列。板载设备（计时器、串行端口等）复位，两个串行端口重新配置为默认状态。在WARM重置期间，将保留162Bug变量和表，以及目标状态寄存器和断点。如果处理器停止或162Bug环境丢失（矢量表被破坏、堆栈损坏等），则必须使用重置。注意：请确保快速释放重置按钮，以避免更改DRAM内容。按住该按钮可能会抑制DRAM刷新，并导致某些板上的内存丢失。按下并松开MVME162FX控制器前面板上的Abort开关可调用Abort Abort。每当执行用户程序（运行目标代码）时调用中止时，就会捕获处理器状态的“快照”并将其存储在目标寄存器中。因此，终止正在调试的用户程序时，中止是最合适的。如果程序陷入循环等，应使用中止重新获得控制。目标PC、寄存器内容等。，
string "BOOT" must be located within the specified memory range. ❏ Your routine must pass a checksum test, which ensures that this routine was really intended to receive control at powerup. For complete details on how to use ROMboot, refer to the Debugging Package for Motorola 68K CISC CPUs User’s Manual. Network Boot Network Auto Boot is a software routine contained in the 162Bug Flash/PROM that provides a mechanism for booting an operating system using a network (local Ethernet interface) as the boot device. The Network Auto Boot 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. 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 " Following this message there is a delay to allow you to abort the Auto Boot process if you wish. 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 key or the software ABORT or RESET switches. 3-12 Computer Group Literature Center Web Site Debugger General Information 3 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 Chapter 5 for additional information. Restarting the System You 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 your setup/operation parameters in NVRAM. This feature can be used in the event your setup/operation parameters are corrupted or do not meet a sanity check. Refer to the ENV command (Chapter 5) for the ROM defaults. Restarting the System http://www.mcg.mot.com/literature 3-13 3 Reset Pressing and quickly releasing the MVME162FX controller’s front panel RESET button initiates a system reset. COLD and WARM reset modes are available. By default, 162Bug is in COLD mode. During COLD reset, a total system initialization takes place, as if the controller 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 reset, the 162Bug 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 162Bug environment is ever lost (vector table is destroyed, stack corrupted, etc.). Note Ensure that the RESET button is released quickly, to avoid altering the DRAM contents. Holding the button down may inhibit the DRAM refresh and cause memory loss on some boards. Abort Abort is invoked by pressing and releasing the ABORT switch on the MVME162FX controller’s front panel. Whenever abort is invoked when executing a user program (running target code), a "snapshot" of the processor state is captured and stored in the target registers. For this reason, abort is most appropriate when terminating a user program that is being debugged. Abort should be used to regain control if the program gets caught in a loop, etc. The target PC, register contents, etc.,
