Co-Processor Adapter Option Diskette Description and Realtime Interface Co-processor Firmware Technical Reference, First Edition (January, 1990) Addendum The term, "Co-Processor Adapter", refers the Realtime Interface Co-Processor Portmaster Adapter/A. The contents of this diskette can be classified into seven groups. These groups are the diagnostic program, the Realtime Control Microcode, Adapter Description File, Adapter Description Program, Set Configuration Program, Miscellaneous Adapter Description Files and Programs, and information files. The diagnostic program is: DEV141 .DGS Diagnostic module for Co-Processor Adapter's diagnostics. This isolates a failure to a customer replaceable unit. The Realtime Control Microcode file is: ICARCM .COM Realtime Control Microcode. This is the Co-Processor Adapter's supervisory microcode which is loaded to the Co-Processor Adapter as task number zero. Loading this file to the Co-Processor Adapter requires the Application Loader Utility of the Realtime Interface Co-Processor DOS Support package, or OS/2 Support package (both separately packaged and priced products), or a user-written loader utility as described in the Realtime Interface Co-Processor Technical Reference. The Adapter Description File is: @8F70 .ADF IBM Realtime Interface Co-Processor Portmaster Adapter/A Description File. This file contains the configuration information for the IBM Realtime Interface Co-processor Portmaster Adapter/A. The following can be configured using this file: 1. Base I/O Address 2. Interrupt Level 3. Bus Master Arbitration Level 4. Fairness 5. Shared Storage Window Location and Size The Adapter Description Program is: C8F70 .ADF IBM Realtime Interface Co-Processor Portmaster Adapter/A Description Program. This file contains code which will be called during set up if the Shared Storage Window Location and Size option, "Above 16M, Window=Memory Size", is selected. This code will allow the user to allocate a window for this adapter between 16M and 4G in system memory. The Set Configuration Program is: SC .EXE Set Configuration Program This file contains code which enables the user to select different options when configuring the system. The Miscellaneous Adapter Description Files and Programs are: Cxxxx .ADF Where xxxx is any alpha-numeric character. Dxxxx .ADF Pxxxx .ADF Sxxxx .ADF @xxxx .ADF The files listed above contain system information required by the Set Configuration program. The information files are: READ .ME The file you are currently reading which describes the files on this diskette. HISTORY .FIL A history file of the Co-Processor Adapter Option diskette which lists major changes to files on the Co-Processor Adapter Option diskette. Note: If "Copy an Option Diskette" is selected during set up, all files on the Option Diskette, with the exception of the Read.Me, History.Fil, and ICARCM.COM will be copied to a reference diskette, provided that the date of the file on the option diskette is later than the date of the corresponding file on the reference diskette. During system configuration, this adapter first attempts to allocate its memory window in the region, C0000h-DFFFFh. These addresses are choices in this adapter's ADF. During IPL, if an XMA2EMS Driver is installed, it searches the memory region, C0000h-EFFFFh, for a page frame through which to access expanded memory. If the two windows are in conflict, the interrupt handler will fail during initialization. To avoid this problem, XMA2EMS device parameters can be set in the CONFIG.SYS file. For a more detailed description of this problem and its solution, refer to the IBM Disk Operating System Manual. For vendor cards that supply their own expanded memory drivers, refer to the vendor driver documentation on how to select the expanded memory page frame. Realtime Interface Co-processor Firmware Technical Reference, First Edition (January, 1990) Addendum: The addendum listed below is required to document changes to RCM for version 2.01. VOLUME II - Functions p. 6-19, REMQUEUE should be corrected by replacing "960KB" with "base memory". p. 6-22, PHYSICAL ADDQUEUE errors should indicate that RCM Version 2.01 does not return the 11h error code for a physical address that is in unallocated memory. (The physical address is still mapped, as before, but no error code is returned.) VOLUME III - Data Structures p. 12-24, The minor version code will be set to 01h by RCM Version 2.01. p. 12-60, The RAM storage request block description should indicate that RCM Version 2.01 considers a 1M Portmaster Adapter/A to have 992k of base RAM. p. 12-117, The following note should be added. RCM Version 2.01 allows a user to disable Peer Services. Refer to section on 'Disabling Peer Services.' p. 12-123, The Move Data command description should be changed to the following: This command is issued to the Realtime Control Microcode to move data from one processor's memory to another processor's memory. A move data command can be issued to the Realtime Control Microcode on another processor. For Realtime Control Microcode 2.0, either the source buffer or the destination buffer, but not both, must be on the same processor as the Realtime Control Microcode which is issuing the command. For Realtime Control Microcode 2.01, the source buffer and/or the destination buffer must be on the same processor as the Realtime Control Microcode which is issuing the command. If the source and destination buffers are on the same processor, the move data command will be implemented by a memory move. If the source and destination buffers overlap, the integrity of the data can not be guaranteed. p. 12-144, The section under Channel Check Errors on setting RCM secondary status should be modified to indicate that the following is true for RCM 2.01. When control is returned to Realtime Control Microcode 2.01, it signals the error to the system unit as follows: 1. Realtime Control Microcode's secondary status is set as follows: Byte 0 = 0Ah Byte 1: Bits 1-7 = Reserved Bit 0: When bit 0 = 0, a Micro Channel write or slave read parity error occurred while this card was a bus master. When this bit = 1, a Micro Channel write parity error or slave read parity error occurred while this card was a slave. Byte 2: Bit 0: When bit 0 = 0, this card was a Micro Channel slave during a memory read operation. The arb level identifier bits specify the bus master during the parity error cycle. When this bit = 1, the parity error was a Micro Channel data parity error. Bit 1: This bit only has meaning when bit 0 = 1. When this bit = 1, the parity error occurred while this card was a bus master reading data from the channel. When this bit = 0, the parity error occurred while another bus master was performing a write to this card. Bit 2: This bit only has meaning when bit 1 = 0. When this bit = 0, the error occurred during a memory write. When this bit = 1, the error occurred during an I/O write. Bits 3-6: These bits represent the arb level that was present on the Micro Channel at the time of the error. Bit 7: This bit is set when the error occurred as a result of a write to the IO/CHCHK register. Byte 3: When Byte 1, bit 0 = 0, this byte contains the task number of the peer service requestor when the parity error occurred. FFh indicates no peer service requestor. 2. Realtime Control Microcode's primary status error and status available bits are set. 3. Realtime Control Microcode sets INTID = FEh and interrupts the system unit. p. 12-146, The following new section is to be added: Disabling Peer Services RCM Version 2.01 allows a user to disable Peer Services by specifying an optional parameter of 1 (one) when invoking either of the system support application loader utilities. ex. ICALOAD 0 ICARCM.COM 0 ( 1 Refer to the Realtime Interface Co-processor DOS Support Version 1.02 User's Guide or the OS/2 Support Version 1.03 User's Guide for information on the operation of the application loader utilities. This parameter will cause RCM to bypass the building of peer related tables. The memory formerly used by these tables will remain in the free storage pool. Calls to the peer request SVI will return an access denied error. This feature is not available on versions of RCM prior to RCM Version 2.01.