Emulex MD21/S2 Technical Manual

MD21/S2 DISK CONTROLLER

TECHNICAL MANUAL

( SCSI-COMPATIBLE)

EM U L E X

3545 Harbor Boulevard

Costa Mesa, California 92626

(714) 662-5600 TWX 910-595-2521

MD2151003-00 Rev E

March, 1988

WARNING

This equipment generates, uses and can radiate

radio frequency energy, and if not installed and used in accordance with the technical manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class B computing device pursuant to Subpart J of Part 15 of the Federal Communications Commission (FCC) Rules, which are designed to provide reasonable protection against such interference when operating in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.

Emulex is a registered trademark of Emulex Corporation.

IBM PC and IBM PC/XT are registered trademarks of International Business Machines Incorporated.

Multibus is a registered trademark of Intel Corporation.

The information in this manual is for information purposes only and is subject to change without notice.

Emulex Corporation assumes no responsibility for any errors which may appear in the manual.

Printed in U.S.A.

PREFACE

This reference manual explains how to install, test, and operate the MD21 Disk Controller. It provides you with the following information:

• Installation instructions

• Disk Controller Specifications

• Compatibility information

• Drive Configuration Parameters

• Initialization and Self-Test Procedures

• Interface information

• A guide to troubleshooting

• PROM Removal and Replacement

This manual has been designed to be used with the Emulex SCSI Disk Controller Programming Reference Manual (manual number MD2352501) and it assumes familiarity with the SCSI standard and the ESDI disk drive interface specification.

The Small Computer System Interface (SCSI) command set for the MD21 Controller is based on the ANSI X3.131-1986 SCSI Specification. Copies of the ANSI SCSI Specification can be obtained from the following publisher:

American National Standard for Information Systems - Small

Computer System Interface (SCSI), ANSI X3.131 - 1986 Computer and Business Equipment Manufacturers Association 311 First Street, NW Suite 500

Washington, DC 20001

The ESDI interface standard for 5.25-inch Winchester disk drives is described in the Enhanced Small Device Interface specification, preliminary working document, ANSI X3T9.3/87 -** Revision 1.1 or ESDI Revision F.3A, (26 January 1987). This specification is available from:

Dal Allan Vice Chairman X3T9.3

ENDL Consulting 14426 Black Walnut Court Saratoga, CA 95070

(408) 867-6630

Table of Contents vii

EMULEX PRODUCT WARRANTY

CONTROLLER WARRANTY: Emulex warrants for a period of twelve (12) months from the date of shipment that each Emulex controller product supplied shall be free from defects in material and workmanship.

CABLE WARRANTY: All Emulex-provided cables are warranted for ninety

(90) days from the time of shipment.

The above warranties shall not apply to expendable components such as fuses, bulbs, and the like, nor to connectors, adapters, and other

items not a part of the basic product. Emulex shall have no obligation to make repairs or to cause replacement required through normal wear and tear or necessitated in whole or in part by catastrophe, fault or negligence of the user, improper or unauthorized use of the product, or use of the product in such a manner for which it was not designed, or by causes external to the product, such as but not limited to, power failure or air conditioning. Emulex's sole obligation hereunder shall be to repair or replace any defective product, and, unless otherwise stated, pay

return transportation cost for such replacement.

Purchaser shall provide labor for removal of the defective product, shipping charges for return to Emulex, and installation of its

replacement. THE EXPRESSED WARRANTIES SET FORTH IN THIS AGREEMENT

ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND ALL OTHER WARRANTIES ARE HEREBY DISCLAIMED AND EXCLUDED BY EMULEX. THE STATED EXPRESS WARRANTIES ARE IN LIEU OF

ALL OBLIGATIONS OR LIABILITIES ON THE PART OF EMULEX FOR DAMAGES,

INCLUDING BUT NOT LIMITED TO SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF, OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE PRODUCT.

RETURNED MATERIAL: Warranty claims must be received by Emulex within

the applicable warranty period. A replaced product, or part thereof,

shall become the property of Emulex and shall be returned to Emulex at Purchaser's expense. All returned material must be accompanied by a RETURN MATERIALS AUTHORIZATION (RMA) number assigned by Emulex.

viii Warranty

Section 1

INTRODUCTION

1.1 OVERVIEW

The MD21/S2 Disk Controller is a single-board controller designed to interconnect Small Computer System Interface (SCSI) host adapters and controllers to one or two Enhanced Small Device Interface (ESDI) ,5.25-inch Winchester disk drives. The controller features the single-ended SCSI option for drivers and receivers. For brevity, the reference MD21 will be used throughout this

manual.

In combination with an independent host adapter, the SCSI bus allows a wide variety of computers to interface with the MD21

Controllers. Compatible computers include IBM Personal Computer

systems such as the IBM PC-XT, Q-Bus, VMS Bus, VAX UNIX, and

Multibus-based computers. Up to eight bus devices, in any

combination of host systems and intelligent controllers, can be supported by the SCSI bus. The MD21 Controller, in combination

with one or two ESDI 5.25-inch magnetic disk drives, provides a

low-cost, compact storage subsystem.

The MD21 Controller's architecture and SCSI features it supports

make it an ideal building block for use by OEMs and system

integrators. The MD21 Controller supports a powerful set of SCSI commands. By using those commands, an efficient multiple-initiator configuration can be constructed with the support of the disconnect function. (The disconnect function allows the MD21 Controller, when it is performing a time-consuming task, to release the SCSI bus temporarily and reconnect at a later time when the task is complete.) The MD21 Controller supports all required SCSI commands and the SCSI Common Command Set (CCS) for direct-access devices described in the CCS standard.

Emulex currently offers other SCSI bus microcontrollers that can be used with SCSI bus subsystems. These include the MT02/MT03 and the MD01. The MT02/MT03 Tape Controller interfaces the SCSI bus to a

5.25-inch streaming cartridge tape drive. The MD01 Disk Controller connects one or two ST506 interface 5.25-inch disk drives to the SCSI bus. Also, the MD23/24 Disk Controller interfaces the SCSI bus

to up to four ESDI single-ended/differential drives and the MD32 connects up to four SMD/SMD-E drives to the SCSI bus.

In addition to basic stand-alone controller products, Emulex also

offers complete SCSI bus disk and tape packaged subsystems for microcomputer applications.

Introduction 1-1

Overview

1.2 FEATURES

The MD21 Controller features are summarized below. More details on

these features are given in subsequent sections.

• Industry standard 5.25-inch form factor and mounting

• Operates from single +5 volt source

• 32K byte by 9-bit on-board dynamic RAM

• 8031 microprocessor operating at 12.0 mHz

• Power Fail Detect input

• User Panel Interface which supports:

-- Write protect switches — Write protect indicators — Ready indicators

• Write protect from the drive

• Support of one or two ESDI Disk Drives

• Provides a transfer rate up to fifteen megabits/sec at the ESDI interface

• Supports physical sector sizes of 256 and 512 bytes

• Supports hard or soft sectoring

• Provides defect skipping, using slip sectoring

• Sequenced drive start up

• Supports embedded servo drives

• Auto configuration during power-up

• Defect management including manufacturer's defect list

• Overlapped Seeks

• Will not destroy manufacturer's defect list

• Provides transfer rate of up to 1.25 Mbytes/sec at the SCSI interface

1-2 Introduction

• Conforms to the latest ANSI Specification (listed on page vii)

• Supports the SCSI Direct Access Device Common Command Set

• Supports SCSI disconnect/reconnect option

• Diagnostic Commands support physical addressing

• Track-to-track and cylinder-to-cylinder format skewing

• Command queuing for each LUN

• Supports logical block sizes of 256, 512, 1024, 2048, and 4096 bytes

• 48-bit ECC correcting up to 17 bits in error

• Supports SCSI bus parity

• ESDI pass-through commands and status

1.3 ORGANIZATION OF THE MANUAL

This manual is designed to help you integrate the MD21 Controller hardware into a subsystem. It provides technical information about the controller and brief overviews of the SCSI and ESDI interfaces. The manual provides no information about the SCSI command set or protocol. For this information, please refer to the Emulex SCSI Disk Controller Programming Reference Manual (manual number MD2352501).

The contents of the seven sections and two appendices of the MD21 Disk Controller manual are briefly described below.

Section 1 Introduction: This section briefly describes the MD21

Controller, provides a list of its features, and describes the organization of this manual. (This section.)

Section 2 General Description: This section contains overviews of

the MD21 Controller, the SCSI bus, and the ESDI

interface. It also discusses SCSI and ESDI

compatibility.

Section 3 MD21 Controller Specifications: This section contains

specifications for the major components of the MD21

Controller .

Section 4

Drive Configuration Parameters: This section contains

recommended parameters of the ESDI disk drives.

Introduction 1-3

Overview

Section 5

Section 6

Section 7

Appendix i

Appendix ]

Installation: This section contains the information necessary to set up and install the MD21 Controller in

your system.

Controller Initialization and Self-Test Procedures

This section describes the diagnostic features of the MD21 Controller, including power up and reset tests and

• online host-initiated diagnostics.

Interfaces: This section describes the SCSI bus and ESDI disk drive interfaces. It also describes the user panel

and DC power connections.

V Troubleshooting: This appendix provides information

regarding technical support and service.

5 PROM Removal and Replacement: This appendix contains

instructions to remove and replace the firmware so that

you can upgrade the MD21 Disk Controller in the field.

1-4 Introduction

Section 2

GENERAL DESCRIPTION

2.1 INTRODUCTION

This section provides brief overviews of the major components of the MD21 Disk Controller subsystem. For more specific information about the SCSI Bus Interface and about the ESDI Interface, please

refer to the ANSI SCSI Specification and the Enhanced Small Device Interface Specification listed on page vii.

For reference convenience, Section 2 is divided into five

subsections, as listed in the following table:

Subsection Title

2.1

2.2

2.3 SCSI Bus Overview

2.4

2.5 Compatibility

2.2 MD21 DISK CONTROLLER OVERVIEW

2.2.1 PHYSICAL DESCRIPTION

The MD21 Controller, shown in Figure 2-1, is assembled on a single board approximately 14.6 centimeters by 20.3 centimeters (5.25

inches by 7.75 inches). It can be installed directly on a mounting bracket located in the subsystem that contains an ESDI 5.25-inch Winchester disk drive. The MD21 Controller contains the following major components:

• Two Emulex custom Very Large Scale Integrated (VLSI) chips: a Buffer Controller and a disk formatter.

• An 8031 microprocessor chip

• A 32-kilobyte (K byte) Erasable Programmable Read Only Memory (EPROM), and a 32K byte Random Access Memory (RAM)

for data buffering.

Introduction

Disk Controller Overview

ESDI Overview

Figure 2-1 shows the MD21 Disk Controller and its components.

General Description 2-1

MD21 Disk Controller Overview

Figure 2-1. The MD21 Disk Controller

2-2 General Description

MD2103-0785

MD21 Disk Controller Overview

2.2.2 FUNCTIONAL OVERVIEW

Figure 2-2 is a block diagram that shows the major functional elements of the MD21. The MD21 is organized around the 8031

microprocessor, the SCSI protocol controller, the disk formatter,

and the buffer controller. The disk formatter and the buffer controller are custom VLSI chips designed by Emulex.

Two buses are used in the MD21: the data bus and the microprocessor bus.

The data bus is connected directly to the disk formatter, SCSI protocol controller, buffer memory, and buffer controller. The buffer controller is connected directly to the data bus and the microprocessor bus, providing an interface between them. Therefore, the buffer controller provides a data path between the buffer memory, the 8031 microprocessor, disk formatter, and SCSI protocol controller.

The microprocessor bus provides a path for transmission of control and status information between the 8031 microprocessor, EPROM, buffer controller, and disk interface. This bus is completely separate from the data bus. The microprocessor may access the data bus via the buffer controller interface.

The MD21 SCSI Interface is implemented using a single LSI chip on the MD21 Controller. In response to commands from the initiator, the chip establishes and monitors SCSI bus phases appropriate to the command. It performs SCSI signal control and timing functions.

General Description 2-3

MD21 Disk Controller Overview

Figure 2-2. MD21 Controller Block Diagram

2-4 General Description

MD2103-0781

MD21 Disk Controller Overview

2.2.,2.1 8031 Microprocessor

With the disk formatter, the 8031 microprocessor controls all disk drive operations. These disk operations include drive control, head positioning, and reading drive status.

During disk operations, the disk formatter controls formatting of

the data that is written to, and read from, the disk drive. The 8031 microprocessor generates read and write commands that are executed by the disk formatter. All read and write commands involve operations only on a single data block (256 or 512 bytes).

2.2.2.2 Disk Formatter

The disk formatter is a 40-pin VLSI IC fabricated with CMOS gate

array technology. This circuit, along with the 8031 microprocessor, handles the read and write operations of the disk drives.

2.2.2.3 Buffer Controller

The buffer controller is a 68-pin VLSI IC fabricated with CMOS

gate-array technology. The circuit is basically a three-channel

DMA controller. The buffer controller controls data movement in or

out of a dynamic buffer memory and provides the connection between

the microprocessor bus and the data bus.

The buffer controller circuit provides the address and control for multiple MD21 Controller activities that access a dynamic buffer memory. The buffer controller performs the following operations:

• Handles buffer addressing and control operations for the disk formatter

• Handles buffer addressing and control operations for the SCSI protocol controller

• Handles dynamic memory timing and refresh

• Performs parity checking and generation for the buffer memory

• Connects the microprocessor bus to the data bus

• Decodes the microprocessor address for the buffer memory and the internal input/output (I/O) space in the MD21 Controller

• Determines priority of buffer memory access

General Description 2-5

SCSI Bus Overview

2.3 SCSI BDS OVERVIEW

The Small Computer System Interface (SCSI)* is a standard interface established to support mass storage, printer output, and network communication for microcomputers and minicomputers. The interface is an eight-port, daisy-chained bus. The SCSI command standard for the MD21 Controller is based on the ANSI SCSI Interface Specification listed on page vii.

The SCSI bus can support up to eight SCSI host adapters and/or

controllers. Each controller can be connected to a maximum of eight devices (called Logical Unit Numbers, or LUNs). The MD21 Controller hardware supports any combination of host adapters,

intelligent controllers, or intelligent peripherals connected to

the SCSI bus. The MD21 Controller supports one or two LUNs (ESDI

disk drives). Three basic SCSI configurations are supported with

the MD21 Controller and SCSI bus:

• Single initiator, single target

• Single initiator, multi target

• Multi initiator, multi target

Communication on the SCSI bus occurs between a host adapter and a controller. When a host adapter and a controller communicate, one acts as the Initiator and the other acts as the Target. The

Initiator (usually the host adapter) originates an operation, and the Target (usually a peripheral controller, such as the MD21 Controller) performs the operation. Sample system configurations supported by MD21 Controller hardware are shown in Figure 2-3.

Some SCSI bus functions are assigned to the Initiator and some

functions are assigned to the Target. The Initiator can arbitrate

for control of the SCSI bus and select a specific Target. The Target can request the transfer of command, data, status, or other

information via the SCSI bus. In some circumstances, the Target can arbitrate for control of the SCSI bus to reselect an Initiator and continue an operation. Sometimes, the Target becomes an Initiator and arbitrates for control of the SCSI bus.

SCSI bus data transfer operations are asynchronous and follow a

defined request/acknowledge (REQ/ACK) handshake protocol. (This protocol is defined in the ANSI SCSI specification.) One eight-bit byte of information can be transferred with each handshake.

The SCSI bus consists of 18 signal lines. Nine signal lines are

for an eight-bit data bus with parity; the other nine signal lines are for control and status signals that coordinate data transfer

operations between the host adapter and SCSI controllers. SCSI bus

signals are described in more detail in subsection 7.2.3.1.

2-6 General Description

SINGLE INITIATOR, SING LE TARG ET

SCSI Bus Overview

PERIPH ERAL UNITS SUCH AS RIGID DISKS

Figure 2-3

MULTI INITIATOR, MULTI TARGET

Sample SCSI Bus Configuration

General Description 2-7

MD2103-0582

ESDI Overview

2.4 ESDI OVERVIEW

The Enhanced Small Device Interface (ESDI) is a standard interface established to support multiple disk drives on the same controller.

ESDI was designed to extend the capabilities of the ST506 interface. The following points regarding the MD21 implementation of the ESDI should be noted:

• The data separator is on the drive (instead of the controller as in ST506 interfaces)? therefore, NRZ data can be used between controller and drive.

• The drive, not the controller, provides the reference clock.

• On the data cable, ESDI replicates rotational information

from the control cable so that each drive position can be monitored radially. This capability increases performance in multiple-disk configurations.

• ESDI supports higher data transfer rates.

A typical multi-drive ESDI configuration is shown in Figure 2-4.

M D 21 03 -0 99 0

Figure 2-4. Typical Multi-Drive Configuration

2-8 General Description

Compatibility

2.5 COMPATIBILITY

The following subsections discuss compatibility of the MD21 Controller with specific ESDI disk drives and SCSI host adapter systems and related microcontrollers. For more information about SCSI programming, refer to the Emulex SCSI Disk Controller Programming Reference Manual (part number MD2352501-00, Rev C).

2.5.1 SCSI BUS HARDWARE COMPATIBILITY

A disk drive that is connected to the SCSI bus, and that follows the protocol outlined in the ANSI SCSI Specification, is compatible with the MD21 Controller/disk drive unit. A standard 50-pin male connector, reference designated J6, plugs directly into the SCSI bus cable.

The MD21 Controller supports the SCSI bus single-ended option. The overall length of the cable that connects the SCSI host adapters and controllers in a daisy-chained manner can extend to 6 meters

(20 feet). All SCSI bus signals in the cable are terminated at each end by terminating resistors of 220 ohms to +5 VDC, and 330 ohms to ground. Terminators are optionally installed, depending on

the physical profile of the SCSI bus. For example, if the host adapter is terminated and no other device except the MD21 is on the SCSI bus, or the MD21 is replacing the last device on the SCSI bus, terminators would be installed in the MD21. The MD21 Controller

complies with the FCC limits for a Class B computing device (see

subsection 5.6 ).

2.5.2 ESDI DISK DRIVE COMPATIBILITY

The MD21 Controller connects one or two ESDI 5.25-inch magnetic disk drives via one 34-pin control connector, designated Jl, and one or two 20-pin data connectors, designated J2 and J3.

The MD21 supports ESDI disk drives that have clocks up to 15 megahertz. It supports hard-sectored, soft-sectored, and embedded

servo disk drives.

See Section 4.2.5 for drives that are supported by the Emulex ESDI-

to-SCSI disk controllers.

General Description 2-9

BLANK

Section 3

DISK CONTROLLER SPECIFICATIONS

3.1 OVERVIEW

This section contains the specifications for the components on the MD21 Controller. A general description of each component is

included under FUNCTIONAL in the General and Electrical Specifications table. (For a detailed description of the MD21 Controller's function as a whole, see Section 2, subsection 2.2.2, Functional Description). The specifications for the MD21 Controller are described in separate subsections, as listed in the

following table.

Subsection

3.1 Overview

3.2

3.3

3.4 Environmental Specifications

3.2 GENERAL AND ELECTRICAL SPECIFICATIONS

Table 3-1 lists and describes the general and electrical

specifications for the MD21 Controller.

Table 3-1. General and Electrical Specifications

Parameter

FUNCTIONAL

Design

General and Electrical Specifications Physical Specifications

Title

Description

High-speed microprocessor-based disk controller for integration of one or

two ESDI 5.25-inch Winchester disk

drives to SCSI bus

SCSI Bus/Controller Interface

Disk Drive Interface

(continued on next page)

Standard SCSI bus interface

via a standard 50-pin male connector

ESDI interface for 5.25-inch Winchester disk drives, via a 34-pin drive control connector and a 20-pin

data connector

Disk Controller Specifications 3-1

General and Electrical Specifications

Table 3-1. General and Electrical Specifications (continued)

Parameter

FUNCTIONAL

Subsystem Configuration

Number of Heads

Sector Size

Data Buffering

Data Burst Rate 1.25 Megabytes/second

Self-Test

Error Detection/ Correction

One or two non-intelligent 5.25-inch disk drives and one disk controller per subsystem

Up to 16 read/write heads

Switch-selectable 256-byte sectors or 512-byte sectors

32K bytes; approximately 14K bytes for each LUN

Controller automatically executes power-up self-test diagnostic routines

48-bit ECC corrects up to 17-bit error bursts. Bad sectors automatically

remapped to spare sectors; bad tracks automatically remapped to spare tracks .

Description

INDICATORS

Fault/Activity Di splay

Option/Configuration

Switches

Operator Controls/

Indicators

(continued on next page)

3-2 Disk Controller Specifications

Light-emitting diodes (LEDs) indicate detected MD21 Controller fault activity; MD21 Controller provides

signals that can be used to control off-board LEDs

On-board switch module for burn-in

self-test procedures and MD21 Controller configuration

Panel connector for remote control of write-protect and display of

ready/busy and write protect status

Physical Specifications

Table 3-1. General and Electrical Specifications (continued)

Parameter

INTERFACES

Bus Interface

Disk Drive Interface

RELIABILITY

Mean-Time Between

Failures (MTBF)

Manufacturing Burn-in

ELECTRICAL

Description

Standard SCSI bus single-ended option using approved receivers and

drivers

Standard ESDI disk drive interface; supports one or two 5.25-inch disk

drives

42,425 hours

96 hours (4 days)

Power

+5 VDC, + 5%, 1.5 amperes nominal,

50 millivolts ripple maximum

3.3 PHYSICAL SPECIFICATIONS

Table 3-2 lists and describes the physical specifications for the MD21 Controller. Figure 3-1 shows the physical dimensions of the MD21 Controller.

Disk Controller Specifications 3-3

General and Electrical Specifications

Table 3-2. Physical Specifications

Parameter

Packaging

Cabling

Lengths

Mounting

Holes (Set 1)

Description

Single board, 5.25-inch footprint,

5.75-inches by 8-inches

20-pin Drive 1 and 2 data cables; daisy-chained 34-pin drive control cable; daisy-chained 4-pin power connector; 50-pin flat-ribbon cable to SCSI bus

20-pin data cable: maximum length of 3 meters (10 feet); 34-pin control cable: maximum length of 3 meters; 50- pin SCSI cable: maximum length of 6 meters (20 feet)

Mounts up to 3 meters (10 feet) away

from the ESDI 5.25-inch Winchester disk drive using standard #6 screws

Length * 7.94 centimeters (cm) (3.125

inches) center to center; offset 4.13 cm (1.625 inches) from the front edge of the board (the end that contains

the SCSI connector)

Width = 13.97 cm (5.5 inches) center

to center; offset 0.318 cm (0.125

inches) from the board edge

Hole Size = 0.396 cm (0.156 inches) minimum

Holes (Set 2) Length = 16.764 cm (6.600 inches)

center to center; offset 1.27 cm

(0.500 inches) from the front edge of

the board (the end that contains the SCSI connector)

Width = 11.684 cm (4.600 inches)

center to center; offset 1.473 cm

(0.580 inches) from the board edge

Hole Size = 0.422 cm (0.166 inches) minimum

3-4 Disk Controller Specifications

Environmental Specifications

MD2103-0774

Figure 3-1. MD21 Controller Dimensions

3.4 ENVIRONMENTAL SPECIFICATIONS

Table 3-3 lists and describes the environmental specifications for the MD21 Controller.

Table 3-3. Environmental Specifications

Parameter

Description

Temperature

Operating

Storage

Relative Humidity

5°C to 50°C (41°F to 122°F)

-40°C to 66°C (-40°F to 150°F)

10% to 95%, noncondensing

Disk Controller Specifications 3-5

BLANK

Section 4

DRIVE CONFIGURATION PARAMETERS

4.1 OVERVIEW

This section contains the configuration parameters and sector settings for the ESDI disk drives which have been tested by Emulex

and are known to be compatible with the MD23 and the MD24. Also

included in this section is a discussion of disk operation.

4.2 ESDI DISK DRIVE PREPARATION

4.2.1 DRIVES SUPPORTED

Emulex has tested the MD2X with the following disk drives:

• CAST

• CDC

• Fujitsu

• Hewlett-Packard

• Hitachi

• Maxtor

• Micropolis

• NEC

• Priam

• Siemens

• Toshiba

4.2.2 DRIVE PLACEMENT

Uncrate and install the disk drives according to the manufacturer's

instruction. Position and level the disk drives in the final places before beginning the installation of the MD2X. This positioning allows the I/O cable routing and length to be accurately judged.

4.2.3 DRIVE NUMBERING

The two ESDI disk drives correspond to LUNs 0 and 1. Be careful that the two drives on the same controller are not assigned the same number. (The logical unit number is determined by the address given to the drive.)

10203 Wren III 94166-182 M2246E 97532EA (Coyote) DK512 EXT-4175 Series 2 , EST-4380E Series 1 1350 D5652 623 Megafile 1300 MK-156FA-I

EXT-4380 Series 3,

Drive Configuration Parameters 4-1

ESDI Disk Drive Preparation

4.2.4 SPINDLE CONTROL

Most ESDI drives can be jumpered so that either (1) the drive spins up whenever power is applied or (2) the drive spins up under

control of the MD21. Emulex recommends that drives always be jumpered to spin up under control of the MD21.

4.2.5 DRIVE SECTORING AND OTHER OPTIONS

The MD21 supports both hard-sectored and soft-sectored drives. Table 4—1 lists the drives supported by the MD21. This list contains every drive that Emulex has tested to conform to the timing requirements for both the Emulex ESDI-to-SCSI disk controllers and the ESDI specification. Note that specific revision levels are listed for each model of drive. Different revision levels of the same drive can sometimes be significantly different.

The drives in this list have not been verified against their own specifications for these parameters: soft/hard error rates, temperature, vibration, humidity, MTBF, MTTR, and others.

Some drives give substantially better performance when they are hard-sectored. These drives are listed in Table 4-1 and Emulex strongly recommends running these drives in hard-sectored mode if possible .

All the parameters listed in Table 4-1 are fully defined in the

section following the table.

4-2 Drive Configuration Parameters

ESDI Disk Drive Preparation

Table 4-1. Recommended Disk Parameters for Use With MD21

Ven dor /M od el Rev Sec tor s/Tr a ck

Siz e an d Typ e

C A S T

102 03

C DC

W ren I II 9 4 1 66-1 8 2 Lot

Fujits u C4

M 22 4 6E

H e w let t- P a cka rd

975 32EA (Coy ote)

H ita chi

D K512

M ax tor

E X T- 4 175 Se rie s 2 7 3 4 /

E XT -4 380 S e rie s 3

86/07

863 2 65 / 256 Hard

87/ 04 64 /

F C /T 3 3 5/ 512 Har d 2 9

35 / 51 2 So ft 18 1 8 2 0880 62 /

256 Soft 33 6

36 /512 Hard 16

35 /512 Ha rd 20 63 /256 H ard

256 Im be d

62/

256 Hard

512 S of t

58 /256 S of t

34 /512 Soft 12

3

58 /

256 S oft

ISG PLO Siz e Size

11

12 2086 4

44

12

13 224 00 34 8

11

26 2080 8 61 1

B yte s pe r tr a ck per sec tor

208 80

209 44

M in b yte s Co mm e nts

59 2

577 32 1

58 3 32 7

59 0 H ard sec tor s 33 4 rec om men de d .

35 2

352

H ard -se cto rs re com m en d ed.

A ggr ess iv e Se ek & Fas t com m an d ti m ing

E X T -4380 E Series 1 7 3 4 /5 12 S o ft 14 2 4

M icr o p olis

135 0 86/11 3 6/ 512 H ard 16

N E C

D 56 5 2

Priam

62 3

Sie m en s

M eg afile 1300

T o shib a

M K 15 6FA -I

86/ 04

C C L-D

19 & 16 64 & 80

60 /256 Soft

64 /

256 Ha rd

512 H ard

35 / 63 / 256 H ard 329

35 / 512 Ha rd 26

256 H ard

63 /

35 /512 I m be d

B

512 H ard 20

35 / 64 /

256 H ard 32 5

24 11 2 0 992

32

209 40

11 2083 3

208 32 58 7

11

16 2 1 280

208 32

11

60 4 34 6

57 7 32 1

585

330

60 8

58 1

Fast & N orm al S e ek

Drive Configuration Parameters 4-3

ESDI Disk Drive Preparation

The parameters shown in Table 4-1 are defined as follows:

Vendor/Model This indicates what company produced the drive and

the model of drive that was tested.

Rev This is the Revision number of date of manufacture

for the drive that was tested.

Sectors/Track This is the maximum number of sectors that can be

used. Note that the drive may not have switch or

jumper options capable of selecting this number of sectors. If this is the case, the next smaller

value should be used.

Size This is the size in bytes for the data portion of

the sector.

Type

ISG

PLO

This is the recommended type of sectoring (Used in calculating this information). In some cases this

is also the only sectoring possible. The possible types are:

Soft The controller determines format.

Hard The drive provides the sector pulses.

Imbedded The drive provides sector pulses but the

drive uses servo information from between the sectors and not from a separate Servo Track. This also

indicates that the Head Switch time will

be equal to a single track seek.

This is the minimum length required for the Inter- Sector Gap as specified by the drive via the ESDI

request configuration command.

This is the minimum number of bytes required in each of the Phase Lock Oscillator fields as

specified by the drive via the ESDI request configuration command. One of these exits before

both the Header and Data fields.

Bytes per Track

4-4 Drive Configuration Parameters

This is the number of bytes guaranteed to be present on a track on one surface (head) of the drive as specified by the ESDI request

configuration command.

Disk Operations

Min bytes per In the Hard Sector mode this is the minimum

sector number of bytes between sector pulses that is

required by the controller. For a soft-sectored

drive, this is the sector length the controller will use. This size includes all controller and drive overhead, gaps, sync, and data fields.

Comments This column Mentions any non-standard ESDI

features supported by both the controller and drive. Having this information may assist you in

setting option jumpers.

4.3 DISK OPERATIONS

The following subsections describe controller functions during operations with the disk drive.

4.3.1 SECTOR AND TRACK FORMAT OPERATIONS

For hard-sectored disk drives, the controller formats each sector

as shown in Figure 4-1. For soft-sectored disk drives, the

controller formats each sector as shown in Figure 4-2. The Inter Sector Gap (ISG) and PLO Sync fields vary between disks and their sizes are returned by the disk drive over the disk interface (see Figure 4-1 and 4-2). The controller formats each track with a

physical address in the header identification (ID) field of each

sector. The controller supports a 5-byte header as shown in Figure

4-1 and 4-2. The track address is defined as the cylinder and head address of the specified track. Spare sectors may be allocated on each track. The interleave factor may be specified during a format operation (see the FORMAT UNIT command in the Emulex SCSI Disk Controller Programming Reference Manual, manual number MD2352501).

When a data track develops multiple error conditions that cannot be

resolved by the use of spare sectors, the controller saves the data

from the track and reformats it as a flawed data track. The defective data track is reformatted with the Defective Track bit and the track address of the allocated alternate track in the header of each sector. The data saved from the defective track is written to the alternate track.

An alternate track is a track in the reserved-controller storage

area on the disk drive. When an alternate track is so allocated,

it is formatted with the sector address of the defective track. The controller considers the interleave factor when it formats an

alternate track.

Drive Configuration Parameters 4-5

Disk Operations

4.3.2 GROWN DEFECT LIST OPERATIONS

The controller maintains the Grown Defect List on one cylinder

in an area that is not accessible to the host. The Grown Defect List is duplicated on each track of the Grown Defect List cylinder and may not be larger than one track. The controller returns the contents of the Grown Defect List during

the Data Out phase of a READ DEFECT LIST command (described in

the Emulex SCSI Disk Controller Programming Reference Manual, manual number MD2352501).

4-6 Drive Configuration Parameters

Disk Operations

INDEX

_TLln

*

CYLINDER

INTER

SECTOR

GAP

SYNC DATA

HI

u.

z

PLO

SYNC

SYNC BYTE

FEh

NUMBER

(MSB)

— *—

1 BYTE

CYLINDER

NUMBER

(LSB)

--v-

1 BYTE

HEADER ID

__

A _

TRACK

NUMBER

------"Y-------

1 BYTE

SECTOR

SECTOR NUMBER

- - - - - --

y .

1 BYTE

4

a

FLAGS

-- - -

CRC PAD

~ ------

2 BYTES

ECC

Y

-----

O D VTC C

PAD

WRITE

SPLICE

------V-----

1 BYTE

SPEED

TOLER-

ANCE

PLO .

SYNC /

SECTOR

* * * *

INTER

SECTOR

GAP

™ n _

----V----

256 OR 512 BYTES

‘ REPORTED BYTES AFTER INDEX FROM THE DRIVE

“ REPORTED PLO FIELD FROM THE DRIVE +1

‘ “ IF THE DRIVE REQUIRES A SPEED TOLERANCE GAP THIS LENGTH IS THE UNFORMATTED

SECTOR SIZE TIMES .01 OR .02 DEPENDING ON WHAT THE DRIVE REPORTS.

“ “ REPORTED INTER SECTOR GAP MINUS REPORTED BYTES AFTER INDEX.

A

6 BYTES 2 BYTES

Figure 4-1. Sector Format for Hard-Sectored Disk Drives

Drive Configuration Parameters 4-7

MD2103-0821

Disk Operations

INTER

SECTOR

ADDRESS

MARK

GAP

PAD

**

PLO

SYNC

SYNC BYTE

FEh

r

CYLINDER

NUMBER

(MSB)

SECTOR

CYLINDER

NUMBER

(LSB)

HEADER ID

_____

TRACK

NUMBER

SECTOR

NUMBER

FLAGS

CRC

PAD

WRITE

SPLICE

3 BYTES | 1BYTE 1 BYTE 1 BYTE 1 BYTE 1 BYTE I 2 BYTES |

1 BYTE 2 BYTES 1 BYTE

9

I PLO

, SYNC

“ REPORTED PLO FIELD FROM THE DRIVE +1.

SYNC

BYTE

FEh

256 OR 512 BYTES

‘ REPORTED BYTES AFTER INDEX FROM THE DRIVE

DATA

Y

-A

ECC

- - - - - - -f- - - - - - -

6 BYTES

PAD

■ A y ./

2 BYTES

SPEED

TOLER

ANCE

MD2103-0822

Figure 4-2. Sector Format for Soft-Sectored Disk Drives

4-8 Drive Configuration Parameters

Section 5

INSTALLATION

5.1 OVERVIEW

This section describes the step-by-step procedure for setting up and installing the MD21 Controller. This section is divided into five subsections, as listed in the following table:

Subsection

5.1

5.2

5.3

5.4

5.5

Overview Inspection MD21 Controller Setup MD21 Controller Installation FCC Compliance

Title

If you are unfamiliar with the MD21 Controller installation

procedure, we recommend reading this Installation Section before beginning.

When you are installing the subsystem, you should make a record of

the subsystem configuration and environment. Figure 5-1 is a Configuration Record Sheet that lists the information required.

Also, this information will be of help to an Emulex service

representative should your subsystem require service.

Installation 5-1

MD21 CONFIGURATION REFERENCE SHEET

GENERAL INFORMATION

• Host computer Type

_____________________

SCSI Bus Address

____

„

• Host computer operating system ________________________________ Version

• Other SCSI Controllers: Type

____________

_________________

, SCSI Bus Address

DRIVE CONFIGURATION PARAMETERS

• Drive Drive 1 Drive 2 Manufacturer(s)

• Model Number

___________________________

_________________

___________________________ _________________

• Parameters:

Number Units Sectors/Track Heads Cylinders

___________________________ _________________ ___________ ___________________________

________________ _________________

_________________

___________________________ _________________

MD21 CONFIGURATION

• Firmware revision number

• Top assembly num ber

• SCSI bus address

__________________

____________

_______________

• Warranty expiration d ate

• Serial number

_______________

_______

LED 4 LED 3 ■ JUMPERS

Figure 5-1. MD21 Configuration Reference Sheet

5-2 Installation

MD 2103- 0776

MD21 03-10 12

MD21 Controller Setup

5.2 INSPECTION

Emulex products are shipped in special containers designed to provide full protection under normal transit conditions.

Immediately upon receipt, please follow this procedure:

1. Inspect the shipping container for evidence of possible damage incurred in transit.

2. Unpack the MD21 Controller and verify that all components listed on the shipping invoice are present.

3. Verify that the model or part number (P/N) designation,

revision level, and serial numbers agree with those on the

shipping invoice.

These verifications are important to confirm warranty. If evidence of physical damage or identity mismatch is found, notify an Emulex representative immediately.

4. Check the MD21 Controller after unpacking for bent or broken connector pins, damaged components or any other evidence of physical damage.

5. Carefully examine all socketed components to ensure that they are firmly and completely seated.

Report any obvious damage to the container, or indications of actual or probable equipment damage, to the carrier company in accordance with instructions on the form included in the container.

5.3 ND21 CONTROLLER SETUP

5.3.1 SWITCH SETTINGS

Some of the switches in DIP switch pack SWl on the MD21 Controller

allow configuration of various options available with the MD21. All switches on the MD21 Controller are set to a standard configuration before the MD21 Controller is shipped from the factory. Table 5-1 lists the function and factory settings of all switches on the MD21 Controller. This subsection provides a detailed description of the function of each switch.

NOTE

If the position of a switch on the MD21 is changed, the host must issue a reset before that switch change becomes permanent.

Installation 5-3

MD21 Controller Setup

Table 5-1. DIP Switch Settings, MD21 Controller

Switch

Function

Options

(Factory Settings

in Boldface)

Section

SW1-1 SW1-2

SW1-3 SWl-4 SW1-5

SW1-6

SW1-7

SW1-8

SCSI Bus Address (LSB) SCSI Bus Address SCSI Bus Address (MSB) Not Used

Physical Sector Size*

Disable Drive Spinup

Disable Soft Error Reporting

SCSI Bus Parity Enable

0 = OFF/OPEN 1 = ON/CLOSED

*This switch applies only to soft-sectored drives and is

ignored by hard-sectored drives.

00, 01 through 07

0=512 bytes, 1=256 bytes

0=Drives are spun up

automatically

l=Drives are not spun

up automatically

0=Errors reported l=Errors not reported

0=Parity Check disabled

l=Parity Check enabled

5.3.1.1

5.3.1.2

5.3.1.3

5.3.1.4

5.3.1.5

Figure 5-1 shows the location of the configuration switches on the MD21 Controller. The configuration switches should be set before

the MD21 Controller and the disk drive are installed in a subsystem, because the switches may not be accessible after the

MD21 Controller and the disk drive are installed.

5.3.1.1 SCSI Device Address Selection (SW1-1 through SW1-3)

Switches SW1-1, SW1-2, and SW1-3 select the SCSI bus address for the MD21 Controller. The selected address establishes the SCSI bus

identity of the MD21 Controller in the system. An Initiator must specify this address to select the MD21 Controller as a Target

device. Verify the switch settings with Table 5-2 and be sure that

the same SCSI device address is not assigned to another host

adapter or controller.

5-4 Installation

MD21 Controller Setup

Table 5-2. SCSI Device Address Selection Switches

Switch

SWl-3 SWl-2

(MSB)

SWl-1 SCSI Device Address

(LSB)

0 0 0 0 0

0

1 0 1 1 1 0 0 1 1

0 1

1 1 1 1

0 = OFF

(OPEN)

1 0 02

0

1 = ON (CLOSED)

00 01

03 04

05 06 07

5.3.1.2 Sector Size (SWl-5)

Switch SWl-5 determines the size of the sector on the disk drive

(soft-sectored drives only). Setting this switch to ON (closed) sets the sector size on the disk drive to 256 bytes. Setting this switch to OFF (open) sets the sector size to 512 bytes. The factory setting is OFF, as shown in Figure 5-2.

512 bytes (factory setting)

256 bytes

Figure 5-2. Sector Size Switch Setting

Installation 5-5

MD21 Controller Setup

5.3.1.3 Disable Drive Spinup (SWl-6)

Switch SWl-6 indicates whether or not the MD21 Controller automatically spins up the drive during controller power up. When

this switch is set to ON (closed), the controller does not spin up the drives during power up. When this switch is set to OFF (open), the controller automatically spins up the drives during power up.

The factory setting is OFF, as shown in Figure 5-3.

3 4 5 6 7 8

1 2

o n r

N — —

t U LI

1 2

o n r

N - -

t u u

BSBBBB

3 4 5 6 7 8

0BBI00

Drive automatically spins up

(factory setting)

Drive does not spin up

Figure 5-3. Drive Spin Up Switch Setting

NOTE

The disk drive must be configured to only spin up upon a command from the controller or this switch will have no effect.

5.3.1.4 Disable Soft Error Reporting (SWl-7)

Switch SWl-7 indicates whether or not the MD21 Controller reports

soft errors that occur during MD21 operations. When switch SWl-7 is left in the OFF (open) position, the MD21 Controller reports soft errors. Setting switch SWl-7 to ON (closed) prevents the MD21

Controller from reporting soft errors. Normally, switch SWl-7 is

set to OFF, as shown in Figure 5-4.

1

2 3 4 0 N

t

5 6 7

e

8

Soft errors are reported

(factory setting)

1

2 3 0

N

t

4 5 6 7

8

Soft errors are not reported

Figure 5-4. Soft Error Reporting Switch Setting

5-6 Installation

MD21 Controller Setup

5.3.1.5 SCSI Bus Parity Enable (SWl-8)

Switch (SWl-8) enables the SCSI bus parity check. The factory setting for this switch is OFF (parity check disabled), as shown in Figure 5-5.

1 2

0 N

t

3 4 5 678

Parity check disabled

■

(Factory setting)

1 2

0 N

t

4 5

3

7

6

8

Parity check enabled

fl

Figure 5-5. Parity Enable Switch Setting

5.3.2 SCSI BUS TERMINATION POWER OPTION

The SCSI termination power option allows the MD21 to supply between +4 and +5 VDC power to the subsystem^ external terminators via pin 26 of the SCSI bus. The SCSI Termination Power option is not

required if the MD21 is resident in an Emulex subsystem that

contains an internal terminator power board. On-board terminators

(see subsection 5.3.3) do not require that the SCSI Termination

Power option be installed.

CAUTION

When this option is implemented, the voltage

supplied on pin 26 is not current limited. If this pin becomes grounded— for example, by a misoriented connector— damage to the MD21 Controller and/or to the system cabling may result.

If the SCSI termination Power option is required, install a #1N5817

diode at reference designator CR2. Also connect a wire-wrap jumper

between jumper posts E and F. See Figure 5-1.

Installation 5-7

MD21 Controller Installation

CAUTION

If diode leads are reversed so that the anode of the diode is in the wrong hole, the system will not function properly (the cathode end is usually

identified by a white line or other unique marking

on the diode).

If there are multiple controllers attached to the SCSI bus and power is removed from the MD21 Controller that is configured to supply the terminator power, the other controllers will not

function correctly. Under these conditions, the host should supply the power.

5.3.3 SCSI BUS TERMINATION

The MD21 Controller can be configured to terminate the SCSI bus by inserting one 220/330-ohm resistor pack in the sockets located at U22 and U35 on MD21. The resistor packs are available in the Emulex SCSI terminators kit, P/N MD0113002. A SCSI system configuration should contain only two devices that terminate the SCSI bus. Usually these devices are a host adapter and one peripheral device controller (such as the MD21 Controller). Termination should be installed only on the controller that is physically last on the SCSI bus.

5.4 MD21 CONTROLLER INSTALLATION

This subsection describes a sample procedure for installing the

MD21 Controller in the disk drive chassis. To install the MD21,

see Figures 5-6 and 5-7 and use the following procedure:

NOTE

The installation instructions and figures in this subsection assume the use of an Emulex mounting

bracket to install the MD21 on top of the ESDI

disk drive. It is necessary to use some kind of

intermediary device so that the controller does not sit directly on the disk drive. One mounting bracket for use with the MD21 is available in Emulex kit number MD0113003.

5-8 Installation

MD21 Controller Installation

1. Configure the MD21 Controller by setting the switches on switch pack SWl. All switches have been set at the factory; however, you may need to reset some switches for your specific needs.

2. Place the disk drive on a flat surface.

3. Place the MD21 Controller (component side up) on top of the mounting bracket. Align the four screw holes on the MD21 Controller with the four screw holes on the mounting bracket

(see Figure 5-6). Secure the MD21 Controller in place with

four 4-40 x 1/4-inch screws.

4. Connect the control cable from the disk drive to connector J1 on MD21 Controller. See Figure 5-7.

5. Connect the data cable(s) from the disk drive to connectors J2 and/or J3 on the MD21 Controller. See Figure 5-7.

6. Connect the cable from the power supply to power connector J7 on MD21. See Figure 5-7.

7. Connect the SCSI bus cable to SCSI bus connector J6 on MD21 Controller. See Figure 5-7.

8. If you are going to connect the controller to a user panel, refer to section 7.4.

NOTE

Note that Figure 5-7 shows a SCSI flat-ribbon cable that is used to internally connect the MD21 Controller with a SCSI host adapter. If the MD21 Controller and SCSI host adapter reside in different cabinets, you must use a shielded SCSI cable to connect them to maintain FCC compliance

(see subsection 5.5). For more information on

shielded cable requirements, see subsection

7.2.1.2.

Installation 5-9

MD21 Controller Installation

Figure 5-6. Installing the MD21 Controller on the Mounting Bracket

Figure 5-7. Connecting the Disk Drive Data and Control Cables

and the SCSI bus to the MD21 Controller

5-10 Installation

FCC Compliance

Table 5-3 summarizes the specifications for each type of cable:

Table 5-3. Disk Drive Cable Requirements

Data Cable

(One cable to

each drive)

10 feet (3 meters)

Number of lines

Maximum cumulative

Control Cable

(daisy-chained to

1 or 2 drives)

34 20

10 feet (3 meters)

cable length

Recommended

connector

AMP ribbon connector

P/N 499560-3

(or equivalent)

MD21 cable J1

5.5 FCC COMPLIANCE

AMP ribbon connector

P/N 499560-6

(or equivalent)

J2 and/or J3

The Federal Communications Commission (FCC) has established technical standards regarding radiation of electromagnetic

interference (EMI) emitted by computing devices. The MD21 Controller has been type tested and found to comply with the EMI emission limits for a Class B computing device in accordance with the specifications in Subpart J of Part 15 of FCC Rules. However, there is no guarantee that interference will not occur in a particular installation.

The MD21 Controller was tested for FCC compliance in a compliant subsystem that was properly shielded (enclosed so that no electro

magnetic radiation escapes). The subsystem was connected to other

SCSI port devices via a shielded SCSI bus cable. Emulex offers shielded cables, compatible with the MD21 Controller, that are

available in various lengths. For information on SCSI bus cable

and connector requirements, see subsection 7.2.1.

The MD21 Controller equipment generates and uses radio frequency energy. If it is not installed and used in strict accordance with Emulex's instructions, it may cause EMI with radio and television reception. It is the responsibility of the user to properly install the MD21 and ESDI disk drives in a subsystem.

Installation 5-11

FCC Compliance

When installing the MD21 and its disk drives, you must take care that the shield that has been built into equipment cabinets is not

defeated.

The routing of the cables that connect the MD21 and its disk drives can have a major impact on the amount of EMI that is radiated by the system, especially if the MD21 and the disk drives are installed in separate cabinets. Emulex is not responsible for any radio or TV interference caused by unauthorized modifications to the MD21 Controller.

If the MD21 Controller causes interference with radio or television reception, as determined by turning the equipment on and off, try to correct the interference by one or more of the following

measures:

• Reorient the receiving antenna.

• Relocate the compliant subsystem (that contains the MD21 Controller) with respect to the receiver.

• Move the compliant subsystem away from the receiver.

• Plug the compliant subsystem into a different outlet so that the subsystem and receiver are on different branch circuits.

• Verify that the mounting screws and grounding wires on the compliant subsystem are tightly secured.

If necessary, consult the dealer or an experienced radio/television technician for additional suggestions. You may find the following booklet prepared by the FCC helpful:

Title: How to Identify and Resolve Radio-TV

Interference Problems Publication Number: Stock No. 004-000-00345-4 Publisher: U.S. Government Printing Office

Washington, D.C. 20402

5-12 Installation

Section 6

CONTROLLER INITIALIZATION AND SELF-TEST PROCEDURES

6.1 OVERVIEW

This section describes the diagnostic features with which the MD21 Controller is equipped. MD21 Controller diagnostic modes include power-up (and reset) self-test and online host-initiated diagnostic facilities. The principal function of these tests is to determine MD21 Controller functional integrity and to distinguish failures of the MD21 Controller from those of the disk drive. This section is divided into four subsections, as listed in the following table:

Subsection

6.1

6.2

6.3

Overview Controller Reset/Power Up Initialization

Self-Test Modes

Title

6.4 Online Diagnostic Commands

6.2 CONTROLLER RESET/POWER UP INITIALIZATION

This section describes the sequence of events during controller initialization and self-test sequences. The self-test sequence occurs before the initialization sequence occurs.

6.2.1 SELF-TEST SEQUENCE

The self-test sequence will be executed only when a controller power-up condition occurs. The self-test sequence verifies the integrity of the hardware. This test is not an exhaustive hardware diagnostic, but simply checks the major components for full functionality. If the self-test fails, the controller

will light the Error Indicator and will stop any further

initialization. If the self-test fails, only a SCSI Bus Reset or Power On Reset condition will restart the controller. During the self-test, the controller will not respond to a

Selection Phase on the SCSI Bus.

Controller Initialization and Self-Test Procedures 6-1

Controller Reset/Power Up Initialization

The self-test sequence consists of the following events:

• Hardware Reset Test - This routine tests the 8031 microprocessor, buffer controller, disk formatter, and

SCSI reset latch for the proper power-up condition. If any of these tests fail, the controller can only be reset by a power-up condition.

• 8031 Test - This routine tests the 8031 internal memory,

timers, and register bank switching for proper

operation.

• PROM Checksum Test - This routine performs a checksum calculation on the controller firmware PROM and compares it against the checksum stored in the PROM.

• Buffer Controller Test - This routine tests the buffer

controller for proper operation. All the registers are tested and the chip is engaged to access RAM memory. Other portions of the self-test check parts of the buffer controller, which cannot be tested at this time.

• Dynamic RAM Test - This routine tests the dynamic RAM

memory by writing and reading different patterns to

memory. In addition, the buffer controller is tested

for proper refresh operation and parity detection. This test also tests the memory parity interrupt.

• Disk Formatter Test - This routine tests the disk formatter chip by writing and reading all possible

patterns to each of the disk formatter chip registers. After the registers are tested, the interrupts are

tested to ensure the formatter chip generates an interrupt when a command completes.

• SCSI Controller Test - This routine tests the SCSI controller chip by executing the chip diagnostic command. After the diagnostic test completes, the interrupts are tested to ensure the SCSI chip generates

an interrupt when a command completes. Finally, the

registers are tested by writing and reading all possible

patterns to each of the SCSI controller chip registers.

If any portion of the self-test fails, except the hardware reset test, the controller can be reset by a SCSI bus reset condition or a power-up reset condition. The failure of the hardware reset test is considered a catastrophic failure and the controller can only be reset from such a failure by a power-up reset condition.

6-2 Controller Initialization and Self-Test Procedures

Controller Reset/Power Up Initialization

During the self-test, the onboard LEDs will indicate which test(s) are in progress as shown in Table 6-1.

Table 6-1. LED Sequences for Self-Test Procedure

Red LED

OFF

Green LED

OFF

ON

Description

Hardware Reset Test

8031 Test PROM Checksum Test Buffer Controller Test Dynamic RAM Test

ON

OFF

Disk Formatter Test SCSI Controller Test

ON

Self-Test Passed

If any of the tests fail, the pattern (ON or OFF) displayed by

the LEDs indicate which portion of the self-test failed.

NOTE

Due to the large amount of RAM memory on some

controllers, the power up self-test may take up

to 10 seconds to complete. During this time,

the controller will not respond to a SCSI Bus

Selection Phase.

6.2.2 INITIALIZATION SEQUENCE

The initialization sequence will be executed for any one of the following three reasons:

• Controller Power-Up condition occurs

• SCSI Bus Reset (-RST) signal is asserted

• BUS DEVICE RESET message (on the SCSI bus) is received

• A RESET occurs if the DC voltage drops to 4.5 or less and an INITIALIZATION sequence occurs when the voltage

returns to 4.515 or above.

Controller Initialization and Self-Test Procedures 6-3

Controller Reset/Power Up Initialization

The initialization sequence consists of the following events:

1. Initialize SCSI firmware

a. Set status for all LUN's to BUSY

b. Initialize SCSI interface

c. Enable SCSI interrupts

2. At this point, the controller responds to a selection phase from the initiator but returns a BUSY status until

the initialization sequence is complete.

3. Initialize the disk firmware for each LUN supported by

the controller.

a. If a drive is not connected to this LUN, stop

initialization for this LUN and go to the next LUN.

b. Read the defalt parameters from the drive and/or

switches.

c. If this is a power-up condition and the disable spin

up switch is off, a START UNIT command is sent to the drive to start the spin up operation. The controller

will not wait for the spin up to complete before

continuing to the initialization sequence. If this is a SCSI bus reset or bus device message reset, no action is taken.

d. Turn on the user panel "ready" LED.

4. At this point, the BUSY status is removed from all LUNs and the controller accepts commands from the initiator.

Once the initialization sequence is complete, the controller enters the IDLE state and flashes the green LED. As long as the green LED is flashing, the controller is in its normal state of operation.

NOTE

The green LED may stop flashing momentarily while executing an command.

6-4 Controller Initialization and Self-Test Procedures

Controller Reset/Power üp Initialization

After this sequence is complete, the first command sent by an

Initiator is terminated with a CHECK status and a UNIT

ATTENTION Sense Key, For more information, see subsection 5.5,

SCSI Error Conditions, in the Emulex SCSI Disk Controller Programming Reference Manual (manual number MD2352501).

Until the drives have been spun up, any command sent by an initiator which accesses the media is terminated with a CHECK status and a DRIVE NOT READY sense key.

After the drive has spun up, the first commmand sent by an initiator which accesses the media loads the SAVED MODE sense

parameters. Prior to the drive being spun up, if an initiator

requests the current MODE SENSE parameters, the controller

returns the default MODE SENSE parameters. An initiator should not request the MODE SENSE parameters until the drive is spun up.

6.3 SELF-TEST MODES

The MD21 Controller performs a self-test procedure when it operates in either of two modes: the normal mode or the burn-in mode. These two modes and their corresponding self-test procedures are described in the following subsections.

6.3.1 NORMAL MODE

The MD21 Controller operates in the normal mode when it performs typical disk controller functions such as a disk format operation or a read operation. When the MD21 Controller is operating in the

normal mode and power-up or reset conditions occur, it performs a

self-test procedure to determine whether its interface circuits, memory, and on-board microprocessor are operative. The self-test procedure consists of several individual tests that exercise separate components of the MD21 Controller. These tests are performed sequentially? the success of one test enables the next test to be executed. If an individual test fails, the MD21

Controller self-test procedure stops at the location of the

failure.

Before the self-test procedure begins, a Power-up Reset Clear code

is output to the two on-board LEDs to indicate that the MD21

Controller is ready to perform a self-test. If the MD21 Controller

self-test procedure succeeds, a Self-Test Pass code is output to the on-board LEDs. The LED locations on the MD21 Controller are shown in Figure 6-1, and LED Test Code descriptions are listed in Table 6-1.

Controller Initialization and Self-Test Procedures 6-5

Controller Reset/Power Up Initialization

LED 4 LED 3 ■ JUMPERS

Figure 6-1. Location of LEDs on the MD21 Controller

Table 6-2. LED Test Code Descriptions

LED 2 LED 1

Test Description

(Red) (Green)

0 0 1 1

Power-up Reset Clear Power-Up Self-Test Pass Code

0 = OFF (not lit) 1 = ON (lit)

MD2103-0776

6-6 Controller Initialization and Self-Test Procedures

Controller Reset/Power üp Initialization

If the MD21 Controller is operative, green LED 1 blinks- If the MD21 Controller fails its self-test procedure, LED 1 does not blink.

After the self-test procedure is successfully completed, the MD21 Controller continues with the initialization routine. If the SCSI interface circuits and the 8031 microprocessor are functioning, the MD21 Controller enters the online mode and is available to the

Initiator. At this time, the Power-Up Self-Test Pass code (see

Table 6-1) is momentarily displayed by LED 1 and LED 2. Failure of any portion of the self-test result in a selection timeout.

6.3.2 BURN-IN MODE

During the burn-in mode, the MD21 Controller self-test procedure is repeated continuously until a failure is detected. The MD21

Controller contains an eight-bit burn-in connector used to report

self-test failures when the MD21 Controller is operating in the burn-in mode. The burn-in connector consists of four pin assignments on the test connector, and four pin assignments on the User Panel connector. The reference designators are as follows (see Figure 6-1):

• MD21 Controller: Test connector: J5 User panel connector: J4

The burn-in connector pin assignments are shown below:

Bit

$MD21 Connector

07

J5-9

06 05 04 03

J5-8

J5-7

J5-12

J4-4 J4-6 J4-7

02 01 00

J4-9

Controller Initialization and Self-Test Procedures

6-7

Online Diagnostic Commands

As each individual test is performed during the MD21 Controller burn-in mode, a test code is output to the burn-in connector to

indicate which component on the MD21 Controller is currently being tested. If an individual test fails, the corresponding test code is output. The individual tests in the self-test procedure and their corresponding hexadecimal codes are listed in Table 6-2.

To establish the MD21 Controller burn-in mode, ground pin J5-5. Once the burn-in mode has been established, to cause the MD21 Controller to perform its self-test procedure continuously, ground pin J4-8 and reset the MD21 Controller.

Table 6-3. MD21 Controller Test Code Descriptions

Test Code *

Test Description

(hexadecimal)

00 01 02 04 40 41 42 43 44 45 46 80 81 83 84 85

Power-up Start Code Buffer Controller Reset Status Test Disk Formatter Reset Status Test SCSI Reset Latch Test

8031 Microprocessor Self-Test ROM Checksum Test Buffer Controller LSI Register Test External RAM Data Test External RAM Parity Test Buffer Controller LSI Parity Detection Test Buffer Controller LSI Parity Interrupt Test Disk Formatter LSI Register Test Disk Formatter LSI Interrupt Test SCSI Controller LSI Self-Diagnostic Test SCSI Controller LSI Interrupt Test SCSI Controller LSI Register Test

* Asserted bits are low true.

6-8 Controller Initialization and Self-Test Procedures

Online Diagnostic Commands

6.4 ONLINE DIAGNOSTIC COMMANDS

The MD21 Controller supports a set of online diagnostic subcommands, which are used to further delineate peripheral or MD21 Controller failures. These diagnostic subcommands are specified by the SEND DIAGNOSTIC command and executed by the RECEIVE DIAGNOSTIC command. The diagnostic subcommands are listed in Table 6-3 and described in the SEND DIAGNOSTIC COMMAND section of the Emulex SCSI Disk Controller Programming Reference Manual, manual number MD2352501.

Table 6-4. MD21 Controller Diagnostic Subcommands

Diagnostic Subcommand

GET DRIVE STATUS

PASS DRIVE COMMAND

READ DISK PARTITIONS

READ HEADER

Description

Causes the MD21 Controller to return unmodified status from the disk drive. |

Causes the MD21 Controller to pass disk drive commands from the

Initiator to the disk drive.

Causes MD21 Controller to transfer the physical addresses related to the logical partitions on the specified disk drive to the Initiator.

Causes the MD21 Controller to perform a read operation of the header address field for each block of a track.

Controller Initialization and Self-Test Procedures

6-9

BLANK

Section 7

INTERFACES

7.1 OVERVIEW

This section describes the interfaces used by the MD21 Controller.

It includes information about how the MD21 implements the SCSI bus interface electrical and mechanical requirements, and how it implements the ESDI interface electrical requirements. It also describes the user panel connection and the DC power connection.

This section is divided into five subsections, as listed in the following table:

Subsection

7.1

7.2 SCSI Bus Interface

7.3

7.4

7.5 DC Power Connection

7.2 SCSI BUS INTERFACE

This subsection provides information about MD21 Controller implementation of SCSI bus electrical and mechanical requirements.

7.2.1 SCSI BUS INTERFACE PHYSICAL DESCRIPTION

The following features of the SCSI Bus Interface should be noted:

• SCSI bus devices are daisy-chained with a common cable; both ends of the cable are terminated.

• All signals are common among all SCSI bus devices.

• The MD21 Controller supports the ANSI SCSI specification single-ended option for drivers and receivers.

Overview

ESDI Disk Drive Interface User Panel Connection

Title

Interfaces 7-1

SCSI Bus Interface

• The maximum cable length allowed is 6 meters (20 feet).

The length of the cable located within the FCC compliant subsystem cabinet (that contains the MD21 Controller) is included when calculating the total length of the SCSI bus.

The SCSI cable that connects the compliant subsystem cabinet

(that contains the MD21 Controller) to the host system must

be shielded and properly grounded.

To support daisy-chain connections, SCSI devices that use shielded connectors should provide two shielded device connectors on the compliant subsystem cabinet. These two connectors may be wired one-to-one, with a stub going to the SCSI device's drivers and receivers (provided the maximum stub length specified in subsection

7.2.1.1 is not exceeded). Alternatively, two cables may be run from two shielded connectors to the drivers and receivers so that the maximum stub length is not exceeded.

7.2.1.1 Internal Cable Requirements

If the MD21 Controller and the SCSI host adapter reside in the same compliant cabinet, you must use a 50-conductor flat-ribbon cable or a 25-twisted-pair flat cable to connect the MD21 Controller and SCSI host adapter. The maximum cumulative cable length is 6

meters. Each SCSI bus connection should have a stub length (the length of the cable beyond the terminator) of no more than 10

centimeters (4 inches). For information on SCSI bus termination,

see subsection 5.3.3.

7,2.1.2 Shielded Cable Requirements

If the MD21 Controller and SCSI host adapter do not reside in the

same compliant subsystem, then a shielded SCSI cable must be used to connect the MD21 Controller and the host adapter. The connector for the SCSI bus shielded cable is a 50-pin connector, designated J6, that contains two rows of 25 female contacts on 100 mil centers. The connector shielding system must provide a direct current (DC) resistance of less than 10 milliohms from the cable shield at its termination point to the compliant subsystem cabinet. For information on FCC compliance, see subsection 5.6.

7-2 Interfaces

SCSI Bus Interface

7.2.2 SCSI INTERFACE ELECTRICAL DESCRIPTION

The MD21 interfaces to SCSI host adapters and other controllers via the SCSI bus. A 50-pin male IDC connector, reference designated J6 on the MD21, plugs directly into the SCSI bus. Component locations for the MD21 are shown in Figure 7-1. All signals use open

collector drivers.

SCSI BUS CONNECTOR

Figure 7-1. MD21 Controller Component Locations

7.2.2.1 Output Signal Characteristics

When measured at the SCSI device's connection, each signal driven

by a SCSI device has the following output characteristics:

• Signal assertion = 0.0 VDC to 0.4 VDC

• Minimum driver output capability = 48 milliamperes (sinking) at 0.5 VDC

• Signal negation = 2.5 VDC to 5.25 VDC

Interfaces 7-3

SCSI Bus Interface

All assigned signals are terminated with 220 ohms to +5 VDC, or 180 ohms to 4.3 VDC (nominal) and 330 ohms to ground at each end of the SCSI cable as shown in Figure 7-2.

+ 5 V (NOM)

Figure 7-2. SCSI Bus Signals Termination

7.2.2.2 Input Signal Characteristics

When measured at the SCSI device's connection, each signal received

by a SCSI device has the following input characteristics:

• Signal true = 0.0 VDC to 0.8 VDC

• Maximum total input load = -0.4 milliamps at 0.4 VDC

• Signal false = 2.0 VDC to 5.25 VDC

• Minimum input hysteresis = 0.2 VDC

7-4 Interfaces

SCSI Bus Interface

7.2.2.3 Terminator Power (Optional)

The MD21 supports the single-ended SCSI option which provides pin 26 with termination power that has the following characteristics:

Vcc = 4.0 VDC to 5.25 VDC (through diode)

800 milliamps maximum source drive capability

For information on implementing the SCSI termination power option, see subsection 5.3.2.

7.2.3 SCSI BUS SIGNALS AND TIMING

SCSI bus activities involve one or more of the following SCSI

phases of operation:

• Arbitration Phase

• Selection Phase

• Reselection Phase

• Command Phase

• Data Phase

• Status Phase

• Message Phase

These phases are described in more detail in Subsection 5.1 of the Emulex SCSI Disk Controller Programming Reference Manual (manual number MD2352501). When the SCSI bus is not involved in one of the above phases, it is in the Bus Free Phase. SCSI phase sequencing is accomplished by asserting or de-asserting the SCSI bus signals; the signals are described in Subsection 7.2.3.1.

7.2.3.1 SCSI Bus Signals

There are 18 signals on the SCSI bus. Nine signals are control signals that coordinate transfer of data between SCSI bus host adapters and controllers; the other nine signals are for an eight- bit data bus with parity. The signals are listed and described in Table 7-1.

Interfaces 7

SCSI Bus Interface

ln Table 7-1, the eight data bit signals are represented by DBO through DB7, where DB7 is the most significant bit and has the highest priority during the Arbitration Phase. Bit number, significance, and priority decrease downward to DBO. The parity, represented by the DBP signal, is always odd. Host adapters and

controllers on the SCSI bus can generate parity and have parity detection enabled. During the Arbitration Phase, parity is not guaranteed to be valid.

Pin/signal assignments for the MD21 SCSI bus interface are listed

in Table 7-2; they support the SCSI single-ended option.

7-6 Interfaces

Table 7-1. SCSI Bus Signals

SCSI Bus Interface

Mnemonic

Signal

Name

DBO DB1 DB2 DB3 DB4 DB5 DB6 DB7 DBP

Data Bus Data Bus Data Bus Bit 1 Data Bus Data Bus

Data Bus Data Bus Data Bus Bit 5 Data Bus

Data Bus Data Bus

ACK Acknowledge

REQ

ATN

Request

Attention*

Description

Data Bus Bit 0

Data Bus Bit 2 Data Bus Bit 3 Data Bus Bit 4

Data Bus Bit 6 Data Bus Bit 7

Data Bus Parity

Indicates acknowledgment for a REQ/ACK data transfer handshake operation.

Indicates a request for a REQ/ACK data transfer handshake operation.

Indicates ATTENTION condition

(i.e., the Initiator has a

message to send to the Target).

RST

Reset*

Indicates RESET condition (i.e.r

clears the SCSI bus of all activity).

SEL Select

Used to select and/or reselect a SCSI bus device.

BSY

Busy

Indicates the SCSI bus is being used.

C/D

Control/Data Indicates command, status

information transfer# or data in

and/or data out transfer.

I/O

Input/Output Indicates direction of data

movement on the data bus with

respect to an Initiator.

MSG

Message

Indicates the SCSI bus is in the

Message Phase.

*This condition is described in Section 5 of the Emulex SCSI Disk

Controller Programming Reference Manual (manual number MD2352501).

I

Interfaces 7-7

SCSI Bus Interface

Table 7-2. Single-Ended Pin/Signal Assignments at SCSI Bus Interface

1 2 3 4 5 6 7 GND 8 -DB(3)

9 10 11 12 -DB(5) 13 14 15

16 “DB (7) 17

18

19 GND 20 21 GND 22 23 24 GND 25 26 27

28

29 30 GND 31

32 -ATN 33 34 GND 35 GND 36 37 GND 38 -ACK 39 40 41

Signal Name Input/Output

GND

-DB(0) GND

-DB(1)

GND

-DB(2)

Input/Output

—

Input/Output

GND

-DB(4)

GND

Input/Output

—

Input/Output

GND

-DB(6) GND

Input/Output

—

Input/Output

GND

—

-DB (P) (Data parity) Input/Output —

GND

GND GND

—

Optional GND TERMPWR GND GND GND

GND

—

Input/Output

GND

—

-BSY Input/Output —

Input/Output

GND

-RST

GND

Input/Output

—

42 -MSG Input/Output 43 44 45

GND

-SEL GND

46 -C/D

47 GND 48 -REQ 49 GND 50

-Input/Output

Input/Output

.—

—

r —

7-8 Interfaces

SCSI Bus Interface

7.2.3.2 SCSI Bus Timings

Except where noted, the delay time measurements for each SCSI device (host adapter or controller) is calculated from signal conditions existing at the SCSI bus connection for that device. Normally these measurements do not consider delays in the SCSI bus cable. The SCSI command timings are listed and described in Subsection 5.3 of the Emulex SCSI Disk Controller Programming Reference Manual (manual number MD2352501).

The timing diagram shown in Figure 7-3, shows the typical relationship between SCSI bus signals and SCSI bus phase sequencing.

Interfaces 7-9

SCSI Bus Interface

HANDSHA KE

Note: All Signa ls Shown Active Low

(Busy)

(Select)

(Con trol/Data)

(Inp ut/Ou tput)

■ (Request)

(Ack nowledg e)

(Attentio n)

(Message)

(Reset)

(Data bit) DB(7-0,P)

DB(7)

( =

'

V= Hi ghest p riority ID for arb itration PH ASE

Note: DB(P) = Data parity (odd). Parit y is no t valid dur ing a rbitration .

The use of p arity is a system option.

Note: In a ty pical system, a c omp u ter's host adapte r will act as the Initiato r and an I/O dev ice’s c ontrol unit will act as the Targ et.

-REQ

-ACK ■

-ATN .

-MS G '

-RST

signi fican t bit. | FR EE

r— BUS SET DELAY M aximum time for an SCSI device to assert BSY and

BUS FREE DELAY Min imum time that an SCSI device shall wait from its

BUS CLEAR DELAY M aximum time for an SCSI device to stop driving all

Initiato r ass erts BSY

Arb itration ID’S

Initi ator trie s to g et bus

-ARB ITRATION .

■ PHASE •

Imple mentat ion of

.th is phase is a

system option.

At least one Bus

Free Delay, but no more than one Bus Set Delay, after Bus Free Phase has

been detect ed. The

Initia tor asserts BSY and its own SCSI device ID bit on the data bus.

The Initia tor waits an Arbitrati on Delay then exa mines the data bus. If a higher

prior ity SCSI device

ID bit is tru e on the data bus (DB7 is the

highest), the Initiator

loses arbitration and

releases BSY. If no

highe r priority SCSI

device ID bit is true

on the data bus,

then the Initiato r

wins arbit ration and

asserts SEL.

Bus devices having

lost arbitratio n, shall

release BSY and

their own SCSI

device ID bit within

a Bus Clear Delay

after SEL becomes

true.

L

The Initiato r that wins arbitra tion waits at least a Bus Clear Delay plus a Bus Settle Delay after assertin g SEL before chang ing any signa ls on th e bus.

BUS

SEL and

BSY are

both false

for at least

one Bus

Settle Delay.

“V

r

its SCSI ID bit on th e data bus after it de tects Bus Free Pha se.

detec tion of Bus Free Phase until its assertion of BSY.

bus signals af ter Bus Free Phase is detecte d or SE L

received from an SCSI device during arbitra tion. ARBIT RATION M inimum time an SCSI device shall wait from DELAY assertin g BSY for arbitratio n until the data bus c an be

exam ined to see if arbitra tion has been won.

BUS SETTLE DELA Y Time to wait for the bus to settl e after changin g

> 4

Li

■4— 1-

I I

certa in control signals.

-Sy stems with no a rbitrati on start here

— — *4— 2 des kew delays

X

Targe

r “■

-<H

H

-f H

-J H

-* H

-f H

In itia to rlD ^T ar ge HD ^

Initia tor h as bus and selects Target.

SELECTION

PHASE

Durin g this phase, the I/O signal is deasserted to distin guish this phase from the Reselec tion Phase.

NON-AR BITRATING SYSTEMS : In systems with the Arbitrati on Phase not implem ented, after detec ting the Bus Free Phase, the Initiato r waits a minimum of one Bus Clear Delay, then it asserts the data bus with both the desired Initiato r ID bit and the Target 's ID bit. After two deskew delays, the Initiator asserts SEL.

ARBITR ATING SYSTEMS : In systems with the Arbitration Phase imple mented, the Initiator that won arbitra tion has both BSY and SEL asserted and change s the data bus after two Bus Settle Delays. The data bus is th en asserte d with both the desired Initiato r ID bit and the Targe t’s ID bit. Two deskew delays later BSY is released.

IN ALL SYSTEM S: The

l~

Target determ ines that it is se lected when SEL and its SCSI device ID bit are tru e and BSY and I/O are false for at least a Bus Settle Delay. The Targe t then asserts BSY within a Selection Abort Time. Two deskew delays

r

after the In itiator detec ts BSY true, it releases SEL and may chang e data bus signals.

y- '

Figure 7-3. SCSI Bus Timing Diagram (Sheet 1 of 3)

MD210 3-0588A

7-10 Interfaces

"Bu s settl e delay ”

SCSI Bus Interface

(Busy)

(Select)

(Contro l/Data)

(Inp ut/Ou tput)

(Request)

(Ack nowledg e)

(Atten tion)

(Message )

(Reset)

(Da tabit) DB (7- 0,P )f-

-BSY f -

-SEL f .

-I /O f-

-REQ (-

-ACK

-ATN f—

-M SG f“

-RST

(-

f -

i i

1st CM D by te-

I—

Last CMD b yte

Tar get “r eques ts” com mand from Initiato r.

: COMM AND PHASE ;

The Targe t asserts, C/D and deasserts I/O and MSG for all of the handshakes of this phase.

The transfer is from Initia tor to Ta rget.

HAND SHAKE PROCED URE:

The Targe t asserts REQ. The Initiato r drive s data (7-0,P) to their desire d value s, waits at lea st one deskew delay plus a cable skew d elay, and asserts ACK. The Initia tor co ntinu es to drive data (7 -0,P) until

REQ is fa lse.

When ACK is true at the Target, the Target reads the data (7-0,P), then ass erts REQ.

When REQ beco mes false at the Initiator, the Initiator may change or release data (7-0,P) and deassert

ACK. The Targe t continues

reque sting com mand bytes. The num ber of bytes depends on the comm and group code dete cted from the first comm and byte received.

-((-

-( (“

Writ e perip heral device

First da ta' Last d at a' (read periphe ral) (read perip heral)

L

- Target asserts I/O, deass erts C/D, and

- HANDSHA KE PROCEDUR E:

- The Initiato r shall read data (7 -0,P) after

- When ACK becom es tru e at the Target,

Targ et “ reques ts” dat a tran sfer wi th In itiator

DATA PHAS E;

DATA IN PHASE: Read Periphera l.

Data is to be sent from Target to Initiator.

MSG during the REQ/ACK handsha ke of this phase.

The Target firs t driv es data (7-0,P) to their desired values, waits at least one deskew delay plus a ca ble skew delay, then asser ts REQ. Data (7-0,P) shall remain valid until ACK is true at the Target.

REQ is tru e, then asserts ACK.

the Target may chan ge or release data (7-0,P) and deass ert REQ.

After REQ is false, the Initiator d easserts ACK. After ACK is false, the Target may contin ue the transfe r by draw ing data (7-0,P) and asserting REQ.

DATA OUT PHASE: Wri te Peripheral.

Data is to be sent from Initia tor to

Target.

Targe t deasserts C/D, I/O and MSG durin g the REQ/ACK hands hake of this phase. Refer to the handshake proce dure of th e Command Phase.

-(L

- ( H

MD210 3-0588B

Figure 7-3. SCSI Bus Timing Diagram (Sheet 2 of 3)

Interfaces 7 - 1 .1

SCSI Bus Interface

(Busy)

(Select)

(Contro l/Data)

(In put /Output)

(Request)

(Ack nowledg e)

(Atten tion)

(Message )

(Reset)

(Data bit)

- "Des kew delay" (45 ns)

-BSV $-

-SEL

C/D f—

--

V 1. v

1 II

* II i/

1 \\ 11!

i ii

___LU_!__II____

i n i ii

V 1

_

1 1

^— !— i

l i i i i n i

i il l 1 1 Ill'll i l

1 \v g ll d _ / | | ^ Status byte |

I Target . ! “ requests" 1 1 Initiator to | 1 take status |

1

......

- STATUS | PHASE . (Ending ' Status) 1

p T arget . requ ests that a 1 1 st atus byte be | | se nt to the |

■ I nitiator. , 1 1

L Target asserts 1 1 C/D and I/O | | and deasse rts | | MSG durin g . . th e ha ndshake

' of this phase. '

Only one byte |

■ of status is |

, tran sferred . i

1 1 1- See handshake

| procedure 1

i und er Da ta In 1

| phase. 1 1 | 1

! i

-------

I

i

1

I

— V

1

\

I

m s

_ __ _

i n m \

1 III!! 1 1

ii i

| \ valid I * Message byte

1 Target "requests"!

' message .

t z z MESSAGE 3 Z J I

------

PHASE

. (Interrupt)

p Target ' requests 1 message 1 byte(s) to be

j sent from

| Ta rget to I Ini tiator.

I— T arget asserts I C/D, I/O and ' MSG during

1 the REQ/ACK

1 handshake(s) 1 of this phase.

1

f— The message

j byte could

1 indicate

COMM AND COMPL ETE

j (00) indicating

interrup t.

1— See handshak e 1 | a Selec tion 1 | pr ocedure

j under Data In

■ phase.

v—

i

/ i

i

iii i

i i

i i i

__

y—

i

7

1 1

------

1 f z : FREE * i

1 |

|

1 1 1 1 |

|

I

1 1

|

j

1

1 1 1

i i

— i

-- --- --- -- --- -

1 Bu s is 1 I re leased 1

1 I

t BUS

, PHASE 1

[-T arget 1 1 d easse rts BSY | 1 t o indicate that i | th e bus is . I a vailable for '

subse quent |

1 users. j

pT arg et releases

1 all bus signals 1

1 within a Bus | 1 Clear Delay ■

| a fter BSY

I becomes

I c ontinu ously 1

; false for a Bus |

1 Se ttle Delay.

1 |

[-T he fo llowing .

■ phase will be ' an Arbitrati on 1 Phase if 1

1 impleme nted or 1

j Phase. |

is

____

i i

r u r r

I

H

j

Figure

7-12 Interfaces

MD210 3-0588C

7-3. SCSI Bus Timing Diagram (Sheet 3 of 3)

Disk Drive Interface

7.3 ESDI DISK DRIVE INTERFACE

The MD21 Disk Controller interfaces with ESDI disk drives via one

34-line control cable, which is daisy-chained, and one or two 20-line data cables. Table 7-3 lists specifications for each type of cable:

Table 7-3. Disk Drive Cable Requirements

Number of pins

Maximum cumulative

Control Cable

(daisy-chained to

1 or 2 drives)

34

10 feet (3 meters)

Data Cable

(One cable to

each drive)

20

10 feet (3 meters)

cable length

Recommended

connector

MD21 cable

AMP ribbon connector

P/N 499560-3

(or equivalent)

J1

AMP ribbon connector

P/N 499560-6

(or equivalent)

J2 and/or J3

7.3.1 ESDI INTERFACE ELECTRICAL DESCRIPTION

7.3.1.1 Output Signal Characteristics

When measured at the ESDI device*s connection, each signal driven by an ESDI device has the following output characteristics:

• Signal assertion = 0.0 VDC to 0.4 VDC

• Minimum driver output capability = 48 milliamperes (mA) (sinking) at 0.4 VDC

• Signal negation = 2.5 VDC to 5.25 VDC

Interfaces 7 -

Disk Drive Interface

7.3.1.2 Input Signal Characteristics

When measured at the ESDI device's connection, each signal received

by an ESDI device has the following input characteristics:

• Signal true = 0.0 VDC to 0.5 VDC

• Signal false = 1.4 VDC minimum

7.3.1.3 Termination

All assigned signals are terminated with 220 ohms to +5 VDC and 330 ohms to ground at each end of the cable.

7.3.3..4 ESDI Signals

The pin/signal assignments for control signal interface between the MD21 Controller and an ESDI disk drive are shown in Figure 7-4 and Table 7-4.

The pin/signal assignments for data signal interface between the MD21 Controller and an ESDI disk drive are shown in Figure 7-5 and

Table 7-5. As indicated in the figure, lines 2, 5, 9, and 20 are

connected to ground at the MD21 data interface. The MD21 does not use lines 2 and 20 to report the sector and index positions from

each drive (as indicated in the ESDI specification), but uses the

sector and index lines on the control cable for the selected drive.

7-14 Interfaces

CONTROLLER

FLAT RIBBON OR

TWISTED PAIR (3 METERS MAX)

Disk Drive Interface

DRIVE

-H EAD SELECT 2 3 r

-H EA D SELECT 22

-W R ITE GATE r

m -CON FIG—STATUS DATA

- TRANSFER ACK

-ATTENTION

- HEAD SELECT 0 r

-SEC TO R/-A DD RES S MARK FOUND

-H EAD SELECT 2 r

m - INDEX

, - READY

-TRANS FER REQ

- DRIVE SELECT 1 - r

-D RIVE SELECT 2 m

- DRIVE SELECT 3 m

- READ GATE m

-CO MM AN D DATA m

2

4

6 7 -o 8 9 -, 1

1 0

12 13—0

14

16

18 19 —0

2 0 21

2 2

24

26

28

30

32

34 —

__

3 —«>

5 >

1 1 —^

15

_

17—<»

_

. 0 3 .

25—i >

27—i »

°9 i »

31—0

33— >

MD2103-078 2

, >

o

Figure 7-4. ESDI Control Cable Pin/Signal

Assignments (Connector Jl)

Interfaces 7

Disk Drive Interface

Table 7-4. Control Cable Pin Assignments

1

Signal Name

GND 2 -HEAD SELECT 2 3 4

-HEAD SELECT 2

5

GND

Input/Output

—

Output

—

Output

—

6 -WRITE GATE Output 7

8

-CONFIGURATION DATA Input

GND

—

-STATUS DATA Input

9

GND 10 -TRANSFER ACK 11 GND 12 13

-ATTENTION GND

14 -HEAD SELECT 2

15 GND

16

-SECTOR Input

—

Input

—

Input

- -

Output

—

-ADDRESS MARK FOUND Input

17

GND

18 -HEAD SELECT 2 19 20 21 22 23

-INDEX

-READY

GND

GND 24 -TRANSFER REQ 25 GND 26 -DRIVE SELECT 1 27 GND 28 29

-DRIVE SELECT 2 GND

—

Output

—

Input

—

Input

—

Output

—

Output

—

Output

—

30 -DRIVE SELECT 3 Output 31

GND

—

32 -READ GATE Output 33

GND

34 -COMMAND DATA

—

Output

7-16

Interfaces

Disk Drive Interface

FLAT RIBBO N OR

CON TROL LER

TWI STE D PAIR (3 M ETERS MAX)

-D R IV E SEL ECTED

-C OM MA ND COM PLETE

' -AD DR ES S MAR K ENAB LE

-R ES ERV ED FOR STEP MODE A

+ WR ITE CLO CK

-W R ITE CLOC K r

-R ES ERV ED FOR STE P MOD E A

+ RE AD/RE FEREN CE CLOC K

* - REA D/RE FERENCE CLOCK

+ NR Z WRITE DATA

- NRZ WR ITE DATA

+ NR Z READ DATA

* - NR Z R EAD DA TA

-IND E X

_________

1

3 4

7 8

10 11

13

14

17 18

DRIVE

n

A

9

15'' 1 6 ' !

1Q .,

A M UST BE AT A LOGIC ZE RO LEVE L

MD2103-0783

Figure 7-5. ESDI Data Pin/Signal Assignments

(Connectors J2 and J3)

1

2

3 4 5

6

7

8

9

10 11 12

13

14 15 16 17 18 19

20

Table 7-5. Data Cable Pin Assignments

Signal Name

-DRIVE SELECTED

Input/Output

Input

GND

-COMMAND COMPLETE

-ADDRESS MARK ENABLE

Input

Output GND GND

+WRITE CLOCK

-WRITE CLOCK

Output

Output GND

+READ REFERENCE CLOCK

-READ REFERENCE CLOCK

Input Input

GND

+NRZ WRITE DATA

-NRZ WRITE DATA

Output

GND GND

+NRZ READ DATA

-NRZ READ DATA

Input

Input GND GND

Interfaces 7-17

User Panel Connection

7.4 USER PANEL CONNECTION

Connector J4 on the MD21 (see Figure 7-8) is used to connect the controller to external LEDs and switches that indicate ready and

write-protect conditions for each disk drive. On Emulex

subsystems, these external LEDs and switches are on a user panel

located on the subsystem bezel, as shown in Figure 7-6.

Figure 7-6. Sample User Panel

The user panel connectors is a 10-pin 3M P/N 3473-XXXX. The pin descriptions for connector J4 are listed in Table 7-6.

7-18

Interfaces

User Panel Connection

Table 7-6. Connector J4 Pin Description

1

Connection True

Ground

— .

2 Power Fail Low 3 SW3 High 4

LED 3 Low 5 SW2 High 6 7 8 None 9 LED 0 10

LED 2

Low

LED 1 Low

— Low

+5 volts

——

Function

'

Detects DC Power Fail Drive 2 Write Protect Drive 2 Ready

Drive 1 Write Protect Drive 1 Ready Drive 2 Write Protect Not Used Drive 1 Write Protect

7.4.1 OUTPUTS FROM THE MD21

These output signals are driven by a 74LS374-type register. When a low level is applied to any of these signal lines, the LED is lit to indicate that the disk drive is either write-protected or on line.

7.4.2 WRITE-PROTECT INPUTS TO THE MD21

These inputs are pulled up with 4.7K ohms to +5 volts, and go to 74LS244-type receivers. When a low level is applied to any signal line, the MD21 inhibits write operations to its respective drive. Figure 7-7 illustrates the write-protect input signal.

+5

WRITE-PROTECT

SWITCH

Figure 7-7. Write-Protect Input Signal

Interfaces

7-19

DC Power Connection

7.4.3 POWER FAIL DETECT SIGNAL

Pin 2 on connector J4 is an optional power fail detect signal. This signal allows the MD21 to detect failing DC power. When the signal is asserted (active low), a latch is set. When the MD21

microprocessor senses the latch, it inhibits disk drive activity.

The signal must be asserted at least 2 milliseconds before the +5

VDC power falls below +4.75 VDC.

To use this power fail detect option, the power supply used in the

subsystem in which the MD21 resides must contain a power fail signal. Connect pin 2 to the power fail signal in the power supply.

7.5 DC POWER CONNECTION

The MD21 Controller power supply, designated J7, (see Figure 7-8)

is an AMP P/N 641737-1. Table 7-7 lists the power connections for

this connector.

LED 4 LED 3

Figure 7-8. Pin Locations for Power Connector

7-20 Interfaces

JUMPERS

MD2103-0776

DC Power Connection

Table 7-7. Power Supply Connections

1

2

3

4*

No Connection

Ground

+5 VDC, + 5%, 1.5 amperes nominal

Description

* A RESET occurs if the DC voltage drops to 4.5 or less

and an INITIALIZATION sequence occurs when the voltage

returns to 4.

515 or above.

Interfaces 7-

B L A N K

Appendix A

TROUBLESHOOTING

A.1 OVERVIEW

The installation of the MD21/S2 Controller, when used with the

recommended devices, should run smoothly and problem-free. The diagnostic procedures described in this manual are intended to help you identify and resolve any problems you may encounter. However, because of the wide variety of host adapters, disk drives and other devices to which the MD21/S2 could be connected, diagnostic procedures cannot be specific or all-inclusive. The following subsections explain how to obtain technical assistance or service for problems you cannot resolve.

A.2 PROBLEM IDENTIFICATION

The self-test, described in Section Six, diagnoses problems within the MD21/S2 itself. It does not diagnose problems with the host adapter, disk drive, or other devices to which the MD21/S2 is connected.

If the MD21/S2 does not pass the self-test when it is connected to the other devices in your system, remove the devices and try the self-test again. If the controller passes the self-test, the problem may be elsewhere in the system. See directions for obtaining help from Emulex's technical support personnel in the subsection on Technical Assistance.

If the controller does not pass the self-test when it is tested apart from the devices, it may be defective and should be returned to the factory for replacement. See directions for returning the

unit in the subsection on Service.

A.3 TECHNICAL ASSISTANCE

If the MD21/S2 controller passed the self-test, but you believe it is not performing as expected, you can obtain assistance from

Emulex's technical support personnel. The SCSI Product Performance Report (see last two pages of Appendix A) allows you to gather all

the required information. Complete the form and mail it to Emulex

at the address on the form. A technical support representative will contact you within five days of receipt of the form.

Note that this form is required in order for you to receive

technical assistance regarding your MD21/S2 controller. Please do

not attempt to contact Technical Support by any other means. (If you have not heard from Emulex after five days, you may call in to

check the status of your report.)

It is suggested that you use a photocopy of this form, so that the form will be available should you need to use it again.

Troubleshooting A-l

A. 4 SERVICE

The components of your Emulex MD21/S2 Controller have been designed to give years of trouble-free service, and they were thoroughly tested before leaving the factory.

If one of the diagnostic procedures described in this manual indicates that a component is not working properly, the MD21/S2 Controller must be returned to the factory, or to an Emulex authorized repair center, for service. Emulex products are not

designed to be repaired in the field.

Before returning the component to Emulex, whether the product is or

is not under warranty, you must contact Emulex's Repair Center for instructions and a Return Materials Authorization (RMA) number.

DO NOT RETURN AN MD21/S2 CONTROLLER TO EMULEX WITHOUT AUTHORIZATION. An MD21/S2 Controller returned for service without an authorization will be returned to the owner at the owner's expense.

In the continental United States, Alaska, and Hawaii contact:

Emulex Repair Center

3545 Harbor Boulevard

Costa Mesa, CA 92626

(714) 662-5600 TWX 910-595-2521

Outside the United States, contact the distributor from whom the

MD21/S2 Controller was initially purchased.

A-2 Troubleshooting

Appendix B

PROM REMOVAL AMD REPLACEMENT

B.l OVERVIEW

This appendix provides instructions for replacing the MD21 firmware

PROM.

B.2 EXCHANGING PROMS

The MD21 firmware PROM is located in the socket at U9. Pry the existing PROM from its socket using an IC puller or an equivalent

tool.

The MD21 PROM is identified by the part numbers on top of the

PROMs. Place the MD21 PROM in socket U9. See Figure 7-8 for the location of the U9 socket. Make certain that the PROM is firmly seated and that no pins are bent or misaligned. (If the two rows of PROM pins are too far apart to fit in the socket, grasp the PROM at

its ends using your thumb and forefinger and bend one of the pin rows inward by pressing it against a table top or other flat surface.

PROM

Number

A98

PCBA

Location

U9

PROM Removal and Replacement B-l

B L A N K

EMULEX Read er’s Comments

Your com m ents and suggestions will help us in our continuous effort to improve the quality and usefulness of

our publication.

Manual P art N umber____________

What is your general reaction to this manual? In your judgment is it complete, accurate, well organized, well written, etc.?

Is it easy to u s e?_______________________________________________________________________________________

What features are most useful?

What faults or errors have you found in the manual?

Does this manual satisfy the need you think it was intended to sa tisfy ?________

Does it satisfy yo ur needs?

_________________________________________

________________

R e v .

-------------------------------------------

Why?

______

_ _

□ Please send me the current copy of the Controller Handboo k, which contains the information on the remainder of EM U L EX’s

controller products.

_______

Nam e

_____

T i t le

______

Company

Department

Additional copies of this document are available from:

__

Emulex Corporation

3545 Harbor Boulevard

E 0. Box 6725

Costa Mesa, CA 92626

Attention: Customer Services

Street

C ity

--------------

State/Country

Zip

__________

Fold Here and Staple

Do Not Tear — Fold Here

NO POSTAGE

NECESSARY

IF MAILED

IN THE

UN ITED STATES

BUSINES S REPLY M A IL

FIRST CLASS P ERMIT NO. 202 C OST A MESA, CA

POS TAGE WIL L BE PAID BY ADD RESSEE

EMULEX CORPORATION

3545 HARBOR BOULEVARD

PO. BOX 6725 COSTA MESA, CALIFORNIA 92626

ATTN: TECHNICAL PUBLICATIONS

SC SI PR O D U CT P E R FO R M A N CE REPORT

Please p rovide all information requested.

CUSTOMER INFORMATION

Nam e

_____________________ ___________ Position/Title Company Nam e

Address ____________________________________________________________________

C ity

_________________

______

_____

___________________________________________________________

_________________________________________________________

________________

PRODUCT INFORMATION

______

S ta te ________________________

. - Phone No

____________„.

Ext._____________

_______

_

_ Z ip

____

EMULEX Product in Use: M D

Top Assembly Number ______________________________________________ Serial Number

Purchased Fro m

_

_______________________________

______________________________

_______

M T

Date of P urchase .................................

Sales Engine er

_______

I B

_____________________

PERIPHERAL INFORMATION

DISK TAPE

Manufacturer: Model N u m ber Interface: ST506__________ ESDI Geometry: No. of Cylinders ____________________ Number of Heads __________ Number of Bytes/Track Number of Drives

_________________________________

____________

_________________________

_____________________________

_______________

S ectors

____

______

- , - Media Interface: QIC11_________QIC24 _

Drive Interface: Q IC36

QIC120________QIC15CL

Tape Type: 3 0 0 Tape Manufacturer: 3 M DYSAN

___________

_______

CARTREX

SYSTEM CONFIGURATION

Bus Type: IB M

Software: Diagnostics

______

MU LTIBUS

Utilities

_____________________

DEC

______

_______

_________________

VME

O THER

__

Amount of Memory Host Ad a pte r Formatter Operating System _

_____

________

_______

______

______________

UC

_

4 5 0

_______

_________

______

...

_

QIC 4 4.

DEI _ SCOTCH

600

GRAPHIC REPRESENTATION OF YOUR SYSTEM

PROBLEM DESCRIPTION

Give a complete description of the problem you are encountering. Provide details of the command packet and/or test loop/routine that you are using to troubleshoot the problem. Include a copy of the program(s) that demonstrates the problem on either hard copy or magnetic media (DOS or FILES 11 format).

Please mail the com pleted form to:

E M U L E X

EMULEX CORPORATION National Technical Support 3545 Harbor Boulevard Costa Mesa, CA 92626

Attn: SCSI Support

Emulex MD21/S2 Technical Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

TABLE OF CONTENTS

PREFACE