
Any other value for the Buffer ID will cause the command to terminate with C H E C K C O N D I T I O N status.
The file shall set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL F I E L D IN
CDB.
7.38.4.1 Download Microprocessor Microcode and Save (Buffer_ID = 00h)
There are 3 types of download function are supported. The first one is "Single Binary Download", the
second is "Single Binary Chunked" and the thered is "RAM/OVR Download".
Buffer ID is 00h. (Single Binary Download)
The first one is that the data set consist of all necessary code and tables in a one big data set.
This is
starting with the special header data followed by tables, R A M code, 2 Overlay codes, E E P R O M data and
Flash-ROM code. (Flash-ROM code is optional depends on the card type and version if card has update
capability.) This download function is available when the file is running with full function (normal running)
before this write buffer is issued.
It takes up to 120 seconds to finish the command. After completion of this type of write buffer command,
the file will start as "Power on Reset" and running with newly downloaded code and configuration. There-
fore initiator may need a special treatment for this target.
Buffer ID is 00h. (Single Binary Chunked)
The second is using the same data set as the first (Single Binary). Separate the big 1 binary file with each
32k bytes chunk, then issue Write buffer command with I D = 0 0 repeatedly as the same number as the
chunk. The last chunk may equal or less than 32K bytes. (For example, in case of single binary file size is
65k bytes, there are 3 chunk like 32k, 32k and 1k. And 3 continuous Write Buffer commands with I D = 0 0
should be issued.) After issuing continuous Write Buffer for all chunk, the file behavior is the same as the
single binary.
Buffer ID is 00h. (RAM/OVR Download)
The thered one is that the data set consist of all code except R O M . This data set is starting without header,
R A M code and 2 Overlay codes are simply concatenated. This type of write buffer is the same effect of 3
times write buffer described just below. At the end of the command, the file is running without "Power on
Reset" automatically. The newly downloaded code becomes effective after Power On Reset.
Buffer Offset must be zero.
If an invalid value is specified, the command is terminated with C H E C K C O N D I T I O N status . File shall
set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL F I E L D IN CDB.
Parameter List Length must be specified for the total byte length of data set.
It may also be set 0000h in which case no code is updated. If an invalid value is specified, the command is
terminated with C H E C K C O N D I T I O N status. File shall set sense key to ILLEGAL REQUEST and addi-
tional sense code to ILLEGAL F I E L D IN CDB.
7.38.4.2 Download Microprocessor Microcode and Save (Buffer_ID = 00h thru 2)
Buffer ID is 00h thru 02h. (RAM/OVR Download step by step)
The code must be downloaded to the file in 3 separate blocks. The 3 blocks must be sent in the correct
sequential order and incremental buffer ID starting from 0. On all write buffer commands except the final
one, the file merely stores the code and no action is taken.
When the final block is received, the code
validity will be checked via checksum and signature for integrity and compatibility with the R O M code.
Once these checks have passed the file will overwrite the old code stored on the disk with the new download.
In between downloading the code blocks, the file will continue to accept and process other commands from
this and any other initiator. However if power is cycled or a reset occurs among them, the download proce-
dure must be restarted.
Buffer Offset must be zero.
SCSI C O M M A N D SET
157
Summary of Contents for DDRS-39130 - Ultrastar 9.1 GB Hard Drive
Page 2: ......
Page 14: ...4 OEM Spec of DDRS 3xxxx...
Page 15: ...Part 1 Functional Specification Copyright IBM Corp 1997 5...
Page 16: ...6 OEM Spec of DDRS 3xxxx...
Page 18: ...8 OEM Spec of DDRS 3xxxx...
Page 26: ...16 OEM Spec of DDRS 3xxxx...
Page 28: ...18 OEM Spec of DDRS 3xxxx...
Page 30: ...20 OEM Spec of DDRS 3xxxx...
Page 56: ...6 8 1 2 68 pin Model Figure 40 Outline of 68 pin Model 46 OEM Spec of DDRS 3xxxx...
Page 57: ...6 8 1 3 80 pin Model Figure 41 Outline of 80 pin Model Specification 47...
Page 60: ...6 8 3 2 68 pin Model Figure 45 Interface Connector 68 pin Model 50 OEM Spec of DDRS 3xxxx...
Page 61: ...6 8 3 3 80 pin Model Figure 46 Interface Connector 80 pin Model Specification 51...
Page 70: ...60 OEM Spec of DDRS 3xxxx...
Page 71: ...Part 2 SCSI Interface Specification Copyright IBM Corp 1997 61...
Page 72: ...62 OEM Spec of DDRS 3xxxx...
Page 172: ...162 OEM Spec of DDRS 3xxxx...
Page 188: ...178 OEM Spec of DDRS 3xxxx...
Page 208: ...198 OEM Spec of DDRS 3xxxx...
Page 214: ...204 OEM Spec of DDRS 3xxxx...
Page 224: ...214 OEM Spec of DDRS 3xxxx...
Page 228: ...Part Number 00K0097 Published in Japan S00K 0097 03...