From: LEDS::UYENO "Alice Terumi Uyeno, DTN 291-7104, NKS1-2/H6" 3-MAR-1988 14:48
To: SUBSYS::DELEO

KFQSA (Qbus to DSSI Adapter)
                          Functional Specification

                              Revision 2.5
                
                             December 14, 1987                  

                            R E V I E W   C O P Y

                              Steve  Banas
                              George Kondos             
                              Tom    Kuzeja
                              Alain  Arnaud
                              Scott  Tate               

                     C O M P A N Y    C O N F I D E N T I A L

               Copyright (C) 1987 by Digital Equipment Corporation

          The information in this document is subject to change  without
          notice  and should not be construed as a commitment by Digital
          Equipment Corporation.  Digital Equipment Corporation  assumes
          no  responsibility  for  any  errors  that  may  occur in this
          document.

          This specification does not describe any  program  or  product
          which   is   currently   available   from   Digital  Equipment
          Corporation nor does Digital Equipment Corporation  commit  to
          implement  this  specification  in  any  program  or  product.
          Digital Equipment Corporation makes no committment  that  this
          document accurately describes any product it might ever make.

KFQSA Functional Specification  (Company Confidential)          Page 2
                                                      14 December 1987

                                   CONTENTS

CHAPTER 1       INTRODUCTION

        1.1     SCOPE  . . . . . . . . . . . . . . . . . . . . . . 1-1
        1.2     REFERENCE AND RELATED DOCUMENTS  . . . . . . . . . 1-1
        1.3     PRODUCT OVERVIEW . . . . . . . . . . . . . . . . . 1-2
        1.4     TARGET SYSTEMS . . . . . . . . . . . . . . . . . . 1-2
        1.4.1     MAIN FEATURES  . . . . . . . . . . . . . . . . . 1-3
        1.5     PRODUCT MOTIVATION . . . . . . . . . . . . . . . . 1-4
        1.6     CONFIGURATION SUPPORT  . . . . . . . . . . . . . . 1-4
        1.6.1     CONFIGURATIONS AT FRS  . . . . . . . . . . . . . 1-4

CHAPTER 2       ARCHITECTURE

        2.1     OVERVIEW . . . . . . . . . . . . . . . . . . . . . 2-1
        2.2     GENERAL INFORMATION  . . . . . . . . . . . . . . . 2-2
        2.2.1     DSA/DSSI ARCHITECTURE COMPLIANCE . . . . . . . . 2-2
        2.3     FUNCTIONAL ELEMENTS OF THE SYSTEM  . . . . . . . . 2-2
        2.3.1     OVERVIEW . . . . . . . . . . . . . . . . . . . . 2-2
        2.3.2     BUFFER ALLOCATION  . . . . . . . . . . . . . . . 2-3
        2.4     CSR CONFIGURATION MECHANISM  . . . . . . . . . . . 2-3
        2.4.1     NORMAL MODE  . . . . . . . . . . . . . . . . . . 2-3
        2.4.2     SERVICE MODE . . . . . . . . . . . . . . . . . . 2-3
        2.4.3     MANUFACTURING MODE   . . . . . . . . . . . . . . 2-5
        2.5     DSSI NODE ADDRESS MAPPING  . . . . . . . . . . . . 2-6
        2.5.1     DEVICE ID  . . . . . . . . . . . . . . . . . . . 2-6
        2.5.2     KFQSA DEVICE ID  . . . . . . . . . . . . . . . . 2-6
        2.6     UQPORT INITIALIZATION  . . . . . . . . . . . . . . 2-6
        2.6.1     OVERVIEW . . . . . . . . . . . . . . . . . . . . 2-6
        2.6.2     DETAILS OF INITIALIZATION  . . . . . . . . . . . 2-9
        2.6.2.1     STANDARD INITIALIZATION STEP 1 . . . . . . . . 2-9
        2.6.2.2     STANDARD INITIALIZATION STEP 2 . . . . . . . . 2-9
        2.6.2.3     STANDARD INITIALIZATION STEP 3 . . . . . . . . 2-9
        2.6.2.4     STANDARD INITIALIZATION STEP 4 . . . . . . .  2-10
        2.6.3     UQPORT DIAGNOSTIC FACILITIES . . . . . . . . .  2-10
        2.6.3.1     DIAGNOSTIC WRAP MODE . . . . . . . . . . . .  2-10
        2.6.3.2     PURGE POLL TEST  . . . . . . . . . . . . . .  2-11
        2.6.3.3     HOST MEMORY AND BUS TEST . . . . . . . . . .  2-11
        2.6.3.4     LAST FAIL ERROR PACKETS  . . . . . . . . . .  2-11
        2.6.3.5     SPECIAL FUNCTION MODE  . . . . . . . . . . .  2-11
        2.7     ERROR HANDLING . . . . . . . . . . . . . . . . .  2-11
        2.7.1     QBUS ERRORS  . . . . . . . . . . . . . . . . .  2-12
        2.7.2     DSSI ERRORS  . . . . . . . . . . . . . . . . .  2-12

CHAPTER 3       HARDWARE DESCRIPTION

        3.1     HARDWARE OVERVIEW  . . . . . . . . . . . . . . . . 3-1
        3.2     HARDWARE FUNCTIONALITY . . . . . . . . . . . . . . 3-1
        3.2.1     Q-BUS INTERFACE AND CONTROL  . . . . . . . . . . 3-1

KFQSA Functional Specification  (Company Confidential)          Page 3
                                                      14 December 1987

        3.2.2     8096 MICROCONTROLLER SUBSYSTEM . . . . . . . . . 3-2
        3.2.3     68000 MICROPROCESSOR SUBSYSTEM . . . . . . . . . 3-2
        3.2.4     DSSI INTERFACE AND CONTROL . . . . . . . . . . . 3-3
        3.3     BUS PERFORMANCE AND FEATURES . . . . . . . . . . . 3-3
        3.3.1     Q-BUS PERFORMANCE AND FEATURES . . . . . . . . . 3-3
        3.3.2     DSSI INTERFACE FEATURES  . . . . . . . . . . . . 3-4

CHAPTER 4       PHYSICAL SPECIFICATION

        4.1     ENVIRONMENTAL  . . . . . . . . . . . . . . . . . . 4-1
        4.1.1     POWER DISSIPATION  . . . . . . . . . . . . . . . 4-1
        4.1.2     TEMPERATURE RANGE  . . . . . . . . . . . . . . . 4-1
        4.1.3     HUMIDITY . . . . . . . . . . . . . . . . . . . . 4-2
        4.1.4     ALTITUDE . . . . . . . . . . . . . . . . . . . . 4-2
        4.1.5     POWER REQUIREMENTS   . . . . . . . . . . . . . . 4-2
        4.1.6     Q-BUS LOADING  . . . . . . . . . . . . . . . . . 4-2
        4.1.7     RELIABILITY (MTBF) . . . . . . . . . . . . . . . 4-2
        4.1.8     CABLING  . . . . . . . . . . . . . . . . . . . . 4-3
        4.1.9     MODULE INTERCHANGEABILITY  . . . . . . . . . . . 4-3
        4.1.10    MODULE EXTENDIBILITY . . . . . . . . . . . . . . 4-3

CHAPTER 5       ADAPTER PERFORMANCE

        5.1     I/O REQUEST LEVEL THROUGHPUT . . . . . . . . . . . 5-1
        5.1.1     DATA BANDWIDTH . . . . . . . . . . . . . . . . . 5-1
        5.1.2     RESPONSE TIME  . . . . . . . . . . . . . . . . . 5-1
        5.1.3     POWER-UP TIMING  . . . . . . . . . . . . . . . . 5-1

CHAPTER 6       POWER ON SELF TESTS

        6.1     PURPOSE  . . . . . . . . . . . . . . . . . . . . . 6-1
        6.2     TESTS PERFORMED  . . . . . . . . . . . . . . . . . 6-2
        6.3     FAILURE ACTION . . . . . . . . . . . . . . . . . . 6-3
        6.4     FUNCTIONS/SECTIONS NOT TESTED  . . . . . . . . . . 6-3
        6.5     TEST GOALS . . . . . . . . . . . . . . . . . . . . 6-3

CHAPTER 7       DSA SUPPORT

        7.1     MSCP, TMSCP, DUP . . . . . . . . . . . . . . . . . 7-1
        7.1.1     OVERVIEW . . . . . . . . . . . . . . . . . . . . 7-1
        7.1.2     RELATED ECOS . . . . . . . . . . . . . . . . . . 7-1
        7.1.3     ERROR LOGS . . . . . . . . . . . . . . . . . . . 7-1
        7.2     UQSSP  . . . . . . . . . . . . . . . . . . . . . . 7-1
        7.2.1     COMPLIANCE . . . . . . . . . . . . . . . . . . . 7-1
        7.2.2     MAINTENANCE READ/WRITE . . . . . . . . . . . . . 7-1
        7.2.3     U/Q PORT GENERIC SA ERROR CODES  . . . . . . . . 7-2
        7.2.4     DSSI ADAPTER SPECIFIC SA ERROR CODES . . . . . . 7-2

KFQSA Functional Specification  (Company Confidential)          Page 4
                                                      14 December 1987

CHAPTER 8       MAINTENANCE READ/WRITE REQUESTS

        8.1     OVERVIEW . . . . . . . . . . . . . . . . . . . . . 8-1
        8.2     COMMAND FORMAT . . . . . . . . . . . . . . . . . . 8-2
        8.2.1     FIELD DEFINITIONS  . . . . . . . . . . . . . . . 8-2
        8.3     END PACKET FORMAT  . . . . . . . . . . . . . . . . 8-6
        8.3.1     FIELD DEFINITIONS  . . . . . . . . . . . . . . . 8-6
        8.4     OTHER ERRORS . . . . . . . . . . . . . . . . . . . 8-8
        8.4.1     PORT GENERIC ERROR CODES . . . . . . . . . . . . 8-8
        8.4.2     KFQSA SPECIFIC ERROR CODES . . . . . . . . . . . 8-8
        8.4.3     ERROR RECOVERY . . . . . . . . . . . . . . . . . 8-8
        8.5     TARGET NODE MAINTENANCE OPERATIONS . . . . . . . . 8-8
        8.6     MAINTENANCE REGIONS  . . . . . . . . . . . . . .  8-10
        8.6.1     68000 RAM REGION . . . . . . . . . . . . . . .  8-10
        8.6.2     68000 LOCAL RAM REGION . . . . . . . . . . . .  8-10
        8.6.3     68000 ROM REGION   . . . . . . . . . . . . . .  8-10
        8.6.4     DUAL PORT RAM REGION . . . . . . . . . . . . .  8-10
        8.6.5     68000 BUFFER RAM REGION  . . . . . . . . . . .  8-10
        8.6.6     68000 BUGCHECK ERROR LOG PACKET REGION . . . .  8-10
        8.6.7     8096 BUGCHECK ERROR LOG PACKET REGION  . . . .  8-11
        8.6.8     MANUFACTURING TEST REGION  . . . . . . . . . .  8-11
        8.6.9     DATA LINK PERFORMANCE COUNTERS REGION  . . . .  8-12
        8.6.10    SOFT RESET REGION  . . . . . . . . . . . . . .  8-13
        8.6.11    PORT PERFORMANCE COUNTERS REGION   . . . . . .  8-14
        8.6.12    SCS CONNECTION STATE REGION  . . . . . . . . .  8-16
        8.6.13    68000 ERROR LOG PACKET REGION  . . . . . . . .  8-16
        8.6.14    8096 ERROR LOG PACKET REGION . . . . . . . . .  8-16
        8.6.15    VIRTUAL CIRCUIT BLOCK  . . . . . . . . . . . .  8-18
        8.6.16    8096 LOCAL RAM . . . . . . . . . . . . . . . .  8-19
        8.6.17    8096 ROM   . . . . . . . . . . . . . . . . . .  8-20
        8.6.18    8096 CONFIGURATION REGION  . . . . . . . . . .  8-20
        8.6.18.1    FIELD DEFINITIONS FOR CONFIGURATION TABLE  .  8-21
        8.6.18.2    PROCEDURE FOR UPDATING CSR ADDRESSES . . . .  8-22
        8.6.19    8096 EEROM REGION  . . . . . . . . . . . . . .  8-23
        8.6.20    8096 SYSTEM PARAMETERS REGION  . . . . . . . .  8-23
        8.6.21    8096 TEST REGION . . . . . . . . . . . . . . .  8-24
        8.6.22    CONFIGURATION TABLE RESET  . . . . . . . . . .  8-24
        8.6.23    8096 USABLE CSR WORD REGION  . . . . . . . . .  8-24
        8.6.24    8096 I/O PORT REGION . . . . . . . . . . . . .  8-25

CHAPTER 9       ERROR LOG FORMATS

        9.1     HOST MEMORY ACCESS ERROR - ERROR LOG FORMAT  . . . 9-1
        9.2     GENERIC KFQSA ERROR - ERROR LOG FORMAT . . . . . . 9-1
        9.3     FORMAT OF 8096 ERROR LOG PACKETS . . . . . . . . . 9-4
        9.3.1     FORMAT FOR 8096 ERROR LOG FOR DMA ERROR  . . . . 9-4
        9.3.2     FORMAT FOR 8096 BUGCHECK ERROR LOG   . . . . . . 9-6
        9.4     68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS . . . 9-9
        9.4.1     68000 ERROR LOG FORMAT 3 . . . . . . . . . . . . 9-9
        9.4.2     68000 ERROR LOG FORMAT 4 . . . . . . . . . . .  9-10
        9.4.3     68000 ERROR LOG FORMAT 5 . . . . . . . . . . .  9-11
        9.4.4     68000 ERROR LOG FORMAT 6 . . . . . . . . . . .  9-12
        9.4.5     68000 ERROR LOG FORMAT 7 . . . . . . . . . . .  9-13

KFQSA Functional Specification  (Company Confidential)          Page 5
                                                      14 December 1987

        9.4.6     68000 ERROR LOG FORMAT 8 . . . . . . . . . . .  9-14
        9.4.7     68000 ERROR LOG FORMAT 9 . . . . . . . . . . .  9-16
        9.4.8     FORMAT OF 68000 BUGCHECK ERROR LOG (FORMAT 10)  9-18
        9.4.9     68000 ERROR LOG FORMAT 11  . . . . . . . . . .  9-21
        9.4.10    68000 ERROR LOG FORMAT 12  . . . . . . . . . .  9-22

APPENDIX A      POST/LED ERROR CODES

APPENDIX B      STANDARD UQSSP ERROR CODES

APPENDIX C      KFQSA SPECIFIC SA ERROR CODES 

APPENDIX D      MAINTENANCE REGIONS 

APPENDIX E      ERROR LOG CONTROLLER FORMAT CODES

APPENDIX F      8096 ERROR LOG REASON CODES 

APPENDIX G      68000 SA ERROR SUB CODES

APPENDIX H      CONNECTION ID VALUES

APPENDIX I      SCS CONNECTION STATES

APPENDIX J      REVISION HISTORY



                               CHAPTER 1

                              INTRODUCTION

      1.1  SCOPE

      This document is the functional specification for the  KFQSA  host
      adapter.   The  KFQSA  adapter  provides the interface between the
      Q-Bus and the new DSSI (Digital Small Storage Interconnect) bus.

      It is not intended for this specification to document the internal
      operation and design of the adapter, these details may be found in
      the related specifications listed below.  The primary goal  is  to
      present a summary of the KFQSA adapter for system integrators.

      1.2  REFERENCE AND RELATED DOCUMENTS

       o  Systems Communications Architecture, August 1985.

       o  VAX-11 CI Port Architecture, Rev 4.0, December 1981.

       o  SII Specification, Rev.  1.3, December 1986.

       o  Digital's Small Storage Interconnect, an Addendum to  DEC  Std
          161, Version X1.0, January 1987.

       o  Computer Interconnect Specification, Rev 2.0, November 1981.

       o  UNIBUS/QBUS Storage Systems Port; Revision 2.0.3.

       o  Mass Storage Control Protocol; Revision 1.2.

       o  KFQSA Power On Self Test Functional Spec, Rev.  1.0,  December
          1986.

       o  KFQSA Hardware Functional Specification,  Rev.   1.2,  January
          1988.

       o  KFQSA Firmware Top level Design  Specification,  February  20,
          1987.

KFQSA Functional Specification  (Company Confidential)        Page 1-2
REFERENCE AND RELATED DOCUMENTS                       14 December 1987

       o  KFQSA MDM Diagnostic Specification, Rev.  0.06, December 1986.

       o  Diagnostic  Engineering  Project   Plan   for   PDP-11   KFQSA
          Subsystem, Rev.  1.0, December 1986.

       o  Error  Specification  KFQSA  Power-On  Self  test,  Rev   0.2,
          February 1987.

      1.3  PRODUCT OVERVIEW

      The KFQSA is a high performance Qbus to DSSI bus storage  adapter.
      This  adapter allows up to 7 DSSI compatible storage devices to be
      attached to the DSSI bus and to communicate with a Qbus based host
      computer.   The  KFQSA  will  be  the  first  host  adapter  to be
      implemented under the DSSI architecture and will be  developed  in
      parallel with the RF disk drives.

      1.4  TARGET SYSTEMS

      The KFQSA is intended to operate on the CVAX and uVAX2  and  PDP11
      systems.   The KFQSA is specifically not intended for use on uVAX1
      systems and other systems that require memory mapping (as  defined
      for the Qbus under UQSSP).

KFQSA Functional Specification  (Company Confidential)        Page 1-3
TARGET SYSTEMS                                        14 December 1987

      1.4.1  MAIN FEATURES

           DEVICE TYPES SUPPORTED         DISK,TAPE,OPTICAL      
         
           INITIAL DEVICE  AT FRS         RF-71
                                                
           STORAGE BUS INTERFACE          DSSI                  

           DSA COMPATIBILITY              UQSSP
                                          MSCP Devices
                                          TMSCP Devices
                                          DUP 
                                    
           Q-BUS INTERFACE                Statically Configurable SA/IP
                                          registers per peripheral device
                                          (up to maximum of 7).
                                          UQSSP Compatible.

           MAX DEVICES/ADAPTER            7

           DSSI BUS PEAK TRANSFER RATE    3.5-4 MB/sec burst                 

           ADAPTER I/O PERFORMANCE        150 I/O Reqs/sec (512 byte
           GOALS                          transfers)

                                          1.3-1.5 MBytes/sec (64Kbyte
                                          transfers)
        
           ERROR DETECTION                DSSI Bus Parity and Check 
                                          Character on all transmissions.

                                          Adapter Byte Parity on Internal
                                          Buffer

                                          Qbus Parity Requirements as 
                                          specified in DEC Std 160.
             
           FORM FACTOR                    QUAD

           MTBF                           100,000 HRS in typical customer
                                          environment (long term steady state).

      The KFQSA Specifically Does Not Provide:

       o  Memory mapping on the Qbus interface


KFQSA Functional Specification  (Company Confidential)        Page 1-4
PRODUCT MOTIVATION                                    14 December 1987

      1.5  PRODUCT MOTIVATION

      The KFQSA allows interfacing of  new  generation  DSSI  compatible
      peripherals to the Q-Bus.

      1.6  CONFIGURATION SUPPORT

      1.6.1  CONFIGURATIONS AT FRS

      For  FRS  the  following  configurations  will  be  supported  and
      formally qualified:

       o  One KFQSA on the Qbus,  one  DSSI  bus  with  only  one  drive
          attached.

       o  One KFQSA on the Qbus, one DSSI bus with multiple  drives  (up
          to 7) attached.

       o  Two KFQSAs on the Qbus, two DSSI buses  with  only  one  drive
          attached to each.

       o  Two KFQSAs on the Qbus, two DSSI buses  with  multiple  drives
          (up to 7) attached.

       o  The  above  configurations  with  both  disk  and  tape  drive
          combinations.



                               CHAPTER 2

                              ARCHITECTURE

      2.1  OVERVIEW

      The KFQSA host adapter will conform to  the  requirements  of  the
      DSSI  architecture document listed in the references section.  The
      KFQSA is a host adapter, not a controller, and as such it will not
      contain specific software for the interpretation of MSCP, TMSCP or
      DUP packets.  The servers  necessary  for  the  interpretation  of
      these packets reside in the individual peripheral devices.

      The KFQSA primarily provides UQSSP to DSSI protocol conversion and
      message routing services.

                              KFQSA SYSTEM OVERVIEW

                +---------+        +---------+          +---------+
                |         |        |         |          | DRIVE 0 |
                |         |        |         |          |---------|
                |  HOST   |/------\|  KFQSA  |/--------\| DRIVE 1 |
                | COMPUTER|  QBUS  | ADAPTER | DSSI BUS |---------|
                |         |\------/|         |\--------/| DRIVE 2 |
                |         |        |         |          |---------|
                |         |        |         |          | DRIVE 3 |
                +---------+        +---------+          |---------|
                                                        | DRIVE 4 |
                                                        |---------|
                                                        | DRIVE 5 |
                                                        |---------|
                                                        | DRIVE 6 |
                                                        +---------+


KFQSA Functional Specification  (Company Confidential)        Page 2-2
GENERAL INFORMATION                                   14 December 1987

      2.2  GENERAL INFORMATION

      2.2.1  DSA/DSSI ARCHITECTURE COMPLIANCE

      The KFQSA adapter  will  comply  with  all  of  the  architectural
      requirements  specified  by  the  Addendum to DEC Std 161 with the
      following restrictions.

      1.  Each SA/IP path supports a  concurrent  maximum  of  one  MSCP
          server and one DUP server connection.

      2.  The  adapter  overall  supports  a  maximum  of   seven   MSCP
          connections and seven DUP connections.

      3.  Additional restrictions listed for the KFQSA in  the  Addendum
          to Dec Std 161.

      2.3  FUNCTIONAL ELEMENTS OF THE SYSTEM

      2.3.1  OVERVIEW

      The major architectural elements of the system are defined by  the
      KFQSA  firmware.   The firmware defines 5 major functional modules
      in the KFQSA.  These modules are:

       o  U/Q Port

       o  Systems Communications Architecture (SCA)

       o  DSSI Port

       o  Maintenance

       o  Power On Self-Test (POST)

      The U/Q Port module runs on the 8096 processor and with  the  help
      of  hardware  implements  the complete UQSSP Qbus interface to the
      host.

      The SCA module implements the features and  functions  defined  by
      SCA.   This  module contains three pieces, a connection manager, a
      systems communication service and an port to port driver.

      The DSSI Port module implements the features and functions defined
      by the CI Port and DSSI specifications.  It contains two pieces, a
      Port and a Data Link.

      The Maintenance module implements the system maintenance read  and
      write   functionality,   including   adapter   DSSI  configuration
      management.

KFQSA Functional Specification  (Company Confidential)        Page 2-3
FUNCTIONAL ELEMENTS OF THE SYSTEM                     14 December 1987

      POST  performs  integrity  checks  on  the   adapter   board   and
      initializes  the  hardware to a known state before passing control
      to the operational microcode.

      2.3.2  BUFFER ALLOCATION

      The buffer space to be  allocated  within  the  KFQSA  adapter  is
      physically  composed  of  two  parts:  1.  a dual port RAM used in
      part for communicating between the two processors  in  the  KFQSA,
      and  2.   a RAM used for transferring packets and messages through
      the adapter.

      The buffer space available for  inter-processor  communication  is
      comprised of a 16Kbyte dual ported static RAM.

      The  buffer  space  available  for  packet,  message   and   frame
      transferring  and  processing is comprised of 256Kbytes of dynamic
      RAM.

      2.4  CSR CONFIGURATION MECHANISM

      The KFQSA  has  three  modes  of  operation.   Each  mode  uses  a
      different  mechanism  for selecting the QBUS CSR addresses and the
      associated DSSI device.  During power up,  the  KFQSA  checks  the
      Post  Loop  Jumper,  the  Manufacturing  Mode jumper and the 4 DIP
      switches to determine the mode of operation.  Based on  these,  it
      enables  the appropriate CSR addresses, sets their associated DSSI
      IDs, and sets the KFQSA's DSSI Bus ID.

      2.4.1  NORMAL MODE

      This is the standard mode of operation for the KFQSA.   The  SA/IP
      CSR  addresses  (up  to  7  maximum)  presented by the adapter are
      stored in the KFQSA's non-volatile  EEROM.   See  the  Maintenance
      Section  for  the  Configuration  Table Format.  The Configuration
      Table is programmed by a diagnostic utility (for  further  details
      see diagnostic specification).

      2.4.2  SERVICE MODE

      In order  to  provide  the  capability  of  addressing  the  KFQSA
      subsystem  in  situations  where  the  EEROM  is  either  not  yet
      programmed or is corrupted, the KFQSA adapter  employs  a  default

KFQSA Functional Specification  (Company Confidential)        Page 2-4
CSR CONFIGURATION MECHANISM                           14 December 1987

      mechanism.  The default CSR addresses presented are:

       o  17772150 (octal) Primary Disk CSR Address

       o  17774500 (octal) Primary Tape CSR Address

       o  17760344 (octal) Secondary Disk CSR Address

       o  17760444 (octal) Secondary Tape CSR Address

      A four position DIP switch  pack  provides  the  required  default
      information.   The  switch pack is located behind the service LEDs
      for easy access.  These switches are valid  if  the  manufacturing
      mode  jumper  is not installed.  The switch meanings are marked on
      the board beside the  switch.   The  switch  positions  and  their
      meanings are shown below.

                                     +-------+
                                     | .   . |         
                              DISK0  | .   . |  TAPE6
                              P_CSR  | .   . |  S_CSR
                             NORMAL  | .   . |  SERV
                                     +-------+                  

                          Service Mode Switch Assignments

      An explanation of the switch positions follows:

             o  Switch 4 - NORMAL/SERV This switch controls  whether  or
                not  the  configuration table in EEROM will be used.  If
                the switch is in the NORMAL position, switches 2  and  3
                are  ignored  and  CSR addresses are read from the EEROM
                configuration table.  If  the  switch  is  in  the  SERV
                position,  the CSR address and DSSI ID are determined by
                the position of switches 2 and 3.

             o  Switch 3 - PCSR/SCSR This switch determines whether  the
                disk  or tape CSR address will be the primary T/MSCP CSR
                address or a secondary T/MSCP  CSR  address.   Switch  2
                determines  whether  a  disk or tape CSR address will be
                loaded.

             o  Switch 2 - DISK0/TAPE6 This switch determines whether  a
                disk  CSR  address or a tape CSR address will be loaded.
                If the switch is in  the  DISK0  position,  a  disk  CSR
                address  will  be  loaded  with  a DSSI ID of 0.  If the
                switch is inthe TAPE6 position, a tape CSR address  will
                be loaded with a DSSI ID of 6.

KFQSA Functional Specification  (Company Confidential)        Page 2-5
CSR CONFIGURATION MECHANISM                           14 December 1987

             o  Switch 1 - The top switch is reserved for  manufacturing
                mode.

      2.4.3  MANUFACTURING MODE

      If the manufacturing mode jumper is installed on  the  board,  the
      KFQSA presents one CSR Address.  The 4 DIP switch settings specify
      a Board Number and thereby determine the board's CSR  Address  and
      DSSI Bus ID.

              Off                On              Off                On
                      +-------+                          +-------+         
                      | []  . |           (1)            | .  [] |          
              DISK0   | []  . |  TAPE6    (2)    DISK0   | []  . |  TAPE6 
              P_CSR   | []  . |  S_CSR    (3)    P_CSR   | []  . |  S_CSR 
             NORMAL   | []  . |  SERV     (4)   NORMAL   | []  . |  SERV
                      +-------+                          +-------+         

                      (Board 0)                          (Board 1) 

                      Manufacturing Mode Board Assignment Examples

      The table below shows the CSR addresses presented and the DSSI  ID
      for each board.
                     Board Number   CSR Pair     DSSI ID
                     -----------------------------------
                          0       0760340 /342      0
                          1       0760344 /346      1
                          2       0760350 /352      2
                          3       0760354 /356      3
                          4       0760360 /362      4
                          5       0760364 /366      5
                          6       0760370 /372      6
                          7       0760374 /376      7
                          8       0760400 /402      0
                          9       0760404 /406      1
                         10       0760410 /412      2
                         11       0760414 /416      3
                         12       0760420 /422      4
                         13       0760424 /426      5
                         14       0760430 /432      6
                         15       0760434 /436      7

KFQSA Functional Specification  (Company Confidential)        Page 2-6
DSSI NODE ADDRESS MAPPING                             14 December 1987

      2.5  DSSI NODE ADDRESS MAPPING

      2.5.1  DEVICE ID

      The mapping between the DSSI bus address (plus  related  priority)
      of  a  peripheral  device  and  its Qbus CSR address is set by the
      diagnostic configuration  utility  or  by  the  default  mechanism
      above.

      2.5.2  KFQSA DEVICE ID

      The KFQSA may be assigned any  (0-7)  DSSI  Node  Address  by  the
      configuration  diagnostic.   DSSI  node  address 7 has the highest
      DSSI priority.  The Service Mode address is seven.

      2.6  UQPORT INITIALIZATION

      2.6.1  OVERVIEW

      With respect to UQSSP Four Step Initialization Sequence, the KFQSA
      must  satisfy  both an Operating System and Maintenance Diagnostic
      Utility requirement.  From an operating system point of view, port
      initialization  should not complete successfully unless the remote
      drive associated with the port is accessible  to  the  host  class
      driver.  KFQSA Diagnostics require port initialization to complete
      to issue UQ Maintenance commands to examine or alter the adapter's
      configuration  regardless  of  the  current configuration, and the
      existence of a remote devices.

      In Operational Mode,  the  KFQSA  will  not  complete  UQSSP  Port
      Initialization unless a Virtual Circuit is established with a DSSI
      device.  While no communication path exists with the remote  port,
      the  KFQSA  defers  processing  of  host  written  data  in the SA
      Register for nine seconds before  starting  the  next  step.   The
      KFQSA will start Step Four only if a Virtual Ciruit is established
      with the Device.  If the VC is not Open, a  VC  TimeOut  Error  is
      posted  in the SA Register.  This gives DSSI Devices approximately
      27 seconds to establish a Virtual Circuit with the KFQSA.

      In Manufacturing and Service Mode, the KFQSA completes UQSSP  Port
      Initialization  with  or  without  a  DSSI  device  present.   The
      sequence  is  processed  immediately  without  delay.   Any   MSCP
      connection  traffic placed in the Command Ring by the Host in this
      mode  is  left  there  by  the  adapter   until   it   establishes
      communication  (a Virtual Circuit) with the remote device.  In the
      mean time, subsequent Maintenance Connection commands are  blocked
      behind  the  MSCP  connection's packet in the UQ Command Ring.  If
      the VC comes up  (before  a  Class  Driver  timeout  occurs),  the
      adapter  pulls  the MSCP message from the Ring and sends it to the
      remote device.  If the VC does not come up, some operating systems

KFQSA Functional Specification  (Company Confidential)        Page 2-7
UQPORT INITIALIZATION                                 14 December 1987

      will time out the command and write the IP register.

      The adapter should not be in this mode for use by the Customer.

KFQSA Functional Specification  (Company Confidential)        Page 2-8
UQPORT INITIALIZATION                                 14 December 1987

                Operational Mode Init Sequence 
                -------------------------------

      HOST                              KFQSA
      ----                              -----

      Power-up                          No access to SA/IP          <Note 1>     
                                               | 
                                               v
                                        SA Register Presents 0's    <Note 2>
                                               | 
                                               v
      BusInit                 ---->       Diagnostics 
                                               |
      IPWrite                 ---->            v
                              <----     Step 1 Data in SA Register  <Note 3>
      Step 1 Response         ---->            |
                                               | (9 Seconds unless VC) 
                                               v
                              <----     Step 2 Data in SA Register
      Step 2 Response         ----->           |
                                               | (9 Seconds unless VC)
                                               v
                              <----     Step 3 Data in SA Register
      Step 3 Response         ----->           |
                                               | (9 Seconds unless VC)
                                               |
                                               v    (No)      
                                        VC Started? ----> VCTimeOut Error
                                               |(Yes) 
                                               v
                              <----     Step 4 Data in SA Register
      Step 4 Response         ----->           |
                                               v
                                           Path Open

      Note 1:  CSR are accessible 70 usec after powerup.

      Note 2:  SA Register presents Zero's for 100 usec after powerup.

      Note 3:   Step 1 Data is presented within 100 uSec  after  powerup
      and immediately following a Bus Init and IPWrite.

KFQSA Functional Specification  (Company Confidential)        Page 2-9
UQPORT INITIALIZATION                                 14 December 1987

      2.6.2  DETAILS OF INITIALIZATION

      This section describes the values presented in the SA Register  by
      the KFQSA during the standard initialization.

      2.6.2.1  STANDARD INITIALIZATION STEP 1

      The KFQSA  starts  Four  Step  Init  upon  detection  of  PowerUp,
      BusInit,  or an IPWrite condition.  It presents the following Step
      1 data in the SA register:

        Field   Value           Description
        -----   -----           ----------
        S1 =      1             Step 1
        NV =      0             Host settable interrupt vector only
        QB =      1             22 bit QBUS supported
        DI =      0             No Enhanced Diagnostic supported
        OD =      1             Odd Addresses in buffer descriptors supported
        MP =      0             Address Mapping not supported
        SM =      1             Special Function Mode supported

      The Host writes the SA register with the Interrupt Vector Address,
      Length of queues, Diagnostic Wrap Bit, and Interrupt Enable bit.

      2.6.2.2  STANDARD INITIALIZATION STEP 2

      The KFQSA writes the SA register with the following value:

        Field           Value           Description
        -----           -----           ----------
        S2        =       1             Step 2
        Port Type =       0             Port Type 
        WR        =       x             WR Bit echoed from Step 1 Response
        C Que Len =       x             Echoed from Step 1 Response
        R Que Len =       x             Echoed from Step 1 Response

      The Host writes the SA register with the  Communication  Base  Low
      Address

      2.6.2.3  STANDARD INITIALIZATION STEP 3

      The KFQSA writes the SA register with the following value:

        Field           Value           Description
        -----           -----           ----------
        S3        =       1             Step 3
        IE        =       x             IE bit echoed from Step 1 Response

KFQSA Functional Specification  (Company Confidential)       Page 2-10
UQPORT INITIALIZATION                                 14 December 1987

        Int Vector=       x             Echoed from Step 1 response

      The Host writes the SA register with the  Communication  Base  Low
      Address

      2.6.2.4  STANDARD INITIALIZATION STEP 4

      The KFQSA writes the SA register with the following value:

        Field           Value           Description
        -----           -----           ----------
        S4        =      1              Step 4
        Model*    =     20              DSSI Disk + DUP
                        21              DSSI Tape + DUP
                        22              DSSI Disk + Tape + DUP
                        23              DSSI Other
        Vers      =      x              KFQSA microcode version number

      The host then completes step 4 by writing into the SA Register the
      LF flag, the Go flag, and the Burst Size **.

      * The Model Number is read from the KFQSA configuration  table  in
      EEPROM.

      ** The Burst Size is not used by the KFQSA, the KFQSA does 16 word
      DMA  bursts  on the QBUS if no other device is requesting the bus,
      otherwise it does 8 word bursts and gets off the bus.     

      2.6.3  UQPORT DIAGNOSTIC FACILITIES

      This section describes the diagnostics facilities built  into  the
      initialization  sequence.   See  section  Power  On Self Test, for
      details of POST Diagnostics.

      2.6.3.1  DIAGNOSTIC WRAP MODE

      Diagnostic wrap is supported  to  provide  a  means  of  low-level
      testing  of  configured  SA  Registers.   This is a deviation from
      UQSSP, since the KFQSA does not support Enhanced Diagnostics.  See
      UQSSP document for programming requirements.

KFQSA Functional Specification  (Company Confidential)       Page 2-11
UQPORT INITIALIZATION                                 14 December 1987

      2.6.3.2  PURGE POLL TEST

      Purge Poll Test is not supported on the KFQSA.  It posts  an  INIT
      Sequence SA Error if the Purge/Poll bit is set by the Host in Step
      3.

      2.6.3.3  HOST MEMORY AND BUS TEST

      The KFQSA verifies access to the Host  Communication  Area  during
      Step3.   This  is done by writing zero's to this comm area, then a
      read/compare.  Failures reported to the host during this test  are
      Posted in the SA Register.

      2.6.3.4  LAST FAIL ERROR PACKETS

      The KFQSA will generate one Last Fail Packet for every Port  Fatal
      Error  Code  posted  in the SA Register.  If the Last Fail Flag is
      set in Step4 and there is a Last Fail, the KFQSA will  deliver  it
      as the first entry in the response ring.  See Errorlog Section for
      packet formats and descriptions.

      2.6.3.5  SPECIAL FUNCTION MODE

      Special Function Mode is a means for Host Diagnostics  to  execute
      the KFQSA's Power On Self Test.

      1.  The Host requests execution of POST, setting  the  SM  and  Go
          Bits during Step 4 of the Init Sequence.

      2.  The KFQSA will respond by presenting 0FFFFH in the SA Register
          within  one  second  of  the  Host  Response  to Step 4.  This
          signals the Host that POST is starting.

      3.  The KFQSA will respond with either 0 in  the  SA  Register  if
          POST is successful, or 08xxxH if POST Fails.  See POST section
          for timing specifications.

      4.  The Host may then restart the Initialization Sequence.

      2.7  ERROR HANDLING

      The KFQSA  will  implement  all  error  handling  requirements  as
      described in the Addendum to DEC Std 161.  Errors will be reported
      to the host through SA register error codes and Last Fail packets.

KFQSA Functional Specification  (Company Confidential)       Page 2-12
ERROR HANDLING                                        14 December 1987

      Other,  non-fatal errors are accumulated by the adapter and can be
      accessed by special UQSSP maintenance  read/write  commands.   The
      diagnostic  package  provides  access to this information.  The SA
      register error codes are provided in appendices B and C.

      2.7.1  QBUS ERRORS

      All Qbus errors will be reported to the host through the use of SA
      register   error   codes.   These  error  codes  are  provided  in
      appendices B and C.

      2.7.2  DSSI ERRORS

      Retries of recoverable DSSI bus errors  will  be  performed.   All
      fatal DSSI errors are reported in the SA Register.  See Appendix C
      for SA Error Codes.


                               CHAPTER 3

                          HARDWARE DESCRIPTION

      3.1  HARDWARE OVERVIEW

      The design philosophy of the KFQSA  hardware  is  one  of  maximum
      integration to produce a cost effective, quad sized module.

      The KFQSA hardware is comprised of four main sections:

      1.  Q-Bus Interface and Control
      2.  8096 Microcontroller Subsystem
      3.  68000 Microprocessor Subsystem
      4.  DSSI interface

      Each of these functional areas is briefly  described  below.   For
      more  detailed information, refer to the KFQSA Hardware Functional
      Specification.

      3.2  HARDWARE FUNCTIONALITY

      3.2.1  Q-BUS INTERFACE AND CONTROL

      This section provides Q-Bus DMA capability (KFQSA as Master),  and
      Host accessibility to the 7 CSR registers (KFQSA as Slave).

      The main components of the Q-Bus Interface are:

       o  Q-Bus Protocol Control,  comprised  of  3  Programmable  Logic
          Arrays  (PALs),  which  handle  the actual Q-Bus data transfer
          protocol for DMA operations,  and  also  implement  the  Q-Bus
          holdoff timer.

       o  CSRD Gate Array.  The CSRD provides three main functions:

          1.  Q-Bus  address  decoding  and   CSR   register   selection
              (generates  7  CSR  select  lines  to  QMI) for Host SA/IP
              accesses

KFQSA Functional Specification  (Company Confidential)        Page 3-2
HARDWARE FUNCTIONALITY                                14 December 1987

          2.  contains   bi-directional   ring   registers   for   UQSSP
              Command/Response Descriptor transfers

          3.  provides 8096 address decoding and wait-state control

       o  QMI Gate Array.  The QMI provides several functions:

          1.  Q-Bus/Buffer-RAM and Q-Bus/Ring-Register DMA Control

          2.  contains 7 SA/IP registers and status

          3.  minimal UQSSP 4-step initialization support

          4.  Q-Bus parity and programmable slave-reply timer

      3.2.2  8096 MICROCONTROLLER SUBSYSTEM

      The  8096  microcontroller  implements  the  UQSSP  protocol   and
      controls  Host-KFQSA  DMA  operations by programming the QMI.  The
      8096 subsystem includes:

       o  12 MHz 8096 microcontroller
       o  16kx16 EPROM
       o  256x8 EEPROM
       o  6 on-board LEDs:  5 red, 1 green, to indicate power-up,  test,
          and error conditions
       o  4   on-board   8096   readable   switches   to   control   CSR
          configuration, and manufacturing test setup.
       o  8kx16   dual-port   RAM   for    8096-68000    inter-processor
          communication (shared with 68000)

      3.2.3  68000 MICROPROCESSOR SUBSYSTEM

      The 68000 microprocessor provides the intelligence  for  the  DSSI
      interface.  The 68000 controls movement of data between the Buffer
      RAM and  the  DSSI,  and  the  generation/removal  of  appropriate
      headers.  This subsystem includes:

       o  10MHz 68000 microprocessor
       o  64kx16 EPROM
       o  8kx16 scratch RAM
       o  4-channeled vectored interrupt controller
       o  10 usec bus error timer
       o  8kx16   dual-port   RAM   for    68000-8096    inter-processor
          communication (shared with 8096)

KFQSA Functional Specification  (Company Confidential)        Page 3-3
HARDWARE FUNCTIONALITY                                14 December 1987

      3.2.4  DSSI INTERFACE AND CONTROL

      The DSSI Interface section includes the following:

       o  DSSI Driver/Receiver Chip to buffer all signals  on  the  DSSI
          cable.

       o  SII gate array, which implements the primary functionality  of
          the DSSI Architecture Data Link layer.

       o  FIFO gate array.  The FIFO gate array includes:

           o  an 8-word byte-aligned FIFO to buffer Q-Bus DMA transfers

           o  Buffer RAM arbitration to arbitrate requests  between  the
              QMI, SII, and the 68000 for Buffer RAM access

           o  Control for Buffer RAM and data paths.

       o  256 kByte Dynamic Buffer RAM.  The Buffer RAM  is  used  as  a
          storage  for packets in transfer between the Host and the DSSI
          peripheral.  Byte parity generation/detection is  provided  on
          entire Buffer space.

       o  10 msec DSSI Timer

      3.3  BUS PERFORMANCE AND FEATURES

      3.3.1  Q-BUS PERFORMANCE AND FEATURES

       o  Burst Mode DMA (16 words/burst max)

       o  2.7 MByte/sec instantaneous burst rate

       o  2.2 MByte/sec max burst rate (1 usec Host DMA latency,  0 usec
          holdoff between bursts)

       o  1.4 MByte/sec max burst rate (1 usec Host DMA latency,  4 usec
          holdoff between bursts)

       o  Odd-byte-aligned transfers supported

       o  Minimal Qbus  parity  checking  and  generation  supported  as
          specified in DEC STd 160.


KFQSA Functional Specification  (Company Confidential)        Page 3-4
BUS PERFORMANCE AND FEATURES                          14 December 1987

      3.3.2  DSSI INTERFACE FEATURES

       o  Single ended bus conforming to Digital Small System Electrical
          and Physical Specification, V0.0, June 5, 1987.

       o  Synchronous DSSI operation at 3.5 to 4 MBytes/sec burst with 4
          bytes maximum offset as provided by SII gate array.



                               CHAPTER 4

                         PHYSICAL SPECIFICATION

        Product Designation     M7769
        
        Mounting Code           MOD

        Dimensions              Standard Quad Module (DEC STD 030)
                                0.5" max height

        Weight                  1.2 lbs

      4.1  ENVIRONMENTAL

      The KFQSA adheres to DEC Standard  102  as  a  device  capable  of
      operating   in   a   class  C  environment,  although  the  actual
      environment is usually  limited  by  the  devices  to  which  this
      adapter interfaces.

      4.1.1  POWER DISSIPATION

       o  22 Watts (typ)

       o  27 Watts (max)

                                     NOTE

              The  above  numbers  do  not  include   DSSI   Bus
              terminator power.

      4.1.2  TEMPERATURE RANGE


KFQSA Functional Specification  (Company Confidential)        Page 4-2
ENVIRONMENTAL                                         14 December 1987

       o  +5 to +50 degrees C operating.

       o  -40 to +66 degrees C storage.

      4.1.3  HUMIDITY

      10% to 95% non-condensing for both operating and storage.

      4.1.4  ALTITUDE

       o  8,000 ft (2.4 Km) operating.

       o  30,000 ft (9.1 Km) storage.

                                       NOTE

                  De-rate the maximum operating  temperature  by
                  1.8 degrees C for each 1000 meters of altitude
                  unless constant cooling  is  provided  as  air
                  density changes with altitude.

      4.1.5  POWER REQUIREMENTS

        +5VDC +/- 5%            4.4 Amps (typ)

      4.1.6  Q-BUS LOADING

          DC Load     -     0.5 unit loads

          AC Load     -     3.8 unit loads

      4.1.7  RELIABILITY (MTBF)

        Class A                 97KHrs
        
        Class B                 66KHrs


KFQSA Functional Specification  (Company Confidential)        Page 4-3
ENVIRONMENTAL                                         14 December 1987

        Class C                 41 KHrs
        
      A goal of 100K hours MTBF has been established  for  ORA  when  in
      steady-state production.  (TBD quarters after FRS).

      4.1.8  CABLING

      A 50 pin header type 12-21545-03 is provided on the  top  edge  of
      the PCB for connection to the DSSI Cable.

      4.1.9  MODULE INTERCHANGEABILITY

      All KFQSA modules will be fully interchangeable (although  address
      programming may be required).

      4.1.10  MODULE EXTENDIBILITY

      The KFQSA module is not extendible.


                               CHAPTER 5

                          ADAPTER PERFORMANCE

      The following performance data does  not  take  into  account  the
      delays or throughput limitations of either host operating systems,
      the DSSI bus or peripheral devices.  In order  to  describe  KFQSA
      performance alone, an "idealized" environment is assumed.

      5.1  I/O REQUEST LEVEL THROUGHPUT

      The KFQSA adapter goal is to support 150 I/O requests  per  second
      (512 byte requests).

      5.1.1  DATA BANDWIDTH

      The KFQSA adapter goal is to allow for the continuous transfer  of
      1.3-1.5 Mbytes of data per second (64Kbyte requests).

      5.1.2  RESPONSE TIME

      The net delay contributed by the KFQSA to the completion of a MSCP
      read  command  (512 byte) across the entire subsystem will be <6.6
      msec over an "ideal" (zero delay) adapter.

      5.1.3  POWER-UP TIMING

      The KFQSA will comply with UQSSP  requirements.   In  addition  it
      will be ready to process UQSSP and DSSI commands within 12 seconds
      of start of power up or bus init.


                               CHAPTER 6

                          POWER ON SELF TESTS

      6.1  PURPOSE

      The purpose of the KFQSA Power On Self Tests (POST) is to  perform
      a  comprehensive self test of the adapter logic.  POST executes at
      system start-up time or in response to a bus init from  the  host.
      To   comply   with  timing  constraints  posed  by  the  U/Q  Port
      initialization sequence, execution time will  be  less  than  nine
      seconds.

      The hardware on the KFQSA adapter is divided into two regions; one
      controlled  by the 8096 microprocessor and the other controlled by
      the 68000 microprocessor.  POST is uniquely designed to execute in
      parallel on the microprocessors and thus reduce the time needed to
      test the board.  The microprocessors communicate with  each  other
      via  inter-processor  interrupts  and  the  Dual Ported RAM.  POST
      tests all the adapter hardware excluding the QBUS  state  machine,
      the  QBUS  transceivers  and  the  DSSI transceivers as testing of
      these devices would require special external loopback hardware.

      The interface between POST  and  functional  firmware  is  clearly
      defined  for  both  microprocessors.   POST  synchronizes  the two
      microprocessors  and  tests  communication  between  them   before
      turning control of the adapter over to functional firmware.

      The majority of POST consists  of  go/no-go  tests.   Any  failure
      encountered  during  one  of these tests causes termination of the
      test sequence and results  in  "hanging"  the  microprocessors  to
      safeguard  the devices.  It is possible for some tests to fail and
      still allow the adapter to  function  in  a  degraded  mode.   For
      example,  a discrete port error in one of the 7 SA registers would
      be considered a non-fatal error and the adapter would  be  allowed
      to function even though this error had been detected.

      A complete status of POST will be displayed on the adapter's LED's
      and  contained  in  all SA registers if the adapter fails its self
      test.  The SA registers may be read from the host  console  or  by
      the host diagnostic program.

      POST determines which SA registers in the QMI chip and  which  CSR
      address  registers  in the CSRD chip are working.  After examining

KFQSA Functional Specification  (Company Confidential)        Page 6-2
PURPOSE                                               14 December 1987

      the CSR/DSSI address configuration enable in EEROM, POST  sets  up
      the  CSRD and QMI for functional operation.  The CSR decode enable
      bits in the CSRD Control register are set  with  a  bit  map  that
      determines  which  accesses  to  the  SA/IP register pairs will be
      recognized.  The software enable register in the  QMI  is  set  up
      with a bit map that determines which SA registers will not be seen
      by the HOST (a bit cleared in  the  SWEN  register)  or  which  SA
      registers  will  respond  to HOST communications (a bit set in the
      QMI SWEN register).

      Only ports with valid CSR/DSSI addresses and working hardware  are
      set up.

      EEROM contains the last fatal error and last non-fatal error codes
      that  may  be  read  by the host diagnostics via UQSSP maintenance
      read commands.

      6.2  TESTS PERFORMED

      POST consists of the following tests:

      1.  Microprocessor basic sanity check - test ALU, condition flags,
          and    internal    general    purpose    registers   of   both
          microprocessors.

      2.  ROM tests  -  each  microprocessor  reads  all  addresses  and
          calculates and verifies the checksums on each ROM.

      3.  RAM tests - the 8096 tests the Dual  Ported  RAM.   The  68000
          tests  its local RAM as well as the Buffer RAM and Dual Ported
          RAM.  All RAM tests include ability to  address  RAM  and  bit
          cell integrity tests using a five step March algorithm.

      4.  EEROM test - the 8096 performs checksum tests on CSR addresses
          stored in EEROM.

      5.  Gate array tests - bit cell integrity tests are  performed  on
          internal  gate  array  registers  and  internal  counters  are
          clocked through transition states.  The 8096 tests the QMI and
          CSRD  gate  arrays;  the  68000  tests  the  FIFO and SII gate
          arrays.

      6.  Timer tests - the 68000 checks the  DSSA  onboard  timers  for
          correct functioning.

      7.  Interrupt tests - each microprocessor  checks  interrupts  for
          correct vectoring.

      8.  Microprocessor  communication  tests  -  the   microprocessors
          synchronize  themselves  and  communicate with one another via
          interprocessor interrupts and flags written to and  read  from
          the Dual Ported RAM.

KFQSA Functional Specification  (Company Confidential)        Page 6-3
FAILURE ACTION                                        14 December 1987

      6.3  FAILURE ACTION

      The KFQSA adapter includes  one  green  and  five  red  LEDs.   On
      power-up  all  LEDs  are lit.  As tests begin to execute, LEDs are
      extinguished.  A successful completion of POST  leaves  the  green
      LED  lit  and the red LEDs off.  If Post detects a fatal error, it
      posts an error code in the five red LEDs with the green  LED  off.
      If  a  non-fatal  error  is  detected,  a  non-fatal error code is
      displayed in the red LEDs  (leaving  the  green  LED  lit)  for  a
      minimum  of  ten  seconds.  The LEDs are mounted on the board edge
      for maximum visibility.

      Upon detection of a failure an error code will also be  posted  in
      the  SA  registers.   Error  codes  will either be port-generic or
      adapter specific (see appendices A and B).  On  fatal  error,  the
      microprocessors  will  be  forced  into  an  infinite loop type of
      instruction sequence which can only be broken by receiving an init
      from the HOST.

      Fatal and non-fatal error codes are  written  into  the  EEROM  in
      order to supply an error history.

      6.4  FUNCTIONS/SECTIONS NOT TESTED

      POST does not test the following:

      1.  The Qbus transceivers.

      2.  The DSSI transceivers.

      6.5  TEST GOALS

      1.  Coverage - 85% via resident microdiagnotics (determined by  IC
          count).

      2.  Fault Isolation - The adapter will be identified as the  Field
          Replaceable  Unit  (FRU).   Due  to test partitioning, sub-FRU
          isolation may be implied for some errors.

      3.  Execution Time - less than nine seconds.

      4.  Operator Interface - LEDs and error codes in the SA  registers
          (see appendix).



                               CHAPTER 7

                              DSA SUPPORT

      7.1  MSCP, TMSCP, DUP

      7.1.1  OVERVIEW

      MSCP, TMSCP and DUP messages are  not  interpreted  in  the  KFQSA
      adapter.   These messages are used by the devices connected to the
      adapter.  The adapter primarily supports the routing  and  passage
      of packets to DSSI bus devices.

      7.1.2  RELATED ECOS

      ECO   MSCP13-5 (assignment of UQSSP/DSSI Generic Device) and ECO  
      MSCP13-6  (assignment  of RF30 and RF70 Drive Model Values) should
      be referenced as required for KFQSA specific MSCP information.

      7.1.3  ERROR LOGS

      The KFQSA supports delivery of Device generated ErrorLogs  to  the
      Host System.

      7.2  UQSSP

      7.2.1  COMPLIANCE

      The KFQSA will comply fully with the requirements of  version  2.2
      of the UQSSP.

      7.2.2  MAINTENANCE READ/WRITE

      The standard  UQSSP  maintenance  read/write  operations  will  be
      supported  by  the  KFQSA  adapter  to  allow  access  to the DSSI
      performance  counters   and   for   SA/IP   register   programming

KFQSA Functional Specification  (Company Confidential)        Page 7-2
UQSSP                                                 14 December 1987

      operations.

      For further definition of the format of these  commands,  see  the
      chapter on Maintenance Read/Write requests.

      7.2.3  U/Q PORT GENERIC SA ERROR CODES

      See Appendix B

      7.2.4  DSSI ADAPTER SPECIFIC SA ERROR CODES

      See Appendix C.


                               CHAPTER 8

                    MAINTENANCE READ/WRITE REQUESTS

      8.1  OVERVIEW

      (For a detailed description, the reader should refer to the  UQSSP
      specification for Maintenance Read/Write commands.)

      Maintenance Commands in the KFQSA are used for performing setup of
      the  board's  I/O page addresses, as well as obtaining information
      about the board; the commands provide  the  host  with  visibility
      into  the  adapter's  internal  data  structures  and  performance
      counters.  All  Maintenance  commands  are  "intercepted"  by  the
      KFQSA;  thus,  any DSSI device must not rely on these commands for
      any reason.  Maintenance Commands may be directed to any  "active"
      port  on  the  KFQSA.   ("Active" is any port for which there is a
      valid CSR address and functioning support hardware.) In  addition,
      maintenance requests may be freely intermixed with data requests.

KFQSA Functional Specification  (Company Confidential)        Page 8-2
COMMAND FORMAT                                        14 December 1987

      8.2  COMMAND FORMAT

      All Maintenance commands use the following packet format:

        15              8 7              0
        +----------------+----------------+
        |          Message Length         |
        +----------------+--------+-------+
        |   Conn ID      | MSTYP  | CRDTS |
        +----------------+--------+-------+
        |                              LSW|
        +---  Command Reference Number ---+
        |                              MSW|
        +---------------------------------|
        |             Undefined           |
        +---------------------------------+
        |             Undefined           |
        +----------------+----------------+
        |    Reserved    |     Opcode     |
        +----------------+----------------|
        |            Reserved             |  
        +---------------------------------+
        |                              LSW|
        +---         Byte Count        ---+
        |                              MSW|
        +---------------------------------+
        |                              LSW|
        +----                         ----+
        |                                 |
        +----                         ----+
        |                                 |
        +----     Buffer Descriptor   ----+
        |                                 |
        +----                         ----+
        |                                 |
        +----                         ----+
        |                              MSW|
        +---------------------------------+
        |                              LSW|
        +---         Region ID         ---+
        |                              MSW|
        +---------------------------------+
        |                              LSW|
        +---       Region Offset       ---+
        |                              MSW|
        +---------------------------------+

      8.2.1  FIELD DEFINITIONS

      Only fields which are  specific  to  Maintenance  Write  and  Read
      commands,  or  which  have  unique  values  for  this context, are

KFQSA Functional Specification  (Company Confidential)        Page 8-3
COMMAND FORMAT                                        14 December 1987

      defined in the sections which follow.  The reader should refer  to
      other  DSA  specifications  for  definitions  and  usage rules for
      fields not defined below.

           Connection ID:

                The CONNID field for all Maintenance commands  is  0xff.
                The  adapter  posts an Invalid Connect ID SA error if it
                receives a Maintenance Command with a  CONNID  of  other
                than 0xff.

           Credits:

                The CRDTS field for all Maintenance commands is  ignored
                by the Port Server.  The host is to assume one credit is
                available.

           Message Type:

                The MSTYP field for all Maintenance  commands  is  0x0f.
                The  adapter posts a High Level Protocol Incompatibility
                SA error if the MSTYP field is not 0x0f and  the  CONNID
                is 0xff.

           Message Length:

                The MESSAGE LENGTH field for all Maintenance commands is
                0x24.

           Operation Code:

                The OPCODE field is either 0x18 for a  Maintenance  Read
                or  0x19  for  a Maintenance Write command.  The adpater
                returns a Status of Invalid Command in the  End  Command
                response  if  it  receives a command for the 0xff CONNID
                that is not a 0x18 or 0x19.

           Byte Count:

                The BYTE COUNT field specifies the number of bytes to be
                transferred to or from host memory for the command.  The
                acceptable range of values for this field is 0 - 2**32-1
                (10) and should be an even number.

                                          NOTE

                    Odd byte  counts  will  be  tolerated,  but  the
                    operation will truncate the data transfer at the
                    highest whole word.  Transfers of 512  bytes  or
                    less    are    guaranteed    to   be   completed
                    successfully, or  an  error  will  be  returned.
                    Larger  transfers are permitted, but reliability
                    is not guaranteed.  A packet may be lost in  the

KFQSA Functional Specification  (Company Confidential)        Page 8-4
COMMAND FORMAT                                        14 December 1987

                    middle   of   a  large  transfer  without  being
                    detected.  If the last packet is  lost,  an  end
                    packet with error status will be sent back.

           Region ID:

                For  KFQSA  targets  only,  the  REGION  ID   field   is
                subdivided into three fields with the following format:

                        15                 7             0
                        +----------------+----------------+
                        |            Region ID            |
                        +----------------+----------------+
                        |  Target Node   |   Sub region   |
                        +----------------+----------------+

                Region ID:

                      1  -  68000 RAM (local node only - special case)  
                      2  -  68000 local RAM                             
                      3  -  68000 program ROM 
                      4  -  Dual Port RAM                               
                      5  -  Buffer RAM                                  
                      6  -  68000 BugCheck                              
                      7  -  8096  BugCheck                              
                      8  -  Manufacturing test                          
                      9  -  Data Link Performance Counters 
                     10  -  Soft Reset 

                                Path Specific Regions

                     16  -  Port Performance Counters 
                     17  -  SCS Connection State  
                     18  -  68000 Error Log                             
                     19  -  8096 Error Log                              
                     20  -  68000 Virtual Circuit Block                 
                          
                                8096 Regions

                     64  -  8096 Local RAM                              
                     65  -  8096 Program ROM 
                     66  -  Configuration EEROM 
                     67  -  8096 EEROM                                  
                     68  -  8096 System Parameters 
                     69  -  8096 Test  (local node only - special case)  
                     70  -  8096 Configuration Reset
                     71  -  8096 Usable CSR Word
                     72  -  8096 I/O Port

KFQSA Functional Specification  (Company Confidential)        Page 8-5
COMMAND FORMAT                                        14 December 1987

                Target Node:

                     Node number  on  which  this  operation  is  to  be
                     performed  (0-7).   This  number maps directly onto
                     the DSSI  Bus  node  number  one-to-one.   Minus  1
                     (0xff) is interpreted as the node through which the
                     maintenance command was received (local node).

                Sub Region:

                     The subregion field specifies the path  number  and
                     is  valid  only  for  path  specific regions.  This
                     field is ignored for  other  regions.   This  value
                     supplies  the  displacement  into the path specific
                     region, specified by the region ID.

           Region Offset:

                The REGION OFFSET field  provides  a  parameter  to  the
                KFQSA  which  defines  the  displacement into the memory
                element defined by REGION ID to be used as the  starting
                point for the specified operation.

                                          NOTE

                    This value must be even; an odd  value  in  this
                    field will result in rejection of the command as
                    invalid with REGION  OFFSET  identified  as  the
                    offending field.

                    If the supplied offset value exceeds the size of
                    the  targeted  memory  element,  the  command is
                    rejected   as   invalid   with   REGION   OFFSET
                    identified as the offending field.

                    If REGION OFFSET plus BYTE COUNT results  in  an
                    ending  address  that  exceeds  the  size of the
                    targeted memory element, the command is rejected
                    as  invalid  with  BYTE  COUNT identified as the
                    offending field.


KFQSA Functional Specification  (Company Confidential)        Page 8-6
END PACKET FORMAT                                     14 December 1987

      8.3  END PACKET FORMAT

      End Packets for both commands use the following format:

               15             8 7              0
              +----------------+----------------+
              |          Message Length         |
              +----------------+--------+-------+
              | Conn ID        |  MSTYP | CRDTS |
              +----------------+--------+-------+
              |                              LSW|
              +---  Command Reference Number  --+
              |                              MSW|
              +---------------------------------+
              |            Undefined            |
              +---------------------------------+
              |            Undefined            |
              +----------------+----------------+
              |     Unused     |   Endcode      |
              +----------------+----------------+
              |             Status              |
              +---------------------------------+
              |                              LSW|
              +----       Byte Count        ----+
              |                              MSW|
              +---------------------------------+

      8.3.1  FIELD DEFINITIONS

      Only fields which are specific to the End Packets  of  Maintenance
      Write  and  Read  commands,  or  which have unique values for this
      context, are defined in the  sections  that  follow.   The  reader
      should refer to other DSA specifications for definitions and usage
      rules for fields not defined below.

           Message Length:

                The MESSAGE LENGTH field for both End Packets is 0x10.

           Status:

                The STATUS field for both commands contains one  of  the
                following three values:

                        0x00   =   Success
                        0x01   =   Invalid Command
                        0x09   =   Host Buffer Access Error

                Moreover, subcodes will provide  additional  information
                when an error occurs.

KFQSA Functional Specification  (Company Confidential)        Page 8-7
END PACKET FORMAT                                     14 December 1987

                Invalid Command:

                             15              8 7              0
                             +----------------+----------------+
                             | Status Subcode |       0x01     |
                             +----------------+----------------+

                     If the status code is 0x01 (Invalid  command),  the
                     status field will also reflect a subcode specifying
                     the violating field; it will be stored in  the  top
                     byte  of  the  status word.  This subcode will have
                     one of the following values:

                             0x08   =   Invalid Opcode
                             0x0c   =   Invalid byte count
                             0x20   =   Invalid region offset 

                     If the subcode for an invalid opcode  is  returned,
                     either the opcode is unknown, a maintenance read is
                     requested of a write-only region, or a  maintenance
                     write is requested for a read-only region.

                Host Buffer Access Error:

                             15              8 7              0
                             +----------------+----------------+
                             | Status Subcode |       0x09     |
                             +----------------+----------------+

                     If the status code  is  0x09  (Host  Buffer  Access
                     Error),  the  status  field  will  also  reflect  a
                     subcode, providing additional error information; it
                     will  be stored in the top byte of the status word.
                     This subcode will have one of the following values:

                             0x00   =   Command timed out
                             0x21   =   Virtual Circuit Closed
                             0x41   =   Invalid Buffer Name
                             0x61   =   Invalid Buffer Length
                             0x81   =   Access Control Error
                             0xa1   =   No Path Available
                             0xc1   =   Memory Parity Error
                             0xe1   =   Invalid Packet Size
                             0xe3   =   Unrecognized Packet
                             0xe5   =   Invalid Destination
                             0xe7   =   Unrecognized Command
                             0xe9   =   Command Aborted
                             0xeb   =   Sequence Number Error

           Endcode:

                The ENDCODE field is 0x98 for  a  Maintenance  Read  End

KFQSA Functional Specification  (Company Confidential)        Page 8-8
END PACKET FORMAT                                     14 December 1987

                Packet or 0x99 for a Maintenance Write End Packet.

           Byte Count:

                The BYTE COUNT field indicates the total number of bytes
                successfully  written  to  host memory for a Maintenance
                Read command, or read from host memory for a Maintenance
                Write command.

      8.4  OTHER ERRORS

      Error conditions, other than those covered in the Status field  of
      an End Packet, may be encountered by the KFQSA while attempting to
      execute Maintenance Write and Read commands.  These errors are  to
      be reported through the SA register and may have values defined as
      Port Generic error codes or Controller Specific error codes.

      8.4.1  PORT GENERIC ERROR CODES

      See Appendix B, Standard UQSSP Error codes.

      8.4.2  KFQSA SPECIFIC ERROR CODES

      See Appendix C, KFQSA Specific SA error codes.

      8.4.3  ERROR RECOVERY

      It should be noted that the KFQSA does not perform automatic retry
      or any other kind of recovery procedure upon encountering an error
      during the execution of Maintenance commands.  Host programs using
      Maintenance commands should handle associated errors in accordance
      with   recovery   procedures   outlined    in    applicable    DSA
      specifications.

      8.5  TARGET NODE MAINTENANCE OPERATIONS

      The KFQSA is capable of  passing  Maintenance  Connection  traffic
      over  the DSSI bus for manufacturing test purposes, Given a number
      of KFQSAs connected on the same DSSI bus, Host  resident  software
      can  perform  Maintenance  read  and  write  operations to a KFQSA
      either  directly  through  the  target  adapter's  IP/SA  pair  or
      indirectly  by  sending  a  Maintenance command to one adapter and
      specifying a Target Adapter in the Target  Node  subfield  of  the
      Maintenance Region ID.

KFQSA Functional Specification  (Company Confidential)        Page 8-9
TARGET NODE MAINTENANCE OPERATIONS                    14 December 1987

      The figure below illustrates direct and indirect  operations.   It
      shows  8 adapters sitting in a backplane which are cabled together
      on the same DSSI bus.  The DIP sitches are correctly set such that
      each board has a unique CSR address and a unique DSSI ID.

      The following scenario describes a way to  indirectly  (ie.   over
      the  DSSI  bus)  write data to adapter 'H' from adapter 'A' and to
      read that data directly from adapter 'H'.

      1.  Host issues Maintenance Write to adapter 'A'.  Target Node  in
          the Maintenance Write Command packet is '7'.  The Region ID is
          '8', Manufacturing Test region.  This causes the Host resident
          data  pointed  to  in  the Write command to be sent across the
          DSSI bus and deposited in the Manufacturing Region in  adapter
          'H'.

      2.  Host issues Maintenance Read to adapter  'H'.   Region  ID  is
          '8',  Target  Node  is  either  -1, (local node default) or 7,
          adapter 'H's' DSSI ID.  This causes the data to be copied from
          adapter  'H's'  Manufacturing  Test Region into Host Memory at
          the specified memory address.

                   IP/SA (Octal)                           DSSI ID
                           +-----+                                
                   0760340 |  A  |------------+                0  
                       /42 +-----+            |                   
                           +-----+            |                   
                   0760344 |  B  |------------+                1  
                       /46 +-----+            |                   
                           +-----+            |                   
                   0760350 |  C  |------------+                2  
                       /52 +-----+            |                   
                           +-----+            |                   
                   0760354 |  D  |------------+                3  
                       /56 +-----+            |                   
                           +-----+            |                   
                   0760360 |  E  |------------+                4         
                       /62 +-----+            |                   
                           +-----+            |                   
                   0760364 |  F  |------------+                5  
                       /66 +-----+            |                   
                           +-----+            |                   
                   0760370 |  G  |------------+                6  
                       /72 +-----+            |                   
                           +-----+            |                   
                   0760374 |  H  |------------+                7  
                       /76 +-----+                                

KFQSA Functional Specification  (Company Confidential)       Page 8-10
MAINTENANCE REGIONS                                   14 December 1987

      8.6  MAINTENANCE REGIONS

      8.6.1  68000 RAM REGION

      Region ID 1 (68000 RAM) is provided in the KFQSA's  implementation
      of  the  Maintenance  Commands  for  backward  compatibility  with
      existing test software.  It  may  be  used  to  verify  the  basic
      operation  of  Maintenance  commands  for path specific regions or
      those regions in  the  68000  addressing  space.   The  the  KFQSA
      defaults  the  byte  count  to  2  for  this  region  ID.  This is
      reflected in the end packet as well.

      This region is physically the first word of the Manufacturing Test
      Region which is located in Buffer RAM.

      8.6.2  68000 LOCAL RAM REGION

      A maintenance read to this read-only region  allows  the  host  to
      access any area in the 68000 local RAM.

      8.6.3  68000 ROM REGION

      A maintenance read to this read-only region  allows  the  host  to
      access any area in the 68000 ROM.

      8.6.4  DUAL PORT RAM REGION

      A maintenance read to this read-only region  allows  the  host  to
      access any area in the Dual Port RAM.

      8.6.5  68000 BUFFER RAM REGION

      A maintenance read to this read-only region  allows  the  host  to
      access any area in the Buffer RAM.

      8.6.6  68000 BUGCHECK ERROR LOG PACKET REGION

      This region contains the Error Log packet that is returned by  the
      adapter  as a Last Fail packet when a 68000 Bugcheck error occurs.
      See the chapter on Error Log Formats for format  of  this  region.
      This  region  is  writeable  and  can therfore be cleared from the
      Host.  Any other use of this region is not recommended.

KFQSA Functional Specification  (Company Confidential)       Page 8-11
MAINTENANCE REGIONS                                   14 December 1987

      8.6.7  8096 BUGCHECK ERROR LOG PACKET REGION

      This region contains the Error Log packet that is returned by  the
      adapter  as a Last Fail packet when an 8096 Bugcheck error occurs.
      See the chapter on Error Log Formats for format  of  this  region.
      This  region  is  writeable  and  can therfore be cleared from the
      Host.  Any other use of this region is not recommended.

      8.6.8  MANUFACTURING TEST REGION

      This is a region that is set aside for use  by  the  Manufacturing
      Exerciser  during manufacturing testing.  It physically resides in
      Buffer RAM.

KFQSA Functional Specification  (Company Confidential)       Page 8-12
MAINTENANCE REGIONS                                   14 December 1987

      8.6.9  DATA LINK PERFORMANCE COUNTERS REGION

               15                             0
               +-------------------------------+  ----+
               |                            LSW|      |
               +---                         ---+   Applicable
               |                               |    only in
               +---   KFQSA System Clock    ---+     read
               |                               |      |
               +---                         ---+      |
               |                            MSW|      |
               +-------------------------------+  ----+
         B: 0  |        Ack Count           LSW|
               +-------------------------------+
         B: 2  |        Ack Count           MSW|
               +-------------------------------+
         B: 4  |        Nack Count          LSW|
               +-------------------------------+
         B: 6  |        Nack Count          MSW|
               +-------------------------------+
         B: 8  |        Bytes Sent          LSW|
               +-------------------------------+
         B:10  |        Bytes Sent          MSW|
               +-------------------------------+
         B:12  |        Bytes Received      LSW|
               +-------------------------------+
         B:14  |        Bytes Received      MSW|
               +-------------------------------+
         B:16  |        Frames Sent         LSW|
               +-------------------------------+
         B:18  |        Frames Sent         MSW|
               +-------------------------------+
         B:20  |        Frames Received     LSW|
               +-------------------------------+
         B:22  |        Frames Received     MSW|
               +-------------------------------+
         B:24  |        Reset Count         LSW|                
               +-------------------------------+
         B:26  |        Reset Count         MSW|
               +-------------------------------+
         B:28  |        No Response Count   LSW|
               +-------------------------------+
         B:30  |        No Response Count   MSW|
               +-------------------------------+
         B:32  |        Parity Error Count  LSW|
               +-------------------------------+
         B:34  |        Parity Error Count  MSW|
               +-------------------------------+
         B:36  |       Command Error Count  LSW|
               +-------------------------------+
         B:38  |       Command Error Count  MSW|
               +-------------------------------+
                                             

KFQSA Functional Specification  (Company Confidential)       Page 8-13
MAINTENANCE REGIONS                                   14 December 1987

              KFQSA system clock:

                A monotonically increasing counter
                which is incremented every 10 milliseconds.

                Other values are described in the 'Counter Descriptions'
                section of the DSSI Specification.

      These counters reflect DSSI bus activity.  A maintenance  read  to
      this region returns the counters preceded by an 8-byte timestamp.

      The first 8 bytes of data returned from a maintenance read to this
      region  contain  a  time-stamp.  The host should increase the byte
      count by eight bytes to compensate for the timestamp when doing  a
      maintenance read of this region.

      The Data Link  Performance  counter  region  is  writable.   These
      counters  can  be  zeroed  by  writing zeroes to this region.  Any
      other use of maintenance write to this region is not  recommended.
      The timer portion of this region is not writable and therefore the
      byte count should not be increased by 8.

      8.6.10  SOFT RESET REGION

      A maintenance write to  this  write-only  region  will  reset  the
      KFQSA.  It should be noted that a maintenance write command to the
      soft reset region is a special case implementation, and  that  the
      byte  count  and  region  offset  fields  MBZ, and that the buffer
      descriptor field of the command packet is ignored.   This  command
      will  always  use the EEROM Configuration Table as its data source
      and will always update all CSR Address Registers for  which  there
      is valid CSR address information.

      This is a "logical" region, there is no physical memory associated
      with it.

KFQSA Functional Specification  (Company Confidential)       Page 8-14
MAINTENANCE REGIONS                                   14 December 1987

      8.6.11  PORT PERFORMANCE COUNTERS REGION

      A set of counters is  kept  for  each  potential  virtual  circuit
      (0-7).   A maintenance read to this region returns the performance
      counters for a particular virtual  circuit.   These  counters  are
      physically kept in 68K local RAM.

               15                             0
               +-------------------------------+  ----+
               |                            LSW|      |
               +---                         ---+   Applicable
               |                               |    only in
               +---   KFQSA System Clock    ---+     read
               |                               |      |
               +---                         ---+      |
               |                            MSW|      |
               +-------------------------------+  ---+
         B: 0  |          Path 0 Ack        LSW|
               +-------------------------------+
         B: 2  |          Path 0 Ack        MSW|
               +-------------------------------+
         B: 4  |          Path 0 Nacks      LSW|
               +-------------------------------+
         B: 6  |          Path 0 Nacks      MSW|
               +-------------------------------+
         B: 8  |          Path 0 NoRsp      LSW|
               +-------------------------------+
         B:10  |          Path 0 NoRsp      MSW|
               +-------------------------------+
         B:12  |          Path 1 Ack        LSW|
               +-------------------------------+
         B:14  |          Path 1 Ack        MSW|
               +-------------------------------+
         B:16  |          Path 1 Nacks      LSW|
               +-------------------------------+
         B:18  |          Path 1 Nacks      MSW|
               +-------------------------------+
         B:20  |          Path 1 NoRsp      LSW|
               +-------------------------------+
         B:22  |          Path 1 NoRsp      MSW|
               +-------------------------------+
         B:24  |      Datagrams Discarded   LSW|
               +-------------------------------+
         B:26  |      Datagrams Discarded   MSW|
               +-------------------------------+
         B:28  |           VC Errors        LSW|
               +-------------------------------+
         B:30  |           VC Errors        MSW|
               +-------------------------------+


KFQSA Functional Specification  (Company Confidential)       Page 8-15
MAINTENANCE REGIONS                                   14 December 1987

              KFQSA system clock:

                a monotonically increasing counter
                which is incremented every 10 milliseconds.

              Path 0 Ack:
                
                total number of acks received on path 0.

              Path 0 Nack:

                total number of Nacks received on path 0.

              Path 0 NoRsp:
          
                total number of no_rsps received on path 0.

              Path 1 Ack:

                total number of acks received on path 1.

              Path 1 Nack: 

                total number of Nacks received on path 1.

              Path 1 NoRsp:

                total number of no_rsps received on path 1.

              Datagrams Discarded:

                total number of datagrams discarded.  All CI packets
                for which a DFREEQ entry is needed but unavailable.

              VC Errors:

                number of errors on Virtual Circuit

      The data returned from a maintenance read to the Port  Performance
      Counters  region or any other time-stamped region (see appendix D,
      Maintenance  Regions)  will  include  in  the  first  8  bytes   a
      time-stamp.   The  host  when  doing  a  maintenance  read  of the
      counters  should  increase  the  byte   count   appropriately   to
      compensate for the added bytes.

      The Port Performance counters may be zeroed by writing  zeroes  to
      this region.  Any other use of maintenance write to this region is
      not recommended.

KFQSA Functional Specification  (Company Confidential)       Page 8-16
MAINTENANCE REGIONS                                   14 December 1987

      8.6.12  SCS CONNECTION STATE REGION

      A Maintenance Read to the SCS Connection State Region returns  the
      Connection  State  Table  for a particular path.  The state of any
      connection on a path is contained in the Connection  State  Table.
      Each  path entry contains the connection state of each of the five
      possible  connections  on  that   path,   (MSCP$DISK,   MSCP$TAPE,
      MSCP$DUP,  CTP$RESPONDER,  and  SCS$DIRECTORY).   The path numbers
      correspond to the remote node's DSSI ID.

      The figure below shows the format of a Path Connection State Table
      Entry.

             15                               0                             
             +----------------+----------------+
      B: 0   |            MSCP$DISK            | --+      PATH
             +----------------+----------------+   |
      B: 2   |            MSCP$TAPE            |   |    CONNECTION
             +----------------+----------------+   |
      B: 4   |             MSCP$DUP            |   |      STATE
             +----------------+----------------+   |
      B: 6   |           CTP$RSPDR             |   |      TABLE
             +----------------+----------------+   |
      B: 8   |          SCS$DIRECTORY          | --+      ENTRY
             +----------------+----------------+

                      PATH CONNECTION STATE TABLE ENTRY

      The  SCS  Connection  States  and  their  respective  values   are
      contained  Table I-1 in Appendix I.  These are the accepted values
      for the SCS states.  Note that REJSENT is not in the  list.   This
      is because the adapter never sends a Reject request.

      The Path Connection State table is physically stored in 68K  Local
      RAM.

      8.6.13  68000 ERROR LOG PACKET REGION

      This region contains the Error Log packet that is returned by  the
      adapter  as  a  Last Fail packet when a 68000 detected fatal error
      occurs.  See the chapter on Error Log Formats for format  of  this
      region.  This region is writeable and can therfore be cleared from
      the Host.  Any other use of this region is not recommended.

      8.6.14  8096 ERROR LOG PACKET REGION

      This region contains the Error Log packet that is returned by  the
      adapter  as  a  Last Fail packet when an 8096 detected fatal error
      occurs.  See the chapter on Error Log Formats for format  of  this

KFQSA Functional Specification  (Company Confidential)       Page 8-17
MAINTENANCE REGIONS                                   14 December 1987

      region.  This region is writeable and can therfore be cleared from
      the Host.  Any other use of this region is not recommended.

KFQSA Functional Specification  (Company Confidential)       Page 8-18
MAINTENANCE REGIONS                                   14 December 1987

      8.6.15  VIRTUAL CIRCUIT BLOCK

      A Virtual Circuit Block is kept for each possible path to  a  DSSI
      node.   The  block includes the port performance counters for that
      virtual circuit.  A maintenance read to this  region  returns  the
      virtual circuit block for a particular virtual circuit.

               15                             0
               +-------------------------------+
        B:  0  /                               /
               /  Virtual Circuit Descriptor   /
               /                               /
               +-------------------------------+
        B:  4  |                          LSW  |
               +---   Local System State    ---+
               |                          MSW  |
               +-------------------------------+
        B:  8  |  Currently Transmitting Flag  |
               +-------------------------------+
        B: 10  |          Retry Count          |
               +-------------------------------+
        B: 12  |          Retry Delay          |
               +-------------------------------+
        B: 14  /                               /
               /        Transmit Queue         /
               /                               /
               +-------------------------------+
        B: 22  /                               /
               /        Retry Timer Block      /
               /                               /
               +-------------------------------+
        B: 54  |                          LSW  |
               +-----  Error Log Address  -----+
               |                          MSW  |
               +-------------------------------+
        B: 58  |         Remote           LSW  |
               +-----                     -----+
               |        Maintenance ID    MSW  |
               +-------------------------------+
        B: 62  |                          LSW  |
               +-----    Code Revision     ----+
               |                          MSW  |
               +-------------------------------+
        B: 66  |                          LSW  |
               +--     Port Functionality   ---+
               |                          MSW  |
               +-------------------------------+
        B: 70  |                          LSW  |
               +----   System State Word   ----+
               |                          MSW  |
               +-------------------------------+
        B: 74  |                          LSW  |
               +-Port Functionality Extension -+

KFQSA Functional Specification  (Company Confidential)       Page 8-19
MAINTENANCE REGIONS                                   14 December 1987

               |                          MSW  |
               +-------------------------------+
        B: 76  /        Rest of Port's         /
               /             ID                /
               +-------------------------------+
        B: 96  |          Path 0 Ack        LSW|
               +-------------------------------+
        B: 98  |          Path 0 Ack        MSW|
               +-------------------------------+
        B:100  |          Path 0 Nacks      LSW|
               +-------------------------------+
        B:102  |          Path 0 Nacks      MSW|
               +-------------------------------+
        B:104  |          Path 0 NoRsp      LSW|
               +-------------------------------+
        B:106  |          Path 0 NoRsp      MSW|
               +-------------------------------+
        B:108  |          Path 1 Ack        LSW|
               +-------------------------------+
        B:110  |          Path 1 Ack        MSW|
               +-------------------------------+
        B:112  |          Path 1 Nacks      LSW|
               +-------------------------------+
        B:114  |          Path 1 Nacks      MSW|
               +-------------------------------+ 
        B:116  |          Path 1 NoRsp      LSW|
               +-------------------------------+
        B:118  |          Path 1 NoRsp      MSW|
               +-------------------------------+
        B:120  |      Datagrams Discarded   LSW|
               +-------------------------------+
        B:122  |      Datagrams Discarded   MSW|
               +-------------------------------+
        B:124  |           VC Errors        LSW|
               +-------------------------------+
        B:126  |           VC Errors        MSW|
               +-------------------------------+

      Refer to KFQSA Top Level Design for description of  fields.   This
      region is physically contained in 68K Local RAM.

      8.6.16  8096 LOCAL RAM

      A maintenance read to this read-only region  allows  the  host  to
      examine any area in the 8096 Local RAM.

KFQSA Functional Specification  (Company Confidential)       Page 8-20
MAINTENANCE REGIONS                                   14 December 1987

      8.6.17  8096 ROM

      A maintenance read to this read-only region  allows  the  host  to
      examine any area in the 8096 ROM.

      8.6.18  8096 CONFIGURATION REGION

             15                                                            0
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 0  |                       Sequence Number                         |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 2  |                        KFQSA DSSI ID                          |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 4  | X | X | X |    CSR  Address 0  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B: 6  |        Path Model Number 0    |      Path DSSI ID 0           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 8  | X | X | X |    CSR  Address 1  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:10  |        Path Model Number 1    |      Path DSSI ID 1           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:12  | X | X | X |    CSR  Address 2  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:14  |        Path Model Number 2    |      Path DSSI ID 2           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:16  | X | X | X |    CSR  Address 3  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:18  |        Path Model Number 3    |      Path DSSI ID 3           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:20  | X | X | X |    CSR  Address 4  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:22  |        Path Model Number 4    |      Path DSSI ID 4           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:24  | X | X | X |    CSR  Address 5  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:26  |        Path Model Number 5    |      Path DSSI ID 5           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:28  | X | X | X |    CSR  Address 6  -   Bits 12:02         | 0 | 0 |
            +---+---+---+-------------------+-----------------------+---+---+
      B:30  |        Path Model Number 6    |      Path DSSI ID 6           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:32  |                            Checksum                           |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

      The configuration table begins with a sequence number and the DSSI
      Bus  ID  of  the  KFQSA.   It  is  the  responsibility of external
      software to increment the configuration table sequence number when
      revising  the contents of EEROM.  When the sequence number exceeds
      0xffff, a maintenance write should be done  to  the  Configuration

KFQSA Functional Specification  (Company Confidential)       Page 8-21
MAINTENANCE REGIONS                                   14 December 1987

      Table  Reset  region  to  clear  out  the  table;  otherwise,  any
      maintenance write to this region will fail, since the  KFQSA  will
      not  update  the  table  unless the new sequence number is greater
      than the one stored in the table.

      8.6.18.1  FIELD DEFINITIONS FOR CONFIGURATION TABLE

             15                                                            0
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 0  |                        Sequence Number                        |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 2  |            Reserved           |          KFQ DSSI ID          |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

                          Controller Specific Configuration Data

      Each of the seven path  entries  in  the  configuration  table  is
      comprised of two words of the following format:

        15   14  13 12  11  10   9   8   7   6   5   4   3   2   1   0
       +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
       | X | X | X |    CSR  Address    -   Bits 12:02         | 0 | 0 |
       +---+---+---+-------------------+-----------------------+---+---+
       |        Path Model Number      |      Path DSSI ID             |
       +-------------------------------+-------------------------------+

                     Path Specific Configuration Table Entry

      CSR Address:

           contains bits 12:02 of the  actual  I/O  address,  stored  in
           their  corresponding  bit  locations.  If this entry does not
           represent an active IP/SA  register  pair,  this  field  must
           contain all 0's.

      Path Model Number:

           Documented in the UQSSP 2.1 specification.

      Path DSSI ID:

           Numerical value in the range 0 -  7,  reflecting  the  actual
           setting  of the Device ID value that is to be associated with
           this CSR address.  If the CSR address field contains all 0's,
           this field is undefined.

      Checksum:

           Following  the  path  entries  is   the   checksum   of   the

KFQSA Functional Specification  (Company Confidential)       Page 8-22
MAINTENANCE REGIONS                                   14 December 1987

           configuration  table External software must compute and store
           this value.  This checksum is calculated using the  following
           algorithm:

                            0x4b46 - configuration table sum

           where the configuration table sum is the 16-bit  sum  of  all
           the words in the configuration table, discarding carries.

             15                                                            0
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 32 |                         Checksum                              |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

      8.6.18.2  PROCEDURE FOR UPDATING CSR ADDRESSES

      1.  Issue a maintenance read of the configuration  table.   If  an
          error  status  is returned in the end packet, do a maintenance
          read of the Usable CSR Word to confirm that there  are  usable
          CSRs.   Since an end packet with error status will be returned
          if the configuration table has invalid data in it, .i.e.,  the
          configuration  table  is  not  set  up yet, only a read to the
          Usable CSR Word will reveal the actual number of usable  CSRs.
          Note, if this occurs, this is not an error condition.

      2.  If there are usable CSRs, issue a  maintenance  write  to  the
          configuration region.

                                       NOTE

                  Host programs, wishing to modify  the  KFQSA's
                  Configuration   Table,  must  always  send  an
                  entire table's worth of information (i.e.,  17
                  words).   Host  software  must also generate a
                  new  checksum  value  reflecting  the  updated
                  information,  as  well  as update the sequence
                  number  as  part  of   the   update   of   the
                  configuration table.

      3.  Issue a maintenance read of the configuration table to  verify
          the update to the EEROM.

                                       NOTE

                  Changing the CSR Address information in  EEROM
                  does not cause the KFQSA to respond to the new
                  CSR addresses.  This will only happen when the
                  new  information is copied from EEROM into the
                  CSR Address Registers contained  in  the  CSRD

KFQSA Functional Specification  (Company Confidential)       Page 8-23
MAINTENANCE REGIONS                                   14 December 1987

                  gate  array.  This action occurs automatically
                  whenever the KFQSA is powered up; it may  also
                  be  forced  by  issuing a Maintenance WRITE to
                  Soft Reset Region.

      4.  Issue a maintenance read to the 8096 I/O Port Region to  check
          what  mode  the  board  is set in.  A maintenance write to the
          soft reset region for  the  purpose  of  reloading  the  CSRDs
          should  only  done  in  normal  mode.   The  KFQSA  allows the
          reloading of the CSRDs  in  any  mode  (service,  maintenance,
          normal);  hence, it is the responsibility of the host software
          to not issue the next step.

      5.  Issue a maintenance write to the Soft Reset Region.

          The events occur in the following chronological order:

          1.  An end packet for  the  maintenance  command  is  returned
              (signifying ONLY validation of the maintenance command).

          2.  The KFQSA performs a  self-initialization;  thus  breaking
              any  existing  connections  to  the  host,  including  the
              connection which received the Maintenance command.

          3.  The  CSRD's  CSR  Address  Registers  are   updated   with
              information stored in the EEROM's Configuration Table.

      8.6.19  8096 EEROM REGION

      A maintenance read to this read-only region  allows  the  host  to
      examine any area in the 8096 EEROM.

      8.6.20  8096 SYSTEM PARAMETERS REGION

      This region resides in the EEROM and contains controller  specific
      information.  Its format is as follows:


KFQSA Functional Specification  (Company Confidential)       Page 8-24
MAINTENANCE REGIONS                                   14 December 1987

             15                                                            0
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 0  |                             LSW                               |
            +---+---+---+---+---+---+               +---+---+---+---+---+---+
      B: 2  |                          Controller                           |
            +---+---+---+---+---+---+    Serial     +---+---+---+---+---+---+
      B: 4  |                            Number                             |
            +---+---+---+---+---+---+               +---+---+---+---+---+---+
      B: 6  |                             MSW                               |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B: 8  |                  Hardware Version Number                      |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

      8.6.21  8096 TEST REGION

      The 8096 Test Region (8096 RAM) is provided for use  in  verifying
      the  basic  operation of Maintenance commands for regions residing
      in the 8096 addressing space.

      8.6.22  CONFIGURATION TABLE RESET

      This write-only region is provided to clear out the  configuration
      table when the sequence number has exceeded 0xffff.  A maintenance
      write to the configuration region will fail if  the  new  sequence
      number  (the  one in the packet) is not greater than that which is
      stored in the table.  Thus, this region is provided to  allow  the
      host   to   re-start   with   sequence   number   0  and  continue
      re-configuring the CSRs.  It should be noted  that  a  maintenance
      write command to the Configuration Table Reset region is a special
      case implementation, and that the byte  count  and  region  offset
      fields  MBZ,  and  that the buffer descriptor field of the command
      packet is  ignored.   This  command  will  always  use  the  EEROM
      Configuration Table as its data source.

      8.6.23  8096 USABLE CSR WORD REGION

      Following the Checksum in EEROM is  the  Usable  CSR  Word.   This
      location  is  written by POST on power-up when it detects a change
      in the number of usable CSR pairs.  This word is accessed by doing
      a maintenance read to this region.

             15                                                            0
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
      B:10  |     Number of usable CSRs     |     Number of usable CSRs     |
            +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+

KFQSA Functional Specification  (Company Confidential)       Page 8-25
MAINTENANCE REGIONS                                   14 December 1987

      8.6.24  8096 I/O PORT REGION

      The 8096 I/O Port Region enables the host  to  read  the  mode  of
      operation of the KFQSA.  A maintenance read to this region returns
      the value of the 8096 input port 0 on  the  KFQSA  hardware.   See
      KFQSA  Functional  Specification,  8096  Input  Port  section  for
      description.


                               CHAPTER 9

                           ERROR LOG FORMATS

      This chapter defines the format of MSCP error log packets used  by
      the KFQSA firmware as Last Fail Packets.

      9.1  HOST MEMORY ACCESS ERROR - ERROR LOG FORMAT

      The format of a Host Memory Access Error Log message is  described
      in  the  MSCP  specification in the MSCP Error Log Message Formats
      section.

      9.2  GENERIC KFQSA ERROR - ERROR LOG FORMAT

      The format of a generic KFQSA Error Log message is shown below.


KFQSA Functional Specification  (Company Confidential)        Page 9-2
GENERIC KFQSA ERROR - ERROR LOG FORMAT                14 December 1987

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--- command reference number  ---+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +----                         ----+
              |                                 |   14
              +----  controller identifier  ----+
              |                                 |   16
              +----                         ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |          SA Error Code          |   22
              +---------------------------------+
              |      Controller Format Code     |   24
              +---------------------------------+
              /        error log format         /   26 
              /      dependent information      /    .
              /                                 /    .
              +---------------------------------+

      Command Reference Number:

           Always zero

      Format:

           0 = indicates controller error format
           1 = indicates host memory access error format

      Flags:

           1 = T/MSCP "sequence number reset" error log flag is set

      Event Code:

           0x00 = success
           0x0a = controller cmd.  timeout
           0x6a = inconsistent data structure
           0x69 = non-existent memory
           0x89 = memory parity error

KFQSA Functional Specification  (Company Confidential)        Page 9-3
GENERIC KFQSA ERROR - ERROR LOG FORMAT                14 December 1987

      Controller ID:

           T/MSCP controller ID

      SW vrsn:

           Firmware Revision Number

      HW vrsn:

           Hardware Version Number

      SA Error Code:

           SA error code if controller error.

      Controller Format Code:

           This code identifies the format  of  the  error  log  packet.
           These  are defined in Appendix E, Error Log Controller Format
           Codes.  The following sections describe the different  format
           error logs and their fields.

KFQSA Functional Specification  (Company Confidential)        Page 9-4
FORMAT OF 8096 ERROR LOG PACKETS                      14 December 1987

      9.3  FORMAT OF 8096 ERROR LOG PACKETS

      9.3.1  FORMAT FOR 8096 ERROR LOG FOR DMA ERROR

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--- command reference number ----+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |         SA Error Code           |   22
              +---------------------------------+
              |      Controller Format Code     |   24
              +---------------------------------+
              |            DSSI  Node           |   26
              +---------------------------------+
              |           Reason Code           |   28
              +---------------------------------+
              |                             LSW |   30
              +----       Host Address      ----+
              |                             MSW |   32
              +---------------------------------+
              |                             LSW |   34
              +----     Buffer Address      ----+
              |                             MSW |   36
              +---------------------------------+    
              |        Requested Byte Count     |   38
              +---------------------------------+
              |       Undelivered Byte Count    |   40
              +---------------------------------+
              |         CSRD Register 0         |   42
              +---------------------------------+
              |         CSRD Register 1         |   44
              +---------------------------------+

KFQSA Functional Specification  (Company Confidential)        Page 9-5
FORMAT OF 8096 ERROR LOG PACKETS                      14 December 1987

              |         CSRD Register 2         |   46
              +---------------------------------+
              |         CSRD Register 3         |   48
              +---------------------------------+
              |        QMI Status Register      |   50
              +---------------------------------+

      DSSI Node:

           0 - 7

      Reason Code:

           See appendix F, 8096 Error Log Reason Codes for  reason  code
           values.

                                     NOTE

              The CSRD Ring Register fields  in  the  error  log
              packet  are  valid  only in the case of a Ring DMA
              error.


KFQSA Functional Specification  (Company Confidential)        Page 9-6
FORMAT OF 8096 ERROR LOG PACKETS                      14 December 1987

      9.3.2  FORMAT FOR 8096 BUGCHECK ERROR LOG

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +-  command reference number     -+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14
              +----  controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |          SA Error Code          |   22
              +---------------------------------+
              |      Controller Format Code     |   24
              +---------------------------------+ 
              |            DSSI Node            |   26
              +---------------------------------+
              |      (BugCheck) Reason Code     |   28
              +---------------------------------+
              |               PC                |   30
              +---------------------------------+
              |               SP                |   32
              +---------------------------------+
              |               PSW               |   34
              +---------------------------------+
              |               REG0              |   36
              +---------------------------------+
              |               REG1              |   38
              +---------------------------------+
              |               REG2              |   40
              +---------------------------------+
              |               REG3              |   42
              +---------------------------------+
              |               REG4              |   44
              +---------------------------------+
              |               REG5              |   46
              +---------------------------------+

KFQSA Functional Specification  (Company Confidential)        Page 9-7
FORMAT OF 8096 ERROR LOG PACKETS                      14 December 1987

              |               REG6              |   48
              +---------------------------------+
              |               REG7              |   50
              +---------------------------------+
              |              Index              |   52
              +---------------------------------+
              |              PDscHi             |   54
              +---------------------------------+
              |              PDscLo             |   56
              +---------------------------------+
              |              DscHi              |   58
              +---------------------------------+
              |              DscLo              |   60
              +---------------------------------+
              |              DReg               |   62
              +---------------------------------+
              |             LRegHi              |   64
              +---------------------------------+
              |             LRegLo              |   66
              +---------------------------------+
              |             ISRReg0             |   68
              +---------------------------------+
              |             ISRReg1             |   70
              +---------------------------------+
              |              Path               |   72
              +---------------------------------+
              |           ActivePath            |   74
              +---------------------------------+
              |          DT?W_SemaPath          |   76
              +---------------------------------+
              |          DT?W_SemaCmd           |   78
              +---------------------------------+
              |          DT?W_SemaTimer         |   80
              +---------------------------------+
              |     Stack Length in longwords   |   82
              +---------------------------------+
              /               Stack             /   84
              /                 .               /
              /                 .               /
              /                 .               /  178
              +---------------------------------+

      DSSI Node:

           0 - 7

      Reason Code:

           See appendix F, 8096 Error Log Reason Codes for  reason  code
           values.

KFQSA Functional Specification  (Company Confidential)        Page 9-8
FORMAT OF 8096 ERROR LOG PACKETS                      14 December 1987

                                     NOTE

              If UQ response buffer is not large enough to  hold
              all the listed data, the packet will be truncated.


KFQSA Functional Specification  (Company Confidential)        Page 9-9
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4  68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS

      9.4.1  68000 ERROR LOG FORMAT 3

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24 
              +---------------------------------+

KFQSA Functional Specification  (Company Confidential)       Page 9-10
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.2  68000 ERROR LOG FORMAT 4

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+
              |        SA Error Sub Code        |   26
              +---------------------------------+

      SA Error Sub Code:

           See Appendix G, 68000 SA Error Sub Codes.

KFQSA Functional Specification  (Company Confidential)       Page 9-11
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.3  68000 ERROR LOG FORMAT 5

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+     
              |       Transmission Error        |   26
              +---------------------------------+

KFQSA Functional Specification  (Company Confidential)       Page 9-12
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.4  68000 ERROR LOG FORMAT 6

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+
              |        SA Error Sub Code        |   26
              +----------------+----------------+
              |   Rcvd Seq No  | Expected Seq No|   28 
              +----------------+----------------+

      SA Error Sub Code:

           See Appendix G, 68000 SA Error Sub Codes.

KFQSA Functional Specification  (Company Confidential)       Page 9-13
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.5  68000 ERROR LOG FORMAT 7

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+
              |         SA Error Sub Code       |   26
              +----------------+----------------+
              |    Path        |   Conn ID      |   28
              +----------------+----------------+

      SA Error Sub Code:

           See Appendix G, 68000 SA Error Sub Codes.

      Path:

           The DSSI Bus ID of the device the adapter was  attempting  to
           Connect to.

      Conn ID:

           The UQSSP  Connection  ID  of  the  failed  connection.   See
           Appendix H.


KFQSA Functional Specification  (Company Confidential)       Page 9-14
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.6  68000 ERROR LOG FORMAT 8

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+
              |       SA Error Sub Code         |   26
              +----------------+----------------+
              |     Path       |    Conn ID     |   28
              +----------------+----------------+
              |             Reason              |   30
              +---------------------------------+

      SA Error Sub Code:

           See Appendix G, 68000 SA Error Sub Codes.

      Path:

           The DSSI Bus ID of the device the adapter was  attempting  to
           Connect to.

      Conn ID:

           The UQSSP  Connection  ID  of  the  failed  connection.   See
           Appendix H.

KFQSA Functional Specification  (Company Confidential)       Page 9-15
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      Reason:

           The Reason field of the SCA/SCS Level Message that  indicated
           connection   failure.    See   Appendix   E,   Rejection  and
           Disconnection Reason Codes, in the SCA Specification, Version
           7.0C.

KFQSA Functional Specification  (Company Confidential)       Page 9-16
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.7  68000 ERROR LOG FORMAT 9

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+        
              |        SA Error Sub Code        |   26
              +----------------+----------------+
              |      Path      |    Conn ID     |   28
              +----------------+----------------+
              |    Received Message Length      |   30
              +---------------------------------+
              |    Received Message Type        |   32
              +---------------------------------+
              |        Connection State         |   34
              +---------------------------------+     

      SA Error Sub Code:

           See Appendix G, 68000 SA Error Sub Codes.

      Path:

           The DSSI Bus ID of the device the adapter was  attempting  to
           Connect to.

      Conn ID:

KFQSA Functional Specification  (Company Confidential)       Page 9-17
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

           The UQSSP  Connection  ID  of  the  failed  connection.   See
           Appendix  H.   If  the message length is less than four, this
           field is undefined.  If the SA Subcode is 'Message Rx'd  with
           bad Rec ID', this field is undefined.

      Received Message Length:

           The length of the errored SCS Message in bytes.

      Received Message Type:

           The value carried in the SCA/SCS TYPE field.  Appendix  B  of
           the  SCA  Specification, Version 7.0C, contains the valid SCS
           Message Types.  This  field  is  undefined  if  the  received
           message's length is less than 2 bytes.

      Connection State:

           The State of the SCS Connection when the error occurred.  See
           Table I-2 in Appendix I.  Table I-1 contains the standard SCS
           Connection  State  values,  table  I-2  contains  the   KFQSA
           implementation   specific  states.   If  the  SA  Subcode  is
           'Message Rx'd with bad Rec ID', this field is undefined.

KFQSA Functional Specification  (Company Confidential)       Page 9-18
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.8  FORMAT OF 68000 BUGCHECK ERROR LOG (FORMAT 10)

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+
              |      BugCheck Reason Code       |   26
              +---------------------------------+
              |                            LSW  |   28
              +----           PC            ----+
              |                            MSW  |   30
              +---------------------------------+
              |                            LSW  |   32
              +----           SP            ----+
              |                            MSW  |   34
              +---------------------------------+
              |                            LSW  |   36
              +----           A6            ----+
              |                            MSW  |   38
              +---------------------------------+
              |                            LSW  |   40
              +----           A5            ----+
              |                            MSW  |   42
              +---------------------------------+
              |                            LSW  |   44
              +----           A4            ----+
              |                            MSW  |   46
              +---------------------------------+

KFQSA Functional Specification  (Company Confidential)       Page 9-19
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

              |                            LSW  |   48
              +----           A3            ----+
              |                            MSW  |   50
              +---------------------------------+
              |                            LSW  |   52
              +----           A2            ----+
              |                            MSW  |   54
              +---------------------------------+
              |                            LSW  |   56
              +----           A1            ----+
              |                            MSW  |   58
              +---------------------------------+
              |                            LSW  |   60
              +----           A0            ----+
              |                            MSW  |   62
              +---------------------------------+
              |                            LSW  |   64
              +----           D7            ----+
              |                            MSW  |   66
              +---------------------------------+
              |                            LSW  |   68
              +----           D6            ----+
              |                            MSW  |   70
              +---------------------------------+
              |                            LSW  |   72
              +----           D5            ----+
              |                            MSW  |   74
              +---------------------------------+
              |                            LSW  |   76
              +----           D4            ----+
              |                            MSW  |   78
              +---------------------------------+
              |                            LSW  |   80
              +----           D3            ----+
              |                            MSW  |   82
              +---------------------------------+
              |                            LSW  |   84
              +----           D2            ----+
              |                            MSW  |   86
              +---------------------------------+
              |                            LSW  |   88
              +----           D1            ----+
              |                            MSW  |   90
              +---------------------------------+
              |                            LSW  |   92
              +----           D0            ----+
              |                            MSW  |   94
              +---------------------------------+
              |               PSW               |   96
              +---------------------------------+
              |    Stack length in longwords    |   98
              +---------------------------------+
              /              Stack              /   100
              /                .                /

KFQSA Functional Specification  (Company Confidential)       Page 9-20
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

              /                .                /
              /                .                /   178
              +---------------------------------+

                                     NOTE

              If UQ response buffer is not large enough to  hold
              all the listed data, the packet will be truncated.


KFQSA Functional Specification  (Company Confidential)       Page 9-21
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.9  68000 ERROR LOG FORMAT 11

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +----------------+----------------+        
              |      Path      | Invalid Conn ID|   26
              +----------------+----------------+

      Path:

           The DSSI Bus ID of the device the adapter was  attempting  to
           send to.

      Invalid Connection ID:

           Only one device connection per path is allowed in the  KFQSA.
           An  attempt  was  made  to  establish  more  than  one device
           connection on a path.  This is the ID of  the  second  device
           connection.  See Appendix H, UQSSP Connection ID.

KFQSA Functional Specification  (Company Confidential)       Page 9-22
68000 ERROR LOG FORMAT FOR CONTROLLER ERRORS          14 December 1987

      9.4.10  68000 ERROR LOG FORMAT 12

              15                               0   Byte Offset
              +---------------------------------+
              |                            LSW  |    0
              +--  command reference number   --+
              |                            MSW  |    2
              +---------------------------------+
              |           unit number           |    4
              +---------------------------------+
              |        sequence number          |    6
              +----------------+----------------+
              |     flags      |    format      |    8
              +----------------+--------------- +
              |            event code           |   10
              +---------------------------------+
              |               LSW               |   12
              +---                          ----+
              |                                 |   14        
              +---   controller identifier  ----+
              |                                 |   16
              +---                          ----+
              |               MSW               |   18
              +----------------+----------------+
              |   HW vrsn      |    SW vrsn     |   20
              +----------------+----------------+
              |           SA Error Code         |   22
              +---------------------------------+     
              |      Controller Format Code     |   24
              +---------------------------------+        
              |    Invalid Region Identifier    |   26
              +---------------------------------+

      Invalid Region Identifier:

           Value in region ID field of  maintenance  command  packet  is
           undefined.   Defined  values  are  in appendix D, Maintenance
           Regions.


                               APPENDIX A

                          POST/LED ERROR CODES

    Green  Red LED's
    LED    4 3 2 1 0     Meaning
    ---    ---------     -------
    X      X X X X X     Never got started, or 8096 CPU error
    0      0 0 0 0 0     8096 in hang state
    0      0 0 0 0 X     CSRD Chip test error
    0      0 0 0 X 0     QMI Chip test error
    0      0 0 0 X X     Fatal configuration table error
    0      0 0 X 0 0     8096 EPROM test error
    0      0 0 X 0 X     8096 DPRAM test error (low byte)
    0      0 0 X X 0     8096 DPRAM test error (high byte)
    0      0 0 X X X     68000's CPU test error
    0      0 X 0 0 0     68000's 10 usec BERR timer test error
    0      0 X 0 0 X     68000's EPROM test error
    0      0 X 0 X 0     68000's Local RAM test error (low byte)
    0      0 X 0 X X     68000's Local RAM test error (high byte)
    0      0 X X 0 0     68000 Interrupt vector test error
    0      0 X X 0 X     DSSA Timer test error
    0      0 X X X 0     FIFO chip test error
    0      0 X X X X     Buffer RAM parity test error
    0      X 0 0 0 0     Buffer RAM test error (first 64K, bits 0..3)
    0      X 0 0 0 X     Buffer RAM test error (first 64K, bits 4..7)
    0      X 0 0 X 0     Buffer RAM test error (first 64K, bits 8..11)
    0      X 0 0 X X     Buffer RAM test error (first 64K, bits 12..15)
    0      X 0 X 0 0     Buffer RAM test error (second 64K, bits 0..3)
    0      X 0 X 0 X     Buffer RAM test error (second 64K, bits 4..7)
    0      X 0 X X 0     Buffer RAM test error (second 64K, bits 8..11)
    0      X 0 X X X     Buffer RAM test error (second 64K, bits 12..15)
    0      X X 0 0 0     SII chip test error
    0      X X 0 0 X     68000's DPRAM test error (low byte)
    0      X X 0 X 0     68000's DPRAM test error (high byte)
    0      X X 0 X X     Microprocessor Interrupt test error
    0      X X X 0 0     68000 Bus Error
    0      X X X 0 X     Unexpected interrupt (68000 side)
    0      X X X X 0     8096 Setup Complete error
    0      X X X X X     Parity Error during BRAM Test
    X      0 0 0 0 X     At least one (but not all) CSR address parity error  *
    X      0 0 0 X 0     At least one (but not all) discrete port error in 
                         the QMI chip  *
    X      0 0 X 0 0     Successful retry during a RAM test

POST/LED ERROR CODES                                          Page A-2
                                                      14 December 1987

    X      0 X 0 0 0     Watchdog timer non-fatal error
    X      0 0 0 0 0     POST passed.

                0 = LED off, X = LED on

        * non-fatal error code is displayed for ten seconds (minimum).
                  A combination of the non-fatal error codes may be displayed
                  by OR'ing the non-fatal error codes together.


                               APPENDIX B

                       STANDARD UQSSP ERROR CODES

     Generic Errors

          0x01          Envelope/Packet Read (parity or timeout)
          0x02          Envelope/Packet Write (parity or timeout)
          0x03          Controller ROM and RAM parity 
          0x04          Controller RAM parity
          0x05          Controller ROM parity
          0x06          Queue Read (parity or timeout)
          0x07          Queue Write (parity or timeout)
          0x08          Interrupt Master
          0x09          Host Access Timeout
          0x0a          Credit Limit Exceeded
          0x0b          Bus Master Error
          0x0c          Diagnostic Controller Fatal Error 
          0x0d          Instruction Loop Timeout
          0x0e          Invalid Connection ID
          0x0f          Interrupt Write Error
          0x10          Maintenance R/W Invalid Region ID
          0x11          Maintenance Write load to non-loadable controller
          0x12          Controller RAM error (non-parity)
          0x13          Init Sequence Error
          0x14          High level protocol incompatibility error
          0x15          Purge/Poll hardware failure
          0x16          Mapping register read error (parity or timeout)
          0x17          Attempt to set data transfer mapping when option
                        not present


                               APPENDIX C

                     KFQSA SPECIFIC SA ERROR CODES

     Post Detected

          0x320         CSRD chip test error
          0x321         QMI Chip test error
          0x322         Fatal configuration table error
          0x323         8096 EPROM test error
          0x324         8096 DPRAM test error (low byte)
          0x325         8096 DPRAM test error (high byte)
          0x326         68000's CPU test error
          0x327         68000's 10 usec BERR timer test error
          0x328         68000's EPROM test error
          0x329         68000's Local RAM test error (low byte)
          0x32a         68000's Local RAM test error (high byte)
          0x32b         68000 Interrupt Vector register test error
          0x32c         8254 Timer test error
          0x32d         FIFO chip test error
          0x32e         Buffer RAM parity test error
          0x32f         Buffer RAM test error (1st 64K, bits 0..3)
          0x330         Buffer RAM test error (1st 64K, bits 4..7)
          0x331         Buffer RAM test error (1st 64K, bits 8..11)
          0x332         Buffer RAM test error (1st 64K, bits 12..15)
          0x333         Buffer RAM test error (2nd 64K, bits 0..3)
          0x334         Buffer RAM test error (2nd 64K, bits 4..7)
          0x335         Buffer RAM test error (2nd 64K, bits 8..11)
          0x336         Buffer RAM test error (2nd 64K, bits 12..15)
          0x337         SII chip test error
          0x338         68000's DPRAM test error (low byte)
          0x339         68000's DPRAM test error (high byte)
          0x33a         Microprocessor Interrupt test error
          0x33b         68000 bus error
          0x33c         Unexpected interrupt (68K side)
          0x33d         8096 Setup Complete error
          0x33e         Parity Error during BRAM test
          0x33f         Unexpected 8096 Interrupt

KFQSA SPECIFIC SA ERROR CODES                                 Page C-2
                                                      14 December 1987

     Functional Firmware Detected

          0x340         Port Level Protocol Error
          0x341         Port: Max Retries Exceeded
          0x342         PPD: Remote Port Restarted
          0x343         PPD: VC Restarted
          0x344         Bug Check
          0x345         SCS Connect Error
          0x346         SCS Level Protocol Error
          0x347         CMM: Too Many Device Connections
          0x348         Host DMA Write Failure
          0x349         Host DMA Read Failure
          0x34a         UQ:  DMA Compare Error
          0x34b         UQ:  No VC during 4-step initialization


                               APPENDIX D

                          MAINTENANCE REGIONS

+---------+--------------------+-----------+-----------+------+-----------+
|Region ID|   Region Name      |Max. Offset|Region Size|Access|Restriction|
+---------+--------------------+-----------+-----------+------+-----------+
|   1     |68000 RAM           |  MBZ      |   0x02    | R/W  | Lcl Node  |
|   2     |68000 Lcl RAM       |  0x3ffe   |   0x4000  | R/O  |           |
|   3     |68000 ROM           |  0x1fffe  |   0x20000 | R/O  |           |
|   4     |Dual Port RAM       |  0x3ffe   |   0x4000  | R/O  |           |
|   5     |68000 Buffer RAM    |  0x3fffe  |   0x40000 | R/O  |           |
|   6     |68000 BugCheck      |  MBZ      |   0xb2    | R/W  |           |
|   7     |8096 BugCheck       |  MBZ      |   0xb2    | R/W  |           |
|   8     |Manufacturing test  |  0x0ffe   |   0x1000  | R/W  |           |
|   9     |Data Link Counters  |  MBZ      |   0x28    | R/W  |Time stamp |
|  10     |Soft Reset          |  MBZ      |   MBZ     | W/O  |           |
+---------+--------------------+-----------+-----------+------+-----------+
|  16     |Port Layer Counters |  MBZ      |   0x20    | R/W  |Time stamp |
|  17     |SCS Conn. State     |  MBZ      |   0x0c    | R/O  |           |
|  18     |68000 Error Log     |  MBZ      |   0xb2    | R/W  |           |
|  19     |8096 Error Log      |  MBZ      |   0xb2    | R/W  |           |
|  20     |68K Virtual Circuit |  MBZ      |   0x82    | R/O  |           |
+---------+--------------------+-----------+-----------+------+-----------+
|  64     |8096 Local RAM      |  0x0fe    |   0x100   | R/O  |           |
|  65     |8096 ROM            |  0x3ffe   |   0x4000  | R/O  |           |
|  66     |8096 Configuration  |  MBZ      |   0x22    | R/W  | cnfg len  |
|  67     |8096 EEROM          |  0x1fe    |   0x200   | R/O  |           |
|  68     |8096 System Param.  |  MBZ      |   0x10    | R/O  |           |
|  69     |8096 Test           |  MBZ      |   0x02    | R/W  | Lcl Node  |
|  70     |8096 Config. Reset  |  MBZ      |   MBZ     | W/O  |           |
|  71     |8096 Usable CSR Word|  MBZ      |   0x02    | R/O  |           |
|  72     |8096 I/O Port       |  MBZ      |   0x02    | R/O  |           |
+---------+--------------------+-----------+-----------+------+-----------+


                               APPENDIX E

                   ERROR LOG CONTROLLER FORMAT CODES

                        8096 Error Log
                        --------------
 
        1       Bug Check Error Log 
        2       DMA Error Error Log 

                        68000 Error Log
                        ---------------

        3       DMA Read, DMA Write, PPD Port Restart, PPD VC Restart 
        4       Port level credit error, Port level invalid length, 
                Port level invalid frame        
        5       Port level: Max Retries Exceeded
        6       Port level: Sequence Number Mismatch Error
        7       SCS level Error
        8       SCS level:  Connect Error
        9       SCS level:  SCS Protocol Error
       10       Bug Check
       11       CMM level Error
       12       Maintenance Error


                               APPENDIX F

                      8096 ERROR LOG REASON CODES

                        DMA Ring Error
                        --------------
 
          0x0b020                 DMA Communications Area Write Error
          0x0b021                 DMA Communications Area Read Error
          0x0b022                 DMA Communications Area Compare Error
          0x0b023                 DMA Command Queue Write Error
          0x0b024                 DMA Command Queue Read Error
          0x0b025                 DMA Command Port Read Error
          0x0b026                 DMA Response Queue Write Error
          0x0b027                 DMA Response Queue Read Error
          0x0b028                 DMA Response Port Read Error
          0x0b029                 DMA Response Port Write Error

                        DMA Message Error   
                        -----------------

          0x0b040                 DMA Command Packet Read Error
          0x0b041                 DMA Response Packet Write Error

                        DMA Data Error
                        --------------

          0x0b060                 DMA Data Read Error
          0x0b061                 DMA Data Write Error


                               APPENDIX G

                        68000 SA ERROR SUB CODES

                        Port Level Protocol Error
                        -------------------------

          0x08001                 Invalid Port Packet Length
          0x08002                 Port Level Credit Violation
          0x08003                 Port Level Sequence Number Error
          0x08004                 Port Level Invalid Frame

                            SCS Connect Error 
                            -----------------

          0x08005                 Connect Response NAK'd by remote
          0x08006                 Accept Response NAK'd by remote
          0x08007                 Connect Rejected by remote

                          SCS Level Protocol Error       
                          ------------------------

          0x08008                 Process Names in Accept Request Invalid
          0x08009                 Message is too short for its type
          0x0800a                 Message Type Invalid
          0x0800b                 Message Rx'd with bad Rec ID
          0x0800c                 Message Rx'd invalid for Connection state
          0x0800d                 Two Requests Rx'd on path concurrently
          0x0800e                 Invalid Credit Response ACK value
          0x0800f                 SCS Level Credit Violation


                               APPENDIX H

                          CONNECTION ID VALUES

             +----------------+----------------------------------+
             |    ID Number   |             Purpose              |
             |    (Decimal)   |                                  |
             +----------------+----------------------------------+
             |        0       |       Disk                       |
             |        1       |       Tape                       |
             |        2       |       DUP                        |
             |      3-253     |       Invalid for KFQSA          |
             |       254      |       Verification Testing       |
             |       255      |       Maintenance Protocol       |
             +----------------+----------------------------------+


                               APPENDIX I

                         SCS CONNECTION STATES

                      SCS STATE   VALUE (DECIMAL) 
                                                  
                       CLOSED        0            
                       LISTEN        1            
                       OPEN          2            
                       DISC_ACK      3            
                       DISC_REC      4            
                       DISC_SENT     5            
                       DISC_MTCH     6            
                       CON_SENT      7            
                       CON_ACK       8            
                       CON_REC       9            
                       ACCP_SENT     10           

             SCS CONNECTION STATE TABLE REGION STATES

                           TABLE I-1

SCS CONNECTION STATES                                         Page I-2
                                                      14 December 1987

                      SCS STATE   VALUE (DECIMAL) 
                                                  
                       CLOSED        0            
                       LISTEN        1            
                       OPEN          2            
                       DISC_ACK      3            
                       DISC_REC      4            
                       DISC_SENT     5            
                       DISC_MTCH     6            
                       CON_SENT      7            
                       CON_ACK       8            
                       CON_REC       9            
                       ACCP_SENT     10           
                       ACPT_REC      11           
                       REJ_REC       12           
                       CON_PEND      13           
                       ACPT_PEND     14           
                       DISC_PEND     15           
                       REJ_SENT      16           

             SCS LEVEL PROTOCOL ERROR LOG STATE VALUES
                  (KFQSA IMPLEMENTATION SPECIFIC)

                           TABLE I-2



                               APPENDIX J

                            REVISION HISTORY

      This appendix tracks the revision history of the document.  Please
      note that change bars present in the document only reflect changes
      from the previous version and are NOT cummulative.

      Changes:

      A.01    9 September 1986        Internal Distribution
      A.02    12 September 1986       Altitude, Class C specified
      A.03    16 December 1986        Add Physical Spec Info, Correct Errors
      B.01    26 February 1987        Revise H/W and F/W info, Correct Errors.
                                      Add Error info, reflect change to SCA.

      1.0     10 June 1987            Correct POST, add SA and LED error codes,
                                      General update and error correction.
      2.0     1 July 1987             Updated Chapter 2.
                                      Added chapter on maintenance read/write
                                      requests.
                                      Updated SA error codes.
                                      Updated list of references.
                                      Added discussion of manufacturing mode.
      2.1     20 August 1987          Corrected maintenance region numbers
                                      Added new SA errors
                                      assigned reserved POST error codes
      2.2     13 October 1987         Corrected maintenance region numbers
      2.3     27 October 1987         Updated chapter on maintenance read/write
                                      requests.  
      2.4       December 1987         Revised chapter 8 (Maintenance Read/Write)
                                      Added chapter 9 (Error Log Formats)
                                      Revised Chapter 2. (Architecture)
                                      Revised Chapter 7. (DSA)
                                      Revised Chapter 1. (Overview)
      2.5     14 December 1987        Editorial Updates
      2.6       28 January 1988         Modified some POST fatal and non-fatal error
                                codes (Appendix)