GE燃机 IS200EPSMG2A自动化卡件
应用8.报头J26定义了当IP DMA控制器是本地总线主控器时监听控制总线的状态。出厂配置中有两个跳线，用于禁止窥探。验证此设置是否适合您的应用程序。9.有关MVME162FX安装的详细信息，请参阅特定机箱或系统的安装程序。10.将用作162Bug系统控制台的终端连接到MVME162FX控制器前面板上串行端口1处的默认调试EIA-232-D端口。有关其他连接选项，请参阅第2章。按如下方式设置终端：–每个字符八位–每个字符一个停止位–禁用奇偶校验（无奇偶校验）–波特率9600波特（MVME162FX控制器端口通电时的默认波特率）通电后，如果需要，可以使用162Bug调试器的端口格式（PF）命令重新配置调试端口的波特率。3-8计算机组文献中心网站调试器一般信息3注意：为了使162Bug和终端之间的高波特率串行通信正常工作，终端必须进行某种形式的握手。如果所使用的终端没有通过CTS线路进行硬件握手，那么它必须进行XON/XOFF握手。如果收到乱码消息和丢失的字符，则应检查终端以确保启用了XON/XOFF握手。11.如果要将设备（如主机系统和/或串行打印机）连接到其他EIA-232-D端口连接器（MVME712x转换模块上标记为serial PORTS 2、3和4），请连接适当的电缆并按照上述步骤3中的详细说明配置端口。通电后，您可以通过编程MVME162FX Z85230串行通信控制器（SCC）或使用162Bug PF命令重新配置端口。12.接通系统电源。162Bug执行一些自检并显示调试器提示“162Bug>”（如果处于Board Mode）。但是，如果ENV命令（第5章）将162Bug置于系统模式，系统将执行自检并尝试自动启动。请参阅ENV和MENU命令。它们列于表4-3中。如果置信度测试失败，当遇到第一个故障时，测试将中止。如果可能，将显示适当的消息，然后控制返回到菜单。13.董事会的自检和操作系统要求实时时钟运行。在初始安装后使用MVME162FX控制器之前，请使用以下命令行结构设置日期和时间：162 Bug>set[mmddyyhhhmm]|[；C]例如，以下命令行启动实时时钟并将日期和时间设置为1998年8月7日上午10:37：162 Bug>set 0807981037 C选项允许您校准实时时钟。有关详细信息，请参阅调试包用户手册。自动引导（Autoboot）http://www.mcg.mot.com/literature3-9 3注意：如果您使用的是162Bug的PROM版本（例如，在没有VMEbus的情况下，MVME162FX控制器的空白闪存版本），并且您希望在后续会话中使用闪存而不是PROM执行调试器，请确保162Bug处于板模式并复制PROM
application. 8. Header J26 defines the state of the snoop control bus when an IP DMA controller is local bus master. The factory configuration has both jumpers in place for snoop inhibition. Verify that this setting is appropriate for your application. 9. Refer to the setup procedure for your particular chassis or system for details concerning the MVME162FX installation. 10. Connect the terminal that is to be used as the 162Bug system console to the default debug EIA-232-D port at serial port 1 on the front panel of the MVME162FX controller. Refer to Chapter 2 for other connection options. Set up the terminal as follows: – eight bits per character – one stop bit per character – parity disabled (no parity) – baud rate 9600 baud (default baud rate of MVME162FX controller ports at power-up) After power-up, you can reconfigure the baud rate of the debug port if necessary by using the Port Format (PF) command of the 162Bug debugger. 3-8 Computer Group Literature Center Web Site Debugger General Information 3 Note In order for high-baud rate serial communication between 162Bug and the terminal to work, the terminal must do some form of handshaking. If the terminal being used does not do hardware handshaking via the CTS line, then it must do XON/XOFF handshaking. If you get garbled messages and missing characters, then you should check the terminal to make sure XON/XOFF handshaking is enabled. 11. If you want to connect devices (such as a host computer system and/or a serial printer) to the other EIA-232-D port connectors (marked SERIAL PORTS 2, 3, and 4 on the MVME712x transition module), connect the appropriate cables and configure the port(s) as detailed in Step 3 above. After power-up, you can reconfigure the port(s) by program-ming the MVME162FX Z85230 Serial Communications Controller (SCC), or by using the 162Bug PF command. 12. Power up the system. 162Bug executes some self-checks and displays the debugger prompt "162-Bug>" (if in Board Mode). However, if the ENV command (Chapter 5) has put 162Bug in System Mode, the system performs a self test and tries to autoboot. Refer to the ENV and MENU commands. They are listed in Table 4-3. 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. 13. The board’s self-tests and operating systems require that the realtime clock be running. Before using the MVME162FX controller after the initial installation, set the date and time using the following command line structure: 162-Bug> SET [mmddyyhhmm]|[;C ] For example, the following command line starts the real-time clock and sets the date and time to 10:37 AM, August 7, 1998: 162-Bug> SET 0807981037 The C option allows you to calibrate the real-time clock. Refer to the Debugging Package User’s Manual for details. Autoboot http://www.mcg.mot.com/literature 3-9 3 Note If you are using a PROM version of the 162Bug (e.g., in noVMEbus, blank-flash versions of the MVME162FX controller) and you wish to execute the debugger out of Flash memory rather than from PROM in subsequent sessions, make sure that 162Bug is in Board Mode and copy the PROM
