Manuale d’uso / di manutenzione del prodotto MVME147 del fabbricante Emerson
Vai alla pagina of 170
1 GENERAL INFORMA TION 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 SCS I bus protocol, the SCS I firmware allows you to pass commands to the bus through high le vel command packets.
GENERAL INFO RMATION 1-2 1 Interrupt mode is the most processor-efficien t mode of operation. Multitas king is allowed fo r TA RGETs that su pport a rbitration, res e lectio n, 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) .
MVME14 7 S CSI Firmware Entry Po ints 1-3 1 6. $FFFE0 79A ( R TE entry ) N ote Within the SCSI firmware, which can stand alone without the debug monitor, t he first six longwords a re the branch table entri es refe renced abov e. The hex offsets pro vided reside withi n the non-volatil e RAM.
GENERAL INFO RMATION 1-4 1 Interrupt Structure paragraph in Chapter 4) or SCS I bus activity is slowed down. Additional comman ds may be sent to the SCSI firmwar e for a differen t peripheral device. $FFFE078E: FUNNEL COMMAND ENTRY This entry point is used by a pplication s that require multiple interfaces to the SCSI firm ware.
Equipment Supported 1-5 1 any particular con troller, nor does Motorola a ssume responsi bilit y for the operation of equipme nt manufactured by non- Motorola com panies.
GENERAL INFO RMATION 1-6 1 Streaming T anberg 36 60 (853 5) 15 0M b 6 Ta p e Cassette TEAC MT - 2ST/45 S2 2 Ta p e CONTROLLE R DEVICE P AR T CODE TYPE MANUF ACTUR ER/MODEL NUMB ER NOT ES 13 W inches t.
Equipment Supported 1-7 1 Floppy 2,3 18 8mm T ape Exabyt e EXB- 8200 82 0010-0 09 2 Devices Supported Un der Common Command Set W inchester T elevideo 700 0/740 0/3500 1,2 Floppy T elevideo 700 0/740 .
GENERAL INFO RMATION 1-8 1 Related Documentation The publications listed in the following table m ay provide additional helpful information. If not shipped with this product, they may be purcha sed from Motorola’ s Literature Distribution Center, 61 6 West 24th Street, Tempe, AZ 85282; te lephone (6 02) 994-65 61.
Manual Term inology 1-9 1 NOTE: Although not shown in the above list , each Motorol a Computer Group manual publication number is suffixed with characters which repres ent the revision level of the do.
GENERAL INFO RMATION 1-10 1 Unless otherwise specified, all addr es s references are in hexa decimal throughout this manual. An asterisk (*) following th e signal name f or signal s which are level signi ficant denotes that the signal is true or valid when the signal is low.
2 CUST OM SCSI P ACKETS Introduction The SCSI firmware requests "canned" functions from SCSI disk controllers and from SCSI tape con trollers. Some of these fun ctions are disk read and write, disk format, tape read and write, and tape positioning operatio ns.
CUSTOM SCSI PACKETS 2-2 2 FC B8 74 30 +$00 Contr oller LUN Device L UN +$02 Stat us Byte 0 Stat u s Byte 1 (N o te 1) +$04 Script Poin ter (M SW) +$06 Script Point er (LSW) +$08 Command T able Pointer.
Initiator Role Cus tom Packet 2-3 2 $0E 00000000 Initia tor r ole (T ARGET enable/sequence bit undefined) $0F 00000000 Reserved $10 xxxxxxxx xxxxxxx x Scatter/g ather en try count.
CUSTOM SCSI PACKETS 2-4 2 This first class is used for command execution and/o r message passing through the MVME147 SCSI firmware while the module is playing the initiator role.
Initiator Role Cus tom Packet 2-5 2 commonly called a "thread"). Th e script allows the SCSI firmware to follow the TARG ET bus sequences and also a llows the firmware to resume a disconnected thread once a disconnect/ res elect occurs.
CUSTOM SCSI PACKETS 2-6 2 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 SC SI firmwa re are listed in the following table.
Initiator Role Cus tom Packet 2-7 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) o r just return as an intermediate return witho ut disconnect from the bus (script code 0 x28).
CUSTOM SCSI PACKETS 2-8 2 FC B8 74 30 +$00 Status /Flag By te Retry Count (00) +$02 Link Poi nter ( M SW) +$04 Link Poin ter (L SW) +$06 Comma nd Leng th +$08 SCSI Command Descriptor Block (CDB) +$0A .
Initiator Role Cus tom Packet 2-9 2 Even Byte Odd Byte FC B8 74 30 +$68 T ran sfer Ad dress + $ 6 A 0000 + $ 6 C 0000 + $ 6 E 0000 + $ 7 0 0000 +$72 Comm and Offset +$74 Sense Data Bl ock . . . +$9E Sense Data Bl ock $00 xxxxxxxx Stat us /flag byte 0.
CUSTOM SCSI PACKETS 2-10 2 status (Note 2 ) ...1.... CSCSI -- does n ot check SCS I statu s (Note 2) ....0... SCSI firmwar e uses SCSI rule s (Note 3) ....1... SASI mode flag -- firmware uses SASI rules (Note 3) .....1.. SG -- sc at ter/ ga ther enable, use da ta points to scatt er/gath er table.
Initiator Role Cus tom Packet 2-11 2 ......0. ASYNC -- asynchrono us transfers e nable $01 00000000 Retry count (must be 00) $02 xxxxxxxx xxxxxxx x Li nk pointer (MSW) -- for l i nke d c o mm an ds.
CUSTOM SCSI PACKETS 2-12 2 the fir mware stat us ($64) and sent to initiat or . If you determin e to use bit 1-4, such as data parity error , th e firmw are non-z ero status o n bit 1- 4 ha s high er priority .
Initiator Role Cus tom Packet 2-13 2 $1E xxxxxxxx xxxxx xxx Me ssage -in le ngth - - bytes expect ed during message-i n (max=2 58 for extended messages) $20 xxxxxxxx xxxxxxx x Message-in poin ter (MSW.
CUSTOM SCSI PACKETS 2-14 2 $62 xxxxxxxx xxxxxxx x Sector number in error ( LSW ) $64 xxxxxxxx Initiato r r ole - Status byte from SCSI contr oller (un chang ed) TA R G E T r o l e - firmwar e determined SCSI status $65 xxxxxxxx Reserved $66 xxxxxxxx xxxxxxx x T ransfer a ddress -- for a read or writ e.
Initiator Role Cus tom Packet 2-15 2 Example: Sending linked commands to a disk controller You intend to implement a read-modify-w rite function for your particular operating sys tem. The benefit of linking com mands on the SCSI bus is a better utilization of bus bandwidth.
CUSTOM SCSI PACKETS 2-16 2 second command. The fo llowing linked command example may be performed on the Arch ive 2150 disk controller ( it supports linked commands). The SCSI firmware does not support linked command with flag. PACKET FOR THE LINKED COMMAND EXAMPLE: PACKET DC.
Initiator Role Cus tom Packet 2-17 2 ******* ***** ******** ***** ****COM MAN D TA BLE FOR THE FIRST COMMAND* ******* ***** * CT1 D C.B %1100000 0 * X LINK FLAG ON * X PARITY CHECKING ENABLED * X DMA ENABLED * X CUSTOM SEQ. FLAG=> FIRMWARE CHECKS STATUS * X FIRMWARE USES SCSI RULES (RES ELECT, ETC.
CUSTOM SCSI PACKETS 2-18 2 ******* ******** ***** ** ***** **CO MMAN D TABLE FOR THE WRITE COMMAND* ******* ***** * CT2 D C.B %0100000 0 * X LINK FLAG OFF * X PARITY CHECKING ENABLED * X DMA ENABLED * X CUSTOM SEQ. FLAG=> FIRMWARE CHECKS STATUS * X FIRMWARE USES SCSI RULES (RES ELECT, ETC.
TARGET Enable Custom Packet 2-19 2 N ote A linked command with the flag bit set is not supported, and the flag bit is ignored if it is set. T ARGET Enable Custom Packet The TARGET enable custom packet is show n in the following table.
CUSTOM SCSI PACKETS 2-20 2 $03 xxxxxxxx Status from SCSI firmwar e (byte 1) (Note 1) $04 xxxxxxxx xxxxxxx x Not used $06 xxxxxxxx xxxxxxx x Not used $08 xxxxxxxx xxxxxxx x Command t able pointer (MSW) (Note 2) $0A xxxxxxxx xxxxxxx x Command t able pointer (L SW) (Note 2) $0C 00000000 0000 0000 Res erved $0E 1.
TARGET Enable Custom Packet 2-21 2 This second "class" of custom packets is used to enable TARG ET role service by the MVME147 S CSI firmware. All eight SCSI-defined logical units can be independently serviced through the f irmware. Each logical unit nee ds to be enabled separately.
CUSTOM SCSI PACKETS 2-22 2 WORD $16: The interrupt level must be no-zero because TARGET role support is not used in non-interrupt mode. (If TA RGET role support were done in po lled mode, nothing else would be able to run on the MVME14 7 other than the TARGE T firmware because the microprocessor would poll for a selection as a TARGET.
TARGET Sequen ce Custom Packet 2-23 2 +$1A 0 0 Retry C ount $00 00000xxx Contr oller logical uni t numb er $01 00000xxx Device logical uni t numb er $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (N.
CUSTOM SCSI PACKETS 2-24 2 This third "class" of custom packets is used to service received commands an d messages for an enabled M VME147 TARGET logical unit.
TARGET Sequen ce Custom Packet 2-25 2 WORDS $0 4 and $06: SCRIPT POINTER -- The address of the TARG ET script to be performed to service the initiator request.
CUSTOM SCSI PACKETS 2-26 2 3. During the m essage-in phase, the COMMAND COMPLETE message is sent to the initi ator . 4. The END OF T ARGET SCRIP T code causes the firmwar e to disconnect fro m the bus.
TARGET Sequen ce Custom Packet 2-27 2 (Byte 01): Not used by the TA RGET role firmware. M ust be set to $00. CT words $02 and $04: LINK POINTER. Not used by the TARGET r ole firmware. CT word $06: COMMAND LENGTH. Not used by the TARG ET sequence call.
CUSTOM SCSI PACKETS 2-28 2 CT words $16 and $18: DATA LE NGTH. The number of by tes to transfer during either the data- in or the data-out phase. Not used if DMA is enabled and SG bit is set in statu s/f la g byte in word o. CT words $1A and $1C: DATA POINTER.
TARGET Sequen ce Custom Packet 2-29 2 STATUS BYTES 2 and 3. Not used by the TARGET role f irmware. Packet word $1A: RETRY COUNT. Not used by the TARGET role firmware.
CUSTOM SCSI PACKETS 2-30 2.
3 P ACKET RETURN ST A TUS Packet Return Status When packets are returned to the user, they contain two status words: on e with an offset of $02 and the other with an offset of $18, as shown in the tables below, respectively. The first table details the status codes co ntained in the word at offset $0 2.
PACKET RETURN STATUS 3-2 3 Bit 15 (FINALSTAT) 1 = Intermediate return. 0 = Fina l sta tus. The script processing completed succ- essfully, OR the s cript processing encountered a f atal error. N ote This does not mea n that the oper ation that the user requeste d on the SCSI was successful.
Packet Return Status 3-3 3 Bit 2 (EOM) End of media . Bit 3 (F M) Filemark Bit 4 (COM MAND RETRY) 1 = Retries were performed. Bit 5 (COM MAND RE- TRY OV ERFL OW) 1 = Retr y ove rflow.
PACKET RETURN STATUS 3-4 3 FC B8 74 30 +$00 . . +$60 Bloc k Numbe r in Er ror (MS W) +$62 Block Number in Err or (LSW) +$64 SCSI Con troller St atu s 0 0 +$66 T ran sfer Ad dress +$68 T ran sfer Ad dress + $ 6 A 0000 + $ 6 C 0000 + $ 6 E 0000 + $ 7 0 0000 +$72 Comm and Offset +$74 Sense Data Bl ock .
Packet Return Status 3-5 3 This is the memory addr ess of the next byte to be tran sferred. $68 xxxxxxxx xxxxxxx x T rans fer address -- for a read or writ e. . . . . $72 xxxxxxxx Command error status byte (v alid following a comman d error $0B) $73 xxxxxxxx Offset within packet.
PACKET RETURN STATUS 3-6 3 $09 (T ARGET mode) data rec eived f rom init iator w ith parity error , user mus t inte rpr et th en con tinue with new t_seq. 1,9 Final Return Codes $00 GOOD. Script pr ocessing is OK. 2 $01 Undefined probl em. 2 $02 T ARGET has Received Data without error , and user may inte rpr et th en con tinue with new t_seq.
Packet Return Status 3-7 3 T able 3- 2. Packet S tatus Codes (cont’d) CODE MEANING NOTES $0A SCSI b us r eset rec eived (A1 pointi ng to packe t list). (Refe r to the SCSI Bus Reset Packet section in Chap ter 7.) 2 $0B Command error (bad command code, bad timing, or command door was closed when a command was r eceived) = 00.
PACKET RETURN STATUS 3-8 3 T able 3- 3. Packet S tatus Codes (cont’d) CODE MEANING NOTES $1B T ARGET module re jected a n initiat or message and r eturned with this stat us to a pa rticular LUN service routin e.
Packet Return Status 3-9 3 T able 3- 4. Packet S tatus Codes (cont’d) CODE MEANING NOTES $26 UNI T A TTENTION. Indi cates that the removable media may have been changed or the T ARGET has been r eset.
PACKET RETURN STATUS 3-10 3 T able 3- 5. Packet S tatus Codes (cont’d) CODE MEANING NOTES Request-Sense -Data Error-Class 0 through 6 Codes (Controlle r-Dependen t) $40 NO ERROR ST A TUS. 2,5,6 $41 NO INDEX SIGNA L. 2,5 ,6 $42 NO S E EK C O MPLE TE.
Packet Return Status 3-11 3 NO TES : 1. Interme diate return co d es. Bit 15- 1, actu al word=$80 xx, $90 xx, etc. 2. F inal retu rn cod es. 3. S ense ke y sta tus codes f or Req uest-Sen se-Data er ror -- class 7. An off set of $ 20 i s added to all sense key codes.
PACKET RETURN STATUS 3-12 3.
4 SCSI FIRMW A RE INTERRUPT STRUCTU RE SCSI Firm ware Interru pt Structure The SCSI interface firmwa re was designed for processo r efficiency. Whenever the SCSI bus is in a state that does not need monitoring, the f irmware releases the processor so it may perfor m other function s such as user tasks and lower priority events.
SCSI FI RMWAR E INTE RR UPT S TRUCTU RE 4-2 4 the REACTIVATION entry point of the SCSI firmware. The WAIT FOR INTERRUPT (OPE N) sta tus is usually given when a particula r TARGET is "threaded" to th e MVME147 on the SCSI bus, and is slow in tran sitioning between information tra nsfer phases.
5 WRITING A DRIVER Introduction This chapter covers information essential in writing a driver to support the SCSI interface in interrupt mode. A driver for non-interrupt mode is a trivi al subset of the interrupt mode driver. The approach taken is to describe the major sections of a driver that need to be w ritten.
WRITING A DRIVER 5-2 5 Return from the SCSI firmware to th e driver is done through the vector supplied in the packet. The VERSAdos driver uses vector $4E (offset $138), and tape driver uses vector $4D (offset $134). These vectors must be initialized to point to a driver ro utine which handles the return.
Interface Rules for the S CSI Fi rmware 5-3 5 information; it does imply that only one routine handles the exit conditions dictated by bit 13 of the s econd word in the user packet (also known as the status word).
WRITING A DRIVER 5-4 5 Command status processing is the result of a firm ware return to the vector specified in the command packet. If this decoupling exists, the command entry execution can only occur if the processor is not tied up performing SCSI firmware functions or perform ing command status functions.
Interface Rules for the S CSI Fi rmware 5-5 5 RTE required, or the RTE entry ($FFFE079A) RTE r equired as status code $xx04 abo ve. This intermediate status only happens when the TARGET ro le is enabled.
WRITING A DRIVER 5-6 5 IF BIT 13 IS SET THEN RETURN TO THE CALLER OF YOUR CODE THROUGH (command 1. AN RTS IF HE CA LLED YOU WITH A BSR/JSR thread) 2. AN RTE IF HE CA LLED YOU WITH A TRAP THAT REQUIRES AN RTE RETURN. ELSE: (bit 13 is cl ear) 1. RESTORE THE REGISTER SET POINTED TO BY A3.
Interface Rules for the S CSI Fi rmware 5-7 5 FUNNEL module queued the request an d returned to you w ith a $A002 intermediate status code. In or der for this packet to r esu me pr ocessing, the firmwar e sets the software interrupt to reenter the interrupt entry point ($FFFE0788) .
WRITING A DRIVER 5-8 5 error because if a subsequent co mmand is queued in the FUNNEL queue or the wait queue, no busy error is given. In average, a device could have on e packet in FUNNEL queue, four packets in wait queue, and an active command in attach table.
Interface Rules for the S CSI Fi rmware 5-9 5 9. T ARGET LUN 6 service h andler: Services requests for l ogical unit 6 of the MVME1 47 T ARGET . 10. T ARGET LUN 7 service handler: Ser vices requests for logical unit 7 of the MVME1 47 T ARGET . The summary below is intended to h elp users who have multiple callers to the SCSI firmware.
WRITING A DRIVER 5-10 5 xx08 : SIMILAR TO xx08 ABOVE, O NLY THE DATA RECEIVED HAS SOM E PARITY ERRO R OCCURRED. 2. F INAL RE TURNS: SAMPLE RETURN CODE FOR O NE OF MANY CALLERS OF THE S CSI FIRMWARE: N ote It may not be clear to th e casual reader that ad dr ess register A3 i s not modified in thi s return code.
Interface Rules for the S CSI Fi rmware 5-11 5 MOVE.W 2(A2),D0 STATUS W ORD TO D0. BTST #15,D0 FINAL/IN TERMEDIATE STATUS? BEQ FINALSTAT IF 0, TH E RETURN IS A FINAL ONE. ************************************** **************************** ************ *THE FOLLOWING CODE CHECKS ALL ALLOWED INTERMEDIATE RETURN CODES.
WRITING A DRIVER 5-12 5 ************************************** **************************** ************ ** * THE CODE BELOW HANDLES FINAL RETURN CODES. FINALSTAT: BSR POSTSTAT POSTSTAT IS A SUBROUTINE THAT POSTS FINAL STATUS * POSTSTAT RETURNS THE Z BIT=1 IF STAT US IS O.
Interface Rules for the S CSI Fi rmware 5-13 5 * RESTORE REGISTERS FOR SCSI ROUTINE * The driver must restore the registers the SCSI firmware has used. * A3 is pointing to a list of the regi sters to restore. * The following code is for 68010 or newer processor and could be more * efficient if more advanced processor as 68020, 68030 is used.
WRITING A DRIVER 5-14 5 by the driver -- specifically, command queuing. If you choose to fo llow the rules for multiple callers, the firmware queues command packets for you whenever the bus is busy.
6 T ARGET ROLE ROUTINES Introduction According to SCSI definition s, an initiator is an SCSI device that initiates a command on the bus to be executed by the TARGET; a TARGET is an SCSI device that is selected by an initiator and executes what is requested by the initiator.
TARGET ROLE ROUTINE S 6-2 6 particular device on the SCSI bus. The in dexing is accom plish ed by simply splitting the 64 entries into 8 entries of 8 peripheral devices. Each block of eight devices correspond ed to each SCSI device. Th e MVME147 is one of these SCSI devices.
MVME147 SCSI Firmware TARGET Role Structure Req uirements 6-3 6 Command Table pointer Script pointer Interrupt level 7 through 1 Return vector TARGET enable/TARG ET sequence Contro l numb er = M VME147 l evel Peripheral device LUN (0 thr ough 7) Scri pt Below are the TARGET role script codes for SCSI bus phases.
TARGET ROLE ROUTINE S 6-4 6 Data Area Only one direction allowed per com mand. If multiple directions of data transfer are required, linked commands could provide a solution.
Enabling TARG ET Role 6-5 6 enable (word $0 E = $C000), and with the following data structures reserved for TARG ET role service. a. Com ma n d T ab le ( 384 byte s) N ote During the TARGET role, when.
TARGET ROLE ROUTINE S 6-6 6 the user command table. The service of this command is pro vided by you. This service is provided by a custom SCSI sequen ce -- T ARGET sequence, which is described in the next section. IMPLEMENTATION NOTE: The TAR GET LUN is deciphered from the identify message sent immediately after the selection phase.
Servicing the TARGET Requests 6-7 6 service performed by the fir mware is now complete. Finishing some housekeeping, the firmware returns to the user service routine for the selected LUN and gives it a final status code of $ xx17.
TARGET ROLE ROUTINE S 6-8 6 The operation code of $0A is for the SEND command. The LUN should match the logical u nit for the MVME14 7 TARGET. The trans fer length tells you how many bytes are going to be excha nged during the data-out phase.
Servicing the TARGET Requests 6-9 6 STEP 3: Data Preparation a. Decode the transfer length fr om the command descriptor block an d load this length into the co mmand table wor ds $16 and $18 -- data length.
TARGET ROLE ROUTINE S 6-10 6 The operation code of $08 is for the R ECEIVE command. The L UN should match the logical unit for the MVME1 47 TARGET. The transfer len gth tells you how many bytes are going to be exchanged during the data-out phase. The flag and link bits should be treated in the sam e manner as for the SE ND command example abo ve.
Servicing the TARGET Requests 6-11 6 c. Decode the link and flag bits and store the proper message to be presented during the message-in phase into th e message-in buff er (pointed to by wor ds $20 an d $22 of t he comm and tabl e).
TARGET ROLE ROUTINE S 6-12 6.
7 SCSI P ACKETS Introduction Command packets for the SCSI functions are listed in Table 7-1. The command packets are described in detail in the following paragraphs.
SCSI PA CKE TS 7-2 7 Read/W rite Packet For common comman d set refer to Appendix A. DISK. Commands sent to the con troller are: Read ($28), and Write ($2A). For a read o r write function, the maximum number of bytes that ca n be transferred in a single call is 16Mb.
Read/Write Packet 7-3 7 space-to-end-of-reco rded-media, or write command. To read, the controller must be at BOT or following a space- blocks, space-filemarks, or read command.
SCSI PA CKE TS 7-4 7 $00 00000xxx Contr oller logical uni t numb er $01 00000xxx Device logical uni t numb er $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from SCSI fi.
Read/Write Packet 7-5 7 in SG ta ble, i f zero , SG is disa bled $12 00000000 0000 0000 Res erved $14 xxxxxxxx Command Control 0....... Cache ON fo r t ype 13 contr oller only 1....... Cache OF F for type 13 contr oll er only .0...... T ape rea d fo rward fo r tape device s that support this .
SCSI PA CKE TS 7-6 7 Old Packet Supported for Compati bility Even Byte Odd Byte NOTE S: 1. R e fer to Ch ap ter 3. 2. R e fer to th e foll owing s catter /gat her tab le for mat. 3. The inter rupt level of th is firmwar e can be fr om level 0 to 7. It should be kept the sa me thr oughout the firmwar e execution; i .
Read/Write Packet 7-7 7 + $ 1 2 0000 +$14 Comm an d Control F unctio n Code ( 00 , 04) +$16 Interrupt Level V ector Numb er +$18 Stat us Byte 2 Stat u s Byte 3 (N o te 1) $00 00000xxx Contr oller logi.
SCSI PA CKE TS 7-8 7 in SG ta ble, i f zero , SG is disa bled $12 00000000 0000 0000 Res erved $14 xxxxxxxx Command Control 0....... Cache ON fo r t ype 13 contr oller only 1....... Cache OF F for type 13 contr oll er only .0...... T ape rea d fo rward fo r tape device s that support this .
Read/Write Packet 7-9 7 DMA Scatter/Gather T able Entry Each scatter/gather table entry has two longwords: first one is DMA memory address, second is control/byte co unt. 310 |functio n code (3 bit s) 1 = link to next entryFor example $5 is 0 = no link, last entryused here (supervisory data space) NOTE S: 1.
SCSI PA CKE TS 7-10 7 Attach/Detac h Pack et (all devices) For common comman d set refer to Appendix A. The following SCSI commands are exec uted during an attach : NOTES: Ther e may be any number of scatter/gather en tries. The scatter/gather tabl e must be in local MVME147 RAM (the DMA channel does n ot table w alk offboa rd RAM).
Attach/Detach Packet (all devices) 7-11 7 An attach is required bef ore any other commands may be sent to the S CSI firmware (except custom SCSI sequence or Bus Reset).
SCSI PA CKE TS 7-12 7 Some SCSI controllers r eturn a "check" status on the first comman d sent to them after power-up or re set. The SCSI firmware retries the comman d if the controller ret.
Attach/Detach Packet (all devices) 7-13 7 +$1E +$20 Pointe r RAM Wo r k A r e a (MSW) +$22 Pointer RAM Wo r k A r e a (LSW) +$24 Logi cal Byte s per Block +$26 +$28 Alt Sectors per Zone No.
SCSI PA CKE TS 7-14 7 ........ .......0 FM encod ing, single density ........ .......1 MFM encod ing, double dens ity ........ ......0. Single t rack d ensity (me d ia TP I = ½ dr ive TPI, double step) ........ ......1. Double t rack de nsity (media TPI = dr ive TPI) .
Attach/Detach Packet (all devices) 7-15 7 $12 xxxxxxxx Contr olle r type (ref er to controlle r ty pe table ) $13 00000000 Drive type (0 = random a ccess dr ive) $14 00000000 Reserved $15 xxxx1x00 SCS.
SCSI PA CKE TS 7-16 7 $20 xxxxxxxx xxxxxxx x Address of 384-byte SCSI RAM ar ea (MSW) $22 xxxxxxxx xxxxxxx x Address of 384-byte SCSI RAM ar ea (LSW) This SCSI RAM work area can no t be deallocate d or moved exce p t after a d etach or r eset comm and.
Attach/Detach Packet (all devices) 7-17 7 Old Packet Supported for Compati bility Even Byte Odd Byte attributes (byt e offset $10). $29 xxxxxxxx Altern ate cyli nders defines th e number of alte rnate c ylinders per disk th at are to be reser ve d at the en d of the disk for alte rnate s.
SCSI PA CKE TS 7-18 7 +$20 RAM W ork Ar ea Addr ess (MSW) +$22 RAM W ork Ar ea Address (L SW) $00 00000xxx Contr oller logical uni t number (SCSI addr ess 0-7) $01 00000xxx Device logical uni t number.
Attach/Detach Packet (all devices) 7-19 7 ........ ......0. Single track d ensity (me d ia TP I = ½ dr ive TPI, double step) ........ ......1. Double track de nsity (media TPI = dr ive TPI) ........ ........ Rese rved ........ ....0... 250K bits/sec data rate (5¼ inch) .
SCSI PA CKE TS 7-20 7 $13 00000000 Drive type (0 = random a ccess dr ive) $14 00000000 Reserved $15 xxxx1x00 SCSI function ($08 = atta ch, $78 = n e w atta ch, $0C = det ach) $16 000000xx Interrupt l .
Attach/Detach Packet (all devices) 7-21 7 Example for floppy: be de scribe d as ei ther a trac k o r a c yli nder , as speci fied by bit 1 1 of the SC SI drive attributes (byt e offset $10). $1F xxxxxxxx Altern ate cyli nders defines th e number of alte rnate c ylinders per disk th at are to be reser ve d at the en d of the disk for alte rnate s.
SCSI PA CKE TS 7-22 7 New Packet Even Byte Odd Byte 250K B/S Da ta 500K B/S Da ta 250K B/S Data 500K B/S Data Rate Rate Rate Rate S t e p R a t e 0000 Heads 2 2 2 2 Precompen satio n $50 (No te 1) $50 o r $4D 8 in.
Attach/Detach Packet (all devices) 7-23 7 +$04 0 0 Number of T racks +$06 0 0 Minimum Read T ran sfer +$08 0 0 Minimum W rite T ransfer +$0A 0 0 Streaming Co unt +$0C Speed Code Density Code + $ 0 E 0.
SCSI PA CKE TS 7-24 7 $07 00000000 Minimum read transfer siz e (not used by all contr ollers $08 00000000 Reserved $09 xxxxxxxx Minimum write transfer siz e (not used by all contr ollers $0A 00000000 .
Attach/Detach Packet (all devices) 7-25 7 $05 1/4 " 4/9 QIC- 24 Cartridg e Se rial 80 00 GC $06 1/2" 9 Reel-to-r eel Pa rallel 3200 PE $0E 00000000 Reserved $10 xxxxxxxx xxxxxxx x SCSI tape att ributes ........ .......0 Non-buffer ed writes (Note 3) .
SCSI PA CKE TS 7-26 7 Old Packet Supported for Compati bility (if this i s set to 0, the firmwar e disables corr ec t ion an d turns of f retr ies in the contr oller . Also, the firmwar e does not autom a tic a lly r etry the SCSI co mm and except "unit at te n ti on" and "not diagno stics".
Attach/Detach Packet (all devices) 7-27 7 Even Byte Odd Byte FC B8 74 30 +$00 Contr oller LUN Device L UN +$02 Stat us Byte 0 Stat u s Byte 1 (N o te 1) +$04 0 0 Number of T racks +$06 0 0 Minimum R.
SCSI PA CKE TS 7-28 7 $04 00000000 Reserved $05 00000000 Number of tracks on media (not used by all contr ollers $07 00000000 Minimum read transfer siz e (not used by all contr ollers $08 00000000 Res.
Attach/Detach Packet (all devices) 7-29 7 $16 00000xxx Interrupt l evel (7 thr ough 0) (0 = polled mode) $17 xxxxxxxx V ector number to use upon return $18 xxxxxxxx Status from SCSI firmwar e (byte 2).
SCSI PA CKE TS 7-30 7 N ote This work area is used by the SCSI firmware to build the SCSI command and to return ad ditional info rmation. The user does not build this table. Shown below are the return parameters. This RAM wor k area cannot be de allocated or moved except after a deta ch or reset command.
Attach/Detach Packet (all devices) 7-31 7 . . +$9E Sense Data Bl ock $00 xxxxxxxx xxxxxxx x Reserved .. .. .. $60 xxxxxxxx xxxxxxx x Block nu mber i n error (MSW) (Note 1) $62 xxxxxxxx xxxxxxx x Block.
SCSI PA CKE TS 7-32 7 Format Packet For common comman d set operation refer to Appendix A. The command sent to the controller is: format device ( $04). The f ollowing SCSI commands ar e executed: $72 xxxxxxxx Command error status byte (v alid foll ow ing a command e rror $08) - - SCSI comman d in error .
Assign Alternate Sector Packet (SCSI) 7-33 7 The defect list is optional for this com mand. If the number of defe cts in the defect list is 0, a format device comma nd with no defects is sent to the controller. If the field is no nzero, the d efect list is sent to the controller.
SCSI PA CKE TS 7-34 7 +$0E Inter le a ve Facto r 0 0 + $ 1 0 0000 + $ 1 2 0000 +$14 Comm an d Control F unctio n Code ( 10 , 14) +$16 Interrupt Level V ector Numb er +$18 Stat us Byte 2 Stat u s Byte .
Assign Alternate Sector Packet (SCSI) 7-35 7 CL Comp lete List Clear and no defect list is supplied. Use existing grown defect list, no user list is suppli e d. Clear and defect list is supplied. Use existing grow n defect list, add user list to the grow n list.
SCSI PA CKE TS 7-36 7 DEFECT LIST TYPE 0 Even Byte Odd Byte $17 xxxxxxxx V ector number to use upon return $18 xxxxxxxx Status from SCSI firmwar e (byte 2) (Note 1) $19 xxxxxxxx Status from SCSI firmwar e (byte 3) (Note 1) NOTE: 1. Refe r to Chapt er 3.
Assign Alternate Sector Packet (SCSI) 7-37 7 DEFECT LIST TYPE 1 Even Byte Odd Byte DEFECT LIST TYPE 2 Even Byte Odd Byte . . 0 0 0 0 (Note 3, 4) 0 0 0 0 (Note 3, 4) 0 0 0 0 (Note 3, 4) 0 0 0 0 (No.
SCSI PA CKE TS 7-38 7 Head Bytes fr om Index (MSW) (Note 2) Bytes fr om Index (LSW) (Not e 2) $00 00000000 0000 00 00 De fect li st code $02 xxxxxxxx xxxxxxx x Reserved $04 xxxxxxxx xxxxxxx x Reserved $06 xxxxxxxx xxxxxxx x Sector nu mber (MSW) (Note 5) $08 xxxxxxxx xxxxxxx x Sector n umber (LSW) (Note 5) .
SCSI Bus Reset Packet 7-39 7 SCSI Bus Reset Packet This function activates the RST* (RESET) line on the SCSI bus (h ardware reset). All devices on the bus are reset and any commands that w ere pending are terminated. The SCSI firmware cle ans up internal flags and the status returned to the user is "command complete" ($0 0).
SCSI PA CKE TS 7-40 7 $00 00000000 Contr oller logical uni t numb er (contr oller r eset only) $01 00000000 Reserved $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from .
SCSI Controller Re s et Packet 7-41 7 SCSI Controller Reset Packet This function sends a bus device reset message ($0C) to the controller specified in the packet. All outstanding packets are returned with a "reset status" ($0A). This command af fects only the specified con troller.
SCSI PA CKE TS 7-42 7 + $ 1 2 0000 +$14 0 0 Func ti on Code (2 C) +$16 Interrupt Level V ector Numb er +$18 Stat us Byte 2 Stat u s Byte 3 (N o te 1) $00 00000000 Contr oller logical uni t numb er $01.
Rewind Packet 7-43 7 Rewind Packet The Rewind command ($01) rewinds the tape to the BOT. If the im mediate response bit is set, status is returned imm ediately, even though the controller is still busy rewin ding .
SCSI PA CKE TS 7-44 7 $01 00000000 Device logical uni t numb er $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from SCSI firmwar e (byte 1) (Note 1) $04 00000000 0000 00.
Read Block Limits Packet 7-45 7 Read Block Limits Packet The read block limits command ($05) returns the maximum and minimum block size written on the tape. The controllers supported by the SCSI firmware only s upport QIC 24 o r QIC 11 type blo cks which equal 5 12 ($200) bytes.
SCSI PA CKE TS 7-46 7 Space (Blocks, Filemarks, End of Recorded Media) Packet The Space command ($11) is used to position the tape. There are four modes: $04 xxxxxxxx xxxxxxxx Return ed maximum block .
Space (Blocks, Filemarks, End of Reco rded Media) Packet 7-47 7 where n = number of blocks o r filemarks to Space. Some dri ves su pport sp acin g backwa rds by us ing n egative 2’ s com plem ent number n. Refer to the drive manual. The table below shows the space packet.
SCSI PA CKE TS 7-48 7 $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from SCSI firmwar e (byte 1) (Note 1) $04 xxxxxxxx xxxxxxx x Number of blocks /filem arks (MSW) (onl.
Write Filemarks Packet 7-49 7 Wr ite Filemarks Packet The write filemarks command ($10 ) writes the specified number of filemarks to the tape. N ote The controller must be in general mode or write mode. Refer to ta pe re ad /write packet fo r more in forma ti on .
SCSI PA CKE TS 7-50 7 $00 00000xxx Contr oller logical uni t numb er $01 00000xxx Device logical uni t numb er $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from SCSI f.
Verify CRC Packet 7-51 7 V erify CRC Packet The verify Cyclic Redundancy Character (CRC) command ($13) instructs the controller to read the s pecified number of blocks and check the CRC of each block. The verify be gins at the current tape position and the tape is left positioned at the end o f the last block verified.
SCSI PA CKE TS 7-52 7 T ape Mode Select/Sense Packet The tape mode select command ($15) con figures the controller for the specified operational par ameters. The tape mode sense co mmand ($1A) return s the QIC format, controller and drive type, block size, and buffered mode.
Tape Mode Select/Sense Packet 7-53 7 The table below shows the tape mode select/sense packet. Even Byte Odd Byte FC B8 74 30 +$00 Contr oller LUN Device L UN +$02 Stat us Byte 0 Stat u s Byte 1 (N o te 1) +$04 0 0 Number of T racks +$06 0 0 Min. R ead T ra nsfer +$08 0 0 Min.
SCSI PA CKE TS 7-54 7 $05 xxxxxxxx Number of tracks on media (4 or 9) $06 00000000 Reserved $07 xxxxxxxx Minimum read transfe r size (contr oller reconn ects wh en it can ta ke spe c ified numb er of .
Inqu iry P ack et 7-55 7 Inquiry Packet The inquiry command ($1 2) returns information fro m the controller that identifies which controller is attached a nd its attributes. The format and the number of bytes returned varies fro m controller to controller (refer to the appropriate controller manual fo r this information).
SCSI PA CKE TS 7-56 7 +$00 Contr oller LUN Device L UN +$02 Stat us Byte 0 Stat u s Byte 1 (N o te 1) +$04 0 0 Inquir y Da ta Len gth +$06 I nquiry Da ta Poin te r (MSW) +$08 Inquiry Data Pointer (LSW.
Inqu iry P ack et 7-57 7 Even Byte Odd Byte $14 00000000 Reserved $15 01000000 SCSI function ($50 = inquiry) $16 000000xx Interrupt l evel (7 thr ough 0) (0 = polled mode) $17 xxxxxxxx V ector number to use upon return $18 xxxxxxxx Status from SCSI firmwar e (byte 2) (Note 1) $19 xxxxxxxx Status from SCSI firmwar e (byte 3) (Note 1) NOTE: 1.
SCSI PA CKE TS 7-58 7 +$1A Data Returned Data Returned +$1C Data Returned Data Returned +$1E Data Returned Data Returned $00 xxxxxxxx Device type code (00 = direct acce ss) (01 = sequential access ) (7F = lo gical unit n ot presen t) $01 xxxxxxxx Device type qualif ier 0.
Load/Unload Packet 7-59 7 Load/Unload Packet The load/unload co mmand ($1B) positions the tape for remova l or to BOT. The load mode positions the ta pe at BOT, and the unload m ode positions the tape at End Of Tape (EOT). The retension bit causes the tape to go to BOT, then to EOT, then to BOT for the loa d mode.
SCSI PA CKE TS 7-60 7 00 0 0 +$14 0 0 Funct ion Cod e (54) +$16 Interrupt Level V ector Numb er +$18 Stat us Byte 2 Stat u s Byte 3 (N o te 1) $00 00000xxx Contr oller logical uni t numb er $01 00000x.
Recover Buffer Data Packet 7-61 7 Recover Buffer Data Packet The recover buffer d ata comman d ($1 4) is used to re cover th e data remaini ng in the controller’ s buffer following an er ror while writing to tape. Th is command returns the data not yet written to tape.
SCSI PA CKE TS 7-62 7 +$0C Number of Blocks + $ 0 E 0000 + $ 1 0 0000 + $ 1 2 0000 +$14 0 0 Funct ion Cod e (58) +$16 Interrupt Level V ector Numb er +$18 Stat us Byte 2 Stat u s Byte 3 (N o te 1) $00.
Request Sense Data Packet 7-63 7 Request Sense Data Packet The request sense data comman d ($03) returns the s tatus of the controller. The maximum len gth parameter a nd the data po inter are used to return this stat us. The actual format and th e number of bytes returned is controller- specific.
SCSI PA CKE TS 7-64 7 $00 00000xxx Contr oller logical uni t numb er $01 00000xxx Device logical uni t numb er $02 xxxxxxxx Status from SCSI firmwar e (byte 0) (Note 1) $03 xxxxxxxx Status from SCSI f.
Check Status Packet 7-65 7 Check Status Packet The check status command ($60) senses a $00 test unit ready comman d to the device. The returned status is in the 4 status bytes (refer to Returned Status Command Table in Chapter 3). The table below shows the check status packet.
SCSI PA CKE TS 7-66 7 Open Packet The open packet is a read o f the first blocks of a device. This command is intended as a "safe" read that won’ t overrun the byte count when the block size of the device is unknown.
Open Packet 7-67 7 Even Byte Odd Byte This command reads the first blocks of a disk or tape up to the maximum number of bytes or the maximum number of blocks, whichever comes first. If the requested number of blocks and the number of bytes match, the returned statu s is $ 00 (good ).
SCSI PA CKE TS 7-68 7.
A COMMON COMMAND SET AND DISK OPERA TION The first high level command required to interface wit h a Winchester disk is an ATTACH. An ATTACH initializes the S CSI firmware pointers and intern al flags.
COMMON COMM AND SET AND D ISK OPER ATION A-2 A Test Unit Ready Command CDB The firmware sends a mode sense command for page 3 , current values. The returned block size is compar ed to the block size in the packet; if they are not the same, the firmware sets a internal flag to block all subsequent read or write commands.
A-3 A If the scatter/gather field at byte offset $10 in th e user packet is not zero, the address at offset $4 i s taken as a scatter/gath er table address.
COMMON COMM AND SET AND D ISK OPER ATION A-4 A The information fo r each page below is used with each f ormat parameter listed in the FOR MAT PAR AMETER PAG E. The FO RMAT comm and performs the following to a Winchester disk: Mode sense for FORMAT PARAMETER PAGE 3 curren t values.
A-5 A If it won’ t fit, put the attach packet parameters offset into the error field in the command table (b yte offset $72), an d return a comma nd error status in the user packet. Send mode se lect command. Mode sense for FORMAT PARAMETER PAGE 4 curren t values.
COMMON COMM AND SET AND D ISK OPER ATION A-6 A The format operation ma y ha ve a defect list, if a defect list is supplied, a new defect list is built below the user s upplied defect list with th e four byte header as required by the SCSI device. Three defect list types are accepted.
A-7 A Below is the Command Descriptor Block for the Form at command. Format Command CDB User Defect List Type and Defect List Format. BYTE OFFSET V ALUE COMMEN TS 0 04 Command code 1 (N ote 1) LUN is .
COMMON COMM AND SET AND D ISK OPER ATION A-8 A MVME147 SCSI Firmware : Winchester Disk Parameter s. Before form atting a Winchester disk, the M VME147 SCSI firmware sends a mode select command fo r read/write error reco very parameters (page 1) to the controller.
A-9 A The remaining 12 bytes that are transferred during the DATA OU T phase for the mode select command are the page 1 parameters. Mode Select Parameter List: Page 1 Parame ters for Winchester drives.
COMMON COMM AND SET AND D ISK OPER ATION A-10 A Before form atting a Winchester disk, the M VME147 SCSI firmware sends a mode select command for format parameters (page 3) to the controller.
A-11 A The remaining 24 bytes that are transferred during the DATA OU T phase for the mode select command are the page 3 parameters. Mode Select Parameter List: Page 3 Parame ters for Winchester drive.
COMMON COMM AND SET AND D ISK OPER ATION A-12 A Mode Select Parameter List: Page 3 Parameters for Winchester drives (cont’ d) 8 (Note 4) Altern ate t racks p er vo lume (M SB) 9 (Note 4) Altern ate .
A-13 A Before form atting a Winchester disk, the M VME147 SCSI firmware sends a mode select command fo r drive geometry parameters (page 4) to the controller. Below is the c ommand descriptor block for the mode select command: Mode Select Command CD B 4.
COMMON COMM AND SET AND D ISK OPER ATION A-14 A The first twelve bytes that are transferred during the DATA OUT phase fo r the mode select command make up the mode select header , and the block descri.
A-15 A Mode Select Parameter List: Page 4 Parame ters for Winchester drives Mode Select Parameter List: Page 4 Parameters for Winchester drives (cont’ d) BYTE OFFSET V ALUE COMMENTS 0 4 Page code 11.
COMMON COMM AND SET AND D ISK OPER ATION A-16 A Before accessing a floppy disk o n the OMTI7000, the MVME14 7 SCSI firmware sends a mode select command to the controller.
A-17 A BYTE OFFSET V ALUE COMMENTS Mode Select Heade r 00 0 R e s e r v e d 1 (N ote 1) Media type 20 0 R e s e r v e d 3 08 Bloc k de sc rip t o r len gth Block Descript or 00 0 R e s e r v e d 1 0 0.
COMMON COMM AND SET AND D ISK OPER ATION A-18 A The remaining 32 bytes that are transferred during the DATA OU T phase for the mode select command are th e page 5 hea der a nd pa ramete rs. The header consists of the first two bytes listed below, the pa rameters are the remainin g bytes.
A-19 A Mode Select Parameter List: Page 5 Par ameters (cont’ d) C (Note 6) Starting cylinder - reduced write current (MSB) D (Not e 6 ) Starting cylinder - reduced write current (LSB) E (Note 7) Dri.
COMMON COMM AND SET AND D ISK OPER ATION A-20 A Pin 2 and Pin 34 Definition for Hig h Density. Pin 2 and Pin 34 Definition for Low Density. 3. Sectors/ track is t a ken fr om the attach packet, byte of fset $0C. 4. The numb er of bytes/ sector is taken from t he bytes per block field in t he attach packet, b yte of fset $1C.
A-21 A PIN 34 CONTROL PIN 2 CONTR OL BIT 76543210 C O M M E N T S 00011101 P i n 3 4 = d r i v e rea dy , low tr ue Bit 3 = 0) Pin 2 = 1 (lo w den sit y) 10.
COMMON COMM AND SET AND D ISK OPER ATION A-22 A.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Emerson MVME147 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Emerson MVME147 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Emerson MVME147 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Emerson MVME147 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Emerson MVME147, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Emerson MVME147.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Emerson MVME147. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Emerson MVME147 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
