Manuals / Emerson / Computer Equipment / Computer Hardware

Emerson MVME147 manual Equipment Supported

Models: MVME147

1 170

Download 170 pages 32.5 Kb

Page 4

Equipment Supported

1

GENERAL INFORMATION

Interrupt Structure paragraph in Chapter 4) or SCSI bus activity is slowed down. Additional commands may be sent to the SCSI firmware for a different peripheral device.

$FFFE078E: FUNNEL COMMAND ENTRY

This entry point is used by applications that require multiple interfaces to the SCSI firmware. Unlike the single user command entry, you may issue commands anytime the firmware does not require an RTE to be performed. If an RTE is required, and you wish to send a command at the same time, you may accomplish both by using the RTE entry (described below). The use of the FUNNEL command entry causes the FUNNEL module to examine the state of the SCSI bus, determine if the bus is currently in use, and send the command to the bus if it is not in use. If the bus is currently in use, the FUNNEL module checks if the device is not busy so it can preprocess or queue the command and return to the caller with an intermediate status of $A002. This preprocessed or queued command is processed and sent to the SCSI bus when the bus is free.

$FFFE0794: COME-AGAIN ENTRY

Branches to FUNNEL entry. All the queued commands are serviced in the interrupt service routine through software interrupt.

$FFFE079A: RTE ENTRY

The SCSI firmware notifies the user/caller that an RTE instruction needs to be executed by the RTE bit (13) of the returned status word. If this bit is 0, an RTE is required; if this bit is 1, an RTE is not required (the SCSI firmware does not execute the RTE instruction so as not to preempt a task in a VERSAdos or SYSTEM V/68 environment). SCSI firmware users may inherit an RTE from another caller because of the multiple caller interface. When an RTE is inherited from another caller, the use of the RTE entry may be required to send down a new command before executing an RTE instruction.

Equipment Supported

The following list shows the controller type assignments for SCSI controllers explicitly supported by the SCSI firmware, and the drives supported by each. /f3Note, however, that Motorola does not necessarily endorse or recommend

1-4

Image 4

Emerson MVME147 manual Equipment Supported

Contents

Features GENERAL INFORMATIONIntroduction Modes of OperationMVME147 SCSI Firmware Entry Points The SCSI firmware initializes these vectors Equipment Supported CONTROLLE CONTROLLE CONTROLLEDEVICE PARTDevices Supported Under Common Command Set CONTROLLEDEVICE PARTRelated Documentation MOTOROLADOCUMENT TITLE PUBLICATION NUMBERManual Terminology MOTOROLAGENERAL INFORMATION Initiator Role Custom Packet CUSTOM SCSI PACKETSIntroduction CUSTOM SCSI PACKETS Initiator Role Custom Packet Page PHASE CODE PHASEInitiator Role Custom Packet +$00 +$68 status Note ASYNC the firmware status xxxxxxxx xxxxxxxx Page CUSTOM SCSI PACKETS Initiator Role Custom Packet CUSTOM SCSI PACKETS TARGET Enable Custom Packet TARGET Enable Custom PacketNOTES Status from SCSITARGET Enable Custom Packet TARGET Sequence Custom Packet TARGET Sequence Custom Packet CUSTOM SCSI PACKETS NOTESTARGET Sequence Custom Packet WORDS $04 and $06 CUSTOM SCSI PACKETS TARGET Sequence Custom Packet CUSTOM SCSI PACKETS TARGET Sequence Custom Packet RETRY COUNT. Not used by the TARGET role firmwareCUSTOM SCSI PACKETS Packet Return Status PACKET RETURN STATUSControl Flags SCSI Bit 3 FM Filemark Bit 4 COMMAND RETRY 1 = Retries were performed Bit 5 COMMAND REThe command was retried retry count times Packet Return Status Bit 2 EOM End of mediaPACKET RETURN STATUS Table 3-1.Packet Status Codes Intermediate ReturnCodes CODEFinal Return Codes Table 3-1.Packet Status CodesCODE Intermediate ReturnTable 3-2.Packet Status Codes cont’d SCSI Bus Reset Packet section in ChapterCODE MEANINGRequest-Sense-Data Error-Class7 Codes Table 3-3.Packet Status Codes cont’dController-Dependent CODESCSI Status Returned in Status Phase Table 3-4.Packet Status Codes cont’dCODE MEANINGRequest-Sense-Data Error-Class0 through 6 Codes Table 3-5.Packet Status Codes cont’dCODE Controller-DependentPage PACKET RETURN STATUS SCSI FIRMWARE INTERRUPT STRUCTURE SCSI Firmware Interrupt StructureSCSI FIRMWARE INTERRUPT STRUCTURE WRITING A DRIVER SCSI_CMDSCSI ACTV SCSI_INTPassing Commands to the SCSI Firmware Building the PacketInterface Rules for the SCSI Firmware Figure 5-1.SCSI Disk Driver Interface to VERSAdosInterface Rules for Multiple Callers WRITING A DRIVER Care must be taken not to modify the contents of WRITING A DRIVER Interface Rules for the SCSI Firmware FUNNEL WRITING A DRIVER Interface Rules for the SCSI Firmware WRITING A DRIVER MOVE.W 2A2,D0 THE CODE BELOW HANDLES FINAL RETURN CODES Interface Rules for a Single Caller WRITING A DRIVER MVME147 SCSI Firmware Background TARGET ROLE ROUTINESIntroduction SCSI Versus SASI Rules Custom Sequence PacketCommand Table ScriptEnabling TARGET Role Enabling TARGET Role Servicing the TARGET Requests Servicing the TARGET Requests TARGET ROLE ROUTINES Servicing the TARGET Requests TARGET ROLE ROUTINES Servicing the TARGET Requests TARGET ROLE ROUTINES SCSI PACKETS Table 7-1.SCSI FunctionsIntroduction SCSIRead/Write Packet TableSCSI Functions cont’d SCSIDISK and TAPE Controller logical unit in SG table, if zero SCSI PACKETS Old Packet Supported for Compatibility+$12 in SG table, if zero DMA Scatter/Gather Table Entry Read/Write Packet|function code 3 bits 1 = link to next entryFor example $5 isCOMMAND Attach/Detach Packet all devicesCOMMAND CONTROLLERCOMMAND Attach/Detach Packet all devicesSCSI PACKETS +$1E FM encoding, single Controller type refer xxxxxxxx attributes byte offset +$20 Single track density Drive type 0 = Attach/Detach Packet all devices Example for floppy3½, 5¼ 3½, 5¼,3½, 5¼ 3½, 5¼,3½, 5¼ 3½, 5¼+$04 Minimum read QIC-24 if this is set to 0, the +$00 Reserved Interrupt level +$00 +$9E $00 Format Packet Assign Alternate Sector Packet SCSI COMMAND+$0E Assign Alternate Sector Packet SCSI SCSI PACKETS DEFECT LIST TYPE0 Note 3, NOTES Head Bytes from Index MSW NoteSCSI Bus Reset Packet Controller logical unit SCSI Controller Reset Packet Erase Packet+$12 Rewind Packet Device logical unit Read Block Limits Packet SCSI PACKETS where n = number of blocks or filemarks to Space Status from SCSI Write Filemarks Packet Write Filemarks PacketThe table below shows the write filemarks packet Controller logical unit Verify CRC Packet The controller must be in general or read modeTape Mode Select/Sense Packet Tape Mode Select/Sense Packet Number of tracks on Inquiry Packet +$00 Reserved +$1A Load/Unload Packet +$14 Recover Buffer Data Packet +$0C Request Sense Data Packet Controller logical unit Check Status Packet Open Packet SCSI PACKETSOpen Packet SCSI PACKETS BYTE OFFSET COMMON COMMAND SET AND DISK OPERATIONBYTE BYTE OFFSET BYTEBYTE OFFSET ENTRY NUMBER BYTE OFFSETCOMMON COMMAND SET AND DISK OPERATION NOTESSend mode select command COMMON COMMAND SET AND DISK OPERATION DEFECT LIST DEFECT LIST TYPEBYTE OFFSET NOTESBYTE OFFSET Mode Select HeaderBYTE OFFSET Block Descriptor BYTE OFFSETCOMMON COMMAND SET AND DISK OPERATION BYTE OFFSETBYTE OFFSET Mode Select HeaderBlock Descriptor BYTE OFFSETBYTE OFFSET BYTE OFFSETNOTES VALUEMode Select Command CDB BYTE OFFSETVALUE COMMENTSCOMMON COMMAND SET AND DISK OPERATION BYTE OFFSETMode Select Header Block DescriptorBYTE OFFSET BYTE OFFSETPage code NOTES COMMON COMMAND SET AND DISK OPERATIONBYTE OFFSET ATTRIBUTE FLAGS MEDIATYPE BYTE OFFSETCOMMON COMMAND SET AND DISK OPERATION ATTRIBUTE FLAGSMEDIA TYPEBYTE OFFSET BYTE OFFSETNOTES VALUEPIN 34 CONTROL COMMON COMMAND SET AND DISK OPERATIONPin 2 and Pin 34 Definition for High Density Pin 2 and Pin 34 Definition for Low DensityPIN 34 CONTROL PIN 2 CONTROLCOMMENTS Pin 34 = driveA-22