DESCRIPTION This document contains the Application Notes, Installation Procedure, Corrections, and Deficiencies for the Interphase HP-UX 10.20 4220 V/SCSI-2 Cougar Driver Release 1.0 for HP 9000 Series 700 computers. Part Numbers: SM00028-A00 DDS tape distribution SX00357-A00 media independent image This release of the 4220 Condor driver is intended for use with the HP-UX 10.20 operating system. The software release supports a maximum of four 4221 Condor VME adapter cards per system. The following HP 9000 Series 700 hardware models are supported by this release 742i, 743i, 747i, 748i BEFORE YOU START This driver may be installed over a previous release. It is not necessary to remove a previous release prior to installation of this driver. SCSI Device Naming Convention: Device nodes are created at installation time with the following naming convention: Block Devices: /dev/cgr/cgr(x)b(y)d(z) Character Raw Devices: /dev/cgr/rcgr(x)b(y)d(z) Device-Independent Character Nodes: /dev/cgr/rcgr(x)b(y) Where x is the controller number, y is either 0 or 1 for the primary or secondary SCSI bus on that controller, and z is the ID of device on the bus. For instance: /dev/cgr/cgr3b1d0 ,Controller 3, Bus 1, Device 0 /dev/cgr/rcgr0b1d1 Controller 0, Bus 1, Device 1 /dev/cgr/rcgr0b0 Controller 0, Bus 0 Tape Devices: Tape devices use the same naming convention as other SCSI devices. Cougar Utility Program: A utility program is provided with the driver to perform the following: a. Reset of a selected SCSI bus b. Perform a board diagnostic c. Perform a low-level device format Command usage is: cgr_util -[b|d|f] [device name] Resetting a selected SCSI bus: Resetting a SCSI bus is useful for manual error recovery, when a SCSI device error has caused the bus to hang. Syntax: cgr_util -b cgr(x)b(y) To reset SCSI bus y on controller x. The following example will reset the secondary SCSI bus on the third installed controller on the system: cgr_util -b cgr2b1 Upon success, this message will be printed to the console, "SCSI bus reset successful.", otherwise an error message will be reported. Performing a Board Diagnostics: The controller diagnostics command will cause the board to perform a set of pass/fail self-diagnostic test that is identical to those performed during the system's power-up self test. NOTE: This test should not be performed while devices are in use. Syntax: cgr_util -d cgr(x)b(y) The following command will execute a diagnostic test on the fourth installed controller in the system. The specified bus is ignored: cgr_util -d cgr3b0 You will be prompted whether you wish to continue. There must be no activity on the board when the diagnostics is executed, otherwise failure will be returned. If the test reports a failure the first time, execute the test again. Since the board is reset after the diagnostics are run, the test should return valid results the second time if no new commands have been issued to the board. Upon success, the message "Cougar diagnostics succeeded" is displayed, else if the test fails a corresponding error message is displayed. Performing a low-level device format: The low-level format option of cgr_util executes the built-in format routine of a SCSI disk or tape driver. All data on the device will be destroyed!! Most devices will have been formatted in the factory prior to shipment, so do not use this command unless you are absolutely certain you want to perform a low-level format. Syntax: cgr_util -f cgr(x)b(y)d(z) For instance, to format the second device on the primary SCSI bus of the first controller, you would execute the following command: cgr_util -f cgr0b0d1 The user is prompted whether one wishes to continue. After acknowledgment, the format process will begin and the following message is displayed to the console: "This will take some time, please allow at least one hour" "Formatting ..." The string "Succeeded" is printed when completed. If the device format did not work, "Failed" is displayed along with the error message retuned by the controller. Hardware Setup: Jumpers: Use the factory default settings except as noted. Refer to the User's Guide for the location and identifier of these jumpers. Firmware Option Jumper, 16-bit Block Mode. Disable 16-bit block mode. This allows block mode transfers to function correctly on the HP CPU boards which do not handle 16-bit block mode. Short I/O Addresses: Only a 2k short I/O configuration is supported. Ensure the 4220 Primary Short I/O size jumpers are set for 2k bytes of short I/O space. For each controller installed, select an address block within A16 short I/O space that will not conflict with any other boards installed in the VME backplane. Set the Primary Base Address for each controller to a unique short I/O base address. Daughterboard Settings: The default setting will provide terminator power to the secondary SCSI bus. LED1 indicates TERMPWR is on. Refer to the User's Guide for more information. System Configuration : If you have a 743i it may inadvertently remove the 1M shared memory needed for the slave mapper. If the slave mapping is not correct the 4221 may print an error message indicating the map_mem_to_bus operation has failed. Use `vme_config -m A32' to verify whether the needed 1M region is present. For instance, A32 Memory Range Size Name --------------------------------------------------------- 0x00100000 - 0x001fffff Size: 1M SHARED_MEM_CPU1 If such an entry does not exist, you will have to edit your vme.CFG file to add a 1M entry in the A32 memory structure entitled `Space for A32 direct mapped window'. For example the following will suffice: // address Name Proc Options align 1M:1M cgr1M hp743i hints=SYSTEM_ONLY, PRIVATE Execute `vme_config -m A32' again to verify the mapper has now recognized the 1M region. In some cases you may notice a second 1M region entry, although the system will function normally. Execute `vme_config' (no options) to save the configuration before the next system reboot. Installation To install begin by powering the system down. Install the 4220 VME adapter into a vacant slot Reboot the machine and load the installation tape(SM00028-A00) To install the 4220 driver (SX00357-A00) run the `swinstall' utility. Upon the install tape's completion, a new kernel will be built and the system will be rebooted. The file cgr.cfg is the Interphase 4220 configuration file which is written in the `/usr/conf/master.d/' directory during the driver installation process. This allows the system vme configuration utility to include specific configuration details about the 4220. The default Short I/O addresses for four 4220 controllers are setup as follows: 0x00001000 - 0x000017ff Size: 2K cgr0_shio 0x00001800 - 0x00001fff Size: 2K cgr1_shio 0x00002000 - 0x000027ff Size: 2K cgr2_shio 0x00003800 - 0x00003fff Size: 2K cgr3_shio If these defaults conflict with your desired system board locations, modify the CGR_START_ADDR and CGR_END_ADDR addresses in the cgr.cfg file to correspond with the desired values such that there is no conflict. The selected addresses and range must correspond to the jumper settings on the controller(s). If you do not need to install multiple 4220 boards in the future and want to conserve short I/O space mapped by the unused boards, comment out the corresponding entries in cgr.cfg. Place comments, `//', at the beginning of the Card Declaration Record and Memory Declaration Record for cgr1, cgr2, and/or cgr3. Once cgr.cfg has been modified, check for syntax errors. vme_config -c -f cgr.cfg Check the entries if an error message is reported, otherwise the command returns nothing. Execute the following commands to ensure the system configuration is as expected. vme_config -m A16 Checks for Short I/O conflicts vme_config -m A32 Checks for A32 conflicts Once it is verified the configuration is correct, execute the command: vme_config this will save the changes made to the configuration. The system now must be rebooted. Installation Verification: Execute `dmesg' and look for a message similar to the following for a typical configuration. -------------------------------------------------------------------- Interphase 4220 V/SCSI Cougar: slva= Product Number: 091 Var: 4 Revision: A23 Date: 03-03-95 Primary ID: 7 Secondary ID 7 FEC 0 ID: 1 FEC 1 ID: 0 cgr 10: SEAGATE -ST31230N -0300 cgr_attach: controller 0 found Interphase 4220 V/SCSI Cougar: slva= Product Number: 077 Var: 4 Revision: A23 Date: 11-30-95 Primary ID: 7 Secondary ID 7 FEC 0 ID: 3 FEC 1 ID: 0 cgr110: SEAGATE -ST31230N -0300 cgr111: SEAGATE -ST31230N -0510 cgr_attach: controller 1 found This means the device driver found 2 boards with these characteristics: Product: Interphase 4220 V/SCSI Cougar Short I/O address, 1st board: 0x1800 Short I/O address, 2nd board: 0x9000 Firmware revision: A23 SCSI ID of SCSI channel 0: 7 (both boards) SCSI ID of SCSI channel 1: 7 (both boards) Front End Ch. 0 type, board1: Differential (table below) Front End Ch. 1 type, board1: Single-ended (table below) Front End Ch. 0 type, board2: Differential Wide (table below) Front End Ch. 1 type, board2: Single-ended (table below) Devices found: 1st board, 2nd bus, 1st dev: ST31230N on cgr 10 2nd board, 2nd bus, 1st dev: ST31230N on cgr110 2nd board, 2nd bus, 2nd dev: ST31230N on cgr111 2 controllers found 0 and 1 Driver Revision: SX00221-A00 Determine the type of front-end SCSI bus from the following table: FEC ID Type --------------------------------------------- 0x0 Single-ended Cougar II 0x1 Differential Cougar II 0x2 Single-ended Cougar II Wide 0x3 Differential Cougar II Wide Board / Bus / Device ---------------------------------------------- cgr 00 Controller 0, Bus 0, Device 0 cgr 01 Controller 0, Bus 0, Device 1 cgr 02 Controller 0, Bus 0, Device 2 cgr 03 Controller 0, Bus 0, Device 3 cgr 04 Controller 0, Bus 0, Device 4 cgr 05 Controller 0, Bus 0, Device 5 cgr 06 Controller 0, Bus 0, Device 6 cgr 07 Controller 0, Bus 0, Device 7 cgr 08 Controller 0, Bus 0, Device 8 cgr 09 Controller 0, Bus 0, Device 9 cgr 0a Controller 0, Bus 0, Device 10 cgr 0b Controller 0, Bus 0, Device 11 cgr 0c Controller 0, Bus 0, Device 12 cgr 0d Controller 0, Bus 0, Device 13 cgr 0e Controller 0, Bus 0, Device 14 cgr 0f Controller 0, Bus 0, Device 15 cgr 10 Controller 0, Bus 1, Device 0 cgr 11 Controller 0, Bus 1, Device 1 cgr 12 Controller 0, Bus 1, Device 2 . . cgr110 Controller 1, Bus 1, Device 0 cgr111 Controller 1, Bus 1, Device 1 cgr112 Controller 1, Bus 1, Device 2 . . cgr210 Controller 2, Bus 1, Device 0 cgr211 Controller 2, Bus 1, Device 1 cgr212 Controller 2, Bus 1, Device 2 . . cgr310 Controller 3, Bus 1, Device 0 cgr311 Controller 3, Bus 1, Device 1 cgr312 Controller 3, Bus 1, Device 2 . . cgr31f Controller 3, Bus 1, Device f Use the diskinfo command to print device information. For example: diskinfo /dev/cgr/rcgr0b1d0 results in the following output when using a Seagate ST31230N: SCSI describe of /dev/cgr/rcgr0b1d0: vendor: SEAGATE product id: ST31230N type: direct access size: 1034930 Kbytes bytes per sector: 512 Contact Information Customer Support United States: Telephone: (214) 654-5555 Fax: (214) 654-5500 E-Mail: intouch@iphase.com United Kingdom: Telephone: 44 (0) 1869-321222 Fax: 44 (0) 1869-247720 France: Telephone: 33 (0)1 41 15 44 00 Fax: 33 (0)1 41 15 12 13 World Wide Web http://www.iphase.com Anonymous FTP Server ftp.iphase.com