ページ1に含まれる内容の要旨
GENERAL INFORMATION
1
Introduction
The MVME147 MPU VMEmodule contains a port to the Small Computer
Systems Interface (SCSI) bus. The hardware interface is the WD33C93 SCSI
interface controller.
To relieve you of having to follow SCSI bus protocol, the SCSI firmware allows
you to pass commands to the bus through high level command packets.
Standard command packets are furnished, as well as custom SCSI sequence
packets that you may easily modify to fit particular applications. With this
ページ2に含まれる内容の要旨
GENERAL INFORMATION 1 Interrupt mode is the most processor-efficient mode of operation. Multitasking is allowed for TARGETs that support arbitration, reselection, and the message-out phase. When using the interrupt mode, you must specify the interrupt level in the packet description (refer to the packet descriptions in Chapter 7). The processor is returned to the caller; i.e., the driver in most applications, whenever the SCSI bus is slowed down (between phases), or whenever the TARGET
ページ3に含まれる内容の要旨
MVME147 SCSI Firmware Entry Points 1 6. $FFFE079A (RTE entry) Within the SCSI firmware, which can stand alone without Note the debug monitor, the first six longwords are the branch table entries referenced above. The hex offsets provided reside within the non-volatile RAM. The following are descriptions of the six entry points. For more detailed descriptions of their use, refer to the Interface Rules for Multiple Callers section in Chapter 5. $FFFE077C: COMMAND ENTRY Branches to FUNN
ページ4に含まれる内容の要旨
GENERAL INFORMATION 1 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
ページ5に含まれる内容の要旨
Equipment Supported 1 any particular controller, nor does Motorola assume responsibility for the operation of equipment manufactured by non-Motorola companies. Refer to Appendix A for information on how to use this firmware program. CONTROLLE DEVICE PART R MANUFACTUR CODE TYPE NUMBER NOTES ER/MODEL 0D Floppy TEAC FD235J 2 0E Winchester Televideo 1002921-1B 1,2,3 7000/7400/3500 Floppy Tape 0F Winchester Common 1,2,3 Command Set Floppy 10 Winchester Seagate WREN 77774620 1,2 III 94161 Winches
ページ6に含まれる内容の要旨
GENERAL INFORMATION 1 CONTROLLE DEVICE PART R MANUFACTUR CODE TYPE NUMBER NOTES ER/MODEL Streaming Tanberg 3660 6 (8535) 150Mb Tape Cassette TEAC MT- 2 2ST/45S2 Tape CONTROLLE DEVICE PART R MANUFACTUR CODE TYPE NUMBER NOTES ER/MODEL 13 Winchester Seagate WREN 77777000 1,2 IV 94171 Winchester Seagate WREN V 77777750 2 94181 Winchester Maxtor 4380S 2 Winchester Maxtor 8760S 2 14 Winchester Seagate ST 1,2,5 157N/M Winchester Seagate ST 1,2,5 125N/M Winchester Seagate ST 1,2,5 1096N Winchester Seaga
ページ7に含まれる内容の要旨
Equipment Supported 1 CONTROLLE DEVICE PART R MANUFACTUR CODE TYPE NUMBER NOTES ER/MODEL Floppy 2,3 18 8mm Tape Exabyte EXB- 820010-009 2 8200 Devices Supported Under Common Command Set Winchester Televideo 1,2 7000/7400/3500 Floppy Televideo 1002921-1B 1,2,3 7000/7400/3500 Winchester Seagate WREN 77774620 1,2 III 94161 Winchester Seagate WREN 1,2 IIIHH 94211 Winchester Micropolis 1375 900475-11-2B 1,2 Winchester Seagate WREN 77777000 1,2,4 IV 94171 Winchester Seagate WREN V 77777750 2,4 94181 W
ページ8に含まれる内容の要旨
GENERAL INFORMATION 1 3. Common Command Set for floppy matches SCSI II rather than revision 17B. 4. Under Common Command Set the cache is not enabled on these devices. 5. Seagate /M means Motorola proprietary. 6. Firmware assembly order number is: 966096. Order number for tape drives is (85xx) as shown with drive type. Order from: Tanberg Data A/S, Data Storage Division, P.O. Box 9, Korsvoll N-0808, Oslo 8, Norway, Phone +47 2 18 90 90 or Tanberg Data Tech. Center, 1077 Business Cente
ページ9に含まれる内容の要旨
Manual Terminology 1 MOTOROLA DOCUMENT TITLE PUBLICATION NUMBER M68000 16/32-Bit Microprocessor M68000UM Programmer’s Reference Manual M68000 Family VERSAdos System Facilities M68KVSF Reference Manual VERSAdos to VME Hardware and Software MVMEDOS Configuration User’s Manual NOTE: Although not shown in the above list, each Motorola Computer Group manual publication number is suffixed with characters which represent the revision level of the document, such as /D2 (the second revision of a
ページ10に含まれる内容の要旨
GENERAL INFORMATION 1 $ dollar specifies a hexadecimal number % percent specifies a binary number & ampersand specifies a decimal number Unless otherwise specified, all address references are in hexadecimal throughout this manual. An asterisk (*) following the signal name for signals which are level significant denotes that the signal is true or valid when the signal is low. An asterisk (*) following the signal name for signals which are edge significant denotes that the actions initiate
ページ11に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 Introduction The SCSI firmware requests "canned" functions from SCSI disk controllers and from SCSI tape controllers. Some of these functions are disk read and write, disk format, tape read and write, and tape positioning operations. The "canned" functions are only provided for the supported SCSI devices that are listed in the Equipment Supported section in Chapter 1. If you want to perform a function that is not "canned", or you want to communicate with SCSI devic
ページ12に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 FC B8 74 30 +$00 Controller LUN Device LUN +$02 Status Byte 0 Status Byte 1 (Note 1) +$04 Script Pointer (MSW) +$06 Script Pointer (LSW) +$08 Command Table Pointer (MSW) (Note 2) +$0A Command Table Pointer (LSW) (Note 2) +$0C 0000 +$0E Flag = 0 0 0 0 +$10 Scatter/Gather Count +$12 0000 +$14 0 0 Function Code (1C) +$16 Interrupt Level Vector Number +$18 Status Byte 2 Status Byte 3 (Note 1) +$1A 0 0 Retry Count $00 00000xxx Controller logical unit number $01 00000xxx Device
ページ13に含まれる内容の要旨
Initiator Role Custom Packet 2 $0E 00000000 Initiator role (TARGET enable/sequence bit undefined) $0F 00000000 Reserved $10 xxxxxxxx xxxxxxxx Scatter/gather entry count. No retry on firmware if scatter/gather DMA is used because command scatter/gather table could be modified after the command is complete if disconnect/reselect occurred. $12 00000000 00000000 Reserved $14 00000000 Reserved $15 00011100 SCSI function ($1C = custom SCSI ) $16 00000xxx Interrupt level (7 to 0)(0 = polled
ページ14に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 NOTES: 1. Refer to Chapter 3. 2. Command Table = 384 bytes RAM work area. This first class is used for command execution and/or message passing through the MVME147 SCSI firmware while the module is playing the initiator role. According to SCSI definition, an initiator is a SCSI device (usually a host system) which requests an operation to be performed by another SCSI device; a TARGET is a SCSI device which performs an operation requested by an initiator. Initiator r
ページ15に含まれる内容の要旨
Initiator Role Custom Packet 2 commonly called a "thread"). The script allows the SCSI firmware to follow the TARGET bus sequences and also allows the firmware to resume a disconnected thread once a disconnect/ reselect occurs. Because the SBC allows "multithreading" of SCSI commands on the SCSI bus, a script is necessary to resume any disconnected threads. Without a script, the SCSI firmware would not have any way to check whether the TARGET performed the command that was requested thr
ページ16に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 PHASE DIRECTION NOTES Message initiator Messages are sent to the TARGET to send bus, out to TARGET command, and controller information. Examples: identify, initiator detected error, abort, device reset. Scripts only specify the information transfer phases. The bus free, arbitration, and selection phases do not need to be specified in a script. The script codes that are understood by the MVME147 SCSI firmware are listed in the following table. (Note that TARGET
ページ17に含まれる内容の要旨
Initiator Role Custom Packet 2 If you suspect data integrity error, you can set up the SCSI script to execute the data phase and then disconnect from the bus (script code 0x2c) or just return as an intermediate return without disconnect from the bus (script code 0x28). Firmware executes the data phase and then returns the firmware parity error status, if any, command packet, and command table back to you. You can examine the data as well as the firmware status to decide what SCSI status
ページ18に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 FC B8 74 30 +$00 Status/Flag Byte Retry Count (00) +$02 Link Pointer (MSW) +$04 Link Pointer (LSW) +$06 Command Length +$08 SCSI Command Descriptor Block (CDB) +$0A SCSI Command Descriptor Block (CDB) +$0C SCSI Command Descriptor Block (CDB) +$0E SCSI Command Descriptor Block (CDB) +$10 SCSI Command Descriptor Block (CDB) +$12 SCSI Command Descriptor Block (CDB) +$14 SCSI Status Initiator SCSI Address (0 to 7) +$16 Data Length (MSW) +$18 Data Length (LSW) +$1A Data Pointer
ページ19に含まれる内容の要旨
Initiator Role Custom Packet 2 Even Byte \ Odd Byte \ FC B8 74 30 +$68 Transfer Address +$6A 0000 +$6C 0000 +$6E 0000 +$70 0000 +$72 Command Offset +$74 Sense Data Block . . . +$9E Sense Data Block $00 xxxxxxxx Status/flag byte 0....... Lnk -- link flag bit disabled 1....... Lnk -- link command tables, support linked commands .0...... Parity disabled .1...... Parity enabled -- MVME147 checks SCSI bus parity ..0..... DMA on ..1..... DMA off flag -- disable DMA for data out/in ...0.... CSCSI
ページ20に含まれる内容の要旨
CUSTOM SCSI PACKETS 2 status (Note 2) ...1.... CSCSI -- does not check SCSI status (Note 2) ....0... SCSI firmware uses SCSI rules (Note 3) ....1... SASI mode flag -- firmware uses SASI rules (Note 3) .....1.. SG -- scatter/gather enable, use data points to scatter/gather table. During custom SCSI packet, you have to set this bit if scatter/gather DMA operation is required .....0.. SG -- scatter/gather disable ......1. SYNC -- synchronous transfers enable On INITIATOR role, SCSI firm
