GE Multilin URRHH工控自动化卡件
（取决于控制器）数据包格式作为参数，并将其转换为特定于控制器的数据包，然后将其发送到指定的设备。有关这些标准化“用户”数据包的格式和结构的更多信息，请参阅Motorola 68K CISC CPU用户手册调试包中的系统调用说明。DSKRD磁盘读取。将块从磁盘读取到内存的系统调用。DSKWR磁盘写入。将块从内存写入磁盘的系统调用。DSKCFIG磁盘配置。此功能允许您更改指定设备的配置。DSKFMT磁盘格式。此函数允许您向指定设备发送格式化命令。DSKCTRL磁盘控制。此功能用于实现任何特殊的设备控制功能，这些功能无法与任何其他磁盘功能一起轻松实现。磁盘I/O支持http://www.mcg.mot.com/literature3-21 3控制器模块期望给出的数据包因控制器而异。特定硬件模块（板）的磁盘驱动程序模块必须接受陷阱功能提供的标准化数据包，并创建一个新数据包，该数据包专门针对发送到的磁盘驱动器控制器。有关数据包的格式和使用IOC命令的信息，请参阅特定控制器模块的文档。默认162Bug控制器和设备参数162Bug初始化控制器和设备的默认配置的参数表（参见附录B）。如果系统需要与此默认配置不同的配置（例如，使用70MB温彻斯特驱动器，默认为40MB温彻斯特驱动器），则必须更改这些表。3-22计算机组文献中心网站调试器一般信息3更改参数表有三种方法：❏ 使用BO或BH。当您调用其中一个命令时，将读取磁盘的配置区域，并根据配置区域中包含的参数信息重写与该设备对应的参数。这是暂时的改变。如果发生冷启动重置，则将默认参数信息写入表中。❏ 使用IOT。您可以使用此命令为不同于默认值的任何控制器和/或设备手动重新配置参数表。这也是一个临时更改，如果发生冷启动重置，则会被覆盖。❏ 获取来源。然后可以更改配置文件并重建162Bug，使其具有不同的默认值。对默认值所做的更改是永久的，直到再次更改。如果磁盘操作失败，磁盘I/O错误代码162Bug将返回错误代码。网络I/O支持网络引导固件提供了使用网络（本地以太网接口）作为引导设备通过Flash/PROM调试器引导CPU的能力。引导过程分两个不同的阶段执行。❏ 第一阶段允许无盘远程节点发现其网络标识和要引导的文件的名称。❏ 第二阶段是无盘远程节点通过网络将引导文件读取到其内存中。以下段落描述了支持整个网络引导功能的各种模块（功能）和这些模块的依赖关系。网络I/O支持http://www.mcg.mot.com/literature3-23 3 Intel 82596 LAN协处理器以太网驱动程序此驱动程序管理/围绕Intel 82596局域网协处理器。管理范围包括数据包的接收、数据包的传输、接收缓冲区刷新和接口初始化。该模块确保在Boot PROM中正确完成以太网数据包的打包和解包。UDP/IP协议模块互联网协议（IP）设计用于分组交换计算机通信网络的互连系统。互联网协议提供从源到目的地的数据块（即用户数据报协议或UDP）传输，其中源和目的地是由固定长度地址标识的主机。UDP/IP协议对于
(controllerindependent) packet format as an argument, and translate it into a controller-specific packet, which is then sent to the specified device. Refer to the system call descriptions in the Debugging Package for Motorola 68K CISC CPUs User’s Manual for additional information on the format and construction of these standardized "user" packets. .DSKRD Disk read. System call to read blocks from a disk into memory. .DSKWR Disk write. System call to write blocks from memory onto a disk. .DSKCFIG Disk configure. This function allows you to change the configuration of the specified device. .DSKFMT Disk format. This function allows you to send a format command to the specified device. .DSKCTRL Disk control. This function is used to implement any special device control functions that cannot be accommodated easily with any of the other disk functions. Disk I/O Support http://www.mcg.mot.com/literature 3-21 3 The packets which a controller module expects to be given vary from controller to controller. The disk driver module for the particular hardware module (board) must take the standardized packet given to a trap function and create a new packet which is specifically tailored for the disk drive controller it is sent to. Refer to documentation on the particular controller module for the format of its packets, and for using the IOC command. Default 162Bug Controller and Device Parameters 162Bug initializes the parameter tables for a default configuration of controllers and devices (refer to Appendix B). If the system needs to be configured differently than this default configuration (for example, to use a 70MB Winchester drive where the default is a 40MB Winchester drive), then these tables must be changed. 3-22 Computer Group Literature Center Web Site Debugger General Information 3 There are three ways to change the parameter tables: ❏ Using BO or BH. When you invoke one of these commands, the configuration area of the disk is read and the parameters corresponding to that device are rewritten according to the parameter information contained in the configuration area. This is a temporary change. If a cold-start reset occurs, then the default parameter information is written back into the tables. ❏ Using the IOT. You can use this command to reconfigure the parameter table manually for any controller and/or device that is different from the default. This is also a temporary change and is overwritten if a cold-start reset occurs. ❏ Obtain the source. You can then change the configuration files and rebuild 162Bug so that it has different defaults. Changes made to the defaults are permanent until changed again. Disk I/O Error Codes 162Bug returns an error code if an attempted disk operation is unsuccessful. Network I/O Support The Network Boot Firmware provides the capability to boot the CPU through the Flash/PROM debugger using a network (local Ethernet interface) as the boot device. The booting process is executed in two distinct phases. ❏ The first phase allows the diskless remote node to discover its network identify and the name of the file to be booted. ❏ The second phase has the diskless remote node reading the boot file across the network into its memory. The various modules (capabilities) and the dependencies of these modules that support the overall network boot function are described in the following paragraphs. Network I/O Support http://www.mcg.mot.com/literature 3-23 3 Intel 82596 LAN Coprocessor Ethernet Driver This driver manages/surrounds the Intel 82596 LAN Coprocessor. Management is in the scope of the reception of packets, the transmission of packets, receive buffer flushing, and interface initialization. This module ensures that the packaging and unpackaging of Ethernet packets is done correctly in the Boot PROM. UDP/IP Protocol Modules The Internet Protocol (IP) is designed for use in interconnected systems of packet-switched computer communication networks. The internet protocol provides for transmitting of blocks of data called datagrams (hence User Datagram Protocol, or UDP) from sources to destinations, where sources and destinations are hosts identified by fixed length addresses. The UDP/IP protocols are necessary for the
