Alta SARM Release8

LSISS2520/LSISS2530
SAS-SATA Bridge
System Application Reference Manual
Version 2.3
October 2010
Revision History
Version and Date Description of Changes

Version 2.3, October 2010 Added the following sections:
• Section 3.7.2.6, Field Replaceable Unit Sense Data Descriptor.
• Section 4.28, REPORT TIMESTAMP and Section 4.35, SET TIMESTAMP.
• Section 5.1.7.1, Mode Page 0Ah – Subpage 01h.
Updated the following sections:
• Section 3.5, Command Processing When Underlying ATA Device not Ready.
• Section 3.6, Command Processing During Persistent Reservation.
• Section 4.3, FORMAT UNIT.
• Section 5.1.13.1, Mode Page 32 – Subpage 1.
• Section G.2, ATA PASS THROUGH Commands with Long Logical Sector SATA Drive.
Updated the following tables:
• Table 18, Format Command Failure Degraded Mode, on page 34 and Table 19, Stop Command Degraded Mode, on page 34.
• Table 50, PAGE CODE, on page 66.
• Table 258, Sense Information, on page 267.
NOTE: This Revision History lists only the changes made to the current version of the document.
For a complete list of all revisions made to every version of this document since its original
publication, see Appendix K.
LSI, the LSI logo, EyeFinder, and Lynx are trademarks or registered trademarks of LSI Corporation or its subsidiaries. All other brand and product names may be trademarks of their respective companies.
LSI Corporation reserves the right to make changes to the product(s) or information disclosed herein at any time without notice. LSI Corporation does not assume any responsibility or liability arising
out of the application or use of any product or service described herein, except as expressly agreed to in writing by LSI Corporation; nor does the purchase, lease, or use of a product or service from
LSI Corporation convey a license under any patent rights, copyrights, trademark rights, or any other of the intellectual property rights of LSI Corporation or of third parties.
This document contains proprietary information of LSI Corporation. The information contained herein is not to be used by or disclosed to third parties without the express written permission of
LSI Corporation.
Corporate Headquarters Email Website

Milpitas, CA globalsupport@lsi.com www.lsi.com
800-372-2447
Document Number: DB15-000413-08

Copyright © 2010 LSI Corporation
All Rights Reserved
LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table of Contents
Table of Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1.2 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3 Supported SCSI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.4 Hardware Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
1.5 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Chapter 2: SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

2.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
2.2 Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
2.3 Mode Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
2.4 Log Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Chapter 3: Command Processing and Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.1 Control Byte Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
3.2 Priority Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.3 Command Processing During Execution of Active I/O Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.4 Command Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.5 Command Processing When Underlying ATA Device not Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
3.6 Command Processing During Persistent Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
3.7 Sense Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.1 Fixed Format Sense Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.2 Descriptor Format Sense Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.8 SCSI Status Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.9 Priority of SCSI Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.10 Unit Attention Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.11 Invalid LUN Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.12 Queue Full Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.13 Deferred Error Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.14 Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.15 Error Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
3.16 Error Reporting Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
3.17 Degraded Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
3.18 Task Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
3.19 Command Priority Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
LSI Corporation Confidential | October 2010 Page 3

Table of Contents LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Chapter 4: SCSI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

4.1 INQUIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
4.1.1 Inquiry Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
4.1.2 Default Inquiry Response Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
4.1.3 Fake Inquiry Response Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4.2 SATA PASS THROUGH Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
4.2.1 ATA PASS THROUGH (12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
4.2.2 ATA PASS THROUGH (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
4.2.3 ATA PASS THROUGH Status Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
4.3 FORMAT UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
4.3.1 Initialization Pattern Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
4.3.2 Sending WRITE FPDMA QUEUED Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
4.4 LOG SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
4.5 LOG SENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4.6 MDIO ACCESS COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
4.6.1 I/O Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
4.7 MDIO ACCESS RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
4.8 MODE SELECT (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
4.9 MODE SELECT (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
4.10 MODE SENSE (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
4.11 MODE SENSE (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
4.12 PERSISTENT RESERVE IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
4.12.1 PERSISTENT RESERVE IN SERVICE ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
4.12.2 PERSISTENT RESERVE IN PARAMETER DATA FOR READ KEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
4.12.3 PERSISTENT RESERVE IN PARAMETER DATA FOR READ RESERVATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
4.12.4 REPORT CAPABILITIES SERVICE ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
4.12.5 READ FULL STATUS SERVICE ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
4.13 PERSISTENT RESERVE OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
4.13.1 SERVICE ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
4.13.2 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
4.13.3 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
4.13.4 PERSISTENT RESERVE OUT PARAMETER LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
4.13.5 SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
4.14 READ (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
4.15 READ (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
4.16 READ (12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
4.17 READ (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
4.18 READ (32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
4.19 READ BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
4.19.1 Data (Mode 02h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
4.19.2 Descriptor (Mode 03h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
4.20 READ CAPACITY (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
4.21 READ CAPACITY (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
4.22 READ LONG (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
4.23 READ LONG (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
4.24 REASSIGN BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
4.25 RELEASE (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
4.26 RELEASE (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Page 4 LSI Corporation Confidential | October 2010

4.27 REPORT LUNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

4.28 REPORT TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.29 REQUEST SENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.30 RESERVE (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.31 RESERVE (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.32 SECURITY IN PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.33 SECURITY OUT PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.34 SEND DIAGNOSTIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.35 SET TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.36 START STOP UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.36.1 Processing of Start Stop Unit Command When DSM is in SATA_WAITING_FOR_SPINUP_REQUEST State . . . . . . . . . . . . 115
4.37 SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4.38 TEST UNIT READY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.39 VERIFY (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.40 VERIFY (12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4.41 VERIFY(16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4.42 WRITE (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.43 WRITE (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.44 WRITE (12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4.45 WRITE (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.46 WRITE (32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.47 WRITE AND VERIFY(10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4.48 WRITE AND VERIFY (12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.49 WRITE AND VERIFY (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.50 WRITE BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4.50.1 Data (Mode 02h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.50.2 Download Microcode and Save (Mode 05h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.50.3 Download Microcode with Offsets and Save (Mode 07h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.51 WRITE LONG (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4.52 WRITE LONG (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.53 WRITE SAME (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.54 WRITE SAME (16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.55 WRITE SAME (32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 5: SCSI Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

5.1 Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.1.1 Mode Parameter Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.1.2 Mode Page 00h (Supported Mode pages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5.1.3 Mode Page 01h (Read-Write Error Recovery Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.1.4 Mode Page 02h (Disconnect/Reconnect Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.1.5 Mode Page 07h (Verify Error Recovery Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.1.6 Mode Page 08h (Caching Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.1.7 Mode Page 0Ah (Control Mode Page Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.1.8 Mode Page 18h (Protocol-Specific Logical Unit Mode Page for SAS SSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.1.9 Mode Page 19h (Protocol-Specific Port Mode Page for SAS SSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.1.10 Mode Page 1Ah (Power Condition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.1.11 Mode Page 1Ch (Informational Exceptions Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.1.12 Mode Page 25h (Logging Configuration Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.1.13 Mode Page 32h (Firmware Parameter Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.1.14 Mode Page 33h (Sector Skewing Support Parameter Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
5.1.15 Mode Page 34h (SATA Link Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.1.16 Mode Page 35h (SATA Queuing and Error Recovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.1.17 Mode Page 36h (SAS Link Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5.1.18 Mode Page 37h (Firmware Debug Mode Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5.1.19 Mode Page 39h (PHY Control Mode Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5.1.20 Mode Page 3Ah (SATA Link Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
5.1.21 Mode Page 3Bh (Device Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
5.2 Log Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.2.1 Log Page 00h (Supported Log Pages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.2.2 Log Page 02h (Write Error Counter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5.2.3 Log Page 03h (Read Error Counter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5.2.4 Log Page 05h (Verify Error Counter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.2.5 Log Page 06h (Non-Medium Error Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
5.2.6 Log Page 0Dh (Temperature Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
5.2.7 Log Page 0Eh (Start Stop Cycle Counter Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5.2.8 Log Page 0Fh (Application Client Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
5.2.9 Log Page 10h (Self-Test Results Log Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
5.2.10 Log Page 15h (Background Scan Results Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
5.2.11 Log Page 16h (ATA PASS-THROUGH Results Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
5.2.12 Log Page 18h (Protocol-Specific Port Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
5.2.13 Log Page 2Fh (Informational Exceptions Log page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
5.2.14 Log Page 30h (SATA Link Errors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
5.2.15 Log Page 31h - SMART Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5.2.16 Log Page 32h - System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5.2.17 Log Page 33h (LSISS2520/LSISS2530 Device Temperature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
5.2.18 Log Page 34h (LSISS2520/LSISS2530 device Log Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5.2.19 Log Page 35h (Versions Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
5.2.20 Log Page 36h (Nonvolatile scratch page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
5.2.21 Log Page 37h - Firmware Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
5.3 VPD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5.3.1 VPD Page 00 - List of pages Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5.3.2 VPD Page 80 - Unit Serial Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
5.3.3 VPD Page 83 - Device Identification Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
5.3.4 VPD Page 86 - Extended Inquiry Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5.3.5 VPD Page 87 - Mode Page Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.3.6 VPD Page 89 -SATA Information VPD Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
5.3.7 VPD Page B1 - Block Device Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Appendix A: System Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

A.1 Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
A.2 Firmware Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
A.3 Device Spin-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Appendix B: State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

B.1 Device State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
B.1.1 Device State Machine Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
B.1.2 State Machine Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
B.2 System State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
B.2.1 LSISS2520/LSISS2530_01: SYS_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
B.2.2 LSISS2520/LSISS2530_02: SYS_RDY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
B.2.3 LSISS2520/LSISS2530_03: SYS_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
B.2.4 LSISS2520/LSISS2530_04: SYS_STANDBY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
B.2.5 LSISS2520/LSISS2530_05:SYS_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Appendix C: Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

C.1 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
C.2 Delaying SAS Links Bring Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
C.3 Device Replacement Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
C.4 LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
C.4.1 Ready LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
C.4.2 Fault LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Appendix D: Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

D.1 Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
D.2 Boot Loader Image Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
D.3 Boot Option Image Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
D.4 Drive Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
D.5 Package Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
D.5.1 Main Package Header Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
D.5.2 Individual Component Header Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Appendix E: Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

E.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
E.1.1 Log Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
E.1.2 Logs Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
E.1.3 Logging Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
E.1.4 Log Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
E.1.5 Crash Log Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
E.2 Crash Dump format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Appendix F: Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

F.1 Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
F.1.1 FRU Code Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
F.1.2 Sense Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
F.1.3 List of InstIds Occurrences and ErrorIdx Class of Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Appendix G: Long Logical Sector SATA Drive Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

G.1 SCSI Commands with Long Logical Sector SATA Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
G.2 ATA PASS THROUGH Commands with Long Logical Sector SATA Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Appendix H: Sector Skewing Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

H.1 Packed Mode Non-512 Byte Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
H.1.1 Read Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
H.1.2 Write Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
H.2 Sparse Mode Non-512 Byte Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
H.3 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Appendix I: T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

I.1 Supported T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
I.2 Unsupported T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Appendix J: SAT-Specific Security Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

J.1 ATA Device Server Password Security Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
J.1.1 SECURITY PROTOCOL IN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
J.1.2 SECURITY PROTOCOL OUT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Appendix K: Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

K.1 Previous Versions Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 1: Introduction | Features
Chapter 1
Introduction
This chapter describes the LSISS2520/LSISS2530 bridge features, technology, and the
SCSI commands.
The LSISS2520/LSISS2530 device brings dual-port Serial Attached SCSI accessibility to a
SATA device, including multiple SAS initiator support. The LSISS2520/LSISS2530 device
supports SATA disk drives independent of speed and capacity and is universally
compatible with third party Serial Attached SCSI (SAS) controllers and expanders.
1.1 Features The LSISS2520/LSISS2530 device has the following features:

 Dual independent SAS Target Interfaces that are compliant with SAS 2.0 SSP
interface protocol.
 Single SATA host interface that is compliant with SATA 2.5.
 Support of Long Logical Sector SATA drive. See Appendix G, Long Logical Sector SATA
Drive Support for details.
 Support of sector skewing (520/528 bytes block lengths on 512 bytes sector sized
SATA devices, and 4104 bytes block lengths on 4096 bytes sector sized SATA
devices). See Appendix H, Sector Skewing Support for a detailed description.
 Support of T10 DIF (Protection Information) for User Data Sizes 512 bytes and
520 bytes for SATA devices that have 512-byte sector sizes. See Appendix I, T10 DIF
Features, for full details on the supported and unsupported DIF features.
 Multiple Initiator Small Computer System Interface (SCSI) access on each path that
supports four initiators per SAS port.
 Multiple commands, supporting a maximum of 64 commands.
 6Gb/s Store and Forward data flow architecture.
 Speed matching.
 SAS backplane signaling.
 Error status and reporting.
 Power and spin-up control.
 Embedded ARM966 processor for initialization, configuration, command
translation, response generation and exception handling.

Chapter 1: Introduction | Technology LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
1.2 Technology The LSISS2520/LSISS2530 device employs the following technologies:

 Implements the LSI™ 90-nm technology.
 Uses the ARM966E-S onboard processor.
1.3 Supported SCSI The LSISS2520/LSISS2530 device supports the following SCSI commands, as listed in
Commands the following table.
Table 1: Supported Commands
SCSI Command
ATA PASS THROUGH (12), ATA PASS THROUGH (16)
FORMAT UNIT
INQUIRY
LOG SELECT
LOG SENSE
MDIO ACCESS COMMAND, MDIO ACCESS RESPONSE
MODE SELECT (6), MODE SELECT (10)
MODE SENSE (6), MODE SENSE (10)
PERSISTENT RESERVE IN, PERSISTENT RESERVE OUT
READ (6), READ (10), READ (12), READ (16), READ (32)
READ BUFFER
READ CAPACITY (10), READ CAPACITY (16)
READ LONG (10), READ LONG (16)
REASSIGN BLOCK
REPORT LUNS
REPORT TIMESTAMP
REQUEST SENSE
SECURITY IN PROTOCOL
SET TIMESTAMP
SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16), RELEASE (10)
RESERVE (10)
SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16)
SECURITY IN PROTOCOL, SECURITY OUT PROTOCOL
SEND DIAGNOSTIC
TEST UNIT READY
VERIFY (10), VERIFY (12), VERIFY(16)
WRITE (6), WRITE (10), WRITE (12), WRITE (16), WRITE (32)
WRITE AND VERIFY(10), WRITE AND VERIFY (12), WRITE AND VERIFY (16)
WRITE BUFFER
WRITE LONG (10), WRITE LONG (16)
WRITE SAME (10), WRITE SAME (16), WRITE SAME (32)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 1: Introduction | Hardware Block Diagram
1.4 Hardware Block Diagram The following diagram shows an example of a hardware block diagram.
5V, 12V
Power
12V Supplies Filter
(3.3V, 1.8V,
1.0V)
3.3V
1.8V
1.0V
Reset HDD Power

Circuit Control
Circuit
SATA Connector
SAS Connector
Host 0
Device
LSISS2520/LSISS2530
Host 1
25 MHz
XTAL
Flash Memory
3_00075-00
Figure 1: Hardware Block Diagram

Chapter 1: Introduction | Acronyms LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
1.5 Acronyms The following acronyms are used throughout the document.
ADC Adaptive Data Compression

ASC Additional Sense Code
ASCQ Additional Sense Code Qualifier
LBA Logical Block Address
LSB Least Significant Byte
LUN Logical Unit Number
MSB Most Significant Byte
RSVD Reserved
SAS Serial-Attached SCSI
SAT SCSI/ATA Translation
SATA Serial Advanced Technology Attachment
SCSI Small Computer System Interface
SCT SMART Command Transport
SSC Spread Spectrum Clocking
SSP Serial SCSI Protocol
TMF Task Management Function
VU Vendor Unique Bits
1.6 References This document uses the following references.

 SCSI Primary Commands 4
 SCSI Block Commands 3
 ATA Translation 2
 SCSI Architecture Model - 4
 ATA 8 Command Set - ATA8-ACS
 Serial ATA 2
 Serial Attached SCSI 2
 SCSI/ATA Translation - 2 (SAT-2)
 LSISS2520 SAS-SATA Bridge Reference Manual, V1.1 (April 2009)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 2: SAS | Features
Chapter 2
SAS
This chapter describes the SAS features, mode pages, and log pages.
2.1 Features The LSISS2520/LSISS2530 device supports the following features:

 SAS 2.0 Draft Compliant
— Serial SCSI Protocol (SSP)
— Break Reply Capable
 Dual-port operation
— Full duplex operation
— G1 (1.5Gb/s), G2 (3Gb/s) and G3 (6Gb/s) SAS physical link rate
— Narrow port
 SAS-2 Disconnect-Reconnect Mode Page 0x02
— BUS INACTIVITY TIME LIMIT
— MAXIMUM CONNECT TIME LIMIT
— MAXIMUM BURST SIZE
 SAS-2 Port Mode Page 0x19
— BROADCAST ASYNCHRONOUS EVENT
— I_T NEXUS LOSS TIME
— READY LED MEANING
— CONTINUE AWT
— REJECT TO OPEN LIMIT
 SAS-2 PHY Control and Discovery Mode Page 0x19 - SUBPAGE CODE 0x01
 SAS-2 Shared Port Control Mode Page 0x19 - SUBPAGE CODE 0x02
— POWER LOSS TIMEOUT (see Section 5.1.9.3, Mode Page 19 - Subpage 2 for
restrictions on this field)
 SAS-2 PHY Mode Page 0x19 - SUBPAGE CODE 0x03
— Programmable PHY capabilities
— CURRENT PHY CAPABILITIES
— ATTACHED PHY CAPABILITIES
— NEGOTIATED SSC
— NEGOTIATED PHYSICAL LINK RATE
— SAS-2 Port Log Page 0x18

Chapter 2: SAS | Unsupported Features LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 NOTIFY (POWER LOSS EXPECTED)

— The LSI22520/LSISS2530 device supports this primitive according to Section
7.2.5.3.3 of the SAS-2 Revision 16 Specification with the following exception. The
LSI22520/LSISS2530 device does not send BREAK if in a SSP connection after the
NOTIFY (POWER LOSS EXPECTED) primitive is received. Instead, the
LSI22520/LSISS2530 device attempts to close the SSP connection as soon
as possible.
2.2 Unsupported Features The LSISS2520/LSISS2530 device does not support the following features:
 SAS 2.0 Draft Compliant – STP and SMP
 Dual-port operation – Wide port
 SAS-2 Disconnect/Reconnect Mode Page 0x02 – FIRST BURST
 SAS-2 Logical Unit Mode Page 0x18 – TRANSPORT LAYER RETRIES
 SAS-2 Port Mode Page 0x19 – INITIATOR RESPONSE TIMEOUT
 SAS-2 PHY Mode Page 0x19 SUBPAGE CODE 0x03 – HW MUXing
 Detection of duplicate Initiator Port Transfer Tag (IPTT)
2.3 Mode Pages The following table describes the SAS mode pages.
Table 2: SSP Target Port Mode pages
LSISS2520/LSISS2530 device
Mode Page Code SUBPAGE Code Description
Support
02h 00h Mode Page 02h (Disconnect/Reconnect Parameters) Yes
18h 00h Mode Page 18h (Protocol-Specific Logical Unit Mode Page for Yes
SAS SSP)
01h to DFh Reserved N/A
E0h to FEh VENDOR SPECIFIC No
FFh Return all subpages for this mode page Yes
19h 00h Mode Page 19h (Protocol-Specific Port Mode Page for SAS SSP) Yes
01h PHY Control and Discover Yes
02h Shared Port Control Yes
03h SAS-2 PHY Yes
04h to DFh Reserved N/A
E0h to FEh VENDOR SPECIFIC No
FFh Return all subpages for this mode page Yes
For mode page description, see Section 5.1, Mode Parameters.
2.4 Log Pages LSISS25x0 supports the Protocol Specific Port Log Page. For the description, see Log
Page 18h (Protocol-Specific Port Log page).

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Control Byte Overview
Chapter 3
Command Processing and Error Handling
This chapter describes the command processing and the error handling.
The following are the standard SCSI command functions that the LSISS2520/LSISS2530
device firmware supports and does not support:
 The LSISS2520/LSISS2530 device does not support the grouping function. Ignore
this field.
 The LSISS2520/LSISS2530 device does not support the Disable Page Out (DPO) bit
for Read and Write commands.
 The LSISS2520/LSISS2530 device does not support the BYTCHK field set to 1
condition except for the WRITE VERIFY command and the LSISS2520/LSISS2530
device support is nonstandard.
 The LSISS2520/LSISS2530 device does not support the FUA_NV (READ and WRITE
type commands) bit.
 The LSISS2520/LSISS2530 device supports the Free Unit Access (FUA) if the
underlying SATA device supports the FUA bit.
 The LSISS2520/LSISS2530 device does not support any XOR type commands.
 The LSISS2520/LSISS2530 device supports Smart Command Transfer (SCT)
commands if the underlying device supports SCT.
3.1 Control Byte Overview Each SCSI CDB contains a CONTROL byte. The location of this field varies from
command to command. For details, refer to SCSI Architecture Model-4 (SAM-4).
Table 3: CONTROL BYTE
Bit
7 6 5 4 3 2 1 0
Vendor Specific Reserved NACA OBSOLETE
NACA (Normal ACA)

The LSISS2520/LSISS2530 device does not support the NACA bit when set to 1. If the
LSISS2520/LSISS2530 device receives a command with the NACA bit set to 1, it returns a
CHECK CONDITION with the sense key set to ILLEGAL REQUEST and ASC set to INVALID
FIELD IN CDB.

Chapter 3: Command Processing and Error Handling | Priority Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
3.2 Priority Commands The SCSI commands that always run with GOOD status are as follows:
 INQUIRY
 REQUEST SENSE
 REPORT LUNS
These commands run prior to completing the execution of any other pending
commands in the queue. These commands are never queued.
The INQUIRY command and the REPORT LUNS command run regardless of the SATA
device's state.
NOTE: Although REQUEST SENSE is listed as a priority command, it requires access to

the SATA device. Because of this dependency, the LSISS2520/LSISS2530 device might
not be able to respond to this command immediately. It must issue a SATA command,
wait for the response, and then transmit the SCSI response. For this reason, the
LSISS2520/LSISS2530 device treats the REQUEST SENSE command as a nonpriority
command.
3.3 Command Processing When the LSISS2520/LSISS2530 device is not executing any I/O processes, a new I/O
During Execution of Active I/O process is then permitted to run (unless another internal target condition prevents
Process its execution).
If an active I/O process exists when the LSISS2520/LSISS2530 device receives a new
command, then the LSISS2520/LSISS2530 device performs the following checks:
 If the command is a priority command, the command is run.
 If the queue is FULL, then the QUEUE FULL status is returned.
 If the LOGICAL UNIT is not ready, CHECK CONDITION status is returned.
 If a Unit Attention exists, CHECK CONDITION status is returned.
 If the command is not allowed to run because of a Persistent Reservation, a
RESERVATION CONFLICT status is returned.
If these checks pass, the new command is added to the task queue.
If a command is added to the task queue, execution occurs when the command
becomes an active I/O process. This occurs if another internal target condition prevents
the execution (See Section 3.13, Deferred Error Condition) at the time the command is
added to the task queue.
3.4 Command Queuing If the LSISS2520/LSISS2530 device defers the execution of a SCSI command, these
commands are held in a queue until execution is scheduled.
The following commands are never queued.
 Priority commands
 Commands for an invalid Logical Unit Number
In these situations, the queue is bypassed and the received command runs
immediately. If one of these situations occurs when there are queued commands, the
order of the queue is preserved.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Command Processing When
Underlying ATA Device not Ready
When the target is ready to run a queued command, it selects the command at the
head of the queue.
When a command is added to the queue, the target examines the attribute to
determine how to position the new command.
 Head of Queue places the command so that it is the next to run. Multiple
commands of this type run Last-In First-Out (LIFO).
 Ordered Queue places the command so that it runs after any command that is
already queued and any command that is subsequently received with Head of
Queue. It runs before any command that is subsequently received with the Ordered
attribute or the Simple attribute.
 Simple Queue places the command so that it runs after any queued command that
has the Ordered attribute and any command that is subsequently received with
Head of Queue. The relative ordering of multiple commands with the Simple
attribute is determined by the queue algorithm that is in effect. See Section 5.1.7,
Mode Page 0Ah (Control Mode Page Parameters).
The target has maximum of 64 slots. Commands are queued in the slots. All queue slots
are returned to the free pool on a reset.
The LSISS2520/LSISS2530 device processes READ and WRITE Streaming Data
commands in FIFO (first in first out) order unless processing the Initiator Task Attribute
and Task Priority fields in the command frame.
3.5 Command Processing If the target receives a command from an initiator when the underlying ATA device is not
When Underlying ATA Device not ready, the LSISS2520/LSISS2530 device's response for various commands is as follows:
Ready
 The following commands run normally:
— INQUIRY
— PERSISTENT RESERVE IN
— PERSISTENT RESERVE OUT
— REPORT LUNS
— REPORT TIMESTAMP
— SET TIMESTAMP
 A CHECK CONDITION status with Sense key NOT READY (0x2), additional sense key
BECOMING READY (0x4), additional sense key qualifier
ASCQ_BECOMING_READY(0x1) is returned when the LSISS2520/LSISS2530 device is
attempting to bring up the device during startup. The Sense key/ASC/ASCQ is
changed to 0x04/0x81/0x00 if the LSISS2520/LSISS2530 device cannot bring up the
device because of any reason such as device qualification failure. See Section 5.1.13,
Mode Page 32h (Firmware Parameter Control) for drive qualification flags.
— FORMAT UNIT
— READ (10)
— READ (12)
— READ (16)
— READ (6)
— READ BUFFER
— READ CAPACITY (10)

Chapter 3: Command Processing and Error Handling | Command Processing When LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
— READ CAPACITY (16)

— READ LONG (10)
— READ LONG (16)
— REASSIGN BLOCK
— REQUEST SENSE
— START STOP UNIT
— SYNCHRONIZE CACHE
— TEST UNIT READY
— VERIFY (10)
— VERIFY (12)
— VERIFY (16)
— WRITE (10)
— WRITE (12)
— WRITE (16)
— WRITE (6)
— WRITE AND VERIFY (10)
— WRITE LONG (10)
— WRITE LONG (16)
— WRITE SAME (10)
— WRITE SAME (16)
 The commands WRITE BUFFER, SATA PASS THROUGH (12), SATA PASS THROUGH (16)
MODE SELECT (6), MODE SELECT (10), MODE SENSE (6), MODE SENSE (10), LOG
SELECT, and LOG SENSE might work or might not work, based on the command
options/parameters. If the options/parameters require the device to be ready and the
device is not ready, the same sense data as mentioned in the last point is returned.
The following mode pages do not support the Mode Select command when the
device is not ready.
— Mode Page 01h (Read-Write Error Recovery Parameters)
— Mode Page 08h (Caching Parameters)
— Mode Page 1Ch (Informational Exceptions Control)
— Mode Page 32h (Firmware Parameter Control)
— Mode Page 32h, Subpage 01h (Firmware Parameter Control Subpage 01h)
— Mode Page 35h (SATA Queueing and Error Recovery)
— Mode Page 3Ah (SATA Link Control)
NOTE: The LSISS25x0 device may support the Mode Select to the preceding Mode
Pages, even when the SATA device is not ready, if the particular Mode Select command
does not require sending an ATA command to the SATA device.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Command Processing When
The following mode pages do not support the Mode Sense command when the
device is not ready.
— Mode Page 0Ah (Control Mode Page Parameters)
— Mode Sense (to fetch all of the Mode Pages)
The following log pages support the Log Select command when the device is
not ready.
— Log Page 0Eh (Start Stop Cycle Counter Log Page)
— Log Page 33h (LSISS2520/LSISS2530 Device Temperature Log Page)
— Log Page 35h (Versions Log Page)
— Log Page 36h (Nonvolatile Scratch Log Page)
The following log pages support the Log Sense command when the device is
not ready.
— Log Page 00h (Supported Log Pages)
— Log Page 02h (Write Error Counter)
— Log Page 03h (Read Error Counter)
— Log Page 05h (Verify Error Counter)
— Log Page 06h (Non-Medium Error Log page)
— Log Page 0Eh (Start Stop Cycle Counter Log Page)
— Log Page 18h (Protocol Specific Port Log Page)
— Log Page 30h (SATA Link Errors)
— Log Page 32h (System Statistics Log Page)
— Log Page 33h (LSISS2520/LSISS2530 Device Temperature)
— Log Page 34h (LSISS2520/LSISS2530 Device Log Page)
— Log Page 35h (Versions Page)
— Log Page 36h (Nonvolatile Scratch Page)
— Log Page 37h (LSISS2520/LSISS2530 Device Firmware Statistics)

Chapter 3: Command Processing and Error Handling | Command Processing During LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Persistent Reservation
3.6 Command Processing The following table describes command processing during persistent reservation.
During Persistent Reservation
Table 4: Command Processing During Persistent Reservation
Type of Persistent Reservation
Addressed Logical Unit Held by Another Initiator

Addressed
From Registered From Initiator Not Registered
Command From Any Initiator Logical Unit
Initiator
Reserved
(Registrants Only
by Another
and All Write Exclusive Exclusive Access
Write Exclusive Exclusive Access Registrants Initiatora
Registrants Only Registrants Only
Access Types)
SATA PASSTHROUGH Allowed Allowed Allowed Allowed Allowed Allowed
FORMAT UNIT Conflict Conflict Allowed Conflict Conflict Conflict
INQUIRY Allowed Allowed Allowed Allowed Allowed Allowed
LOG SELECT Conflict Conflict Allowed Conflict Conflict Conflict
LOG SENSE Allowed Allowed Allowed Allowed Allowed Conflict
MODE SELECT (6) Conflict Conflict Allowed Conflict Conflict Conflict
MODE SELECT (10)
MODE SENSE (6) Allowed Conflict Allowed Allowed Conflict Conflict
MODE SENSE (7)
PERSISTENT RESERVATION IN Allowed Allowed Allowed Allowed Allowed Conflict
PERSISTENT RESERVATION OUT See Table 5.
READ (6) Allowed Conflict Allowed Allowed Conflict Conflict
READ (10)
READ BUFFER Allowed Conflict Allowed Allowed Conflict Conflict
READ CAPACITY Allowed Allowed Allowed Allowed Allowed Allowed
READ LONG Conflict Conflict Allowed Conflict Conflict Conflict
REASSIGN BLOCKS Conflict Conflict Allowed Conflict Conflict Conflict
REPORT LUN Allowed Allowed Allowed Allowed Allowed Allowed
REPORT TIMESTAMP Allowed Allowed Allowed Allowed Allowed Allowed
REQUEST SENSE Allowed Allowed Allowed Allowed Allowed Allowed
SECURITY PROTOCOL IN Allowed Conflict Allowed Allowed Conflict Conflict
SECURITY PROTOCOL OUT Conflict Conflict Allowed Conflict Conflict Conflict
SET TIMESTAMP Conflict Conflict Allowed Conflict Conflict Conflict
START/STOP UNIT Allowed Allowed Allowed Allowed Allowed Allowed
START = 1 or
POWER CONDITION = 0
START/STOP UNIT Conflict Conflict Allowed Conflict Conflict Conflict
START = 0 or
POWER CONDITION <> 0
SYNCHRONIZE Conflict Conflict Allowed Conflict Conflict Conflict
CACHE
a. The reservation is not released by the RESERVED/RELEASE method.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Command Processing During
Persistent Reservation
Table 4: Command Processing During Persistent Reservation (Continued)

Addressed
From Registered From Initiator Not Registered
Command From Any Initiator Logical Unit
Initiator
Reserved
(Registrants Only
by Another
and All Write Exclusive Exclusive Access
Write Exclusive Exclusive Access Registrants Initiatora
Registrants Only Registrants Only
Access Types)
TEST UNIT READY Allowed Allowed Allowed Allowed Allowed Conflict
VERIFY (10), (12), (16) Allowed Conflict Allowed Allowed Conflict Conflict
WRITE (6) Conflict Conflict Allowed Conflict Conflict Conflict
WRITE (10)
WRITE AND VERIFY Conflict Conflict Allowed Conflict Conflict Conflict
WRITE BUFFER Conflict Conflict Allowed Conflict Conflict Conflict
WRITE LONG Conflict Conflict Allowed Conflict Conflict Conflict
WRITE SAME Conflict Conflict Allowed Conflict Conflict Conflict
The following table describes PERSISTENT RESERVE OUT service actions allowed in the
presence of various reservations.
Table 5: PERSISTENT RESERVE OUT Service Actions Allowed in the Presence of Various Reservations

Command Service Action Addressed Logical Unit
Command From Registered Command From Unregistered Reserved by Another Initiator a
Initiator Initiator
CLEAR Allowed Conflict Conflict
PREEMPT Allowed Conflict Conflict
PREEMPT and ABORT Allowed Conflict Conflict
REGISTER Allowed Allowed Conflict
REGISTER and IGNORE EXISTING KEY Allowed Allowed Conflict
REGISTER and MOVE Conflict Conflict Conflict
RELEASE Alloweda Conflict Conflict
RESERVE Conflict Conflict Conflict
NOTE: During the firmware upgrade, the LSISS25x0 device maintains the persistent
reservations (use APTPL functionality to write into the nonvolatile memory), but during
firmware downgrade, all the persistent reservations are cleared off.

Chapter 3: Command Processing and Error Handling | Sense Data LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
3.7 Sense Data Sense data is returned as a CHECK CONDITION status (see Section 3.8, SCSI Status Byte)
and as parameter data in response to the REQUEST SENSE command (see Section 4.29,
REQUEST SENSE, on page 101). Sense data returned as a CHECK CONDITION status is
either fixed or in descriptor format sense data based on the value of the D_SENSE bit in
the Control mode page (see Section 5.1.7, Mode Page 0Ah (Control Mode Page
Parameters), on page 152). The REQUEST SENSE command can request either the fixed
format sense data or the descriptor format sense data. The first byte of the sense data
contains the RESPONSE CODE field that indicates the error type and format of the sense
data.
3.7.1 Fixed Format Sense Data The fixed format sense data for response codes 70h (current errors) and 71h (deferred
errors) is defined in the following table.
Table 6: Fixed Format Sense Data for REQUEST SENSE
Bit
Byte
7 6 5 4 3 2 1 0
0 VALID = 0 RESPONSE CODE = 70h or 71h
1 OBSOLETE
2 FILE MARK = 0 EOM = 0 ILI Reserved = 0 SENSE KEY
3:6 INFORMATION
7 ADDITIONAL SENSE LENGTH (N – 7)
8:11 COMMAND SPECIFIC INFORMATION
12 ASC
13 ASC QUALIFIER
14 FIELD REPLACEABLE UNIT CODE
15 SKSV = 0 (MSB)
SENSE KEY SPECIFIC
(LSB)
16:17 SENSE KEY SPECIFIC
18:N ADDITIONAL SENSE BYTES
 VALID bit set to 0 indicates that the INFORMATION field is not defined. A VALID bit
set to 1 indicates the INFORMATION field contains valid information defined by the
command related to the sense data.
 The contents of the RESPONSE CODE field indicate the error type and format of the
sense data. For fixed format sense data, the RESPONSE CODE field is set to 70h or 71h.
 The LSISS2525/LSISS2530 device always returns FILEMARK and EOM fields as 0.
 The INCORRECT LENGTH INDICATION (ILI) bit indicates that the requested data
length (in a READ LONG command or WRITE LONG command) does not match the
length of the logical block.
 The SENSE KEY field, the ADDITIONAL SENSE CODE field, and the ADDITIONAL
SENSE CODE QUALIFIER field provide information relating to the error and
exception conditions.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Sense Data
 The SENSE KEY field indicates generic information describing an error or exception
condition. For a list of the various status codes reported by the
LSISS2525/LSISS2530 device. See Section 3.8, SCSI Status Byte, on page 27.
 The contents of the INFORMATION field are device type or command specific.
 The ADDITIONAL SENSE LENGTH field indicates the number of additional sense
bytes that follow.
 The ADDITIONAL SENSE BYTES carry the additional sense information.
 The COMMAND SPECIFIC INFORMATION field contains information that depends on
the command on which the exception condition occurred.
 To assist in debugging problems, the FIELD REPLACEABLE UNIT CODE field of sense
data that is returned with a check condition is populated with the lower 8 bits of the
Instance ID. This allows easier identification of the particular instance of check
condition being generated from within the LSISS2520/LSISS2530 device firmware.
See Table 259 for the numeric value for the various FRU codes.
3.7.2 Descriptor Format Sense Data The descriptor format sense data for response codes 72h (current errors) and 73h
(deferred errors) is defined in the following table.
Table 7: Descriptor Format Sense Data for REQUEST SENSE
Bit
Byte
7 6 5 4 3 2 1 0
0 RESERVED = 0 RESPONSE CODE = 72h or 73h
1 RESERVED = 0 SENSE KEY
2 ADDITIONAL SENSE CODE
3 ADDITIONAL SENSE CODE QUALIFIER
4:6 RESERVED = 0
7 ADDITIONAL SENSE LENGTH N-7
8 Sense Data Descriptor 0
n Sense Data Descriptor X
 The contents of the RESPONSE CODE field indicate the error type and format of the
sense data. For Descriptor format sense data, the RESPONSE CODE field is set to 72h
or 73h.
 The SENSE KEY field, the ADDITIONAL SENSE CODE field, and the ADDITIONAL
SENSE CODE QUALIFIER field provide information relating to the error and
 The ADDITIONAL SENSE LENGTH field indicates the number of additional sense
bytes that follow.
 Sense data descriptors provide specific sense information.

The following table shows the format of the sense data descriptor format.
Table 8: Sense Data Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
0 DESCRIPTOR TYPE
1 ADDITIONAL LENGTH
2:N Sense Data Descriptor Specific
 The DESCRIPTOR TYPE field identifies the type of sense data descriptor.
 The ADDITIONAL LENGTH field indicates the number of sense data descriptor
specific bytes that follow in the sense data descriptor.
The following descriptor types are supported by the LSISS2520/LSISS2530 device.
3.7.2.1 Information Sense Data The information sense data descriptor provides information that is device type or
Descriptor command specific.
Table 9: Information Sense Data Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
0 DESCRIPTOR TYPE (00H)
1 ADDITIONAL LENGTH (0AH)
2 VALID RESERVED = 0
3 RESERVED = 0
4:11 INFORMATION
The contents of the INFORMATION field are command specific. See Section 4.22, READ
LONG (10), on page 94, Section 4.23, READ LONG (16), on page 95, Section 4.51, WRITE
LONG (10), on page 131, and Section 4.52, WRITE LONG (16), on page 133.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Sense Data
3.7.2.2 Command-Specific The command specific information sense data descriptor provides information that
Information Sense Data Descriptor depends on the command on which the exception condition occurred.
Bit
Byte
7 6 5 4 3 2 1 0
1 ADDITIONAL LENGTH (0AH)
2
RESERVED = 0
3
4:11 COMMAND-SPECIFIC INFORMATION
The COMMAND-SPECIFIC INFORMATION field contains information that depends on

the command on which the exception condition occurred. See Section 4.24, REASSIGN
BLOCK, on page 95.
3.7.2.3 Block Commands Sense The following table shows the block commands sense data descriptor format.
Data Descriptor
Table 10: Block Commands Sense Data Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
1 ADDITIONAL LENGTH (02H)
2 RESERVED = 0
3 RESERVED = 0 ILI RESERVED = 0
The INCORRECT LENGTH INDICATION (ILI) bit indicates that the requested data length
in a READ LONG(10)/(16) command or WRITE LONG(10)/(16) command did not match
the length of the logical block.

3.7.2.4 Progress Indication The progress-specific information sense data descriptor provides progress
Sense Data Descriptor indication data.
Table 11: Progress Indication Sense Data Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
0 DESCRIPTOR TYPE (0AH)
2 SENSE KEY
5 RESERVED = 0
6:7 PROGRESS INDICATION
The PROGRESS INDICATION field indicates a percent completion.
3.7.2.5 ATA Return Sense Data See Section 4.2.3.1, ATA PASS THROUGH Status Return – Descriptor Format Sense Data, on
Descriptor page 47.
3.7.2.6 Field Replaceable Unit The field replaceable unit sense data descriptor provides information about the
Sense Data Descriptor location in the LSISS2520/LSISS2530 firmware where a check condition occurred. See
Table 259 for the numeric value for the various FRU codes. FRU codes are returned with
both fixed and descriptor format sense data.
Table 12: Field Replaceable Unit Sense Data Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
0 DESCRIPTOR TYPE (03h)
1 ADDITIONAL LENGTH (02h)
2 RESERVED
3 Field Replaceable Unit Code
3.7.2.7 Debug Sense Descriptor See Section 3.16, Error Reporting Codes, on page 33.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | SCSI Status Byte
3.8 SCSI Status Byte A SCSI Status Byte is sent to the initiator at the termination of each SCSI command
unless the command is cleared by a Task Management function, such as ABORT TASK
SET or CLEAR TASK SET. The following table shows a description of the status
represented by each Status Byte.
Table 13: Status Bytes
Value Meaning Description

00h GOOD status This status indicates that the target has successfully completed the
command. For this status, Sense data is not valid and the Sense Key
and the ASC are set to 0.
02h CHECK This status indicates that an error, exception, or abnormal condition
CONDITION has caused a sense data with SKey, ASC and ASCQ is sent out with
status this status. See Section F.1, Error Lookup Table for a complete list of
errors returned by the LSISS25x0 device.
04h CONDITION The LSISS2520/LSISS2530 device does not support this status.
MET status
08h BUSY status The LSISS2520/LSISS2530 device does not support this status.
10h INTERMEDIATE/ The LSISS2520/LSISS2530 device does not support this status.
GOOD status
14h INTERMEDIATE/ The LSISS2520/LSISS2530 device does not support this status.
CONDITION
MET status
18h RESERVATION This status indicates that the LUN is reserved for a different initiator
CONFLICT and cannot run the command received from the current initiator.
status
28h QUEUE FULL This status indicates that the target does not have enough resources
status to enter the I/O process into the queue. For this status, Sense data is
not valid and the Sense Key and the ASC are set to 0.
30h ACA ACTIVE The LSISS250/LSISS2530 device does not support this status.
status
40h TASK ABORTED This status is returned when a command or task management
function on another IT_NEXUS or the LSISS250/LSISS2530 device
aborts a command because of an error.
3.9 Priority of SCSI Status Following is the sequence in which the LSISS2520/LSISS2530 device checks the
Reporting conditions that result in a SCSI status other than Good status:
 QUEUE FULL status
 CHECK CONDITION status when the System State Machine is in System Down State
 CHECK CONDITION status for an invalid Logical Unit Number
 CHECK CONDITION status when the Enable First Burst bit in the command frame is set
 CHECK CONDITION status when the maximum number of initiators that can be
supported is exceeded (Insufficient Resource)
 CHECK CONDITION status for an invalid or unsupported command opcode
 CHECK CONDITION status for Unit Attention Condition
 CHECK CONDITION status when the command translates to a SATA command, and
the Device State Machine is in the Device Down state
 CHECK CONDITION status when the command is received during a Format operation

Chapter 3: Command Processing and Error Handling | Unit Attention Condition LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 CHECK CONDITION status when the command is received during a SATA Device
microcode upgrade in progress
 CHECK CONDITION status when the SATA Device startup operation is in progress
 CHECK CONDITION status for Deferred Error Condition
 RESERVATION CONFLICT status because of an existing reservation
 CHECK CONDITION status when the LSISS2520/LSISS2530 device is in Stopped
power condition state
 CHECK CONDITION status when the LSISS2520/LSISS2530 device is in Active_Wait
power condition state
 CHECK CONDITION status when the Self Test is in progress
 CHECK CONDITION status if the LSISS2520/LSISS2530 device is in Format Degraded
Mode and the Report Format Corrupt bit in Mode Page 32h is set
 CHECK CONDITION status when the LU is in Security Locked/Frozen state
 CHECK CONDITION status for invalid command descriptor block
3.10 Unit Attention Condition The LSISS2520/LSISS2530 device generates a unit attention condition whenever one of
the following events occurs:
 A Hard Reset, Logical Unit Reset or I_T NEXUS loss occurs.
 The mode parameters and/or log parameters associated with an I_T NEXUS are
changed by a command received on another I_T NEXUS.
 INQUIRY data is changed.
 When the SATA device State Machine reaches the device DOWN state (ASC/ASCQ =
0x81/0x00). See Section B.1, Device State Machine.
 The LSISS2520/LSISS2530 device restarts after a crash (ASC/ASCQ = 0x29/0x04).
 The LSISS2520/LSISS2530 device cannot bring up the SATA link at the minimum
SATA link speed indicate in the Mode Page 3Ah (ASC/ASCQ = 0x82/0x00).
 The LSISS2520/LSISS2530 device enters device down State because of
incompatibility between the LSISS2520/LSISS2530 device chip revision and the FW
(ASC/ASCQ = 83/0).
 When the LSISS2520/LSISS2530 device enters system-down state (ASC/ASCQ = 81/1).
See Section B.2, System State Machine.
 Disk capacity changes because of change in block descriptor by another I_T NEXUS.
 When the Persistent Reservation from an initiator is preempted.
3.11 Invalid LUN Processing The target's response to an invalid LUN varies according to the command.
The INQUIRY command to an invalid LUN returns INQUIRY data indicating an unknown
device type (byte 0 = 7Fh), and returns GOOD status. All other bytes are valid.
The REQUEST SENSE command returns the sense data with the Sense Key set to
ILLEGAL REQUEST, the ASC/ASCQ set to LOGICAL UNIT NOT SUPPORTED, and returns
GOOD status.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Queue Full Status
All other SCSI commands return a CHECK CONDITION status. The Sense Key is set to
ILLEGAL REQUEST and the ASC/ASCQ is set to LOGICAL UNIT NOT SUPPORTED.
In all cases, the target's response to the command for an invalid LUN does not affect the
current execution of a command on a valid LUN for this initiator or any other initiator.
3.12 Queue Full Status The target responds with QUEUE FULL status to a SCSI command when all queue slots
are utilized.
3.13 Deferred Error Condition The LSISS2520/LSISS2530 device generates SCSI Standard Deferred Error Condition,
which is an error generated by a background operation. The following conditions can
result in background errors:
 Failure of a Start Stop Unit command with the Immediate Bit Set
 Failure of a Format command with the Immediate Bit Set
For both these cases, the Deferred Error is returned for one command received on each
I_T NEXUS. If multiple deferred errors have accumulated for an I_T NEXUS, only the last
error is returned. The LSISS2520/LSISS2530 device does not return deferred errors for
the Inquiry and Report LUNS commands.
3.14 Error Lookup Table The LSISS2520/LSISS2530 device performs Error lookup when it returns a SCSI Status of
Check Condition. The LSISS2520/LSISS2530 firmware maintains the tables of Error
codes and the SCSI Sense Information that is sent out with each of the Error code.
The LSISS2520/LSISS2530 firmware maintains two tables to provide the Error lookup
and override functionality.
 Sense Information table
 Instance Override table
The Error lookup tables are a part of Configuration data.
 Sense Information table
The Sense Information table has the Sense Information (Sense Key, ASC and ASCQ)
that the LSISS2520/LSISS2530 firmware sends out.
The table is divided into two sections:
— Unit Attention Conditions
— Check Conditions with non-unit-attention check conditions
The indices are referred to as error index - ErrorIdx. The ErrorIdx specifies a class of
errors. Each ErrorIdx is associated with an unique combination of Sense Key, ASC
and ASCQ. See Section F.1.2, Sense Information for the default Sense Information
table used by the LSISS2520/LSISS2530 firmware.
Using Configuration data update method, the SenseKey, ASC and ASCQ for a given
class of errors (ErrorIdx) in the Sense Information table could be overridden.
The LSISS2520/LSISS2530 device firmware looks up the Sense Information table for
either the default or overridden ErrorIdx for a given InstId and sends out the
corresponding SenseKey, ASC and ASCQ along with the check condition response.

Chapter 3: Command Processing and Error Handling | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 Instance Override table

The LSISS2520/LSISS2530 device firmware has multiple instances wherein it sends
out the error responses to the initiator, which belongs to the same class of errors.
Each instance is identified by a unique instance Id - InstId. Each InstId is associated
with a unique ErrorIdx in the Sense information table by default.
See Section F.1.3, List of InstIds Occurrences and ErrorIdx Class of Errors for a complete
list of InstIds and the default ErrorIdx's for an LSISS2520/LSISS2530 device.
This default association can be overridden by adding entries in the Instance
Override table.
Each entry of the Instance Override table has two parts: InstId and nondefault
ErrorIdx (the modified ErrorIdx for a given InstId).
The first entry of the Instance Override table is a special entry that contains the
number of entries present in the table. By default, the table contains only this entry.
As the entries get added to the table, the first entry needs to be modified to indicate
the total number of entries in the table.
The following figure depicts the lookup process followed in the LSISS2520/LSISS2530
device firmware.
A lookup is performed errorIdx SKey/ASC/ASCQ

into the Instance Override
table for the InstanceId of If the entry is found errorIdx SKey/ASC/ASCQ
the error condition for the InstId, the
default errorIdx is
InstId overriden by the errorIdx SKey/ASC/ASCQ Skey/ASC/ASCQ
Instld errorIdx
errorIdx in the table sent back to the
LSISS2520/ entry. initiator
LSISS2530 firmware Instld errorIdx errorIdx SKey/ASC/ASCQ
encounters an error
condition. Based
upon the condition, a Instld errorIdx
pair of InstId and
corresponding default Instld errorIdx
errorIdx is generated.
errorIdx
Instance Override Table Sense Information Table
If No entry is
found, the The second lookup is performed
default errorIdx into the Sense Information table
is carried and the corresponding Skey/ASC/
forward as it is. ASCQ is sent back to the initiator
3_00070-00
Figure 2: Lookup Process

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Error Lookup Table
Example:
The following Sense Information can be sent out from multiple commands such as
Mode Sense command and Read Capacity command.
SCSI_SENSE_ILLEGAL_REQUEST
ASC_INVALID_FIELD_IN_CDB
ASCQ_INVALID_FIELD_IN_CDB (5/24/0)
Hence, this combination is identified by the unique ErrorIdx
CC_ERROR_CODE_INV_FIELD_IN_CDB (65) and the instances are identified by the
following InstIds:
INST_MDSNS_CHK_NONZERO_CONTROL_CC_INV_FIELD_IN_CDB(137)
INST_RD_CAPACITY10_CDB_CHK_CC_INV_FIELD_IN_CDB (156)
They all are by default associated with the following ErrorIdx:
CC_ERROR_CODE_INV_FIELD_IN_CDB (65)
To override the sense Information for complete class of this error, the
[errorIdx = CC_ERROR_CODE_INV_FIELD_IN_CDB (65)] entry in the Sense
Information table needs to be modified with the new Sense key/ASC/ASCQ.
To override a specific instance, for example,
INST_MDSNS_CHK_NONZERO_CONTROL_CC_INV_FIELD_IN_CDB), an entry can
also be added to Instance Override table. The following table lists Instance Override
table entry.
Table 14: Instance Override
InstId ErrorIdx
INST_MDSNS_CHK_NONZERO_CONTROL_CC_INV_FIELD_IN_CDB(137) CC_ERROR_CODE_ILLEGAL_REQ_NO_SENSE (64)
Adding the previously mentioned entry in the Instance Override table makes the
LSISS25x0 device send ILLEGAL REQUEST/NO SENSE/NO SENSE when it detects a
nonzero control byte in the mode sense CDB.

Chapter 3: Command Processing and Error Handling | Error Translations LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
3.15 Error Translations The SATA device errors are translated to SCSI errors as shown in the following table. The
LSISS2520/LSISS2530 device uses the SATA status register and Error register to translate
the SATA status to SCSI sense key, ASC and ASC qualifier.
Table 15: Translation of SATA Errors to SCSI Errors
SATA Error SCSI Error
Status Error Sense Key ASC

DF N/A HARDWARE ERROR INTERNAL TARGET FAILURE
ERR NM NOT READY MEDIUM NOT PRESENT
ERR UNC MEDIUM ERROR UNRECOVERED READ ERROR
ERR WP DATA PROTECT WRITE PROTECTED
ERR IDNF ILLEGAL REQUEST LOGICAL BLOCK ADDRESS OUT OF RANGE
ERR ABRT ABORTED COMMAND NO ADDITIONAL SENSE INFORMATION
ERR MC UNIT ATTENTION NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
ERR MCR UNIT ATTENTION OPERATOR MEDIUM REMOVAL REQUEST
ERR ICRC ABORTED COMMAND INFORMATION UNIT CRC ERROR DETECTED
The LSISS25x0 error lookup table provides flexibility to override the sense data
generated by the LSISS25x0 device when the driver encounters the drive error.
The previous table provides the details about the default sense data generated when
the LSISS25x0 device receives an error from the drive for a drive command.
To override a specific drive error, an entry must be added in the Instance Override table.
For example, for an IDNF error from the drive, the LSISS25x0 device generates the
CC_ERROR_CODE_LBA_OUT_OF_RANGE (0x5/0x21/0x0) error code. If the driver needs
the CC_ERROR_CODE_MEDIUM_ERR_RECORD_NOT_FOUND (0x3/0x14/0x1) error code
for the SCSI read command, an entry must be added into the Instance Override table.
Use the following equation to calculate the InstId variable and the errIdx variable
for the entry:
InstId = INST_RD_DRV_ERR_BASE + DRV_ERR_IDNF
See Table 259 for the base address and Table 260 for the address offset for the
following values:
InstId = 466 + 4 = 470 = 0x1D6
Look up the errIdx index of CC_ERROR_CODE_MEDIUM_ERR_RECORD_NOT_FOUND
(0x3/0x14/0x1) from Table 258 for errIdx = 107 = 0x6B.
InstId ErrorIdx
INST_RD_DRV_ERR_BASE + CC_ERROR_CODE_MEDIUM_ERR_RECORD_NOT_FOUND
DRV_ERR_IDNF (0x1D6) (0x6B)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Error Reporting Codes
3.16 Error Reporting Codes When the LSISS25x0 device returns a nonunit attention check condition status, the
device returns the InstId associated with the error occurred in the sense data for the
check condition status if the EnableDebugSenseInformation flag from Mode Page 0x32
Subpage 0x1 is set.
This additional sense information is returned in both fixed format sense data and
descriptor format sense data depending on the setting of D_SENSE bit in control
mode page.
If the D_SENSE bit is cleared, the debug sense information is returned in the following
table format in the additional sense bytes of fixed format sense data.
Table 16: Debug Sense Information
Bit
Byte
7 6 5 4 3 2 1 0
0:1 Instance Id
2 Drive State Machine state
3:5 RESERVED
If the D_SENSE bit in the control mode page is set, the following table depicts the
debug descriptor returned by the LSISS25x0 device.
Table 17: Debug Sense Information Descriptor
Bit
Byte
7 6 5 4 3 2 1 0
0 Descriptor type = 0x80
1 Additional length = 0x6
2:7 Debug information (In the form of Table 16)

Chapter 3: Command Processing and Error Handling | Degraded Mode LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
3.17 Degraded Mode The LSISS2520/LSISS2530 device is designed to be as responsive as possible, but
certain errors or conditions can impair the LSISS2520/LSISS2530 device's ability to
function normally. In most cases, some action by the initiator is used to restore normal
operation. This mode of limited operation is called Degraded Mode.
There are two conditions in the Degraded Mode:
 Format Degraded
This condition occurs when a FORMAT UNIT command fails.
 Stopped
This condition occurs when the LSISS2520/LSISS2530 device is stopped using a
Start Stop Unit command.
Table 18: Format Command Failure Degraded Mode
Command Response
READ (6)/(10)/(12)/(16)/(32), READ LONG (10)/(16), REASSIGN BLOCKS, Not Executed. CHECK CONDITION status is returned with
REQUEST SENSE, VERIFY (10)/(12)/(16)/(32), WRITE(6)/(10)/(12)/(16)/(32), Sense Key 03h (MEDIUM ERROR) ASC/ASCQ 3100h (FORMAT
WRITE LONG (10)/(16), WRITE SAME (10)/(16)/(32), WRITE AND VERIFY CORRUPTED).
(10)/(12)/(16)/(32)
REQUEST SENSE Executed. The target returns Good Status for the Request Sense
command and the Sense data have following information:
Sense Key 03h (MEDIUM ERROR) ASC/ASCQ 3100h (FORMAT
CORRUPTED)
Other Commands Executed.
Table 19: Stop Command Degraded Mode
Command Response
REQUEST SENSE Executed. The target returns Sense Key 02h (NOT READY)
ASC/ASCQ 04 02h (INITIALIZING COMMAND REQUIRED).
INQUIRY, LOG SELECT (except Log Page 0Fh), LOG SENSE (except Log Pages Executed.
0Dh, 0Fh, 10h, 15h, 2Fh and 31h), MDIO ACCESS,
MODE SELECT (6)/(10) (except Mode Pages 01h, 08h, 1Ch, 32h and subpage
01h, 35h and 3Ah), MODE SENSE (6)/(10) (except Mode Pages 0Ah and fetch all
of the Mode Pages), PERSISTENT RESERVE IN/OUT,
READ CAPACITY (10)/(16), RELEASE (6)/(10), REPORT LUNS,
RESERVE (6)/(10) START STOP UNIT (except power condition set to
'Force_Standby_0'), and WRITE BUFFER (except to upgrade device firmware)
START STOP UNIT CHECK CONDITION status with Sense Key set to ILLEGAL
(Force_Standby_0) REQUEST and ASC/ASCQ set to INVALID FIELD IN CDB returned.
Other Commands Not Executed. CHECK CONDITION status is returned with Sense
Key 02h (NOT READY) ASC/ASCQ 04/02h (INITIALIZING
COMMAND REQUIRED).

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Task Management Functions
3.18 Task Management The LSISS2520/LSISS2530 device supports the following Task Management Functions
Functions (TMFs) as defined in the SAM-4 specification.
 Abort Task
 Abort Task Set
 Clear Task Set
 Logical Unit Reset
 I_T Nexus Reset
 Query Task
 Query Task Set
 Query Asynchronous Event
For all these TMFs, if one or more commands to be aborted are active on the SATA
device, then the LSISS2520/LSISS2530 device resets the SATA device. As a result, all
commands active on the device get aborted. For the commands that the TMF does
not intend to abort, one of the following is possible.
— For commands that have data to be transferred to the SATA device and from the
SATA device, and the data transfer has been initiated, the LSISS2520/LSISS2530
device returns a Check Condition status, with Sense Key set to Aborted
command, and ASC/ASCQ set to Command Cleared by Device Server.
— For commands that either do not have data to be transferred to the device and
from the device, or the data transfer has not been initiated, the
LSISS2520/LSISS2530 device resubmits the command to the SATA device.
3.19 Command Priority The LSISS2520/LSISS2530 device complies to the SAT specifications for command
Translation priority translation. SAM-4 command priority supports 16 priorities (0 to 15), whereas
SATA NCQ (Native Command Queuing) only supports two priorities through the
priority bits in the READ FPDMA QUEUED and WRITE FPDMA QUEUED commands. The
LSISS2520/LSISS2530 device translates SAM-4 command priorities to SATA NCQ
priorities as shown in the following table.
Table 20: SCSI Command Priority to SATA NCQ Priority Mapping
SAM-4 Command Priority SATA NCQ Priority

0 0
0 to 3 1
4 to 15 0

Chapter 3: Command Processing and Error Handling | Command Priority Translation LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | INQUIRY
Chapter 4
SCSI Commands
This chapter describes the SCSI commands supported by the LSISS2520/LSISS2530
device. It also describes the translation of SCSI commands.
4.1 INQUIRY This section describes the INQUIRY command.
Table 21: INQUIRY CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 12h
1 RESERVED OBSOLETE VPD
2 PAGE CODE
3:4 ALLOCATION LENGTH
5 CONTROL
The LSISS2520/LSISS2530 device follows SPC4 for the INQUIRY command.

The INQUIRY command requests the following target parameters to be sent to the
initiator.
 VPD
This bit set to 1 specifies that the LSISS2520/LSISS2530 device returns the vital
product data page identified by the PAGE CODE field in the CDB. When the VPD bit
is set to 0, the LSISS2520/LSISS2530 device returns the standard INQUIRY data.
 PAGE CODE
This field specifies the page of vital product data information that the
LSISS2520/LSISS2530 device returns.
Table 22: Supported VPD PAGE CODEs
VPD PAGE Code Description

0 0 The LSISS2520/LSISS2530 device returns the standard INQUIRY data.
0 Nonzero The LSISS2520/LSISS2530 device returns the CHECK CONDITION status with the Sense Key of Illegal Request and
the ASC of the Invalid Field in the CDB.
1 Supported The LSISS2520/LSISS2530 device returns the vital product data of page code requested.
1 Unsupported The LSISS2520/LSISS2530 device returns the CHECK CONDITION status with the Sense Key of Illegal Request and
the ASC of the Invalid Field in the CDB.

Chapter 4: SCSI Commands | INQUIRY LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 ALLOCATION LENGTH
This field specifies the number of bytes that the initiator has allocated for INQUIRY
data to be returned. An ALLOCATION LENGTH of 0 implies that no data is to be
returned. The LSISS2520/LSISS2530 device transfers all available INQUIRY data or
the amount specified in the allocation length field, whichever is less.
NOTE: Standard INQUIRY data and VPD Pages use the saved Identify Device Data and
do not directly translate to a SATA IDENTIFY_DEVICE command where the
LSISS2520/LSISS2530 device has a valid saved Identify Device Data. That is, the
LSISS2520/LSISS2530 device has received a valid Identify Device Data from a SATA
device at least once. The INQUIRY command response is generated by using the saved
values. See Default Inquiry Response Data when the LSISS2520/LSISS2530 device does
not have a valid saved Identify Device Data. That is, the device has never received a valid
Identify Device Data from a SATA device.
If an INQUIRY command is received from an initiator with a pending unit attention

condition (before the target reports CHECK CONDITION status), the
LSISS2520/LSISS2530 device processes the INQUIRY command. The unit attention
condition is not cleared by this action.
4.1.1 Inquiry Data The character fields are alphanumeric and are represented in ASCII.
This section describes the Standard Inquiry Data Format.
Table 23: Standard Inquiry Data Format
Bit
Byte
7 6 5 4 3 2 1 0
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE
1 RMB = 0 RESERVED
2 VERSION
3 OBSOLETE OBSOLETE NormACA = 0 HiSup = 0 RESPONSE DATA FORMAT = 2
4 ADDITIONAL LENGTH = 9Fh
5 SCCS = 0 ACC = 0 TPGS = 00 3PC = 0 RESERVED PROTECT
6 BQUE = 0 ENC-SERV = 0 VS MULTIP = 1 OBSOLETE OBSOLETE OBSOLETE Addr16 = 0
7 OBSOLETE OBSOLETE WBUS16 = 0 SYNC = 0 LINKED = 0 OBSOLETE CMDQUE = 1 PORTNUM
8:15 T10 VENDOR IDENTIFICATION
16:31 ASCII PRODUCT IDENTIFIER
32:35 ASCII Product Revision Level
36:43 SATA DEVICE SERIAL NUMBER
44:55 RESERVED
56 RESERVED CLOCKING = 0 QAS = 0 IUS = 0
57 RESERVED
58:59 VERSION Descriptor 1
:

Table 23: Standard Inquiry Data Format (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
72:73 VERSION Descriptor 8
74:104 RESERVED
105 DEVICE STATE MACHINE STATE
106:163 RESERVED
In accordance with SBC-3, for all the commands, except INQUIRY and REQUEST SENSE, a
CHECK CONDITION is returned if an invalid LUN is specified.
 PERIPHERAL QUALIFIER
This field is set to 0 to indicate that the LUN specified in the Command Block is
supported. PERIPHERAL QUALIFIER is set to 011b when the LUN specified in the
Command Block is not present.
 PERIPHERAL DEVICE TYPE
This field is set to 0 to indicate that the device is a direct access. PERIPHERAL DEVICE
TYPE is set to 1Fh when the LUN specified in the Command Block is not present.
 Removal Media Bit (RMB)
This bit is always set to 0 and indicates that no removal media exists.
 Hierarchical support (HISUP)
This bit set to 0 indicates the SCSI target device does not use the hierarchical
addressing model to assign LUNS to logical units by the LSISS2520/LSISS2530 device.
 RESPONSE DATA FORMAT
This field is set to two to indicate that the INQUIRY Data Format as specified in the
ANSI SCSI Standard is supported by the LSISS2520/LSISS2530 device.
 ADDITIONAL LENGTH
This field indicates the number of bytes of INQUIRY information.
 SCCS
This bit set to 1 indicates the target device is embedded storage controller array
support. The LSISS2520/LSISS2530 device sets this bit to 0, because this bit does not
support embedded storage controller array support.
 ACC
This bit set to 0 indicates that the no access control coordinator is addressed
through this logical unit. The LSISS2520/LSISS2530 device sets this bit to 0.
 TPGS
This field is set to 0 and Groups are not supported by the LSISS2520/LSISS2530 device.

 3PC
Extended Copy command is not supported. The LSISS2520/LSISS2530 device does
not support this field.
 Protect
When this bit is set to 0, the LSISS2520/LSISS2530 device does not support
protection information. If set to 1, the LSISS2520/LSISS2530 device supports Type 1,
Type 2, and Type 3 protection.
 BQUE and CMDQUE
The LSISS2520/LSISS2530 device supports the Basic Task Management model, as
the following table shows.
Table 24: BQUE and CMDQUE Definitions
BQUE CMDQUE Description

0 0 Obsolete
1 0 Full task management model supported
0 1 Basic task management model supported
1 1 Illegal combination of BQUE and CMDQUE bits
 EncSerV (Enclosure Services)

This bit is set to 1 to indicate that the Target can provide access to an Enclosure
Services Device, which executes the SCSI-3 Enclosure Services (SES) command set.
The LSISS2520/LSISS2530 device sets this bit to 0.
 MULTIP (MultiPort)
This bit is set to 1 to indicate that the Target is a dual-ported device.
 Addr16 (Wide SCSI Address 16)
This bit is set to 0 to indicate that the Target does not support 16-bit wide SCSI
Addresses.
 WBUS16
This bit is set to 0 to indicate that the LSISS2520/LSISS2530 device does not support
16-bit wide data transfers.
 LINKED
This bit is set to 0 to indicate that the LSISS2520/LSISS2530 device does not support
linked commands.
 T10 VENDOR IDENTIFICATION
This field contains eight bytes of left-aligned ASCII data, identifying the vendor of
the product. This field sets to ATA, which indicates that this is SCSI/ATA translator
firmware.

 PRODUCT IDENTIFICATION
This field contains 16 bytes of left-aligned ASCII data. This field represents the first
16 bytes of the Model number field of the SATA device.
 PRODUCT REVISION LEVEL
This field contains four bytes of left-aligned ASCII data defined by the vendor. This
field represents the Firmware revision field of SATA device. Refer to the SAT
specifications for more information.
 VERSION DESCRIPTOR
These fields provide for identifying up to eight standards to which the SCSI target
device claims conformance.
The standards supported are as follows.
VERSION Descriptor Standard Name

0x0060 SAM-3
0x1EC0 SAT-2
0x0300 SPC3
0x0400 SBC
0x0C00 SAS 1.1
0x0C20 SAS 2.0
0x1600 SATA /ATAPI 7
0x1623 SATA/ATAPI-8 ATA8-ACS SATA/ATAPI Command Set
 DEVICE STATE MACHINE STATE

This field returns the Device state.
The Device states are defined as follows:
Device State Value

SSD1 – SATA_DRIVE_INIT 1
SSD2 – SATA_DRIVE_RDY 2
SSD3 – SATA_DRIVE_RESET 3
SSD4 – SATA_DRIVE_DOWN 4
SSD5 – SATA_WAITING_FOR_SPINUP_REQUEST 5
For details on Device State Machine, see Section B.1, Device State Machine.

4.1.2 Default Inquiry Response Data The following is the default inquiry response data that is returned when the
LSISS2520/LSISS2530 device does not detect the SATA device.
If the LSISS2520/LSISS2530 device detects the SATA device, the inquiry response data
defined in section Section 4.1.1, Inquiry Data is returned.
The following table lists the default inquiry response data format for standard inquiry
command.
Table 25: Default Inquiry Response Data Format for Standard Inquiry Command
Bit
Byte
7 6 5 4 3 2 1 0
1 RMB = 0 RESERVED
2 VERSION
3 OBSOLETE OBSOLETE NORMACA = 0 HISUP = 0 RESPONSE DATA FORMAT = 2
4 ADDITIONAL LENGTH = 9Fh
6 BQUE = 0 ENC-SERV = 0 VS MULTIP = 1 OBSOLETE OBSOLETE OBSOLETE ADDR16 = 0
16:31 ASCII PRODUCT IDENTIFIER = 0
32:35 ASCII PRODUCT REVISION LEVEL = 0

36:43 SATA DEVICE SERIAL NUMBER = 0
44:55 RESERVED
56 RESERVED CLOCKING = 0 QAS = 0 IUS = 0
57 RESERVED
58:59 VERSION DESCRIPTOR 1
:
74:104 RESERVED
106:163 RESERVED
For the field description, see Section 4.1.1, Inquiry Data.

4.1.3 Fake Inquiry Response Data Fake inquiry data is the inquiry data response that is returned when the
LSISS2520/LSISS2530 device has not yet received Identify Device Data (IDD) from the
SATA drive since it restarted. Fake inquiry data is returned only if the Offline Drive
Change feature is enabled.
If Offline Drive Change feature is not enabled, Stale inquiry data (that is, Inquiry Data that
is present in the nonvolatile memory) is returned until IDD is received from the drive.
The following table shows the fake inquiry response data format for standard inquiry
command.
Table 26: Fake Inquiry Response Data Format for Standard Inquiry Command
Bit
Byte
7 6 5 4 3 2 1 0
1 RMB = 0 RESERVED
2 VERSION
3 OBSOLETE OBSOLETE NORMACA = 0 HISUP = 0 RESPONSE DATA FORMAT = 2
4 ADDITIONAL LENGTH = 9FH
6 BQUE = 0 ENC-SERV = 0 VS MULTIP = 1 OBSOLETE OBSOLETE OBSOLETE ADDR16 = 0
16:31 ASCII PRODUCT IDENTIFIER (ASCII BLANKS)
32P:35 ASCII PRODUCT REVISION LEVEL (ASCII BLANKS)
36:43 DRIVE SERIAL NUMBER (ASCII BLANKS)
44:55 RESERVED
56 RESERVED = 0 CLOCKING = 0 QAS = 0 IUS = 0
57 RESERVED
:
74:95 RESERVED
96:104 SIGNATURE = LSISS25X0
106:163 RESERVED
 SIGNATURE
The signature field when set to the LSISS2520/LSISS2530 device states that this inquiry
data is Fake Inquiry data.
For the other field description, see Section 4.1.1, Inquiry Data.

Chapter 4: SCSI Commands | SATA PASS THROUGH Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.2 SATA PASS THROUGH SATA PASS THROUGH commands provide a method for the following scenarios:
Commands
 An application client to transmit a SATA command to a SATA device
 Transferring data between an application client and a SATA device (optionally)
 A SATA device to transfer completion status through the LSISS2520/LSISS2530 device.
4.2.1 ATA PASS THROUGH (12) The following table lists the ATA PASS THROUGH (12) commands.
Table 27: ATA PASS THROUGH (12) CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE (A1H)
1 MULTIPLE_COUNT PROTOCOL RESERVED
2 OFF_LINE CK_COND RESERVED T_DIR BYTE_BLOCK T_LENGTH
3 FEATURES (7:0)
4 SECTOR_COUNT (7:0)
5 LBA_LOW (7:0)
6 LBA_MID (7:0)
7 LBA_HIGH (7:0)
8 DEVICE
9 COMMAND
10 RESERVED
11 CONTROL
The Protocol field can contain one of the following values:
Table 28: Protocol Field Definitions
Protocol Description
0 SATA Hardware Reset
1:2 Reserved
3 Nondata
4 PIO Data In
5 PIO Data Out
6 DMA
7 DMA Queued
8 Device Diagnostic
9 Reserved
10 UDMA Data In
11 UDMA Data Out

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SATA PASS THROUGH Commands
Table 28: Protocol Field Definitions (Continued)
Protocol Description
12 FPDMA
13, 14 Reserved
15 SATA Return Response
NOTE: LSISS25x0 does not support the value of the Protocol field when it is set to 15.
 If the MULTIPLE_COUNT field is nonzero and the command field is not a READ
MULTIPLE command, a READ MULTIPLE EXT command, a WRITE MULTIPLE
command, a WRITE MULTIPLE EXT command, or a WRITE MULTIPLE FUA EXT
command, then the LSISS2520/LSISS2530 device terminates the command with
CHECK CONDITION status with the SENSE KEY set to ILLEGAL REQUEST and the ASC
set to INVALID FIELD in CDB. Currently, the LSISS2520/LSISS2530 device does not
implement the functionality related to this field.
 The OFF_LINE field specifies the time period during which the SATA Status register
and the SATA Alternate Status register is invalid after command acceptance. This
field must be set to 0.
 If the CK_COND bit is set to 1, the LSISS2520/LSISS2530 device reports Check
Condition status regardless of the completion status of the command and returns
the ATA Normal Output fields in the sense data.
 If the CK_COND bit is set to 0, the LSISS2520/LSISS2530 device reports Check
Condition status for the error responses only.
 T_DIR bit indicates the Data transfer direction.
— T_DIR bit set to 0 – Data transfers from the LSISS2520/LSISS2530 device to device.
— T_DIR bit set to 1 – Data transfers from device to the LSISS2520/LSISS2530 device.
 The BYTE BLOCK field specifies the type of data in the T-LENGTH field.
— If the BYTE_BLOCK is set to 0, the T_LENGTH refers to the number of bytes
transferred to or from the SATA device.
— If the BYTE_BLOCK is set to 1, the T_LENGTH specifies the number of blocks to
be transferred to or from SATA device.

 T_LENGTH fields specify the field that has the TRANSFER LENGTH of the data. The
following table indicates the information of the T_LENGTH field.
 DEVICE bit is set to 1 or 0 depending on the device number. The LSISS2520/LSISS2530
device has only one device, hence the DEVICE bit does not mean anything.
Table 29: T_LENGTH Field Description
T_LENGTH Description
00 No Data transfer occurs.
01 The transfer length is an unsigned integer specified in the FEATURES (7:0) field.
10 The transfer length is an unsigned integer specified in the SECTOR_COUNT (7:0) field.
11 The transfer length is an unsigned integer specified in the TPSIU (Transport
Protocol-Specific Information Unit).
Not supported in the LSISS2520/LSISS2530 device.
NOTE: LSISS25x0 cache commands such as ATA Pass, which bypass normal LSISS25x0
command handling, caches some drive parameters and updates the cached drive
parameter by causing discrepancy in the LSISS25x0 cache. This action results in
incorrect parameter values sent during normal command execution. You can
synchronize LSISS25x0 cache only by restarting the LSISS25x0 device.
The LSISS25x0 device does not support the following ATA commands with ATA
PASS-THROUGH commands and the behavior is unspecified:
 READ DMA QUEUED
 READ DMA QUEUED EXT
 WRITE DMA QUEUED
 WRITE DMA QUEUED EXT
 WRITE DMA QUEUED FUA EXT
4.2.2 ATA PASS THROUGH (16) This section lists the ATA PASS THROUGH (16) commands.
Table 30: ATA PASS THROUGH (16) CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE (85h)
1 MULTIPLE_COUNT Protocol Extend
2 OFF_LINE CK_COND RESERVED T_DIR BYTE_BLOCK T_LENGTH
3 FEATURES (15:8)
4 FEATURES (7:0)
7 LBA_LOW (15:8)

Table 30: ATA PASS THROUGH (16) CDB (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
8 LBA_LOW (7:0)
9 LBA_MID (15:8)
10 LBA_MID (7:0)
11 LBA_HIGH (15:8)
12 LBA_HIGH (7:0)
13 DEVICE
14 COMMAND
15 CONTROL
 If the EXTEND bit is set to 0, ignore the FEATURES (15:8) field, the SECTOR_COUNT
(15:8) field, the LBA_LOW (15:8) field, the LBA_MID (15:8) field, and the LBA_HIGH
(15:8) field. The LSISS2520/LSISS2530 device sends a 28-bit address to the device.
 If the EXTEND bit is set to 1, then the FEATURES (15:8) field, the SECTOR_COUNT (15:8)
field, the LBA_LOW(15:8) field, the LBA_MID (15:8) field, and the LBA_HIGH (15:8) field
are valid, the LSISS2520/LSISS2530 device sends a 48-bit address to the device.
For the rest of the fields, see Section 4.2.1, ATA PASS THROUGH (12).
4.2.3 ATA PASS THROUGH Status When the CK_COND bit is set in the ATA PASS THROUGH CDB, or when the ATA
Return command completes with an error, the LSISS2520/LSISS2530 device terminates the
command with a CHECK CONDITION status and returns the ATA register information in
the sense data either in descriptor or fixed format, depending on the D_SENSE bit of
Control Mode page.
For descriptor format sense data, the ATA Status Return Descriptor is returned.
4.2.3.1 ATA PASS THROUGH Each time the ATA Return descriptor is returned, the LSISS2520/LSISS2530 device
Status Return – Descriptor Format returns the ATA registers in the sense data. If the sense data is for an ATA PASS
Sense Data
THROUGH (12) command or for the ATA PASS THROUGH (16) command with the
EXTEND bit set to 0, the LSISS2520/LSISS2530 device returns the 28-bit extended status
and sets the EXTEND bit to 0. If the sense data is for an ATA PASS-THROUGH (16)
command with the EXTEND bit set to 1, the LSISS2520/LSISS2530 device returns the
48-bit extended status and sets the EXTEND bit to 1.

The following table shows the ATA Return Descriptor format.
Table 31: ATA Return Descriptor Format
Bit
Byte
7 6 5 4 3 2 1 0
0 DESCRIPTOR CODE (09h)
1 ADDITIONAL DESCRIPTOR LENGTH (0Ch)
2 RESERVED EXTEND
3 ERROR
6 LBA_LOW (15:8)
7 LBA_LOW (7:0)
8 LBA_MID (15:8)
9 LBA_MID (7:0)
10 LBA_HIGH (15:8)
11 LBA_HIGH (7:0)
12 DEVICE
13 STATUS
4.2.3.2 ATA PASS-THROUGH The following table shows the fields returned in the fixed format sense data for the ATA
Status Return – Fixed Format Sense PASS-THROUGH commands.
Data
Table 32: Fixed Format Sense Data Fields for ATA PASS-THROUGH Commands
Bit
Byte
7 6 5 4 3 2 1 0
0 VALID = 0 RESPONSE CODE = 70h or 71h
1 OBSOLETE
2 FILE MARK = 0 EOM = 0 ILI = 0 RESERVED SENSE KEY
INFORMATION
3 ERROR
4 STATUS
5 DEVICE
6 SECTOR COUNT (7:0)
7 ADDITIONAL LENGTH (N – 7)
COMMAND SPECIFIC INFORMATION
8 EXTEND SECTOR COUNT LBA UPPER RESERVED LOG INDEX
NONZERO NONZERO
9 LBA_HIGH (7:0)
10 LBA_MID (7:0)

Table 32: Fixed Format Sense Data Fields for ATA PASS-THROUGH Commands (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
11 LBA_LOW (7:0)
12 ASC
13 ASC QUALIFIER
14 FIELD REPLACEABLE UNIT CODE = 0
15 SKSV = 0 MSB
SENSE KEY SPECIFIC = 0
LSB
16:17 SENSE KEY SPECIFIC
18:N ADDITIONAL SENSE BYTES
 An EXTEND bit set to 1 indicates that the sense data is for an ATA
PASS-THROUGH (16) command with the EXTEND bit set to 1.
 An EXTEND bit set to 0 indicates that the sense data is for an ATA
PASS-THROUGH (16) command with the EXTEND bit set to 0, or for an ATA
PASS-THROUGH (12) command.
 If the EXTEND bit is set to 1, the SECTOR_COUNT (15:8) field, the LBA_LOW (15:8)
field, the LBA_MID (15:8) field, and the LBA_HIGH (15:8) field cannot be returned in
fixed format sense data.
 If the LBA UPPER NONZERO bit is set to 1, one or more of the LBA_LOW (15:8) field,
the LBA_MID (15:8) field, and the LBA_HIGH (15:8) field returned by the SATA device
are not set to 00h. If the LBA UPPER NONZERO bit is set to 0, the LBA_LOW (15:8)
field, the LBA_MID (15:8) field, and the LBA_HIGH (15:8) field returned by the SATA
device are set to 00h.
 If the SECTOR_COUNT UPPER NONZERO bit is set to 1, the SECTOR_COUNT (15:8)
field returned by the SATA device is not set to 00h. If the SECTOR_COUNT UPPER
NONZERO bit is set to 0, the SECTOR_COUNT (15:8) field returned by the SATA
device is set to 00h.

Chapter 4: SCSI Commands | FORMAT UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.3 FORMAT UNIT This section lists the FORMAT UNIT commands.
Table 33: FORMAT UNIT CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE = 04h
1 FMTPINFO LONGLIST = 0 FMTDATA CMPLST = 0 DEFECT LIST FORMAT
2 VENDOR SPECIFIC
3:4 (MSB)
OBSOLETE
(LSB)
5 CONTROL
The FORMAT UNIT command performs a physical formatting of the

LSISS2520/LSISS2530 device media, which includes handling of defective sectors and
the overwriting of all data areas with a constant data pattern.
 FMTDATA
This field set to 1 specifies that a Format Unit Parameter List (which includes defect
list-DList) is supplied by the Initiator. FmtData set to 0 specifies that no Parameter
List is transferred.
 CMPLST
This bit set to 1 specifies that the defect list sent by the initiator is a complete list of
defects. Any existing defect list except the PLIST is ignored by the
LSISS2520/LSISS2530 device. This bit set to 0 specifies that the defect list sent by the
initiator is used in addition to the existing list of defects.
NOTE: The LSISS2520/LSISS2530 device does not support PLIST or GLIST.
 FMTPINFO (Format Protection Information)

This field, in combination with the PROTECTION FIELD USAGE field (see Table 34),
specifies whether to use protection information. If this field is set to a nonzero
value, then the FMTDATA field must be set to 1. Refer to the SBC-3 specification for
details.
NOTE: The SPT field is set to 0x7 for the LSISS2520/LSISS2530 device.
 LONGLIST
This bit set to 0 specifies that the parameter list, if any, contains a short parameter
list header as defined in the following table. A LONGLIST bit set to 1 specifies that
the parameter list, if any, contains a long parameter list header. Set this field to 0 for
the LSISS2520/LSISS2530 device.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | FORMAT UNIT
The following table lists the Parameter List Header format.
Table 34: Short Parameter List Header
Bit
Byte
7 6 5 4 3 2 1 0
0 RESERVED PROTECTION FIELD USAGE
1 FOV = 0 DPRY = 0 DCRT = 0 STPF = 0 IP = 0 OBSOLETE IMMED VENDOR
SPECIFIC
2:3 (MSB)
DEFECT LIST LENGTH
(LSB)
 PROTECTION FIELD USAGE

This field in combination with the FMTPINFO field specifies the requested
protection type. Refer to the SBC-3 specification for details.
NOTE: The SPT field is set to 0x7 for the LSISS2520/LSISS2530 device.
 FOV
This bit set to 1 specifies that the LSISS2520/LSISS2530 device examines the setting
of the DPRY, DCRT, STPF, and IP bits.
This bit set to 0 specifies that the LSISS2520/LSISS2530 device uses its default
settings for the DPRY, DCRT, STPF, and IP bits.
 DPRY
This bit is ignored by the LSISS2520/LSISS2530 device.
The LSISS2520/LSISS2530 device does not support PLIST.
The LSISS2520/LSISS2530 device does not support CLIST.
 IMMED (Immediate)
This bit set to 0 requests that status be returned at the end of the format operation.
An immediate bit set to 1 requests that status be returned immediately. GOOD
status is returned following CDB validation and the successful transfer and
validation of any Dlist supplied by the initiator. If the immediate format operation
terminates in error, Deferred Error sense data is generated.
 IP (Initialization Pattern)
This bit set to 0 specifies that an initialization pattern descriptor is not included and
that the LSISS2520/LSISS2530 device uses its default initialization pattern. An IP bit
set to 1 specifies that an initialization pattern descriptor is included in the FORMAT
UNIT parameter list following the parameter list header. Set the FOV bit to 1 when
the IP bit is set to 1.

 STPF (Stop format)

This bit controls the behavior of the LSISS2520/LSISS2530 device if one of the
following events occurs:
— The LSISS2520/LSISS2530 device is requested to use the PLIST and the
LSISS2520/LSISS2530 device is neither able to locate the list nor determine
whether the list exists.
— The LSISS2520/LSISS2530 device has been requested to use the PLIST, and the
LSISS2520/LSISS2530 device encounters an error while accessing the defect list.
The LSISS2520/LSISS2530 device does not support the STPF bit. Set this field to 0 for
4.3.1 Initialization Pattern The initialization pattern descriptor specifies that the LSISS2520/LSISS2530 device
Descriptor initializes logical blocks to a specified pattern, as shown in the following figure. The
initialization pattern descriptor is sent to the device server as a part of the FORMAT
UNIT parameter list.
Table 35: Initialization Pattern Descriptor
Bit
Byte
7 6 5 4 3 2 1 0
0 IP Modifier SI RESERVED
1 Initialization Pattern Type
(MSB)
2:3 Initialization Pattern Length (n-3)
(LSB)
4:n Initialization Pattern

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | FORMAT UNIT
 Initialization Pattern Modifier (IP Modifier)

The IP Modifier field specifies the type and location of a header that modifies the
initialization pattern, as shown in the following figure.
Table 36: IP Modifier Field
Code Description
00b No header. The LSISS2520/LSISS2530 device does not modify the initialization
pattern.
01b The LSISS2520/LSISS2530 device overwrites the initialization pattern to write
the LBA in the first four bytes of each logical block. The LBA is written with the
most significant byte first. If the LBA is more than four bytes, the least significant
four bytes are written ending with the least significant byte. The
LSISS2520/LSISS2530 device does not support the IP Modifier field set to 01b.
10b The LSISS2520/LSISS2530 overwrites the initialization pattern to write the LBA
in the first four bytes of each physical block contained within the logical block.
The lowest numbered logical block (or its part) that occurs within the physical
block is used. The LBA is written with the most significant byte first. If the LBA is
more than four bytes, the least significant four bytes are written ending with the
least significant byte. The LSISS2520/LSISS2530 device does not support the IP
Modifier field set to 10b.
11b Reserved
If the Initialization Pattern Modifier field is not set to 0, the LSISS2520/LSISS2530

device terminates the command with the CHECK CONDITION status with the sense
key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.
 Security Initialize (SI)
The SI bit set to 0 specifies that the LSISS2520/LSISS2530 device initializes the
application client accessible part of the medium. The SI bit set to 1 specifies that the
LSISS2520/LSISS2530 device attempts to write the initialization pattern to all areas
of the medium, including those that may have been reassigned (that is, are in a
defect list). The LSISS2520/LSISS2530 device does not support the SI bit set to 1. If
the SI field is not set to 0, the LSISS2520/LSISS2530 device terminates the command
with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the
Additional Sense Code set to INVALID FIELD IN PARAMETER LIST.

 Initialization Pattern Type

The Initialization Pattern Type field specifies the type of pattern that the
LSISS2520/LSISS2530 device uses to initialize each logical block within the
application client accessible part of the medium. All bytes within a logical block are
written with the initialization pattern.
Table 37: Initialization Pattern Type field
Code Description
00h Use a default initialization pattern.
NOTE: If the INITIALIZATION PATTERN LENGTH field is not set to 0, the

LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION
status with the sense key set to ILLEGAL REQUEST and the additional sense code
set to INVALID FIELD IN PARAMETER LIST.
01h Repeat the pattern specified in the Initialization Pattern field as required to fill
the logical block.
NOTE: If the INITIALIZATION PATTERN LENGTH field is set to 0, the

LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION
status with the sense key set to ILLEGAL REQUEST and the additional sense code
set to INVALID FIELD IN PARAMETER LIST.
02h to FFh Reserved
 Initialization Pattern Length

The Initialization Pattern Length field specifies the number of bytes contained in the
Initialization Pattern field. If the initialization pattern length exceeds the current
logical block length, the LSISS2520/LSISS2530 device terminates the command
with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.
 Initialization Pattern
The Initialization Pattern field specifies the initialization pattern.
4.3.2 Sending WRITE FPDMA As part of the FORMAT UNIT operation, the LSISS2520/LSISS2530 device writes 0s or the
QUEUED Commands Initialization Pattern to the entire device. The LSISS2520/LSISS2530 device sends a
series of WRITE FPDMA QUEUED commands by using the LSISS2520/LSISS2530 device’s
WRITE SAME hardware acceleration support to initialize the entire disk. This entire
operation takes minutes or hours, depending upon the size of the disk. If the initiator
sets the IMMED bit to 1, then it receives the response immediately upon the target's
receipt of the command. If the initiator sets the IMMED bit to 0, then the
LSISS2520/LSISS2530 device waits for the FORMAT operation to complete and then
transmits the SCSI response.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | LOG SELECT
This command supports the variable command time-out feature. See Mode Page 32h
(Firmware Parameter Control). The equation used for time-out calculation is: Time out
Value = (TRANSFER LENGTH / 32) + command time-out specified in Mode page 0x01h.
NOTE: Currently, the LSISS2520/LSISS2530 device does not support the Initialization
Pattern, and it uses a zero pattern implicitly.
4.4 LOG SELECT The LOG SELECT command lets the initiator manage statistical information maintained
by the LSISS2520/LSISS2530 device and report through the LOG SENSE command. The
LOG SELECT command provides for sending 0 or more log pages through the Data-Out
Buffer. The LSISS2520/LSISS2530 device does not support sending more than one log
page through the Data-Out buffer.
Table 38: LOG Select CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 4Ch
1 RESERVED PCR SP
2 PC RESERVED
3:6 RESERVED
7:8 (MSB)
PARAMETER LIST LENGTH
(LSB)
9 CONTROL
 PCR (PARAMETER CODE Reset)

This field determines whether the Log Parameters are to be cleared and the unit
attention posted for all other initiators. A value of 1 indicates that the parameters
are cleared, and a value of 0 (except when PC = 11b) indicates that the parameters
are not cleared. If this bit is set to 1, then the PARAMETER LIST LENGTH field must be
set to 0.
 SP (Save Parameters)
This bit set to 0 indicates that the page parameters are not saved. A value of 1
indicates that the parameters that are savable are saved after they have been
changed.
 PC (Page Control)
This field defines the type of parameters to be selected. This field must be set to
either 01b (cumulative values) or 11b (default cumulative values). The PC field set to
11b (and PCR is then a do not care) or the PC field set to 01b and PCR set to 1
indicates that the Current Cumulative values are set to their default values of 0. If
this field is set to 11b, then the PARAMETER LIST LENGTH field must be set to 0.

Chapter 4: SCSI Commands | LOG SELECT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 PARAMETER LIST LENGTH

This field indicates the amount of data to be transferred from the initiator to the
LSISS2520/LSISS2530 device. The PARAMETER LIST LENGTH must not be greater
than 0x500 and must not truncate any of the log data.
If one or more fields of the CDB are not set correctly, the command is terminated with a
CHECK CONDITION status. The Sense Key is set to Illegal Request and the ASC is set to
Invalid Field in CDB.
The LSISS2520/LSISS2530 device allows updates to the Start Stop Cycle (0Eh),
Application Client (0Fh), LSISS2520/LSISS2530 Device Temperature (33h), Version (35h),
and NV Scratch (36h) log pages only. If the Data-Out buffer contains multiple log
parameters within a log page, then the data is sent in an ascending order by the
PARAMETER CODE value. Otherwise the LOG SELECT command is terminated with a
CHECK CONDITION status. The Sense Key is set to Illegal Request and the ASC is set to
INVALID FIELD IN PARAMETER LIST.
The LSISS2520/LSISS2530 device generates a Unit Attention Condition, to indicate
that parameters have changed, for all initiators except the one that issued the
LOG SELECT command.
The log parameters within following log pages are set to their default value of zero in
response to the LOG SELECT command with the PCR bit set to 1 or PC set to 11b
(PARAMETER LIST LENGTH is set to 0 in both the cases):
 Write Error Counter log page (02h)
 Read Error Counter log page (03h)
 Verify Error Counter log page (05h)
 Non Medium Error log page (06h)
 LSISS2520/LSISS2530 device Firmware Statistics log page (37h)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | LOG SENSE
4.5 LOG SENSE This section describes the LOG SENSE command.
Table 39: LOG SENSE CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 4Dh
1 RESERVED PPC = 0 SP
2 PC PAGE CODE
3 SUBPAGE CODE
4 RESERVED
5:6 (MSB)
PARAMETER POINTER
(LSB)
7:8 (MSB)
ALLOCATION LENGTH
(LSB)
9 CONTROL
The LOG SENSE command allows the initiator to retrieve statistical data or operational
information about the LSISS2520/LSISS2530 device.
 PPC (Parameter Pointer Control)
This field must be set to 0.
 SP (Save Parameters)
This bit set to 0 specifies that the LSISS2520/LSISS2530 device does not save any log
parameters.
If this bit is set to 1, all page parameters that are savable (those pages denoted by a
DS = 0 in the parameter control byte) are saved.
 PC (Page Control)
This field defines the type of parameters to be selected. This field must be set to 01b
to specify the cumulative values.
If this bit is set to any other value, then the command is terminated with a CHECK
CONDITION status with a SENSE KEY set to ILLEGAL REQUEST and the ASC set to
INVALID FIELD in CDB.
 PAGE CODE
This field identifies which page is being requested. This field must be set to the
values indicated in Page 0. If the PAGE CODE value is invalid, a CHECK CONDITION
status is returned with a SENSE KEY of ILLEGAL REQUEST and ASC of INVALID Field
IN CDB.

Chapter 4: SCSI Commands | LOG SENSE LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 BIT 7 OF SUBPAGE
This field set to 0 specifies that the LSISS2520/LSISS2530 device returns the
requested log page and does not clear counters within the requested log page.
If this field is set to 1, the LSISS2520/LSISS2530 device returns the requested log
page and clears the counters within the requested log page. If the
LSISS2520/LSISS2530 device does not support the clear operation for a particular
log page and the bit 7 of the SUBPAGE field is set to 1, then the command is
terminated with CHECK CONDITION status, with SENSE KEY set to ILLEGAL
REQUEST, and the ASC set to INVALID FIELD in CDB.
 PARAMETER POINTER
This field specifies the beginning field for the transfer. If the value of the PARAMETER
POINTER field is larger than the largest available PARAMETER CODE known to the
SCSI target device for the specified log page, the command terminates with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the ASC set to
INVALID FIELD IN CDB. PARAMETER POINTER is 0 for the LSISS2520/LSISS2530
device. This field must be set to 0 if the page code is not 0Fh.
This field specifies the maximum number of bytes the initiator has allocated for
returned LOG SENSE data. No bytes are transferred if the length is 0. This condition
is not considered an error.
Each log page begins with a four-byte page header followed by 0 or more
variable-length log parameters, as listed in the following table.
Table 40: LOG PAGE Parameters Format
Bit
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE
1 RESERVED
2:3 (MSB)
PAGE LENGTH (N-3)
(LSB)
— LOG PARAMETERS
4 LOG PARAMETER (FIRST)
LENGTH (X)
x+3 —
— —
— —
N-y+1 LOG PARAMETER (LAST)
LENGTH (Y)
N —

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | LOG SENSE
Table 41: LOG PARAMETER Description
Bit
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE
(LSB)
2 DU DS TSD ETC TMC LBIN LP
3 PARAMETER LENGTH (N-3)
4:N PARAMETER VALUE
 PAGE CODE
This field identifies which log page is being transferred.
 PAGE LENGTH
This field specifies the length in bytes of the following log parameters.
Each log parameter begins with a four-byte parameter header followed by one or
more bytes of parameter value data.
 PARAMETER CODE
This field identifies which log parameter is being transferred for that log page.
Parameter Control field, the third byte of each parameter header, contains several
fields.
— DU (Disable Update) bit is set to 0, which indicates that the LSISS2520/LSISS2530
device updates the log parameter value to reflect events that the parameter notes.
— DS (Disable Save) bit is set to 1 to indicate the parameter is non-savable and is
set to 0 to indicate the parameter is savable.
— TSD (Target Save Disable) bit is set to 0, which indicates the
LSISS2520/LSISS2530 device provides a target defined method for saving log
parameters.
— ETC (Enable Threshold Comparison) bit is set to 0 to indicate that the
LSISS2520/LSISS2530 device does not perform any comparison.
— TMC (Threshold Met Criteria) is not valid and is set to 0.
— LBIN (List Binary) bit is only valid if the LP bit is set to 1. If the LP bit is set to 1 and
the LBIN bit set to 0, then the list parameter is ASCII data. If the LP bit is set to 1
and the LBIN bit set to 1, then the list parameter is binary data.
— LP (List Parameter) bit set to 0 indicates that the parameter is a data counter.
And if set to 1, indicates that the parameter is a list parameter.
For the definition of the supported log pages, See Section 5.2, Log Parameters.

Chapter 4: SCSI Commands | LOG SENSE LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The LSISS2520/LSISS2530 device supports the following Log page codes:
Table 42: PAGE CODE Usage
Support by
Read Clear
Page Description LSISS2520/LSISS2
Support
530 Device
00h List of Supported Page Yes No
02h Write Error Counter Yes Yes
03h Read Error Counter Yes Yes
05h Verify Error Counter Yes Yes
06h Non-Medium Errors Yes Yes
0Dh Temperature Yes No
0Eh Start Stop Cycle Counters Yes No
0Fh Application Client Log Yes No
10h Self-Test Results Yes No
15h Background Scan Results Yes No
18h Protocol-Specific Port Yes No
2Fh Informational Exceptions Yes No
30h Device Errors Yes Yes
31h SMART Data Yes No
32h Systems Statistics Yes Yes
33h LSISS2520/LSISS2530 Device Temperature Yes No
34h LSISS2520/LSISS2530 Device Log Page Yes Yes
35h Versions Page Yes No
36h NV Scratch Page Yes No
37h LSISS2520/LSISS2530 Device Firmware Statistics Yes Yes
If a LOG SENSE to any of the Log Pages 30h, 32h and 37h with Read-Clear is requested,
then the following counters within these Log Pages are cleared with the other counters
within the Log Page specified in the LOG SENSE CDB.
 Log Page 30h counters
— Receive Error Count
— Transmit Error Count
— Link Down Count
— Disparity Error Count
— Invalid DWORD Count
— Loss of DWORD Sync Count
— Speed Negotiation Error Count

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | MDIO ACCESS COMMAND
 Log Page 32h counters

— Number of PHY Resets (SATA)
— Number of Disparity Errors (SATA PHY)
— Number of CRC Errors (SATA PHY)
 Log Page 37h counter: Read Log Ext-10 Count
4.6 MDIO ACCESS COMMAND This vendor-specific command allows an initiator to read/write the EyeFinder™ registers
in the LSISS2520/LSISS2530 device by using the same Operation Code.
Table 43: MDIO ACCESS Parameters Format
Bit
Byte
7 6 5 4 3 2 1 0
0 Operation Code (C0h)
1 RESERVED FW Enable Device Type Direction
2:3 RESERVED
4:5 (MSB)
EyeFinder Register Address
(LSB)
6:9 (MSB)
Write Data
(LSB)
 Set the Direction bit to indicate a write access. Clear the bit to indicate a read access.
 Set the Device Type bit to indicate the SATA EyeFinder register must be used. Clear
the bit to indicate the SAS EyeFinder register.
 The FW Enable bit indicates that firmware may use the internal MDIO interface to
access the EyeFinder register. Set this bit for all regular MDIO Access commands.
When the initiator is done sending the MDIO Access commands, it must send one
more command with the FW Enable bit cleared to return the control to external
MDIO interface.
 The EyeFinder Register Address field is the offset of the EyeFinder register. It is a
16-bit value that is also 4-byte-aligned, which means the least significant 2 bits of
the address must always be 0.
 The Write Data field indicates what the initiator wants to write to the EyeFinder
register. This field is only valid when the Direction bit is set.
When the LSISS2520/LSISS2530 device receives the MDIO Access command, it must call
the appropriate MDIO interface functions accordingly.

Chapter 4: SCSI Commands | MDIO ACCESS COMMAND LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.6.1 I/O Flow The following diagram show the typical I/O flow when the MDIO Access command is
used to plot eye diagrams. The host starts by sending the MDIO Access commands,
with each field filled out appropriately. The host EyeFinder application can access the
EyeFinder registers thousands of times to establish the statistical eye. At the end of the
session, the host sends one last MDIO Access command with the FW Enable bit cleared.
This result allows the firmware to return the control of EyeFinder registers back to the
external MDIO interface.
Host Driver/ LSISS2520/LSISS2530

Initiator SAS-SATA Bridge
MDIO Access Command
MDIO Access Reply
The host/initiator
. LSISS2520/LSISS2530
. SAS-SATA Bridge
sends as many MDIO
firmware calls the MDIO
Access commands . interface functions to
as necessary, all with . access the EyeFinder
FW Enable bit set.
. registers.
.
.
. LSISS2520/LSISS2530
The host/initiator shall MDIO Access Command SAS-SATA Bridge
send one last MDIO firmware returns the
Access command with control of EyeFinder
the FW Enable bit registers back to the
cleared. MDIO Access Reply external MDIO
interface.
Figure 3: Typical I/O Flow

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | MDIO ACCESS RESPONSE
4.7 MDIO ACCESS RESPONSE For MDIO write access, the LSISS2520/LSISS2530 device sets the DATAPRES field in the
response frame to 00b (No data) and replies with good SCSI status.
For MDIO read access, the LSISS2520/LSISS2530 device sets the DATAPRES field in the
response frame to 10b (sense data present), Sense Data Length to 6, and returns the
Read Data in the Sense Data field with good SCSI status. The following table shows the
sense data format for an MDIO read access.
Table 44: Sense Data Format
Bit
Byte
7 6 5 4 3 2 1 0
0 Vendor Specific Response Code (7Fh)
1 RESERVED
2:5 (MSB)
Read Data
(LSB)
4.8 MODE SELECT (6) This section describes the MODE SELECT (6) command.
Table 45: MODE SELECT (6) CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED PF RESERVED SP
2:3 RESERVED
4 PARAMETER LIST LENGTH
5 CONTROL
The MODE SELECT (6) command lets the initiator specify device parameters to the
Target. It also allows an initiator specify options the Target uses.
A single set of Mode Page parameters is shared by all initiators.
 PF
A page format (PF) bit set to 0 specifies that all parameters after the block
descriptors are vendor specific. A PF bit set to 1 specifies that the MODE SELECT
parameters following the header and block descriptors are structured as pages of
related parameters and are as defined in this standard.

Chapter 4: SCSI Commands | MODE SELECT (6) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 SP
This field is Save pages, as shown in the following table.
Table 46: SP Setting Descriptions
Field Description
0 The LSISS2520/LSISS2530 device does not save the pages sent by the initiator, but
uses them until the power is removed. A reset is received or an overriding MODE
SELECT command is received.
1 The LSISS2520/LSISS2530 device performs the specified MODE SELECT operation,
and saves to a nonvolatile vendor-specific location all the savable mode pages.

This specifies the number of bytes to be sent from the initiator. A PARAMETER LIST
LENGTH of 0 transfers no data and is not considered an error.
The MODE SELECT parameter list contains a four-byte header, followed by a 0 block
descriptor or a 1 block descriptor, followed by 0 or more pages. See Section 5.1,
Mode Parameters.
Application Note:
The initiator issues a MODE SENSE command requesting all changeable values prior to
issuing a MODE SELECT command. This action is necessary to find out which pages are
implemented by the LSISS2520/LSISS2530 device and the length of those pages. The
LSISS2520/LSISS2530 device returns, in the pages of the MODE SENSE command, the
number of bytes supported for each Page. The PAGE LENGTH set by the initiator in the
MODE SELECT command must be the exact value as that returned by the
LSISS2520/LSISS2530 device in MODE SENSE PAGE LENGTH. If the length differs, then
the LSISS2520/LSISS2530 device returns a CHECK CONDITION status with the Sense Key
of Illegal Request.
Mode parameters do not get restored back to the older values if the setting value of
later mode parameters are present in multiparameter page/multipage mode select
case fails. In this case, mode select returns a CHECK CONDITION with an appropriate
Sense key, ASC and ASCQ.
NOTE: If an initiator sends a MODE SELECT command that changes any parameters that
apply to other initiators, the LSISS2520/LSISS2530 device generates a unit attention
condition for all initiators except the one that issues the MODE SELECT command. The
LSISS2520/LSISS2530 device sets the ASC to PARAMETERS CHANGED. The initiator pulls
the changeable values and changes only those bits allowed to be changed. If any bits
change that are not changeable, then a CC with ASC INVALID FIELD and PARAMETER
LIST is generated.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | MODE SELECT (10)
4.9 MODE SELECT (10) This section describes the MODE SELECT (10) command.
Table 47: MODE SELECT 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED PF RESERVED SP
2:6 RESERVED
7:8 (MSB)
(LSB)
9 CONTROL
The MODE SELECT (10) command lets the initiator specify device parameters to the
Target. For the definition of fields, see Section 4.8, MODE SELECT (6).
4.10 MODE SENSE (6) This section describes the MODE SENSE (6) command.
Table 48: MODE SENSE 6 CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 1Ah
1 RESERVED DBD RESERVED
2 PCF PAGE CODE
3 SUBPAGECODE
4 ALLOCATION LENGTH
5 CONTROL
The MODE SENSE (6) command lets the LSISS2520/LSISS2530 device report various
device parameters to the initiator. It complements the MODE SELECT command.
 DBD
If (Disable Block Descriptor) bit is 0, the target returns the Block Descriptor. If the
DBD bit is set to 1, the target does not return the Block Descriptor.
This field indicates the maximum number of bytes the initiator has set aside for the
mode page data associated with this command. A value of 0 is not considered an
error. If the allocation length is smaller than the number of bytes of data that the
Target has available to send to the initiator, then that portion of the data up to the
allocation length is sent. This action results in only a portion of a multibyte field
being sent.

Chapter 4: SCSI Commands | MODE SENSE (6) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 PCF (Page CONTROL Field)

This field defines the type of Mode Page Parameter values to be returned. The PCF
values are listed in the following table.
Table 49: PCF (Page CONTROL Field) Values
PCF Values Description

0 0 Report current values. The LSISS2520/LSISS2530 device returns the current
values for the logical unit as presently configured for the page code specified.
The current values returned are as follows:
• The parameters set in the last successful MODE SELECT command.
• The saved values if a MODE SELECT command has not been executed since
the last poweron or TARGET RESET message.
0 1 Report changeable values. The LSISS2520/LSISS2530 device returns the
changeable values for the page code specified. The page requested is returned
with information that indicates which fields are changeable. The bits for
parameters that are changeable are set to 1. Parameters that are not
changeable are set to 0. If any part of a field is changeable, all bits in that field
are set to 1.
1 0 Report default values. The LSISS2520/LSISS2530 device returns the default
values for the page code specified.
1 1 Report saved values. The LSISS2520/LSISS2530 device returns the saved values
for the page code specified. Saved values are one of the following:
• Values saved as a result of MODE SELECT command with SP set
• Identical to the default values
 PAGE CODE
This field specifies which page or pages are to be returned. See the following table
for the page codes and their descriptions.
Table 50: PAGE CODE
PAGE CODE SUBPAGE CODE Description

00h NA Vendor Unique Parameters (Supported mode pages)
01h NA Read-Write Error Recovery mode page
02h NA Disconnect/Reconnect Control Parameters mode page
07h NA Verify Error Recovery mode page
08h NA Caching Parameters mode page
0Ah 00h Control mode page
0Ah 01h Control Extension mode page
0Ah FFh Return main page and all the subpages of mode page 0Ah
18h 00h Protocol-specific LUN mode page
19h 00h Protocol-specific port mode page
19h 01h PHY control and discover mode page
19h 02h Shared port control mode page
19h 03h SAS2PHY mode page

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | MODE SENSE (10)
Table 50: PAGE CODE (Continued)
PAGE CODE SUBPAGE CODE Description

19h FFh Return main page and all the subpages of mode page 19h
1Ch NA Informational Exceptions Control mode page
25h NA Logging Configuration Parameters mode page
32h NA Firmware Parameter Control mode page
33h NA Sector Skewing Support Parameter mode page
34h NA SATA Link Configuration mode page
35h NA SATA Queuing and Error Recovery mode page
36h NA SAS Link Configuration mode page
37h NA Firmware Debug mode page
39h 00h SAS PHY Control mode page
39h 01h SATA PHY Control mode page
39h FFh Return main page and all the subpages of mode page 39h
3Fh 00h Return all supported pages by the LSISS2520/LSISS2530
device
(Only the main pages)
3Fh FFh Return all supported pages by the LSISS2520/LSISS2530
device
(Including the subpages)
Any other Any other Invalid combination of page code and subpage code
page code subpage code
NOTE: In Mode Sense 6 with Page code 0x3F, the LSISS2520/LSISS2530 device returns
the standard mode pages and does not return the vendor-specific mode pages. It is
advised to use Mode Sense 10 to obtain all the LSISS2520/LSISS2530 mode pages,
including standards and the vendor-specific mode page.
For the definition of the supported mode pages, see Mode Page 00h (Supported Mode
pages).
4.11 MODE SENSE (10) The following table lists the MODE SENSE (10) command.
Table 51: MODE SENSE 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED LLBAA DBD RESERVED
2 PCF PAGE CODE
3 SUBPAGE CODE

Chapter 4: SCSI Commands | PERSISTENT RESERVE IN LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 51: MODE SENSE 10 CDB (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
4:6 RESERVED
7:8 (MSB)
ALLOCATION LENGTH
(LSB)
9 CONTROL
The MODE SENSE (10) command lets the LSISS2520/LSISS2530 device report various
device parameters to the initiator.
 If the Long LBA Accepted (LLBAA) bit is set to 1, the LSISS2520/LSISS2530 device
may return parameter data with the LONGLBA bit equal to 1. If the LLBAA bit is set
to 0, the LONGLBA bit is set to 0 in the parameter data returned by the
LSISS2520/LSISS2530 device, followed by any short LBA format block descriptor.
See Section 4.10, MODE SENSE (6) for description of the fields in this command.
4.12 PERSISTENT RESERVE IN This section lists the PERSISTENT RESERVE IN commands.
Table 52: PERSISTENT RESERVE IN CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 5Eh
1 RESERVED SERVICE ACTION
2:6 RESERVED
7:8 (MSB)
ALLOCATION LENGTH
(LSB)
9 CONTROL
The PERSISTENT RESERVE IN command obtains information about persistent

reservations and reservation keys that are active within the LSISS2520/LSISS2530 device.
This command is used in conjunction with the PERSISTENT RESERVE OUT command.
The PERSISTENT RESERVATION IN command does not conflict with a reservation
established by the PERSISTENT RESERVATION OUT command.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE IN
4.12.1 PERSISTENT RESERVE IN The following table lists the supported service action codes. If a reserved service action
SERVICE ACTION code is specified, the LSISS2520/LSISS2530 device returns a CHECK CONDITION status.
The SENSE KEY is set to Illegal Request and the Additional Sense data is set to INVALID
Field in CDB.
Table 53: PERSISTENT RESERVE IN SERVICE ACTION Codes
Support in
Code Name Description
LSISS2520/LSISS2530 Device
00h Read Keys Reads all registered Reservation Yes
Keys.
01h Read Reservations Reads all current persistent Yes
reservations
02h Report Capabilities Returns capability information Yes
03h Read Full Status Reads complete information about Yes
any registrations and persistent
reservations
04 to 1Fh Reserved Reserved No
4.12.2 PERSISTENT RESERVE IN This section lists the PERSISTENT RESERVE IN parameter data.
PARAMETER DATA FOR READ KEYS
Table 54: PERSISTENT RESERVE IN Parameter Data for Read Keys
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
PRGENERATION
(LSB)
4:7 (MSB)
ADDITIONAL LENGTH (N-7)
(LSB)
8:15 (MSB)
FIRST RESERVATION KEY
(LSB)
: :
n-7|:N (MSB)
LAST RESERVATION KEY
(LSB)
The LSISS2520/LSISS2530 device supports this type of service action.

 GENERATION
The Generation counter increments when a PERSISTENT RESERVATION OUT
command with a service action code of Register, Register and Ignore Existing Key, or
Preempt and Abort completes successfully. The Generation counter is set to 0 as
part of the power-on reset process and the hard reset process.
 ADDITIONAL LENGTH
This field contains the count of number of bytes in the Reservation key list.
 Reservation Keys
The reservation key list contains the 8-byte reservation keys for all I_T NEXUS
commands that have been registered.
4.12.3 PERSISTENT RESERVE IN The following table describes the PERSISTENT RESERVE IN PARAMETER DATA FOR READ
PARAMETER DATA FOR READ RESERVATIONS command.
RESERVATIONS
Table 55: PERSISTENT RESERVE IN PARAMETER DATA FOR READ RESERVATIONS
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
PRGENERATION
(LSB)
4:7 (MSB)
ADDITIONAL LENGTH (n-7)
(LSB)
8:n (MSB)
RESERVATION DESCRIPTORS
(LSB)
The LSISS2520/LSISS2530 device supports this type of service action.

When there is no persistent reservation held, the ADDITIONAL LENGTH field is set to 0
and there are no RESERVATION DESCRIPTORS.

When a persistent reservation is held, see the following table for the
Reservation Descriptor format.
Table 56: PERSISTENT RESERVE IN READ RESERVATIONS DESCRIPTOR
Bit
Byte
7 6 5 4 3 2 1 0
0:7 (MSB)
RESERVATION KEY
(LSB)
8:11 (MSB)
OBSOLETE
(LSB)
12 RESERVED
13 SCOPE = 0 TYPE
14:15 OBSOLETE = 0
 RESERVATION KEY
The reservation key field specifies the reservation key of the Persistent reservation
holder. If the Persistent reservation is of All Registrants access types (Exclusive
access - All Registrants or Write exclusive access All Registrants), the Reservation Key
is set to 0.
 SCOPE
The scope field is set to 0h (LU_SCOPE), which indicates that Persistent reservation
applies to the full logical unit.
 TYPE
The type field specifies the characteristics of the persistent reservation being
established for all logical blocks within the logical unit.
4.12.4 REPORT CAPABILITIES SERVICE The following table describes the REPORT CAPABILITIES SERVICE ACTION command.
ACTION
Table 57: PERSISTENT RESERVE IN Parameter Data for REPORT CAPABILITIES
Bit
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
LENGTH (08h)
(LSB)
2 RESERVED CRH (0h) SIP_C (0h) ATP_C (0h) RESERVED PTPL_C (1h)

Table 57: PERSISTENT RESERVE IN Parameter Data for REPORT CAPABILITIES (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
3 TMV(1h) ALLOWED COMMAND (000h) RESERVED PTPL_A (1h)
4:5 (MSB)
PERSISTENT RESERVATION TYPE MASK
(LSB)
6:7 RESERVED
The LSISS2520/LSISS2530 device supports this service action.

 Compatible Reservation Handling (CRH)
A compatible reservation handling (CRH) bit set to 1 indicates that the device server
supports the exceptions to the SPC-2 RESERVE and RELEASE commands.
The LSISS2520/LSISS2530 device does not support the RESERVE/RELEASE
commands and hence sets the CRH bit to 0.
 Specify Initiator Ports Capable (SIP_C)
This bit indicates whether the device server supports the SPEC_I_PT bit in the
PERSISTENT RESERVE OUT command parameter data. The LSISS2520/LSISS2530
device does not support this bit and hence sets it to 0h.
 ALLOWED COMMANDS
The allowed commands field indicates if certain commands are allowed through
certain types of persistent reservations. The LSISS2520/LSISS2530 device supports a
value of 000b, which indicates that no additional information is provided.
 All Target Ports Capable (ATP_C)
This bit indicates that the device server supports the ALL_TG_PT bit in the
PERSISTENT RESERVE OUT command parameter data. The LSISS2520/LSISS2530
device does not support this bit and hence sets it to 0h.
 Persist Through Power Loss Capable (PTPL_C)
This bit indicates that the device server supports persist through power loss
capability for persistent reservations and the APTPL bit in the PERSISTENT RESERVE
OUT command parameter data. The LSISS2520/LSISS2530 device supports this bit
and hence sets it to 1h.
 Persist Through Power Loss Active (PTPL_A)
This bit indicates that the device server has activated the persist through power loss
feature. A value of 1 indicates the feature is active. A value of 0 indicates the feature
is not active.
 Type Mask Valid (TMV)
This bit indicates that the PERSISTENT RESERVATION TYPE MASK field contains a
bitmap indicating the persistent reservation types that the device server supports.
A TMV bit set to 0 indicates ignoring the PERSISTENT RESERVATION TYPE MASK field.

 PERSISTENT RESERVATION TYPE MASK

The LSISS2520/LSISS2530 device sets the following bits in the bitmap:
— Write Exclusive – All Registrants (WR_EX_AR)
— Exclusive Access – All Registrants (EX_AC_AR)
— Exclusive Access – Registrants Only (EX_AC_RO)
— Write Exclusive – Registrants Only (WR_EX_RO)
— Exclusive Access (EX_AC)
— Write Exclusive (WR_EX)
4.12.5 READ FULL STATUS SERVICE The READ FULL STATUS SERVICE ACTION requests that the device server return a
ACTION parameter list that describes the registration and persistent reservation status of each
currently registered I_T NEXUS for the logical unit, as the following table shows.
Table 58: PERSISTENT RESERVE IN PARAMETER DATA FOR READ FULL STATUS
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
PRGENERATION
(LSB)
4:7 (MSB)
ADDITIONAL LENGTH (n-7)
(LSB)
8 FIRST FULL STATUS DESCRIPTOR
: :
N LAST FULL STATUS DESCRIPTOR
The LSISS2520/LSISS2530 device supports this service action.

The format of the full status descriptors is shown in the following table.
Table 59: READ FULL STATUS DESCRIPTOR Format
Bit
Byte
7 6 5 4 3 2 1 0
0-7 (MSB)
RESERVATION KEY
(LSB)
8:11 RESERVED
12 RESERVED ALL_TG_PT R_HOLDER
13 Scope TYPE
18:19 RELATIVE TARGET PORT IDENTIFIER
20:23 ADDITIONAL DESCRIPTOR LENGTH (n-23)
24:n TRANSPORT ID

 All Target Ports (ALL_TG_PT)

All targets ports set to 0 indicates that this status descriptor represents a single I_T
NEXUS. The LSISS2520/LSISS2530 device sets this bit to 0.
 Reservation Holder (R_Holder)
A Reservation Holder bit set to 1 indicates that all I_T NEXUSs described by this full
status descriptor are registered and are persistent reservation holders. A
Reservation Holder bit set to 0 indicates that all I_T NEXUSs described by this full
status descriptor are registered but are not persistent reservation holders.
 RELATIVE TARGET PORT IDENTIFIER
The Relative Target Port Identifier contains the relative port identifier of the target
port that is part of the I_T NEXUS described by this full status descriptor.
 TRANSPORT ID
The Transport ID contains information by identifying the initiator port that is part of
the I_T NEXUSs described by this full status descriptor. The following table shows
the format of the Transport ID.
Table 60: Transport ID (Format)
Bit
Byte
7 6 5 4 3 2 1 0
0 FORMAT CODE (00B) RESERVED PROTOCOL IDENTIFIER (6h)
1:3 RESERVED
4:11 SAS ADDRESS
12:23 RESERVED
 FORMAT CODE
This is a reserved field and is set to 00b.
 PROTOCOL IDENTIFIER
This field specifies the SCSI transport protocol to which this transport ID applies. For
the LSISS2520/LSISS2530 device, this value is 6h. This value represents the
SAS protocol.
 SAS ADDRESS
This field specifies the SAS address of the initiator port.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT
4.13 PERSISTENT RESERVE The PERSISTENT RESERVE OUT command requests service actions that reserve a logical
OUT unit for the exclusive use or shared use of a particular I_T NEXUS. The command uses
other service actions to manage and remove such persistent reservations. The
command is used in conjunction with the PERSISTENT RESERVE IN command and is not
used with the Reserve and Release commands.
Table 61: PERSISTENT RESERVE OUT
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 5Fh
1 RESERVED SERVICE ACTION
2 SCOPE TYPE
3:6 RESERVED
7:8 (MSB)
(LSB)
9 CONTROL
4.13.1 SERVICE ACTION The following table describes the supported SERVICE ACTION Codes. If an action code
that is not supported or a reserved service action code is specified, the
LSISS2520/LSISS2530 device returns a CHECK CONDITION status. The SENSE KEY is set
to Illegal Request and the Additional Sense data is set to INVALID Field in CDB.
Table 62: Persistent Reservation Out Service Action Codes
Support in LSISS2520/LSISS2530
Device
00h Register Register a reservation key with the target Yes
01h Reserve Create a Persistent Reservation by using a reservation key Yes
02h Release Release a Persistent Reservation Yes
03h Clear Clear all reservation keys and all Persistent Reservations Yes
04h Preempt Preempt Persistent Reservations from another initiator Yes
05h Preempt and Abort Preempt Persistent Reservations from another initiator and Yes
abort task set for preempted initiator.
06h Register and Ignore Existing Key Register a reservation key with the target Yes
07h Register and Move Creates the new registration and Moves the persistent Yes
reservation to specified I_T NEXUS.
08h to 1Fh RESERVED Reserved —

Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 Register
The REGISTER service action could be used to register a key with LSISS25x0, Change
the existing registration key from an initiator or un-register a key from the initiator.
If the ReservationKey from the PERSISTENT RESERVE OUT - REGISTER parameter list
(Table 65) is set to 0, LSISS25x0 assumes it is a new registration request and
performs the registration. If the same key is already found registered on the same
port, LSISS25x0 returns RESERVATION CONFLICT status else, the initiator gets
registered successfully.
If the ReservationKey from the PERSISTENT RESERVE OUT - REGISTER parameter list
(Table 65) is set to nonzero value, the LSISS25x0 device assumes the registration key
change request is for an existing registrant. If the same key is not found registered,
the LSISS25x0 device returns a RESERVATION CONFLICT status. Otherwise, the key
update is performed or the initiator gets unregistered.
The LSISS2520/LSISS2530 device can hold up to four keys at the same time. When
four keys are registered, a PERSISTENT RESERVATION OUT command with a Register
service action (that does not replace an existing key or unregister) is rejected with a
CHECK CONDITION status with the sense key set to INSUFFICIENT REGISTRATION
RESOURCES status. When a PERSISTENT RESERVATION OUT command with a
Register service action completes successfully, increment the Generation counter.
If the APTL bit is set, the LSISS2520/LSISS2530 device ensures that the registration
details are stored to nonvolatile memory and can be retrieved when the
LSISS2520/LSISS2530 device comes up after a power loss.
 Reserve
The PERSISTENT RESERVATION OUT command with a Reserve service action is used
to establish a PERSISTENT RESERVATION from a registered initiator.
The PERSISTENT RESERVATION OUT command with a Reserve service action is
rejected with a status of RESERVATION CONFLICT if the initiator requesting the
command has not previously performed a Register service action. If a key specified
in the Reservation key field is already registered but the initiator which registered
the key is different from the initiator requesting the command, the
LSISS2520/LSISS2530 device returns a RESERVATION CONFLICT status.
If a new PERSISTENT RESERVATION conflicts with a previously established
PERSISTENT RESERVATION, the LSISS2520/LSISS2530 device returns a RESERVATION
CONFLICT status.
The established PERSISTENT RESERVATION applies to all commands received after
the successful completion of the command.

 Release
The PERSISTENT RESERVATION OUT command with a Release service action is
primarily used to release an existing persistent reservation. PERSISTENT
RESERVATION OUT command with a release service action is rejected with a status
of RESERVATION CONFLICT if the initiator requesting the command has not
previously performed a Register service action. If a key specified in the Reservation
key field is already registered but the initiator which registered the key is different
from the initiator requesting the command, the LSISS2520/LSISS2530 device
returns a RESERVATION CONFLICT status. GOOD status is returned when a key
specified in Reservation key field is not found.
When the key is found but the scope is different from the registered scope or the
type is different from the registered type, a CHECK CONDITION status is returned.
The Sense Key is set to Illegal Request and the Additional Sense data is set to
INVALID RELEASE OF ACTIVE PERSISTENT RESERVATION.
 Preempt
The PERSISTENT RESERVATION OUT command with a Preempt service action is
primarily used to preempt the Reservation/Registration from the initiator pointed
by the SERVICE ACTION RESERVATION KEY.
PERSISTENT RESERVATION OUT command with a Preempt service action is rejected
with a status of RESERVATION CONFLICT if the initiator requesting the command
has not previously performed a Register service action. If a key specified in the
Reservation key field is already registered but the initiator which registered the key
is different from the initiator requesting the command, the LSISS2520/LSISS2530
device returns a RESERVATION CONFLICT status.
When an initiator is preempted, UNIT ATTENTION CONDITION is reported to the
initiator, which was preempted. The Sense Key is set to UNIT ATTENTION and the
additional sense data is set to RESERVATION PREEMPTED. When a PERSISTENT
RESERVATION OUT command with a Preempt service action completes successfully,
the Generation counter is incremented.
The commands received from the initiator being preempted before processing
persistent RESERVE OUT-PREEMPT command are processed under the purview of
the older reservations and the commands received afterwards results in
RESERVATION CONFLICT. This depends on the type of new reservation once
established successfully.
 Preempt and Abort
The PERSISTENT RESERVATION OUT command with a Preempt and abort service
action is primarily used to preempt the Reservation/Registration from the initiator
pointed by the SERVICE ACTION RESERVATION KEY and abort all the ongoing tasks
from the same initiator. PERSISTENT RESERVATION OUT command with a Preempt
and Abort service action is rejected with a status of RESERVATION CONFLICT if the
initiator requesting the command has not previously performed a Register service
action. If a key specified in the Reservation key field is already registered but the
initiator which registered the key is different from the initiator requesting the
command, the LSISS2520/LSISS2530 device returns a RESERVATION CONFLICT status.

When an initiator is preempted, UNIT ATTENTION CONDITION is reported to the

initiator, which was preempted. The Sense Key is set to UNIT ATTENTION and the
additional sense data is set to RESERVATION PREEMPTED. When a PERSISTENT
RESERVATION OUT command with a Preempt and Abort service action completes
successfully, the Generation counter is incremented.
The commands received from the initiator being preempted before processing the
PERSISTENT RESERVE OUT-PREEMPT AND ABORT command and pending with the
LSISS2520/LSISS2530 device are check conditioned with sense key set to ABORTED
COMMAND and the commands received later results in RESERVATION CONFLICT
depending on the type of new reservation if gets established successfully.
 Clear
The PERSISTENT RESERVATION OUT command with a Clear service action is
primarily used to clear the registrations and Reservations if any wilt. PERSISTENT
RESERVATION OUT command with a Clear service action is rejected with a status of
RESERVATION CONFLICT if the initiator requesting the command has not previously
Registered.
When a Registered Initiator requests for a Clear service action, the
LSISS2520/LSISS2530 device clears all the Registrations and Reservations associated
with it. A UNIT ATTENTION CONDITION is reported to the initiator. The initiator’s
registrations/reservations are cleared because of the Clear service action, with the
exception of the initiator that has sent out the PERSISTENT RESERVE OUT command
with CLEAR service action. The Sense Key is set to UNIT ATTENTION and the
additional sense data is set to RESERVATION PREEMPTED.
When a PERSISTENT RESERVATION OUT command with a CLEAR service action
completes successfully, increment the Generation counter.
 Register and Ignore Existing Key
An initiator establishes a registration without regard for whether one has previously
been established by issuing a PERSISTENT RESERVE OUT command.
If a PERSISTENT RESERVE OUT with a Register and Ignore Existing Key service action
is sent when an established registration key exists, the registration supersedes with
the specified SERVICE ACTION RESERVATION KEY. If a PERSISTENT RESERVE OUT with
a Register and Ignore Existing Key service action is sent when there is no
established registration key, a new registration is established.
The LSISS2520/LSISS2530 device can hold up to maximum four keys at the same
time. When four keys are registered, a PERSISTENT RESERVATION OUT command
with a Register and Ignore Existing Key service action (that does not replace an
existing key) is rejected with a RESERVATION CONFLICT status.
When a PERSISTENT RESERVATION OUT command with a Register and Ignore Existing
Key service action completes successfully, increment the Generation counter.
details are stored to non-volatile memory so that it is retrieved when the

 Register and Move

The PERSISTENT RESERVATION OUT command with a Register and move service
action requires a successfully established persistent reservation. PERSISTENT
RESERVATION OUT command with a Register and move service action is rejected
with a status of ILLEGAL REQUEST if the initiator specified by the SERVICE ACTION
RESERVATION KEY does not have a Persistent reservation. The command releases
the original persistent reservation, un-registers the initiator if UNREG bit is set,
creates a new registration and reservation for the initiator who issued the persistent
RESERVE OUT command with Register and move service action.
The commands received from the initiator being preempted before processing
persistent RESERVE OUT-REGISTER AND MOVE command is processed under the
purview of the older reservations and the commands received later results in
RESERVATION CONFLICT depending upon the type of new reservation if gets
established successfully.
When a PERSISTENT RESERVATION OUT command with a Register and Move service
action completes successfully, increment the Generation counter.
details are stored to non-volatile memory so that it is retrieved when the
For REGISTER AND MOVE service action, a status of RESERVATION CONFLICT is sent
out for either of the following types of newly established persistent reservation:
— Write Exclusive – All Registrants (WR_EX_AR)
— Exclusive Access – Registrants Only (EX_AC_AR)
4.13.2 SCOPE The following table describes the supported Scope Codes. If a scope code which is not
supported or a reserved scope code is specified, the LSISS2520/LSISS2530 device
returns a CHECK CONDITION status. The Sense Key is set to Illegal Request and the
Additional Sense data is set to Invalid Field in CDB. In case of PERSISTENT RESERVATION
OUT command executing a Register service action, ignore this field.
Table 63: Persistent Reservation Scope Code

00h LU Persistent Reservation applies to the full logical unit
03h to 0Fh RESERVED Reserved

4.13.3 TYPE The following table describes the supported Type Codes. If a type code which is not
supported or a reserved type code is specified, the LSISS2520/LSISS2530 device returns
a CHECK CONDITION status. The SENSE KEY is set to Illegal Request and the Additional
Sense data is set to INVALID Field in CDB. In case of PERSISTENT RESERVATION OUT
command executing a Register service action, this field is ignored.
Table 64: Persistent Reservation Type Codes
Code Name Support in LSISS2520/LSISS2530 device

01h Write Exclusive No
03h Exclusive Access No
05h Write Exclusive Reg. Only No
06h Exclusive Access Reg. Only No
07h Wr Ex - All Reg Yes
08h Ex - All Reg No
Rest All NA No
4.13.4 PERSISTENT RESERVE OUT The section provides two tables that show PERSISTENT RESERVE OUT parameter lists for
PARAMETER LIST different service actions.
4.13.4.1 REGISTER, REGISTER The following table shows the PERSISTENT RESERVE OUT parameter list for REGISTER,
AND IGNORE EXISTING KEY, REGISTER AND IGNORE EXISTING KEY, RESERVE, RELEASE, PREEMPT. PREEMPT AND
RESERVE, RELEASE, PREEMPT.
PREEMPT AND ABORT, and CLEAR ABORT and CLEAR service actions.
Service Actions
Table 65: PERSISTENT RESERVE OUT Parameter List
Bit
Byte
7 6 5 4 3 2 1 0
0:7 (MSB)
RESERVATION KEY
(LSB)
8:15 (MSB)
SERVICE ACTION RESERVATION KEY
(LSB)
16:19 OBSOLETE
20 RESERVED SPEC_I_PT ALL_TG_PT RESERVED APTPL
21 RESERVED
22:23 (MSB)
OBSOLETE = 0
(LSB)

 RESERVATION KEY
Reservation key is verified in each service action process except when either of the
following scenarios occur.
— The REGISTER AND IGNORE EXISTING KEY service action where the
RESERVATION KEY field is ignored;
— The REGISTER service action for an unregistered I_T NEXUS where the
RESERVATION KEY field contains zero.
If the initiator which registered a key is different from the initiator requesting
PERSISTENT RESERVATION OUT command, RESERVATION CONFLICT status is
returned.
 SERVICE ACTION RESERVATION KEY
The SERVICE ACTION RESERVATION KEY field contains information needed for the
following service actions:
REGISTER, REGISTER AND IGNORE EXISTING KEY, PREEMPT, and PREEMPT AND
ABORT and REGISTER AND MOVE.
The SERVICE ACTION RESERVATION KEY field is ignored for the following service
actions: RESERVE, RELEASE, and CLEAR.
For the REGISTER service action and REGISTER AND IGNORE EXISTING KEY service
action, the SERVICE ACTION RESERVATION KEY field contains one of the following:
— The new reservation key to be registered in place of the registered reservation key
— Zero to unregister the registered reservation key
 SPEC_I_PT
The LSISS2520/LSISS2530 device does not support this field.
 ALL_TG_PT
 APTPL
The APTPL is valid only for the Register service action, Register and move service
action, and REGISTER AND IGNORE EXISTING KEY service action. The
LSISS2520/LSISS2530 device ignores the APTPL in other service actions. The
following table shows the relationship between the last valid APTPL value and
information held by the LSISS2520/LSISS2530 device.
Table 66: APTPL and Information Held by a LSISS2520/LSISS2530 Device
Information held by a LSISS2520/LSISS2530 The last valid APTPL value

Device 0 1
Registration all keys are set to 0 retained
Persistent Reservation all are removed retained
Generation Counter set to 0 set to 0

4.13.4.2 PERSISTENT RESERVE The following table shows the Persistent RESERVE OUT command parameter list for the
OUT Command Parameter List for REGISTER AND MOVE service action.
Register and Move Service Action
Table 67: Persistent Reserve Out Command Parameter List for Register And Move Service Action
Bit
Byte
7 6 5 4 3 2 1 0
0:7 (MSB)
RESERVATION KEY
(LSB)
8:15 (MSB)
SERVICE ACTION RESERVATION KEY
(LSB)
16 RESERVED
17 RESERVED UNREG APTPL
18:19 (MSB)
RELATIVE TARGET PORT IDENTIFIER
(LSB)
20:23 (MSB)
TRANSPORT PARAMETER DATA LENGTH (n - 23)
(LSB)
24:n (MSB)
TRANSPORT ID
(LSB)
 RESERVATION KEY
For details, see REGISTER, REGISTER AND IGNORE EXISTING KEY, RESERVE, RELEASE,
PREEMPT. PREEMPT AND ABORT, and CLEAR Service Actions.
 SERVICE ACTION RESERVATION KEY
 UNREG
If UNREG bit is set, the initiator requesting the REGISTER AND MOVE service action is
unregistered upon successful establishment of new reservation.
 APTPL

 RELATIVE TARGET PORT IDENTIFIER

The Relative Target Port Identifier contains the relative port identifier of the target
port that is part of the I_T NEXUS described by this full status descriptor.
 Transport ID
The Transport ID contains information identifying the initiator port that is part of
the I_T NEXUSs described by this full status descriptor. For details, see Table 60.
4.13.5 SUMMARY The following table shows the Service action and parameters and generation counter.
Table 68: Service Action and parameters and generation counter
Parameters
Generation
Service Action Service Action
Scope Type Reservation Key APTPL Counter
Reservation Key
(0) Register Ignore Verify Save Apply +1
(1) Reserve Apply Verify Ignore Ignore —
(2) Release Apply Verify Ignore Ignore —
(3) Clear Ignore Verify Ignore Ignore +1
(4) Preempt Apply Verify Save Ignore +1
(5) Preempt and Apply Verify Save Ignore +1
Abort
(6) Register and Ignore Ignore Save Apply +1
Ignore Existing Key
(7)Register and Ignore Verify and Register and Reserve Apply +1
Move Release

Chapter 4: SCSI Commands | READ (6) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.14 READ (6) The following table describes the READ (6) command.
Table 69: READ 6 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED (MSB)
LOGICAL BLOCK ADDRESS
(LSB)
2:3 (MSB)
(LSB)
4 TRANSFER LENGTH
5 CONTROL
The READ command requests that the LSISS2520/LSISS2530 device transfer the
specified number of blocks of data to the initiator starting at the specified
LOGICAL BLOCK ADDRESS. Data includes user data.
 LOGICAL BLOCK ADDRESS
This field specifies the logical block at which the READ operation begins.
 TRANSFER LENGTH
This field specifies the number of blocks to be transferred. A TRANSFER LENGTH of 0
indicates that 256 blocks is transferred to the initiator. Any other value specifies the
number of logical blocks that is transferred.
This command also supports the variable command time-out feature. See
Mode Page 32h (Firmware Parameter Control). The equation used for time-out
calculation is: Time-Out Value = (TRANSFER LENGTH / 64) + Command time-out
specified in Mode page 0x01h.
If the LSISS2520/LSISS2530 device is formatted to use DIF, it checks the protection
information according to Table 42 in SBC3-r21.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ (10)
4.15 READ (10) This following table describes the READ (10) command.
Bit
Byte
7 6 5 4 3 2 1 0
1 RDPROTECT DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE
2:5 (MSB)
(LSB)
6 RESERVED GROUP NUMBER = 0
7:8 (MSB)
TRANSFER LENGTH
(LSB)
9 CONTROL
The READ(10) command requests that the LSISS2520/LSISS2530 device transfer data to
the initiator. Data includes user data. The larger LOGICAL BLOCK ADDRESS and
TRANSFER LENGTH fields permit greater quantities of data to be requested per
command than with the READ(6) command and are required to access the full LBA
range of the larger capacity LSISS2520/LSISS2530 device.
This field specifies the first logical block of the range of logical blocks for this
command.
 DPO (Disable Page Out)
This bit of 0 indicates the priority is determined by the retention priority field in the
caching parameter mode page (Mode Page 08h (Caching Parameters)). The
LSISS2520/LSISS2530 device does not support DPO bit set to 1 condition
 Force Unit Access (FUA) and Force Unit Access NonVolatile cache (FUA_NV)
These bits are defined in the following tale.
FUA FUA_NV Description

0 X This indicates that LSISS2520/LSISS2530 device can read the requested
blocks from volatile cache, non-volatile cache and/or the medium.
If the FUA_NV bit is set to 1, then the LSISS2520/LSISS2530 device returns
a CHECK CONDITION.
1 X This indicates that the LSISS2520/LSISS2530 device must read the
requested blocks from the medium. If the LSISS2520/LSISS2530 device is
not in NCQ mode then when the FUA bit is set and the device's write
cache is enabled, then the LSISS2520/LSISS2530 device issues a SATA
verify command followed by a SATA read command.
If the FUA_NV bit is set to 1, then the LSISS2520/LSISS2530 device returns
a CHECK CONDITION.

 GROUP NUMBER
This field specifies the group into which attributes associated with the command is
collected. Do not collect a group number value of 0 specifies that any attributes
associated with the command into any group. The LSISS2520/LSISS2530 device
does not support this field.
 TRANSFER LENGTH
This field specifies the number of contiguous logical blocks of data transferred. A
TRANSFER LENGTH field set to 0 specifies that no logical blocks is transferred. Any
other value specifies the number of logical blocks transferred.
This command also supports the variable command time-out feature described in
the Read(6) command handler description. For details, refer to SBC3 (revision 10).
 RDPROTECT
If the LSISS2520/LSISS2530 device is formatted to use DIF, it checks the protection
information according to Table 44 in SBC3-r21.
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = A8h
1 RDPROTECT DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE
2:5 (MSB)
(LSB)
6:9 (MSB)
TRANSFER LENGTH
(LSB)
10 RESTRICTED RESERVED GROUP NUMBER = 0
FOR MMC-4
11 CONTROL
The READ (12) command requests that the LSISS2520/LSISS2530 device transfer data to
the initiator from the medium. Data includes user data. The larger LOGICAL BLOCK
ADDRESS and TRANSFER LENGTH fields permit greater quantities of data to be
requested per command than with the READ (10) command and are required to access
the full LBA range of the larger capacity LSISS2520/LSISS2530 device.
Read(6) command handler description.
See Section 4.15, READ (10) for description of the fields in this command.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ (16)
Bit
Byte
7 6 5 4 3 2 1 0
1 RDPROTECT DPO = 0 FUA RESERVED FUA_NV = 0 RESERVED
2:9 (MSB)
(LSB)
10:13 (MSB)
TRANSFER LENGTH
(LSB)
FOR MMC-4
15 CONTROL
the initiator from the medium. Data includes user data. The larger LOGICAL BLOCK
ADDRESS and TRANSFER LENGTH fields permit greater quantities of data to be
requested per command than with the READ (12) command and are required to access
the full LBA range of the larger capacity LSISS2520/LSISS2530 device.
READ(6) command handler description.
See Section 4.15, READ (10) for description of the fields in this command.
Table 73: READ Command
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE (7Fh)
1 CONTROL
2:5 RESERVED
7 ADDITIONAL CDB LENGTH (18h)
8:9 (MSB)
SERVICE ACTION (0009h)
(LSB)
10 RDPROJECT DPO = 0 FUA RESERVED FUA_NV RESERVED

Table 73: READ Command
Bit
Byte
7 6 5 4 3 2 1 0
11 RESERVED
(MSB)
12:19 LOGICAL BLOCK ADDRESS
(LSB)
(MSB)
20:23 EXPECTED INITIAL LOGICAL BLOCK REFERENCE TAG
(LSB)
(MSB)
24:25 EXPECTED INITIAL LOGICAL BLOCK APPLICATION TAG
(LSB)
(MSB)
26:27 LOGICAL BLOCK APPLICATION TAG MASK = 0xFFFF
(LSB)
(MSB)
28:31 TRANSFER LENGTH
(LSB)
the initiator from the medium. This command can also request that the transferred data
is checked against the protection information fields in the CDB, depending on the
value of the RDPROTECT field. This command also supports the variable command
time-out feature described in READ(6) command handler description.
 EXPECTED INITIAL LOGICALBLOCK REFERENCE TAG
Defined in SBC3-r21 – 5.12.
 EXPECTED LOGICAL BLOCK APPLICATION TAG
Defined in SBC3-r21 – 5.12.
 LOGICAL BLOCK APPLICATION TAG MASK
The LSISS2520/LSISS2530 device supports only the value of 0xFFFF for the logical
block application tag mask.
See Section 4.15, READ (10) for descriptions of the other fields in this command.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ BUFFER
4.19 READ BUFFER The LSISS2520/LSISS2530 device translates the READ BUFFER SCSI command per the
SAT specification guidelines.
Table 74: READ BUFFER CDB
Bit
Byte
7 6 5 4 3 2 1
0 COMMAND CODE = 3Ch
1 RESERVED MODE
2 BUFFER ID
3:5 (MSB)
BUFFER OFFSET
(LSB)
6:8 (MSB)
ALLOCATION LENGTH
(LSB)
9 CONTROL
The function of this command depend on the contents of the MODE field. The following
table lists the various values of the MODE field supported by the LSISS25x0 device.
The LSISS25x0 device returns Check condition status with INVALID FIELD IN CDB if a
Read Buffer command is received with a mode not supported by the LSISS25x0 device.
Table 75: Valid Mode Field Values for READ BUFFER Command
LSISS2520/LSISS2530
Mode Description
Device Support
00h Combined header and data No
01h Vendor Specific No
02h Data Yes
03h Descriptor Yes
0Ah Echo Buffer No
0Bh Echo Buffer Descriptor No
1Ah Enable expander communications protocol and No
Echo buffer
04:09h Reserved No
0C:19h No
1B:1Fh No
4.19.1 Data (Mode 02h) In this mode, the LSISS25x0 device issues the ATA READ BUFFER command and
transfers the retrieved data back to the initiator.
In this mode, the buffer ID and buffer offset fields must be 0. If they are not, the
LSISS25x0 device returns the Check Condition status with the sense key set to ILLEGAL
REQUEST and ASC set to INVALID FIELD IN CDB.

Chapter 4: SCSI Commands | READ CAPACITY (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.19.2 Descriptor (Mode 03h) In this mode, four bytes of READ BUFFER descriptor information are returned.
The READ BUFFER descriptor is defined in following table.
Table 76: Read Buffer Descriptor
Bit
Byte
7 6 5 4 3 2 1
0 OFFSET BOUNDARY
1:3 (MSB)
BUFFER CAPACITY
(LSB)
In this mode, the following settings result when the buffer ID field is set to 0:
 OFFSET BOUNDRY: The LSISS25x0 device sets the OFFSET BOUNDRY to 0x9,
indicating the offsets are at a 512-byte boundary.
 BUFFER CAPACITY: The LSISS25x0 device sets the buffer CAPACITY to 0x200,
indicating 512 bytes of buffer capacity.
For all nonzero buffer IDs in this mode, the zero-filled descriptor is returned back to the
initiator.
4.20 READ CAPACITY (10) The READ CAPACITY (10) command requests the device server to transfer 8 bytes of
parameter data containing the capacity and medium format of the block device.
Table 77: READ CAPACITY 10 CDB
Byte Bit
7 6 5 4 3 2 1 0
1 RESERVED OBSOLETE
2:5 (MSB)
LOGICAL BLOCK ADDRESS = 0
(LSB)
6:7 RESERVED
8 RESERVED PMI = 0
9 CONTROL
The READ CAPACITY command returns information regarding the capacity of the device.
The LSISS2520/LSISS2530 device does not support PARTIAL MEDIUM INDICATOR.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ CAPACITY (16)
The following table shows the data returned to the initiator in response to the
READ CAPACITY command.
Table 78: Format of READ CAPACITY 10 Command Reply
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
RETURNED LOGICAL BLOCK ADDRESS
(LSB)
4:7 (MSB)
BLOCK LENGTH
(LSB)
 BLOCK LENGTH
This field contains the number of bytes of user data in the logical block.
 RETURNED LOGICAL BLOCK
This field is the LBA of the last logical block on the direct access block device or
FFFFFFFFh. If the value is FFFFFFFFh, the initiator can chose to use the READ
CAPACITY (16) command to retrieve the actual block address.
4.21 READ CAPACITY (16) The READ CAPACITY (16) command requests that the device server transfer the
parameter data describing the capacity and medium format of the direct-access block
device.
Table 79: READ CAPACITY 16 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED SERVICE ACTION = 10h
2:9 (MSB)
LOGICAL BLOCK ADDRESS = 0
(LSB)
10:13 (MSB)
ALLOCATION LENGTH
(LSB)
14 RESERVED PMI=0
15 CONTROL

Chapter 4: SCSI Commands | READ CAPACITY (16) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The READ CAPACITY command returns information regarding the capacity of the device.
 SERVICE ACTION
SERVICE ACTION = 10h indicates a READ CAPACITY (16) command
This field is used in conjunction with the PMI field. The following are the valid cases.
— LOGICAL BLOCK ADDRESS and PMI set to 0
— LOGICAL BLOCK ADDRESS and PMI not set to 0
 PMI
For details, see Section 4.20, READ CAPACITY (10).
This field specifies the maximum number of bytes that the application client has
allocated for returned parameter data. An allocation length of zero indicates that no
data is transferred. The LSISS2520/LSISS2530 device does not consider this as an error.
The data returned to the initiator in response to the READ CAPACITY command is
shown in the following table.
Table 80: Format of READ CAPACITY 16 Command Reply
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
RETURNED LOGICAL BLOCK ADDRESS
4:7 (MSB)
(LSB)
8:9 (MSB)
LOGICAL BLOCK LENGTH IN BYTES
(LSB)
10:11 (MSB)
BLOCK LENGTH
(LSB)
12 RESERVED P_TYPE PROT_EN
13 P_I_EXPONENT LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT
14:15 TPE TPRZ (MSB)
LOWEST ALIGNED LOGICAL BLOCK ADDRESS
(LSB)
16:31 RESERVED

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ CAPACITY (16)
 RETURNED LOGICAL BLOCK ADDRESS

See Section 4.20, READ CAPACITY (10). The maximum value returned in this field is
0xFFFFFFFF_FFFFFFFE.
 BLOCK LENGTH
This field contains the number of bytes of user data in the logical block.
 P_TYPE
The protection type field and the protection enable (PROT_EN) bit indicate the
logical unit's current type of protection.
 PROT_EN
This bit set to 1 indicates that the medium was formatted with protection
information enabled. A PROT_EN bit set to 0 indicates that the medium was not
formatted with protection information enabled.
Table 81: PROT_EN
PROT_EN P_TYPE Description

0 xxxb The logical unit is formatted for type 0 protection.
1 000b The logical unit is formatted for type 1 protection.
1 011b to 111b Reserved
 P_I_EXPONENT
The LSISS2520/LSISS2530 device does not support this field and returns zero value
for the field.
 LOGICAL BLOCKS PER PHYSICAL EXPONENT
When sector skewing and DIF are not enabled, the LSISS2520/LSISS2530 device
returns ATA logical sectors per Physical sector exponent in this field.
When sector skewing and DIF are enabled, the LSISS2520/LSISS2530 device returns
0 in this field.
 TPE and TPRZ
The LSISS2520/LSISS2530 device does not support these fields.
 LOWEST ALIGNED LOGICAL BLOCK ADDRESS
When sector skewing and DIF are not enabled, the LSISS2520/LSISS2530 device
returns the ATA logical sector alignment subtracted from the ATA logical sectors per
physical sector.
When sector skewing and DIF are enabled, the LSISS2520/LSISS2530 device returns
0 in this field.
The LSISS2520/LSISS2530 device emulates this command using the information
obtained using the SATA IDENTIFY DEVICE command.

Chapter 4: SCSI Commands | READ LONG (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.22 READ LONG (10) This section lists the READ LONG (10) command.
The READ LONG (10) command requests that the LSISS2520/LSISS2530 transfer one
block of data to the initiator. The transferred data includes data and ECC field data. If
the underlying device does not support the SCT Long Sector Access feature, then the
LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status,
with sense key set to ILLEGAL REQUEST (0x05) and ASC set to invalid command
operation code (0x20), otherwise the LSISS2520/LSISS2530 device translates this
command into a SATA SCT READ LONG command to the device.
Table 82: READ LONG 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED PBLOCK = 0 CORRCT = 0 OBSOLETE
2:5 (MSB)
(LSB)
6 RESERVED
7:8 (MSB)
BYTE TRANSFER LENGTH
(LSB)
9 CONTROL
 PBLOCK
This bit must be set to 0.
 CORRCT
This bit must be set to 0. This causes the logical block to be read without any
correction made by the LSISS2520/LSISS2530 device.
This field specifies the logical block at which the READ operation occurs.
 BYTE TRANSFER LENGTH
This field must exactly specify the number of bytes of data that are available for
transfer. If a nonzero byte TRANSFER LENGTH does not match the available data
length, the LSISS2520/LSISS2530 device terminates the command with CHECK
CONDITION status, the Sense Key is set to Illegal Request and an ASC set to Invalid
Field in CDB. The valid and ILI bits are set to 1 and the information field is set to the
difference of the requested length minus the actual length in bytes. Negative values
are indicated by two's complement notation. The TRANSFER LENGTH is calculated
as follows: TRANSFER LENGTH = logical block size + number of ECC bytes.
A BYTE TRANSFER LENGTH field set to 0 indicates not to transfer any bytes. Do not
consider this condition as an error.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ LONG (16)
4.23 READ LONG (16) The READ LONG (16) command requests that the LSISS2520/LSISS2530 device transfer
one block of data to the initiator. The transferred data includes data and ECC field data.
If the underlying device does not support the SCT Long Sector Access feature, then the
command into a SATA SCT READ LONG command to the device.
Table 83: READ LONG 16 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED SERVICE ACTION (11h)
2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB)
10:11 RESERVED
12:13 (MSB)
(LSB)
14 RESERVED PBLOCK = 0 CORRCT = 0
15 CONTROL
See Section 4.22, READ LONG (10) for the definitions of the fields in this command.
4.24 REASSIGN BLOCK The REASSIGN BLOCKS command requests the SCSI target device to reassign the
defective Logical blocks to another area on the medium set aside for this purpose. The
initiator transfers a defect list that contains the LBA to be reassigned.
Table 84: REASSIGN BLOCK CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED LONGLBA LONGLIST
2:4 RESERVED
5 CONTROL
REASSIGN BLOCKS defect list contains a four-byte header followed by one or more
address descriptors.

Chapter 4: SCSI Commands | REASSIGN BLOCK LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The REASSIGN BLOCKS parameter list, shown in the following table, contains a four-byte
parameter list header followed by a defective LBA list containing one or more LBAs.
Table 85: Reassign Blocks Parameter List
Bit
Byte
7 6 5 4 3 2 1 0
0:3 PARAMETER LIST HEADER
4:n DEFECTIVE LBA LIST (IF ANY)
If LONGLIST is set to 0, then the parameter list header is defined in the following table.
Table 86: Reassign Blocks Short Parameter List Header
Bit
Byte
7 6 5 4 3 2 1 0
0:1 RESERVED
2:3 (MSB)
DEFECT LIST LENGTH
(LSB)
If LONGLIST is set to 1, then the parameter list header is defined in the following table.
Table 87: Reassign Blocks Long Parameter List Header
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
DEFECT LIST LENGTH
(LSB)
The DEFECT LIST LENGTH field indicates the total length in bytes of the DEFECTIVE LBA
LIST field. The DEFECT LIST LENGTH field does not include the parameter list header
length and is equal to either of the following values:
 Four times the number of LBAs, if the LONGLBA bit is set to 0.
 Eight times the number of LBAs, if the LONGLBA bit is set to 1.
The DEFECTIVE LBA LIST field contains a list of defective LBAs. Each LBA is a four-byte
field if the LONGLBA bit is set to 0 or an eight-byte field if the LONGLBA bit is set to 1.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | RELEASE (6)
The LSISS2520/LSISS2530 device processes the LBA List for the reassignment. For the
given list of LBA to be reassigned, for each LBA SATA verify command is posted to device,
if the SATA verify command fails, subsequent SATA Write command is issued to the same
LBA with 0x00 data. If the Write command also fails, then the LSISS2520/LSISS2530
device reports the CHECK CONDITION status and the sense key is set to MEDIUM ERROR
with the ASC set to UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED. The first
LBA not reassigned is returned in the COMMAND-SPECIFIC INFORMATION field of the
sense data. If the SATA Write command succeeds, the LSISS2520/LSISS2530 device
reissues the SATA verify command on the same block to make sure the LBA has been
reassigned. This process occurs for each LBA specified in the DEFECT LIST.
4.25 RELEASE (6) The RELEASE (6) command is used to release a previously reserved logical unit. The
RELEASE (6) command does not release third-party reservations.
Table 88: RELEASE 6 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED Obsolete
2 Obsolete
3 RESERVED
4 RESERVED
5 VU = 0 RESERVED = 0 NACA FLAG LINK
Obsolete Bits 1 through 4 of Byte 1 provide a method, limited to device addresses 0

through 7, to handle third-party reservations in earlier versions of the SCSI standard.
The obsolete method has been replaced by the RESERVE (10) and RELEASE (10).
Bit 0 in Byte 1, and Byte 2 provide an obsolete way to release previously reserved
extents within a logical unit. If Byte 1, Bit 0 is equal to one, the SCSI target device not
implementing the obsolete capability terminates the command with CHECK
CONDITION status and the sense key is set to ILLEGAL REQUEST.
4.26 RELEASE (10) The RELEASE (10) command is used to release a previously reserved logical unit.
Table 89: RELEASE 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED 3rdPty RESERVED LONGID Obsolete
2 Obsolete
3 Third Party Device ID

Chapter 4: SCSI Commands | REPORT LUNS LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 89: RELEASE 10 CDB (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
4 RESERVED
5 RESERVED
6 RESERVED
7 (MSB) Parameter List Length
8 (LSB) Parameter List Length
 3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not
0, the Check Condition status is returned with a sense key of Illegal Request and an
additional sense code of Invalid Field in CDB.
 3rd Party ID must be 0.
 Extents must be 0. Extension is not supported.
 Reservation Identification field must be set to 0.
4.27 REPORT LUNS The REPORT LUNS command is used by an initiator to discover the logical units that are
accessible to the I_T NEXUS on which the command was sent. This command requests
that the target return the known Logical Unit Numbers (LUNS) to the initiator. The
REPORT LUNS command is always available and is unaffected by any reservations.
Table 90: REPORT LUNS CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = A0h
1 RESERVED
2 SELECT REPORT
3:5 RESERVED
6:9 (MSB)
ALLOCATION LENGTH
(LSB)
10 RESERVED
11 CONTROL

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | REPORT LUNS
 SELECT REPORT
This field specifies the types of logical unit addresses reported. The
LSISS2520/LSISS2530 device reports only one LU with number 0 for all the three
types of SELECT REPORT field.
Table 91: SELECT REPORT Fields
Field Description
00h This list contains the logical units accessible to the I_T NEXUS with the following
addressing methods.
Logical unit addressing method
Peripheral device addressing method
Flat space addressing method
02h The list contains all logical units accessible to the I_T NEXUS.
This field must be at least 16 bytes. If the ALLOCATION LENGTH is less than 16 bytes,
the LSISS2520/LSISS2530 device returns a CHECK CONDITION status with Sense Key
of Illegal Request and ASC of Invalid Field in CDB. If the ALLOCATION LENGTH is not
sufficient to contain the LUN values for all configured logical units, the
LSISS2520/LSISS2530 device reports as many logical unit number values that is
sufficient for the specified ALLOCATION LENGTH. This is not considered an error.
The format of the LUN List is shown in the following table.
Table 92: LUN List Format
Bit
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
LUN LIST LENGTH = 8
(LSB)
4:7 RESERVED
8:15 (MSB)
LUN LIST = 0
(LSB)
The LUN LIST LENGTH is the number of logical unit numbers in the logical unit
inventory multiplied by eight. Since the LSISS2520/LSISS2530 device supports only
LUN 0, the LUN List Length is set to 8.

Chapter 4: SCSI Commands | REPORT TIMESTAMP LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.28 REPORT TIMESTAMP The following section describes the REPORT TIMESTAMP command.
Table 93: REPORT TIMESTAMP CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE (A3h)
1 RESERVED SERVICE ACTION (0Fh)
2:5 RESERVED
6:9 ALLOCATION LENGTH
10 RESERVED
11 CONTROL
The REPORT TIMESTAMP command requests that the LSISS2520/LSISS2530 device

return the value of its logical unit’s timestamp.
 SERVICE ACTION
This field set to 0Fh indicates that it is the REPORT TIMESTAMP command. If this field
is not set to 0Fh, the REPORT TIMESTAMP command is terminated with the Check
Condition status with the Sense Key set to ILLEGAL REQUEST and ASC/ASCQ set to
INVALID FILED IN CDB.
This field indicates the maximum number of bytes that an initiator has allocated for
the data associated with this command. No data is transferred if this field is set to zero.
Table 94: REPORT TIMESTAMP Parameter Data
Bit
Byte
7 6 5 4 3 2 1 0
0:1 TIMESTAMP PARAMETER DATA LENGTH (000Ah)
2 RESERVED TIMESTAMP ORIGIN
3 RESERVED
4:9 TIMESTAMP
10:11 RESERVED
 TIMESTAMP PARAMETER DATA LENGTH

This field indicates the number of bytes of parameter data that follow the
TIMESTAMP PARAMETER DATA LENGTH field.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | REQUEST SENSE
 TIMESTAMP ORIGIN
This field indicates the origin of the timestamp. This field is set to one of the
following values.
— 000b – Timestamp initialized to 0 at poweron or as a result of a hard reset.
— 010b – Timestamp initialized by the SET TIMESTAMP command.
 TIMESTAMP
This field contains the current value of the timestamp in milliseconds.
NOTE: The LSISS2520/LSISS2530 device initializes the timestamp to 0 when a hard reset
request is received.
4.29 REQUEST SENSE The REQUEST SENSE command requests that the LSISS2520/LSISS2530 device transfer
sense data to the initiator.
Table 95: REQUEST SENSE CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED DESC = 0
2:3 RESERVED
4 ALLOCATION LENGTH
5 CONTROL
 Descriptor format (DESC)

This bit specifies which sense data format is returned. If DESC is set to 0, the
LSISS2520/LSISS2530 device returns the fixed format sense data. If DESC is set to 1
and descriptor format sense data is supported, the LSISS2520/LSISS2530 device
returns the descriptor format sense data.

Chapter 4: SCSI Commands | REQUEST SENSE LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
This field specifies the maximum number of bytes that an application client has
allocated in the Data-In Buffer. Application clients must request 252 bytes of sense
data to ensure they retrieve all the sense data. If fewer than 252 bytes are requested,
sense data is lost since the REQUEST SENSE command with any allocation length
clears the sense data.
The LSISS2520/LSISS2530 device returns CHECK CONDITION status for a REQUEST
SENSE command only to report exception conditions specific to the REQUEST
SENSE command itself.
These are examples of conditions that cause a REQUEST SENSE command to return
a CHECK CONDITION status:
— An invalid field value is detected in the CDB.
— An error that is not recovered is detected by the service delivery subsystem.
— A malfunction prevents the return of the sense data.
If the LSISS2520/LSISS2530 device has no sense data to return, it completes the
REQUEST SENSE command with GOOD status with the sense key set to NO SENSE and
the additional sense code set to NO ADDITIONAL SENSE DATA.
The following is the sequence in which the LSISS2520/LSISS2530 device checks and
returns sense data for the REQUEST SENSE command.
 Unit attention condition established
The LSISS2520/LSISS2530 device returns parameter data containing sense data
describing the unit attention condition and completes the REQUEST SENSE
command with a GOOD status.
 DSM in Drive Down state
If the LSISS2520/LSISS2530 device is in the Drive Down state, then the
LSISS2520/LSISS2530 device returns a GOOD status with the parameter data
containing sense data with the sense key set to HARDWARE_ERROR and the
additional sense code set to 0x81/0x00 (vendor-specific).
 Format operation in progress
If the LSISS2520/LSISS2530 device is processing a FORMAT UNIT, then the
LSISS2520/LSISS2530 device returns a GOOD status with the parameter data
containing sense key set to NOT READY and the ASC/ASCQ set to LOGICAL UNIT
NOT READY, FORMAT IN PROGRESS. The sense key-specific bytes are set to progress
indication, as defined in Section 3.7.2.4, Progress Indication Sense Data Descriptor, on
page 26.
 DSM set to Getting Ready
If the LSISS2520/LSISS2530 device is in the Getting Ready state because of the drive
initialization sequence in progress, then the LSISS2520/LSISS2530 device returns a
GOOD status with the parameter data containing sense data with the sense key set
to NOT READY and the ASC/ASCQ set to LOGICAL UNIT IS IN PROCESS OF
BECOMING READY.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | REQUEST SENSE
 Stopped power condition

If the LSISS2520/LSISS2530 device is in the stopped power condition, then the
LSISS2520/LSISS2530 device returns a GOOD status with parameter data containing
sense data with the sense key set to NOT READY and the ASC/ASCQ set to LOGICAL
UNIT NOT READY, INIITALIZING COMMAND.
 Idle power condition
If the logical unit is in the idle power condition, then the LSISS2520/LSISS2530
device returns a GOOD status with parameter data containing sense data with the
sense key set to NO SENSE and the ASC/ASCQ set to either of these conditions:
— IDLE CONDITION ACTIVATED BY COMMAND if the logical unit entered the idle
power condition because of a START STOP UNIT command or receipt of a
command requiring the idle power condition.
— POWER CONDITION CHANGE TO IDLE if the SATA device indicates its POWER
MODE as Idle state.
 Standby power condition
If the emulated logical unit is in the standby power condition, then the
sense data with the sense key set to NO SENSE and the ASC/ASCQ set to either of
these conditions:
— STANDBY CONDITION ACTIVATED BY COMMAND if the logical unit entered the
standby power condition because of a START STOP UNIT command or receipt of
a command requiring the standby power condition.
— POWER CONDITION CHANGE TO STANDBY if the if the SATA device indicates its
POWER MODE as Standby state.
 Active_Wait power condition
If the emulated logical unit is in the Active_Wait power condition, then the
sense data with the sense key set to NOT READY and the ASC/ASCQ set to LOGICAL
UNIT NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED.
 Self Test in Progress
If the LSISS2520/LSISS2530 device is processing a Send Diagnostic command in fore
ground mode, then the LSISS2520/LSISS2530 device returns a GOOD status with
parameter data containing sense data with the sense key set to NOT READY and the
ASC/ASCQ set to LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS.
 Format Degraded Mode
If the LSISS2520/LSISS2530 device has entered Format Degraded Mode, and if the
REPORT FORMAT CORRUPT bit of Mode page 32h is enabled, then the
sense data with the sense key set to MEDIUM ERROR and the ASC/ASCQ set to
MEDIUM FORMAT CORRUPTED.

Chapter 4: SCSI Commands | RESERVE (6) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 SMART threshold exceeded condition

If the MRIE field in the Informational Exceptions Control mode page is set to 6h, the
LSISS2520/LSISS2530 device checks whether the attached SATA device indicates
that the error threshold has been exceeded or not. If exceeded, the
LSISS2520/LSISS2530 device returns parameter data containing sense data with the
sense key set to NO SENSE with the ASC/ASCQ set to HARDWARE IMPENDING
FAILURE GENERAL HARD DRIVE FAILURE and completes the REQUEST SENSE
command with a GOOD status.
4.30 RESERVE (6) The RESERVE command is used to reserve a LUN for an initiator.
Table 96: RESERVE 6 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED = 0 Ext = 0
2 RESERVED = 0
3 (MSB) Extent List Length
4 (LSB) Extent List Length
The RESERVE command reserves the entire LUN for the initiator until one of the
following actions takes place:
 The reservation is superseded by another valid RESERVE command from the
initiator that made the reservation.
 The reservation is released by a RELEASE command from the same Initiator when
the new reservation is granted.
 A hard Reset condition occurs.
 A Device Reset Task Management Function is received from any initiator.
 A power off/on cycle occurs.
Extents are not supported in the LSISS2520/LSISS2530 device.
Reservation queuing is not supported by the LSISS2520/LSISS2530 device.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | RESERVE (10)
4.31 RESERVE (10) The RESERVE command is used to reserve a LUN for an initiator. This reservation can be
either for the initiator sending the command or for a third party as specified by the
initiator.
Table 97: RESERVE 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED 3rdPty RESERVED LONGID Obsolete
2 Reservation Identification = 0
3 Third Party Device ID = 0
4 RESERVED
5 RESERVED
6 RESERVED
The RESERVE command reserves the entire LUN for the initiator until one of the
following actions takes place:
 The reservation is superseded by another valid RESERVE command from the
initiator that made the reservation.
 The reservation is released by a RELEASE command from the same initiator.
 A hard Reset condition occurs.
 A Device Reset Task Management Function is received from any initiator.
 A power off/on cycle occurs.
Note the following information:
 Extents are not supported in the LSISS2520/LSISS2530 device; they must be set to 0.
 The 3rdPty bit must be 0. Third Party reservations are not supported. If the 3rdPty
bit is not zero, a Check Condition status is returned with a sense key of Illegal
Request and an additional sense code of Invalid Field in CDB.
 3rd Party ID must be 0.
 LongID is ignored.
 Reservation Identification field is set to 0.
 Reservation queuing is not supported by the LSISS2520/LSISS2530 device.

Chapter 4: SCSI Commands | SECURITY IN PROTOCOL LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.32 SECURITY IN PROTOCOL This section describes the Security In Protocol command.
Table 98: Security In Protocol
Bit
Byte
Security In Protocol
0 OPERATION CODE (A2h)
1 SECURITY PROTOCOL
2:3 SECURITY PROTOCOL SPECIFIC
4 INC_512 RESERVED
5 RESERVED
6:9 (MSB)
ALLOCATION LENGTH
(LSB)
10 RESERVED
11 CONTROL
 SECURITY PROTOCOL
This field specifies the protocol used. See the following table.
Table 99: SECURITY PROTOCOL Codes
Supported
Code Description
by LSISS25x0
00h Yes Security protocol information
01h – 06h Yes Defined by the Trusted Computing Group (TCG)
07h No 07h CbCS
08h to 1Fh No Reserved
20h No Tape Data Encryption SSC-3
21h No Data Encryption Configuration ADC-3
22h to 3Fh No Reserved
40h No Security Associations (SA) Creation Capabilities
41h No IKEv2-SCSI
42h to ECh No Reserved
EDh No SD Card TrustedFlash specification
EEh No Authentication in Host Attachments of Transient Storage Devices
EFh Yes ATA Device Server Password Security SAT-2
F0h to FFh No Vendor-specific

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SECURITY IN PROTOCOL
 SECURITY PROTOCOL SPECIFIC

The contents of the SECURITY PROTOCOL SPECIFIC field depend on the protocol
specified by the SECURITY PROTOCOL field.
 INC_512
A 512 increment bit set to 1 specifies that the ALLOCATION LENGTH field expresses
the maximum number of bytes available to receive data in increments of 512 bytes
(for example, a value of 1 means 512 bytes, 2 means 1024 bytes). Pad bytes can be
appended to meet this length. Pad bytes have a value of 00h. An INC_512 bit set to
0 specifies that the ALLOCATION LENGTH field expresses the number of bytes to be
transferred.
This field specifies the number of bytes that the initiator allocates for the Security In
Protocol data to be returned.
An ALLOCATION LENGTH of 0 is not supported: the LSISS2520/LSISS2530 device
returns a CHECK CONDITION status, the SENSE KEY is set to ILLEGAL REQUEST, and
the Additional Sense data is set to INVALID FIELD IN CDB.
If the INC_512 bit is set to 1 and the ALLOCATION LENGTH field is greater than
FFFFh, the SCSI to ATA Translation Layer (SATL) returns a CHECK CONDITION status
with the sense key set to ILLEGAL REQUEST and the additional sense code set to
INVALID FIELD IN CDB. Otherwise, the ATA Transfer_Length field is set to
ALLOCATION LENGTH (15:0). After completion of the ATA TRUSTED RECEIVE or ATA
TRUSTED RECEIVE DMA command, the data is transferred to the SCSI application
client.
If the INC_512 bit is set to 0 and if the ALLOCATION LENGTH field is greater than
1FF_FE00h, the SATL returns a CHECK CONDITION status with the sense key set to
ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN CDB.
Otherwise, the ATA Transfer_Length field is translated from bytes to a number of
padded 512-byte units from the result of the following calculation:
ATA Transfer_Length(15:0) = ((ALLOCATION LENGTH + 511) / 512)
The LSISS2520/LSISS2530 device does not support the INC_512 bit set to 0.
After successful completion of the ATA TRUSTED RECEIVE or ATA TRUSTED RECEIVE
DMA command, the data is transferred to the SCSI application client to the specified
ALLOCATION LENGTH number of bytes.

Chapter 4: SCSI Commands | SECURITY OUT PROTOCOL LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.33 SECURITY OUT PROTOCOL This section describes the Security Out Protocol command.
Table 100: Security Out Protocol
Bit
Byte
Security Out Protocol
0 OPERATION CODE (B5h)
1 SECURTITY PROTOCOL
2:3 SECURTITY PROTOCOL SPECIFIC
4 INC_512 RESERVED
5 RESERVED
6:9 (MSB)
TRANSFER LENGTH
(LSB)
10 RESERVED
11 CONTROL
 TRANSFER LENGTH
This field specifies the number of blocks to be transferred for Security Out Protocol.
A TRANSFER LENGTH of 0 is not supported and the LSISS2520/LSISS2530 device
returns a CHECK CONDITION status. The SENSE KEY is set to ILLEGAL REQUEST and
the Additional Sense data is set to INVALID FIELD IN CDB.
If the INC_512 is set to 1 and TRANSFER LENGTH is greater than FFFFh, the SATL
returns the CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB. Otherwise, the ATA
Transfer_Length field is set to ALLOCATION LENGTH (15:0). The ATA TRUSTED SEND
or ATA TRUSTED SEND DMA command transfer the data.
If the INC_512 bit is set to 0 and TRANSFER LENGTH is greater than 1FF_FE00h, the
SATL returns CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB. Otherwise, the ATA
Transfer_Length field is translated from bytes to a number of padded 512-Byte units
from the result of the following calculation:
ATA Transfer_Length(15:0) = ((TRANSFER LENGTH + 511) / 512)
The final data block can be padded (refer to SPC-4). The ATA TRUSTED SEND or ATA
TRUSTED SEND DMA command transfer the padded data for ATA Transfer_Length
number of data blocks.
The LSISS2520/LSISS2530 device does not support an INC_512 bit setting of 0.
See Section 4.32, SECURITY IN PROTOCOL for descriptions of the fields in this
command.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SEND DIAGNOSTIC
4.34 SEND DIAGNOSTIC The SEND DIAGNOSTIC command requests the LSISS2520/LSISS2530 device to perform
the diagnostic operation on the target device, logical unit or both.
Table 101: SEND DIAGNOSTIC CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE = 1Dh
1 Self test Code PF RSVD = 0 Self-Test DEVOFF LEN UNITOFF LEN
2 RESERVED = 0
5 CONTROL
Table 102: Self-Test Codes
Value Function Name Specific

000b NA This value is used when the Self-Test bit is set to 1,
or if the Self-Test bit is set to 0 and the PF bit is set
to 1.
001b Background Short self-test The target starts its short self-test routine in the
background mode.
010b Background Extended self-test The target starts its extended self-test in the
background mode.
011b NA Reserved
100b Abort Background self-test Abort the current self-test in the background
mode. This value is only valid if a previous SEND
DIAGNOSTIC command specified a background
self-test function and that function has not
completed.
101b Foreground Short self-test The target starts its short self-test routine in the
foreground mode.
110b Foreground Extended self-test The target starts its extended self-test routine in
the foreground mode.
111b NA Reserved
 The Page Format (PF) bit set to 1 indicates the data sent by the initiator conforms to
the page structure as specified in the ANSI SCSI standard. This bit must be set to 1 if
the Self-Test bit is set to 0. This bit is ignored by the Target if the Self-Test bit is set.
 The Self-Test bit set to 1 indicates the device performs its logical unit default self
test. If the bit is set to 0, the device server starts the diagnostic operation specified
by SELF-TEST CODE field or in parameter list. The LSISS2520/LSISS2530 device does
not support Self-Test set to 1.
 The DEVOFFLEN bit is ignored by the target for compatibility. The
LSISS2520/LSISS2530 device sends a CHECK CONDITION status with a Sense Key of
Illegal Request and additional sense of Invalid Field in CDB for DEVOFFLEN set to 1.

Chapter 4: SCSI Commands | SET TIMESTAMP LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 The UNITOFFLEN bit is ignored by the target for compatibility. The

LSISS2520/LSISS2530 device sends a CHECK CONDITION status with a Sense Key of
Illegal Request and additional sense of Invalid Field in CDB for UNITOFFLEN set to 1.
 Self-test Code. See Table 102.
 The Parameter List Length must be 0 when the Self-Test bit is 1. Otherwise, it is set
to the length of the page to be transferred. If it does not match the expected length
of the page a CHECK CONDITION status is generated with a Sense Key of Illegal
Request and additional sense of Invalid Field in CDB.
4.35 SET TIMESTAMP The following section describes the SET TIMESTAMP command.
Table 103: SET TIMESTAMP CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE (A4h)
1 RESERVED SERVICE ACTION (0Fh)
2:5 RESERVED
6:9 PARAMETER LIST LENGTH
10 RESERVED
11 CONTROL
The SET TIMESTAMP command requests the LSISS2520/LSISS2530 device to initialize

the timestamp to a value specified in SET TIMESTAMP parameter data.
 SERVICE ACTION
This field set to 0Fh indicates that it is the SET TIMESTAMP command. If this field is
not set to 0Fh, the SET TIMESTAMP command is terminated with the Check
INVALID FILED IN CDB.
This field specifies the number of bytes to be sent from the initiator. A PARAMETER
LIST LENGTH of 0 transfers no data and no change is made to the timestamp value.
If this field is not set to a value equal to length of the SET TIMESTAMP Parameter
Data or 0, then the SET TIMESTAMP command is terminated with the Check
INVALID FILED IN CDB

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | START STOP UNIT
Table 104: SET TIMESTAMP Parameter Data
Bit
Byte
7 6 5 4 3 2 1 0
0:3 RESERVED
4:9 TIMESTAMP
10:11 RESERVED
 TIMESTAMP
This field contains the initial value of the timestamp in milliseconds. If the higher
order byte in the TIMESTAMP field is greater than F0h, the SET TIMESTAMP
command is terminated with CHECK CONDITION status, with the Sense Key set to
ILLEGAL REQUEST, and the ASC/ASCQ set to INVALID FIELD IN PARAMETER LIST.
4.36 START STOP UNIT The START STOP UNIT command provides an initiator a method to control the power
condition of a logical unit. The START/STOP UNIT command is used to spin up or stop
the spindle motor. The LSISS2520/LSISS2530 device translates this command as per the
SAT specification guidelines.
Table 105: START/STOP UNIT CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 1Bh
1 RESERVED IMMED
2 RESERVED
3 RESERVED POWER CONDITION MODIFIER
4 POWER CONDITIONS RESERVED NO_FLUSH LOEJ START
5 CONTROL
 IMMED
If this bit is set to 0, the Status is to be returned at the end of the operation.
If this bit is set to 1, a GOOD status is always returned immediately after the
command has been validated. The TEST UNIT READY command is used to
determine when the LSISS2520/LSISS2530 device becomes ready after a spin-up.
 NO_FLUSH
If set to 1, the LSISS2520/LSISS2530 device does not send ATA Flush commands to
the SATA device while processing the Start Stop Unit commands with the Power
Condition field set to IDLE/STANDBY/FORCE_STANDBY_0, and vice versa.

Chapter 4: SCSI Commands | START STOP UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 START
The START and LOEJ bits are valid only if the Power Condition value set to
START_VALID, if not then the LSISS2520/LSISS2530 device ignores the values of
these bits.
Setting the START bit to 0 stops the spindle and causes the LU to transition to
Stopped power condition state.
Setting the START bit to 1 starts the spindle and causes the LU to transition to the
Active/Active_Wait power condition state.
 LOEJ (load Eject)
If this bit is set to 0, then the logical unit takes no action regarding loading or
ejecting the medium. If it is set to 1, then the logical unit unloads the medium if the
START bit is set to 0. If the underlying device does not support the Removable
Media Feature set, then the LSISS2520/LSISS2530 device terminates the command
with CHECK CONDITION status, with the SENSE KEY set to ILLEGAL REQUEST and the
ASC/ASCQ set to INVALID FIELD IN CDB.
The LSISS2520/LSISS2530 device does not support the LOEJ and START bit set to 1
and terminates the command with CHECK CONDITION status, with the SENSE KEY
set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD in CDB.
Table 106: Power Condition Values

00h START_VALID The START and LOEJ bits are valid.
01h ACTIVE Place the LSISS2520/LSISS2530 device into the active
power condition.
02h IDLE Place the LSISS2520/LSISS2530 device into the idle power
condition.
03h STANDBY Place the LSISS2520/LSISS2530 device into the standby
power condition.
0Bh FORCE_STANDBY_0 Place the LSISS2520/LSISS2530 device into the standby
power condition.
For other Power Condition values, the LSISS2520/LSISS2530 device terminates the Start
Stop Unit commands with the CHECK CONDITION status, with the SENSE KEY set to
ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CDB. Also, while in the
Stopped/Active_Wait power condition state, the LSISS2520/LSISS2530 device
terminates the Start Stop Unit – FORCE_STANDBY_0 commands with the CHECK
CONDITION status, with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set
to INVALID FIELD IN CBD.
 POWER CONDITION MODIFIER
This field is supported only if the Power Condition value is set to IDLE. The
supported values are 0, 1, and 2. For all other Power Condition values, this field must
be set to 0. Otherwise the LSISS2520/LSISS2530 device terminates the Start Stop
Unit commands with the CHECK CONDITION status, with the SENSE KEY set to
ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CBD.

When the Immediate bit is set to 0 and one of the following is true, then the
LSISS2520/LSISS2530 device uses the value configured in the DSM Spinup Timeout
field of Mode Page 32h as the command time-out value for the particular Start Stop
Unit command:
 Power Condition value set to ACTIVE or START_VALID, with the START bit set to 1,
and the particular Start Stop Unit command changes the LU power condition state
to Active.
 Power Condition value set to START_VALID, with the START bit set to 0, and the
particular Start Stop Unit command changes the LU power condition state to
Stopped.
 Power Condition value set to IDLE/STANDBY/FORCE_STANDBY_0, with the
NO_FLUSH bit set to 0, and the particular Start Stop Unit command changes the LU
power condition state to Idle/Standby respectively.
The following table lists the possible power condition states within the
LSISS2520/LSISS2530 device, command processing while in particular power condition
state, and next possible power condition states from the particular power condition state.
Table 107: Possible Power Condition States
Next Possible
Power Command Processing
Power Condition State
Active Capable of processing all the supported Any supported power
commands condition state except
Active_Wait
Stopped Capable of processing all the supported Any supported power
commands except TEST UNIT READY and media condition state
access type commands
NOTE: While in the Stopped power condition

state, all the media access type commands and
the TEST UNIT READY command terminated
with CHECK CONDITION status, with the Sense
Key set to NOT READY and ASC/ASCQ set to
LOGICAL UNIT NOT READY, INITIALIZING
COMMAND REQUIRED.
Active_Wait Capable of processing all the supported Any supported power

commands except TEST UNIT READY and media condition state
access type commands
NOTE: While in the Active_Wait power

condition state, all the media access type
commands and the TEST UNIT READY command
terminated with CHECK CONDITION status with
the Sense Key set to NOT READY and ASC/ASCQ
set to LOGICAL UNIT NOT READY, NOTIFY
(ENABLE SPINUP) REQUIRED.

Table 107: Possible Power Condition States (Continued)
Next Possible
Power Command Processing
Power Condition State
Standby Capable of processing all the supported Any supported power
commands (assuming the transition to the condition state
Active_Wait power condition state is disabled.
When a media access type SCSI command is
received, the LSISS2520/LSISS2530 device
transitions to the Active power condition state
before processing the command.
NOTE: If transition to the Active_Wait power

condition state is enabled, the
LSISS2520/LSISS2530 device transitions to the
Active_Wait power condition state and
terminates the media access command that
caused the particular power state transition
with the CHECK CONDITION status, with the
Sense Key set to NOT READY and ASC/ASCQ set
to LOGICAL UNIT NOT READY, NOTIFY (ENABLE
SPINUP) REQUIRED.
Idle Capable of processing all the supported Any supported power

commands. condition state except
Active_Wait
NOTE: When a media access type SCSI
command is received, the LSISS2520/LSISS2530
device transitions to the Active power condition
state before processing the command.
NOTE: The LSISS2520/LSISS2530 device considers a SCSI command as a media access

type command if the particular SCSI command requires that an ATA command be sent
to the SATA device.
NOTE: The LSISS2520/LSISS2530 device transitions to an Active_Wait power condition

state from the Stopped/Standby power condition state when: transition to the
Active_Wait power condition state is enabled, and a START STOP UNIT command with
the power condition field set to ACTIVE/START_VALID (START = 1) is processed.

4.36.1 Processing of Start Stop Unit Table 108 and Table 109 shows the details for processing of Start Stop Unit command
Command When DSM is in when the Device State Machine is in SATA_WAITING_FOR_SPINUP_REQUEST state. For
SATA_WAITING_FOR_SPINUP_REQUEST more information, see Section 5.1.13, Mode Page 32h (Firmware Parameter Control) and
State Section B.1, Device State Machine.
Table 108: DEVICE SPINUP ALGORITHM Set to SPINUP ON STARTSTOP - DRIVEPOWER/DRIVEPHY
ENABLE ACTIVE WAIT

Current LU Power Start Stop Unit Command Within Firmware Parameter Start Stop Unit Command Resultant LU Power
Condition State Power Condition Control Mode Page (32h) Processing Status Condition State
Enabled/Disabled
ACTIVE_WAIT START_VALID: START = 1 NA Good Status ACTIVE
START_VALID: START = 0 NA Good Status STOPPED
ACTIVE Enabled Good Status ACTIVE_WAIT
Disabled Check Condition status with ACTIVE_WAIT
Sense Key set to NOT READY
and ASC/ASCQ set to
LOGICAL UNIT NOT READY,
NOTIFY (ENABLE SPINUP)
REQUIRED
STANDBY/FORCE_STANDBY_0/ NA Check Condition status with ACTIVE_WAIT
IDLE/LU_CONTROL Sense Key set to NOT READY
and ASC/ASCQ set to
REQUIRED
STOPPED START_VALID: START = 1 NA Good Status ACTIVE
ACTIVE NA Check Condition status with STOPPED
and ASC/ASCQ set to
REQUIRED
STANDBY/FORCE_STANDBY_0/ NA Check Condition status with STOPPED
and ASC/ASCQ set to
REQUIRED

Table 109: DEVICE SPINUP ALGORITHM Set to SPINUP ON NOTIFY PRIMITIVE - DRIVEPOWER/DRIVEPHY
ENABLE ACTIVE WAIT

Current LU Power Start Stop Unit Command Within Firmware Parameter Start Stop Unit Command Resultant LU Power
Condition State Power Condition Control Mode Page (32h) Processing Status Condition State
Enabled/Disabled
ACTIVE_WAIT START_VALID: START = 1 Enabled Good Status ACTIVE_WAIT
and ASC/ASCQ set to
REQUIRED
and ASC/ASCQ set to
REQUIRED
STANDBY/FORCE_STANDBY_0/ NA Check Condition status with ACTIVE_WAIT
and ASC/ASCQ set to
REQUIRED
STOPPED START_VALID: START = 1 Enabled Good Status ACTIVE_WAIT
Disabled Check Condition status with STOPPED
and ASC/ASCQ set to
REQUIRED
Disabled Check Condition status with STOPPED
and ASC/ASCQ set to
REQUIRED
STANDBY/FORCE_STANDBY_0/ NA Check Condition status with STOPPED
and ASC/ASCQ set to
REQUIRED

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16)
4.37 SYNCHRONIZE CACHE(10) The SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) commands ensure that
and SYNCHRONIZE CACHE(16) logical blocks in the cache have their most recent data value recorded on the media.
The LSISS2520/LSISS2530 device translates these SCSI commands to the SATA FLUSH
CACHE/SATA FLUSH CACHE EXT command to ensure that the SATA device flushes all its
data to the media.
Table 110: SYNCHRONIZE CACHE (10) CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED SYNC_NV = 0 IMMED = 0 OBSOLETE
2:5 (MSB)
(LSB)
7:8 (MSB)
NUMBER OF BLOCKS
(LSB)
9 CONTROL
Table 111: SYNCHRONIZE CACHE (16) CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED SYNC_NV = 0 IMMED = 0 RESERVED
2:9 (MSB)
(LSB)
10:13 (MSB)
NUMBER OF BLOCKS
(LSB)
15 CONTROL

This field specifies where the operation is to begin.
 NUMBER OF BLOCKS
This field specifies the total number of contiguous logical blocks within the range.

Chapter 4: SCSI Commands | TEST UNIT READY LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 IMMED (Immediate)
An IMMED bit set to 0 indicates that the status is not returned until the operation
has completed. An IMMED bit set to 1 causes the LSISS2520/LSISS2530 device to
return a GOOD status as soon as the CDB is validated.
 GROUP NUMBER
 SYNC_NV
This bit specifies whether the SCSI target device is required to synchronize volatile
and nonvolatile caches. A SYNC_NV bit set to 0 indicates that the SCSI target device
synchronizes volatile and nonvolatile caches to the medium.
The SYNC_NV bit must be 0. If the SYNC_NV bit is set to 1, the LSISS2520/LSISS2530
device returns a CHECK CONDITION status. The SENSE KEY is set to ILLEGAL
REQUEST and the ASC is set to INVALID FIELD in CDB.
4.38 TEST UNIT READY The TEST UNIT READY command provides a mechanism to check the state of a Logical
Unit. The TEST UNIT READY command checks if the Logical Unit accepts a
medium-access command without returning CHECK CONDITION status.
Table 112: TEST UNIT READY CDB
Bit
Byte
7 6 5 4 3 2 1 0
2:4 RESERVED
5 CONTROL
The LSISS2520/LSISS2530 device maintains the current state of the SATA device in its
device state machine. Alternatively, the LSISS2520/LSISS2530 device uses SATA CHECK
POWER MODE (SATA) command to check the status of the serial SATA device when
required. Based on the current state of the SATA device, construct and return a SCSI
response to the SAS initiators.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | VERIFY (10)
4.39 VERIFY (10) The VERIFY command requests that the LSISS2520/LSISS2530 device verify the data
written on the media. A verification length of 0 indicates that no data is transferred on
the media starting at the specified LOGICAL BLOCK ADDRESS. This condition is not
considered an error. Data includes user data, if any.
Table 113: VERIFY 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 VRPROTECT DPO = 0 RESERVED BYTCHK = 0 OBSOLETE
2:5 (MSB)
(LSB)
FOR MMC-4
7:8 (MSB)
VERIFICATION LENGTH
(LSB)
9 CONTROL
 VRPROTECT
This field specifies the protection information to be verified. It is implemented per
SBC3r21.
This bit set to 0 indicates the priority is determined by the retention priority field in
the caching parameter mode page (Mode Page 08h (Caching Parameters)).
The LSISS2520/LSISS2530 device does not support DPO bit set to 1 condition.
 BYTCHK
This bit set to 0 indicates that the data is verified using SATA Verify command. If an
error is detected in the verify process, CHECK CONDITION status is returned with
Sense Key set to MEDIUM ERROR. The LSISS2520/LSISS2530 device supports Byte
Chk bit set 0 conditions only.
This field specifies the logical block at which the VERIFY operation begins.
 GROUP NUMBER
The LSISS2520/LSISS2530 device does not support Grouping.

Chapter 4: SCSI Commands | VERIFY (12) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 VERIFICATION LENGTH
This field specifies the number of blocks to be verified. A verification length of 0
indicates that no logical blocks are verified. This condition is not considered as an
error.
If the LOGICAL BLOCK ADDRESS plus the verification exceeds the capacity of the
medium, the target returns CHECK CONDITION status with the sense key set to
ILLEGAL REQUEST and the ASC set to LOGICAL BLOCK ADDRESS OUT OF RANGE.
4.40 VERIFY (12) This section lists the VERIFY (12) commands.
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = AFh
1 VRPROTECT DPO = 0 RESERVED BYTCHK = 0 OBSOLETE
2:5 (MSB)
(LSB)
6:9 (MSB)
VERIFICATION LENGTH
(LSB)
FOR MMC-4
11 CONTROL
See Section 4.39, VERIFY (10) for the description of fields in this command.
4.41 VERIFY(16) This section lists the VERIFY (16) commands.
Bit
Byte
7 6 5 4 3 2 1 0
1 VRPROTECT DPO = 0 RESERVED BYTCHK = 0 RESERVED
2:9 (MSB)
(LSB)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE (6)
Table 115: VERIFY 16 CDB (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
10:13 (MSB)
VERIFICATION LENGTH
(LSB)
FOR MMC-4
15 CONTROL
See Section 4.39, VERIFY (10) for the description of fields in this command.
4.42 WRITE (6) The WRITE(6) command requests that the Logical Unit transfer the specified blocks
from the Data-Out buffer and write them. Each logical block transferred includes user
data but does not include protection information.
Table 116: WRITE 6 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 RESERVED LBA
2:3 (MSB)
(LSB)
4 TRANSFER LENGTH
5 CONTROL

This field specifies the logical block at which the WRITE operation begins.
 TRANSFER LENGTH
This field specifies the number of blocks to be transferred. A TRANSFER LENGTH
field set to 0 specifies that 256 logical blocks are written. Any other value specifies
the number of logical blocks to be written.
If the LSISS2520/LSISS2530 device has been formatted to use protection
information, the DIF fields (logical block guard, logical block reference, and logical
block application tag) are generated according to SBC3-r21, Section 5.28.
Any other value specifies the number of logical blocks transferred. If the LOGICAL
BLOCK ADDRESS plus the TRANSFER LENGTH exceeds the capacity of the medium, the
target returns CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the ASC set to LOGICAL BLOCK ADDRESS OUT OF RANGE.

Chapter 4: SCSI Commands | WRITE (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
This command also supports the variable command time-out feature. See Mode Page
32h (Firmware Parameter Control). The equation used for time-out calculation is Time out
Value = (TRANSFER LENGTH / 32) + command timeout specified in Mode page 0x01h.
If the LSISS2520/LSISS2530 device is configured such that NCQ is disabled, then the
LSISS2520/LSISS2530 device uses WRITE DMA or WRITE DMA EXT instead of WRITE
FPDMA QUEUED SATA command to translate the SCSI WRITE command.
4.43 WRITE (10) The WRITE (10) command requests that the device server transfer the specified logical
blocks from the Data-Out buffer and write them. Each logical block written includes
user data.
Bit
Byte
7 6 5 4 3 2 1 0
1 WRPROTECT DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE
2:5 (MSB)
(LSB)
7:8 TRANSFER LENGTH
9 CONTROL
 WRPROTECT
When the LSISS2520/LSISS2530 device is formatted to use protection information, it
follows Table 85 in SBC3-r21 to verify the DIF fields in the incoming data.
LSISS2520/LSISS2530 device does not support this bit.
 Force unit access bits (FUA and FUA_NV)
These bits are defined in the following table.
Table 118: FUA and FUA_NV Descriptions
FUA FUA_NV Description

0 X This indicates that the target can return GOOD status prior to writing the data to volatile cache,
nonvolatile cache and/or the medium
1 X This indicates that the target must write the data to the media before returning GOOD status.
If the FUA_NV bit is set to 1, then the LSISS2520/LSISS2530 device returns a CHECK
CONDITION.


This field specifies the logical block at which the WRITE operation begins.
 GROUP NUMBER
The GROUP NUMBER field specifies the group into which attributes associated with
the command is collected. The LSISS2520/LSISS2530 device does not support
grouping function and hence ignores this field.
 TRANSFER LENGTH
This field specifies the number of blocks to be transferred. A TRANSFER LENGTH of 0
indicates that no logical blocks are transferred. Do not consider this condition as an
error and do not write any data.
Any other value specifies the number of logical blocks transferred. If the LOGICAL
BLOCK ADDRESS plus the TRANSFER LENGTH exceeds the capacity of the medium, the
target returns CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the ASC set to LOGICAL BLOCK ADDRESS OUT OF RANGE.
WRITE(6) command handler description.
4.44 WRITE (12) The WRITE (12) command requests that the LSISS2520/LSISS2530 device write the
specified number of blocks of data from the initiator to the medium starting at the
specified LOGICAL BLOCK ADDRESS. The data transferred from the initiator includes
user data as required by the medium format. This command is processed as per the
standard WRITE command except for the longer TRANSFER LENGTH.
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = AAh
2:5 (MSB)
(LSB)
6:9 (MSB)
TRANSFER LENGTH
(LSB)

FOR MMC-4
11 CONTROL
See Section 4.43, WRITE (10) for details of the fields.

Chapter 4: SCSI Commands | WRITE (16) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.45 WRITE (16) The WRITE (16) command requests that the LSISS2520/LSISS2530 device write the
user data as required by the medium format. This command is processed as per the
standard WRITE (10) command except for the TRANSFER LENGTH Field.
Bit
Byte
7 6 5 4 3 2 1 0
2:9 (MSB)
(LSB)
10:13 (MSB)
TRANSFER LENGTH
(LSB)
FOR MMC-4
15 CONTROL
4.46 WRITE (32) The following table describes the WRITE (32) command.
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE (7Fh)
1 CONTROL
2:5 RESERVED
7 ADDITIONAL CDB LENGTH (18h)
8:9 (MSB)
SERVICE ACTION (000Bh)
(LSB)
10 WRPROJECT DPO = 0 FUA RESERVED FUA_NV RESERVED
11 RESERVED
(MSB)
(LSB)

Table 121: WRITE 32 CDB (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
(MSB)
(LSB)
(MSB)
24:25 EXPECTED INITIAL LOGICAL BLOCK APPLICATION TAG
(LSB)
(MSB)
(LSB)
(MSB)
28:31 TRANSFER LENGTH
(LSB)
The WRITE (32) command requests that the LSISS2520/LSISS2530 device write the
user data as required by the medium format. When the LSISS2520/LSISS2530 device is
formatted to use protection information, the following fields are defined:
Defined in SBC3-r21 – 5.32
Defined in SBC3-r21 – 5.32
The LSISS2520/LSISS2530 device only supports the value of 0xFFFF for the logical

Chapter 4: SCSI Commands | WRITE AND VERIFY(10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.47 WRITE AND VERIFY(10) This following table describes the WRITE AND VERIFY(10) command.
Table 122: WRITE AND VERIFY 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 WRPROTECT DPO = 0 RESERVED BYTCHK OBSOLETE
2:5 (MSB)
(LSB)
7:8 (MSB)
TRANSFER LENGTH
(LSB)
9 CONTROL
WRITE AND VERIFY(10) command requests that the LSISS2520/LSISS2530 device write
the data transferred from the initiator to the medium and then verify that the data is
correctly written.
LSISS2520/LSISS2530 device supports DPO set to 0 conditions only.
 WRPROTECT
This field specifies the protection information to be verified. It is implemented per
SBC3r21.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE AND VERIFY(10)
 BYTCHK
This bit set to 0 indicates that after writing, the device server perform a medium
verification with no data comparison. A BYTCHK bit set to 1 specifies that, after
writing, the device server perform a CRC comparison of data written on the medium
with the data just written. If the comparison is unsuccessful for any reason, the
device server returns CHECK CONDITION status with the sense key set to
MISCOMPARE with the appropriate ASC for the condition. The LSISS2520/LSISS2530
device implements a non-standard implementation of the BYTCHK bit set to 1.
When the WRITE AND VERIFY command is received with the BYTCHK field set to 1,
the LSISS2520/LSISS2530 device does not perform a CRC comparison of the initiator
data with the data read from medium. Instead it uses the saved CRC calculated
across the write data as the mechanism to detect whether the written data matches
the data on the medium. The algorithm is as follows:
— When BYTCHK = 1, the LSISS2520/LSISS2530 device writes the initiator's data to
the device. While writing, it also generates a CRC value for the data.
— When the WRITE DATA phase completes, the LSISS2520/LSISS2530 device reads
the data from the device starting at the block where the initiator's data was
written. The LSISS2520/LSISS2530 device discards the read data after it passes
through the CRC generator.
— Once the read completes, the LSISS2520/LSISS2530 device compares the CRC
obtained from the original write and the subsequent read. If the CRC matches
then the LSISS2520/LSISS2530 device transmits a SCSI GOOD response to the
initiator. If there is a CRC mismatch, then the LSISS2520/LSISS2530 device
transmits a CHECK CONDITION response to the initiator along with the
calculated read and write CRC (CC response format).
NOTE: The CRC generation is only performed for the BYTCHK = 1 case. If the BYTCHK =
0, the LSISS2520/LSISS2530 device does not generate any CRC nor does the
LSISS2520/LSISS2530 device read the data from the device.

This field specifies the first logical block of the range of logical blocks for this
command.
 GROUP NUMBER
does not support Grouping.
 TRANSFER LENGTH
This field specifies the number of contiguous blocks of data to be transferred.

Chapter 4: SCSI Commands | WRITE AND VERIFY (12) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.48 WRITE AND VERIFY (12) This following table describes the WRITE AND VERIFY(12) command.
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = AEh
2:5 (MSB)
(LSB)
6:9 (MSB)
TRANSFER LENGTH
(LSB)
FOR MMC-4
11 CONTROL
correctly written.
See Section 4.47, WRITE AND VERIFY(10) for a description of the fields in this command.
4.49 WRITE AND VERIFY (16) This following table describes the WRITE AND VERIFY(16) command.
Bit
Byte
7 6 5 4 3 2 1 0
2:9 (MSB)
(LSB)
10:13 (MSB)
TRANSFER LENGTH
(LSB)
FOR MMC-4
15 CONTROL

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE BUFFER
correctly written. Data transferred from the application client includes user data as
required by the medium format.
See Section 4.47, WRITE AND VERIFY(10) for description of the fields in this command.
4.50 WRITE BUFFER The LSISS2520/LSISS2530 device translates the WRITE BUFFER SCSI command as per
the SAT specification guidelines.
Table 125: WRITE BUFFER CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 COMMAND CODE = 3Bh
1 RESERVED MODE
2 BUFFER ID
3:5 (MSB)
BUFFER OFFSET
(LSB)
6:8 (MSB)
(LSB)
9 CONTROL
The following table lists the various mode and buffer ID combinations supported by
the LSISS25x0 device. The device returns a Check condition status with INVALID FIELD
IN CDB if a Write Buffer command is received with a mode that it does not support.
Table 126: Valid Mode Field Values for LSISS25x0
LSISS2520/LSISS2530
Mode Description
device Support
00h Write combined header and data No
01h Vendor specific No
02h Write data Yes
04h Download microcode No
05h Download microcode and save Yes
06h Download microcode with offsets No
07h Download microcode with offsets and save Yes
0Ah Echo buffer No
0Eh Download microcode with offsets and defer activation No
0Fh Activate deferred microcode No
1Ah Enable expander communications protocol and Echo buffer No

Chapter 4: SCSI Commands | WRITE BUFFER LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 126: Valid Mode Field Values for LSISS25x0
LSISS2520/LSISS2530
Mode Description
device Support
1Bh Disable expander communications protocol No
1Ch Download application log No
03h Reserved No
08h - 09h No
0Bh - 0Dh No
10h - 19h No
1Dh - 1Fh —
4.50.1 Data (Mode 02h) The LSISS2520/LSISS2530 device supports Data Mode (02h) only if the connected
device supports ATA WRITE BUFFER.
The LSISS2520/LSISS2530 device does not support any buffer ID other than 0 in mode 2
(Data Mode).
The LSISS2520/LSISS2530 device only supports buffer offset set to 0 in this mode. For
any other buffer offset with mode 2, the command terminates with CHECK CONDITION
status and with the sense key set to ILLEGAL REQUEST and the ASC set to INVALID
FIELD IN CDB.
The PARAMETER LIST LENGTH field specifies the number of bytes transferred from the
Data-Out Buffer of the initiator to the drive.
4.50.2 Download Microcode and Save In this mode, if the Buffer ID = 0, the LSISS25x0 device performs the drive firmware
(Mode 05h) upgrade through a single Write Buffer command. See Section D.4, Drive Firmware
Upgrade for more details.
In this mode, if the buffer ID is set to 0xA, the LSISS25x0 device performs a Package
firmware upgrade. The package upgrades through a single Write Buffer command. See
Section D.5, Package Firmware Upgrade for information on the package firmware
upgrade.
4.50.3 Download Microcode with In this mode, if the buffer ID is set to 0, the LSISS25x0 device performs the drive
Offsets and Save (Mode 07h) firmware upgrade through multiple Write Buffer commands. See Section D.4, Drive
Firmware Upgrade for more details.
In this mode, if the buffer ID is set to 1, the LSISS25x0 device performs the firmware
upgrade. This LSISS2520/LSISS2530 firmware upgrade is considered an online upgrade
process. During this activity, the LSISS2520/LSISS2530 device I/O performance
degrades by not more than 50%. See Section D.1, Firmware Upgrade for information on
Non-disruptive LSIS25x0 firmware upgrade.
In this mode, if the buffer ID is set to 0xA, the LSISS25x0 device performs Package
firmware upgrade. The package upgrades through multiple Write Buffer commands.
See Section D.5, Package Firmware Upgrade for information on the package firmware
upgrade.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE LONG (10)
In this mode, if the buffer ID is set to 0x3, the LSISS25x0 device performs boot options
firmware upgrade. See Section D.3, Boot Option Image Upgrade for information on boot
options upgrade.
In this mode, Buffer ID 0xEF(Boot Loader upgrade) upgrades the Boot Loader of the
LSISS2520/LSISS2530 device. For details, see Section D.2, Boot Loader Image Upgrade.
4.51 WRITE LONG (10) The WRITE LONG (10) command requests that the LSISS2520/LSISS2530 device mark a
logical block or physical block as containing an error, or transfer data for a single logical
block or physical block from the Data-Out buffer and write it to the medium. The data
written is the same length and is in the same order as the data returned by the READ
LONG (10) command. The LSISS2520/LSISS2530 device writes the logical block or
physical block to the medium, and does not return GOOD status until the logical block
is written on the medium. If the underlying device does not support the SCT Long
Sector Access feature, then the LSISS2520/LSISS2530 device terminates the command
with CHECK CONDITION status, with sense key set to ILLEGAL REQUEST (0x05) and ASC
set to invalid command operation code (0x20), otherwise the LSISS2520/LSISS2530
device translates this command into a SATA SCT WRITE LONG command to the device.
Table 127: WRITE LONG 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE = 3FH
1 COR_DIS WR_UNCOR PBLOCK = 0 RESERVED OBSOLETE
2:5 (MSB)
(LSB)
6 RESERVED
7:8 (MSB)
(LSB)
9 CONTROL

Chapter 4: SCSI Commands | WRITE LONG (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 COR_DIS (correction disabled)

This bit set to 0 specifies that, when the specified logical block is read, the
LSISS2520/LSISS2530 device performs normal error recovery on that logical block.
This bit set to 1 specifies that, when the specified logical block is read, the SCSI
target device takes the following actions:
— Performs no error recovery on that logical block including any read error
recovery enabled by the Read-Write Error Recovery mode page.
— Performs no automatic reallocation of that logical block including any automatic
reallocation enabled by the Read-Write Error Recovery mode page.
— Does not consider errors on logical blocks to be informational exception
conditions as defined in the Information Exceptions Control mode page
(refer SPC-4).
— Returns a CHECK CONDITION status with the sense key set to MEDIUM ERROR
and the ASC set to READ ERROR - LBA MARKED BAD BY APPLICATION CLIENT.
This field specifies the logical block at which the WRITE LONG operation occurs.
 BYTE TRANSFER LENGTH
This field must exactly specify the number of bytes of data that are available for
transfer. If a nonzero byte TRANSFER LENGTH does not match the available data
length, the LSISS2520/LSISS2530 device terminates the command with CHECK
CONDITION status, the Sense Key is set to Illegal Request and an ASC set to Invalid
Field in CDB. The valid and ILI bits are set to 1 and the information field is set to the
difference of the requested length minus the actual length in bytes. Negative values
are indicated by two's complement notation.
The correction disabled (COR_DIS) bit, the write uncorrectable error (WR_UNCOR)
bit, and the physical block (PBLOCK) bit are defined in the following table.
NOTE: The LSISS2520/LSISS2530 device reports one logical block per physical block
(i.e., the LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT field in the READ CAPACITY
(16) data (see Section 4.21, READ CAPACITY (16)) is set to a zero value).
Table 128: WR_UNCOR bit and PBLOCK bit
COR_DIS (WR_UNCOR) PBLOCK

Description
(Correction Disable) Write Uncorrectable error (Physical Block)
0 0 0 Write only the specified logical block using the value in the BYTE TRANSFER
LENGTH field. The LSISS2520/LSISS2530 device supports this configuration.
0 1 0 The LSISS2520/LSISS2530 device marks only the specified logical block as
containing a pseudo unrecovered error with logging.
Ignore the BYTE TRANSFER LENGTH field, and transfer no data.
1 1 0 The LSISS2520/LSISS2530 device marks only the specified logical block as
containing a flagged error without logging.
Ignore the BYTE TRANSFER LENGTH field, and transfer no data.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE LONG (16)
4.52 WRITE LONG (16) The WRITE LONG (16) command requests that the LSISS2520/LSISS2530 device mark a
logical block or physical block as containing an error, or transfer data for a single logical
block or physical block from the Data-Out buffer and write it to the medium.
The LSISS2520/LSISS2530 device writes the logical block or physical block to the
medium, and does not return GOOD status until the logical block is written on the
medium. This command is implemented as a service action of the SERVICE ACTION
OUT operation code.
If the underlying device does not support the SCT Long Sector Access feature, then the
command into a SATA SCT WRITE LONG command to the device.
The following table lists the WRITE LONG 16 CDB.
Table 129: WRITE LONG 16 CDB
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE = 9Fh
1 COR_DIS WR_UNCOR PBLOCK SERVICE ACTION = 11h
2:9 (MSB)
(LSB)
10:11 RESERVED
12:13 (MSB)
(LSB)
14 RESERVED
15 CONTROL
See Section 4.51, WRITE LONG (10) for definitions of the fields in this command.

Chapter 4: SCSI Commands | WRITE SAME (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
4.53 WRITE SAME (10) The WRITE SAME (10) command requests that the LSISS2520/LSISS2530 device transfer
a single logical block from the Data-Out buffer and write the contents of that logical
block, with modifications based on the LBDATA bit, to the specified range of LBAs. Each
logical block address includes user data and can include protection information, based
on the WRPROTECT field and the medium format.
Table 130: WRITE SAME 10 CDB
Bit
Byte
7 6 5 4 3 2 1 0
1 WRPROTECT RESERVED PBDATA = 0 LBDATA RESERVED
2:5 (MSB)
(LSB)
6 RESERVED Group Number = 0
7:8 (MSB)
NUMBER OF BLOCKS
(LSB)
9 CONTROL

This field specifies the address at which the WRITE begins.
 NUMBER OF BLOCKS
This field specifies the number of contiguous blocks to be written. If the number is
0, write all the remaining blocks on the specified Logical Unit.
This command also supports the variable command time-out feature. See
Mode Page 32h (Firmware Parameter Control). The equation used for time-out
calculation is Time-out Value = (TRANSFER LENGTH / 32) + command time-out
specified in Mode page 0x01h.
 WRPROTECT
When the LSISS2520/LSISS2530 device is formatted to use protection information, it
follows table 85 in SBC3-r21 to verify the DIF fields in the incoming data.
 GROUP NUMBER
does not support grouping.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE SAME (16)
Table 131: Physical Block Data and Logical Block Data Values
LBDATA PBDATA
Description
(Logical Block Data) (Physical Block Data)
0 0 The LSISS2520/LSISS2530 device writes the single block of user data received from the Data-Out
buffer to each logical block without modification.
If the LSISS2520/LSISS2530 device is formatted for protection information, it follows the first row of
Table 98 in SBC2-r21 to specify the DIF data that is written to the medium.
1 0 The LSISS2520/LSISS2530 device replaces the first four bytes of the block received from the
Data-Out buffer with the least significant four bytes of the LBA of the block being written, ending
with the least significant byte.
If the LSISS2520/LSISS2530 device is configured for sector skewing, the LSISS2520/LSISS2530 device
terminates the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the ASC set to INVALID FIELD IN CDB.
0 1 The LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status with the
sense key set to ILLEGAL REQUEST and the ASC set to INVALID FIELD IN CDB.
1 1
4.54 WRITE SAME (16) The WRITE SAME (16) command requests that the LSISS2520/LSISS2530 device transfer
a single logical block from the Data-Out buffer and write the contents of that logical
block, with modifications based on the LBDATA bit, to the specified range of LBAs. Each
logical block address includes user data and can include protection information, based
on the WRPROTECT field and the medium format.
Bit
Byte
7 6 5 4 3 2 1 0
1 WRPROTECT RESERVED UNMAP = 0 PBDATA = 0 LBDATA OBSOLETE
2:9 (MSB)
(LSB)
10:13 (MSB)
NUMBER OF BLOCKS
(LSB)
15 CONTROL
The LSISS2520/LSISS2530 device does not support the UNMAP field.

This command also supports the variable command time-out feature described in the
WRITE SAME (10) command handler description. See Section 4.53, WRITE SAME (10) for
the definitions of the fields in this command.

4.55 WRITE SAME (32) The WRITE SAME (32) command requests that the device server transfer a single logical
block from the Data-Out buffer and write the contents of that logical block, with
modifications based on the LBDATA bit, to the specified range of LBAs. Each logical
block includes user data and can include protection information, based on the
WRPROTECT field and the medium format.
Bit
Byte
7 6 5 4 3 2 1 0
0 OPERATION CODE (7Fh)
1 CONTROL
2:5 RESERVED
(MSB)
8:9 SERVICE ACTION (000Dh)
(LSB)
10 WRPROTECT RESERVED UNMAP = 0 PBDATA = 0 LBDATA RESERVED
11 RESERVED
(MSB)
(LSB)
(MSB)
(LSB)
(MSB)
24:25 EXPECTED LOGICAL BLOCK APPLICATION TAG
(LSB)
(MSB)
(LSB)
(MSB)
28:31 NUMBER OF LOGICAL BLOCK
(LSB)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE SAME (32)
When the LSISS2520/LSISS2530 device is formatted to use protection information the

following fields are defined:
As defined in SBC3-r21 – 5.41.
As defined in SBC3-r21 – 5.41.
The LSISS2520/LSISS2530 device only supports the value of 0xFFFF for the logical
See Section 4.54, WRITE SAME (16) for the definitions of the other fields in this command.


LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters
Chapter 5
SCSI Parameters
This chapter describes the Mode, Log and VPD parameters.
5.1 Mode Parameters The LSISS2520/LSISS2530 device supports various SCSI and SAS mode parameters.
This section describes the mode parameters supported by the LSISS2520/LSISS2530
device in detail.
5.1.1 Mode Parameter Header The LSISS2520/LSISS2530 device mode parameters list format for Mode SENSE/SELECT
(6/10) is as follows.
Table 134: Mode Parameter List
BIT
Byte
7 6 5 4 3 2 1 0
MODE PARAMETER HEADER
BLOCK DESCRIPTOR
MODE PAGE(S)
The following table defines the MODE PARAMETER HEADER used by the MODE
SELECT(6) command and the MODE SENSE(6) command.
Table 135: Mode Parameter Header for Mode Sense 6/Mode Select 6 Commands
BIT
Byte
7 6 5 4 3 2 1 0
0 MODE DATA LENGTH
1 MEDIUM TYPE
2 DEVICE-SPECIFIC PARAMETER
3 BLOCK DESCRIPTOR LENGTH

Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The following table defines the MODE PARAMETER HEADER that is used by the MODE
SELECT(10) command and the MODE SENSE(10) command.
Table 136: Mode Parameter Header for Mode Sense 10/Mode Select 10 Commands
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
MODE DATA LENGTH
(LSB)
2 MEDIUM TYPE
3 DEVICE-SPECIFIC PARAMETER
4 RESERVED LONGLBA
5 RESERVED
6:7 (MSB)
BLOCK DESCRIPTOR LENGTH
(LSB)
 MODE DATA LENGTH

When using the MODE SENSE command, the MODE DATA LENGTH field indicates
the length in bytes of the following data that is available to be transferred. The
mode data length does not include the number of bytes in the MODE DATA LENGTH
field. When using the MODE SELECT command, this field is reserved.
 LONGLBA
The LSISS25x0 device supports both short LBA and long LBA format block descriptors.
The LSISS25x0 device returns the LONG LBA format block descriptor only for the
Mode Sense 10 command if the LONGLBAA bit in CDB is set and if the number of
logical blocks cannot be represented in short LBA format block descriptor.
For Mode Sense 10 commands, if the LONGLBA bit in the block descriptor is set, the
block descriptors in the following mode parameter data, if any, are in the long LBA
format.
For the Mode Select 10 command, if any discrepancy is detected in the LONGLBA
bit in the mode parameter header and following block descriptor length, the
LSISS25x0 device terminates the mode select command with a check condition
status and ASC/ASCQ set to invalid field in the parameter list.
 MEDIUM TYPE
The contents of the MEDIUM TYPE field are unique for each device type. Being the
block device, the LSISS2520/LSISS2530 device populates a zero value in this field.

 DEVICE SPECIFIC PARAMETER

This field for the LSISS2520/LSISS2530 device is defined in following table.
Table 137: DEVICE-SPECIFIC PARAMETER
Device Specific parameter
7 6 5 4 3 2 1 0
WP RESERVED DPOFUA RESERVED
 WP
When used with the MODE SELECT command, the write protect (WP) bit is not
defined. When used with the MODE SENSE command, a WP bit set to 1 indicates
that the medium is write-protected. The LSISS2520/LSISS2530 device does not
support this bit set to 1, and always returns a 0 value for it in the MODE SENSE
command return data.
 DPOFUA
When used with the MODE SELECT command, the DPOFUA bit is reserved. When
used with the MODE SENSE command, a DPOFUA bit set to 0 indicates that the
device server does not support the DPO and FUA bits. The LSISS2520/LSISS2530
device supports and sends out the DPOFUA bit set to 0. But, if the Disable DPO
Check bit within the Firmware Parameter Control Mode Page (32h) is set to 1, the
LSISS2520/LSISS2530 device sets the DPOFUA bit to 1.
 BLOCK DESCRIPTOR LENGTH
This field contains the length in bytes of all the block descriptors. The
LSISS2520/LSISS2530 device supports only one block descriptor in Short - LBA
format. Hence the value for BLOCK DESCRIPTOR LENGTH supported is 8 bytes only.
 MODE PARAMETER BLOCK DESCRIPTOR
The following table depicts the Short LBA format BLOCK DESCRIPTOR while
Table 139 depicts the Long LBA format BLOCK DESCRIPTOR supported by the
LSISS2520/LSISS2530 device.
Table 138: Short LBA Format BLOCK DESCRIPTOR
BIT
Byte
7 6 5 4 3 2 1 0
0:3 (MSB)
NUMBER OF LOGICAL BLOCKS
(LSB)
4 RESERVED
5:7 (MSB)
LOGICAL BLOCK LENGTH
(LSB)

 NUMBER OF LOGICAL BLOCKS

This field indicates the number of logical blocks present in the
 Logical BLOCK LENGTH
This field indicates the length in bytes of each logical block present with the given
Table 139: Long LBA Format BLOCK DESCRIPTOR
BIT
Byte
7 6 5 4 3 2 1 0
0:7 (MSB)
NUMBER OF BLOCKS
(LSB)
8:11 RESERVED
12:15 (MSB)
BLOCK LENGTH
(LSB)
5.1.2 Mode Page 00h (Supported Page 0 indicates the supported Mode pages. This page determines the additional
Mode pages) pages requested by an Initiator.
Table 140: Mode Page 00h
BIT
Byte
7 6 5 4 3 2 1 0
0 PS = 1b SPF = 0b PAGE CODE = 00h
1 PAGE LENGTH = 13h
2 FIRST SUPPORTED PAGE 00H
3 SECOND SUPPORTED PAGE 01H
4 THIRD SUPPORTED PAGE 02H
5 FOURTH SUPPORTED PAGE 07H
6 FIFTH SUPPORTED PAGE 08H
7 SIXTH SUPPORTED MODE PAGE 0AH
8 SEVENTH SUPPORTED PAGE 18H
9 EIGHTH SUPPORTED PAGE 19H
10 NINTH SUPPORTED PAGE 1AH
11 TENTH SUPPORTED PAGE 1CH
12 ELEVENTH SUPPORTED PAGE 25H
13 TWELFTH SUPPORTED PAGE 32H
14 THIRTEENTH SUPPORTED PAGE 34H
15 FOURTEENTH SUPPORTED PAGE 35H

Table 140: Mode Page 00h (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
16 FIFTEENTH SUPPORTED PAGE 36H
17 SIXTEENTH SUPPORTED PAGE 37H
18 SEVENTEENTH SUPPORTED PAGE 39H
19 EIGHTEENTH SUPPORTED PAGE 3AH
20 NINETEENTH SUPPORTED PAGE 3BH
5.1.3 Mode Page 01h (Read-Write This section describes Mode Page 01h.
Error Recovery Parameters)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS RESERVED PAGE CODE = 01h 81h
1 PAGE LENGTH = 0AH 0Ah
2 AWRE =1 ARRE=0 TB=0 RC=0 EER PER=0 DTE=0 DCR=0 88h
3 READ RETRY COUNT 08h
4:6 OBSOLETE 00h
7 RESERVED Restricted for MMC-6 00h

8 WRITE RETRY COUNT 04h
9 RESERVED 00h
10:11 (MSB) 1Fh
RECOVERY TIME LIMIT 40h
(LSB)
The Read-Write Error Recovery mode page specifies the error recovery parameters that
the LSISS2520/LSISS2530 device uses during any command that performs a read or
write operation to the medium (for example, READ, WRITE, WRITE AND VERIFY).
 AWRE
This bit set to 1 specifies that the LSISS2520/LSISS2530 device enables automatic
reallocation to be performed during write operations. AWRE bit is not changeable.
 ARRE
ARRE bit set to 0 specifies that the device server disables automatic reallocation of
defective logical blocks during read operations. AWRE bit is not changeable.

 TB
This bit set to 0 specifies that a logical block that is not recovered within the
recovery limits specified is not transferred to the initiator. A TB bit set to 1 specifies
that a logical block that is not recovered within the recovery limits specified is
transferred to the initiator before CHECK CONDITION status is returned. The
LSISS2520/LSISS2530 device does not support this bit set to 1.
 RC
This bit set to 0 specifies that error recovery operations that cause delays are
acceptable during the data transfer. Data is not fabricated. An RC bit set to 1
specifies the device server transfers the entire requested length of data without
adding delays to perform error recovery procedures. The LSISS2520/LSISS2530
device does not support this bit set to 1. The LSISS2520/LSISS2530 device allows this
field to be changed but the assignment does not translate into any behavior change.
 Enable Early Recovery (EER)
This bit set to 1 specifies that LSISS2520/LSISS2530 device uses the most expedient
form of error recovery first. An EER bit set to 0 specifies that the
LSISS2520/LSISS2530 device uses as error recovery procedure that minimizes the
risk of mis-detection or mis-correction. EER is not changeable.
 Post Error (PER)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device reports recovered
errors. A PER bit set to 0 specifies that the LSISS2520/LSISS2530 device does not
report recovered errors. Error recovery procedures is performed within the limits
established by the error recovery parameters. PER is not changeable.
 DTE
This bit set to 1 specifies that the LSISS2520/LSISS2530 device terminates the
data-in or Data-Out buffer transfer upon detection of a recovered error. A DTE bit set
to 0 specifies that the LSISS2520/LSISS2530 device does not terminate the data-in
or Data-Out buffer transfer upon detection of a recovered error. The
LSISS2520/LSISS2530 device supports 0h condition only.
 Disable correction (DCR)
This bit set to 1 specifies that error correction codes is not used for data error
recovery. A DCR bit set to 0 allows the use of error correction codes for data error
recovery. The LSISS2520/LSISS2530 device supports 0h condition only.
 READ RETRY COUNT
This field specifies the number of times the recovery algorithm is attempted during
the read operation. The LSISS2520/LSISS2530 device does not support this feature
and returns a value 8 for it.
 WRITE RETRY COUNT
This field specifies the number of times the recovery algorithm is attempted during
the write operation. The LSISS2520/LSISS2530 device does not support this feature
and returns a value 4 for it.

 RECOVERY TIME LIMIT

This field specifies in milliseconds the maximum time duration that the
LSISS2520/LSISS2530 device uses for data error recovery procedures. The default
value is 1F40h (8 seconds). This is the command time-out for the
LSISS2520/LSISS2530 device. If the user tries to set this field to a value of 0, then the
LSISS2520/LSISS2530 device configures it to the default value (1F40h).
NOTE: Modify this field with caution, since, if a very small value is used, the
LSISS2520/LSISS2530 device can time out every command that it receives, and the
LSISS2520/LSISS2530 device can become unusable.
5.1.4 Mode Page 02h This section describes the Mode Page 02h.
(Disconnect/Reconnect Parameters)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0b) PAGE CODE = 02h 82h
1 PAGE LENGTH= 0Eh 0Eh
2 RESERVED 00h
3 RESERVED 00h
4:5 (MSB) 00h
BUS INACTIVITY TIME LIMIT
(LSB)
6:7 RESERVED 00h
8:9 (MSB) 00h
MAXIMUM CONNECT TIME LIMIT
(LSB)
10:11 (MSB) 00h
MAXIMUM BURST SIZE
(LSB)
12 RESERVED 00h
13 RESERVED 00h
14:15 (MSB) 00h
FIRST BURST SIZE
(LSB)
The Disconnect/Reconnect mode page enables the initiator to tune the performance of
the transmission medium.

 BUS INACTIVITY TIME LIMIT

The value in this field contains the maximum time in 100-μs increments that an SSP
target port is permitted to maintain a connection without transferring a frame to
the SSP initiator port. If this time elapses, the SSP target port prepares to close the
connection by requesting the link layer transmit DONE.
 MAXIMUM CONNECT TIME LIMIT
The value in the MAXIMUM CONNECT TIME LIMIT field contains the maximum
duration of a connection in 100-μs increments.
If this time elapses, the SSP target port prepares to close the connection. If the
MAXIMUM CONNECTION TIME LIMIT has elapsed while transferring a frame, the SSP
target port completes transferring the frame before closing the connection. Round
up this value as defined in SCSI Primary Commands - 4 (SPC - 4). A value of 0000h
indicates that there is no MAXIMUM CONNECTION TIME LIMIT. The port layer
enforces the MAXIMUM CONNECTION TIME LIMIT.
 MAXIMUM BURST SIZE
For read data, the value in the MAXIMUM BURST SIZE field contains the maximum
amount of data that the target port transfers during a single data transfer operation.
The data transferred during a connection consists of data for a single I_T_L_Q nexus.
The SSP target port prepares to close the connection on transferring the amount of
data, as specified by the MAXIMUM BURST SIZE field to the SSP initiator port, when
both of these conditions exist.
— The SSP target port has read data to transfer for only one I_T_L_Q nexus.
— The SSP target port has no requests to transfer write data for any I_T_L_Q nexus.
For write data, the value specifies the maximum amount of data that an SSP target
port requests through a single XFER_RDY frame.
This value is in 512-byte increments. For example, a value of 1 in this field indicates
that the number of bytes allowed for the SSP initiator port for the nexus is less than or
equal to 512. A value of 2 in this field indicates that the number of bytes allowed for
the SSP initiator port for the nexus is less than or equal to 1024. Internally, the only
values supported are a 32K or a 16K burst size. Nonzero values less than 64 (32K bytes)
results in a burst size of 16K. Values greater than or equal to 64 result in a burst size of
32K. A value of 0 in this field indicates that there is no MAXIMUM BURST SIZE.
 FIRST BURST SIZE
The LSISS2520/LSISS2530 device does not support Enable FIRST BURST for
command frames and hence does not support this field.

5.1.5 Mode Page 07h (Verify Error This section describes Mode Page 07h.
Recovery Parameters)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS RESERVED PAGE CODE = 07h 87h
1 PAGE LENGTH = 0Ah 0Ah
2 RESERVED EER = 0 PER = 0 DTE = 0 DCR = 0 00h
3 VERIFY RETRY COUNT = 0 00h
4 OBSOLETE 00h
5:9 RESERVED 00h
10:11 (MSB) 1Fh
VERIFY RECOVERY TIME LIMIT 40h
(LSB)
The Verify Error Recovery mode page specifies the error recovery parameters that the
LSISS2520/LSISS2530 device uses during the VERIFY command and the verify operation
of the WRITE AND VERIFY command.
 Enable Early Recovery (EER)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device uses the most
expedient form of error recovery first. An EER bit set to 0 specifies that the
LSISS2520/LSISS2530 device uses as error recovery procedure that minimizes the
risk of mis-detection or mis-correction. The LSISS2520/LSISS2530 device does not
support this bit set to 1.
 Post Error (PER)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device reports recovered
errors. A PER bit set to 0 specifies that the LSISS2520/LSISS2530 device does not
report recovered errors. Error recovery procedures is performed within the limits
established by the error recovery parameters. The LSISS2520/LSISS2530 device does
not support this bit set to 1.
 DTE
This bit set to 1 specifies that the LSISS2520/LSISS2530 device terminates the
data-in or Data-Out buffer transfer upon detection of a recovered error. A DTE bit set
to 0 specifies that the LSISS2520/LSISS2530 device does not terminate the data-in
or Data-Out buffer transfer upon detection of a recovered error. The
 Disable correction (DCR)
This bit set to 1 specifies that error condition codes are not used for data error
recovery. A DCR bit set to 0 allows the use of error condition codes for data error
recovery. The LSISS2520/LSISS2530 device does not support this bit set to 1.

 VERIFY RETRY COUNT

This field specifies the number of times that the LSISS2520/LSISS2530 device
attempts its recovery algorithm during a verify operation. This field is not
changeable. The LSISS2520/LSISS2530 device returns a zero value for it.
 VERIFY RECOVERY TIME LIMIT
This field specifies in milliseconds the maximum time duration that the
LSISS2520/LSISS2530 device uses for data error recovery procedures. The default
value is 1F40h (8 seconds).
5.1.6 Mode Page 08h (Caching This section describes Mode Page 08h.
Parameters)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS RESERVED PAGE CODE = 08H 88H
1 PAGE LENGTH 12H
2 IC=0 ABPF=0 CAP=0 DISC SIZE=0 WCE MF=0 RCD=0 00H
3 DEMAND READ RETENTION PRIORITY= 0H WRITE RETENTION PRIORITY = 0H 00H
4:5 (MSB) 00H
DISABLE PRE-FETCH TRANSFER LENGTH = 0H
(LSB)
6:7 (MSB) 00H
MINIMUM PRE-FETCH
(LSB)
8:9 (MSB) 00H
MAXIMUM PRE-FETCH
(LSB)
10:11 (MSB) 00H
MAXIMUM PRE-FETCH CEILING
(LSB)
12 FSW LBCSS=0 DRA VENDOR SPECIFIC RESERVED NV_DIS = 1 01H
13 NUMBER OF CACHE SEGMENTS 00H

14:15 (MSB) 00H
CACHE SEGMENT SIZE = 00H
(LSB)
16 RESERVED 00H
17:19 OBSOLETE 00H

The Caching Parameters page defines parameters that affect the use of the cache.
 Initiator Control (IC) Enable
This bit set to 1 specifies that the LSISS2520/LSISS2530 device use the NUMBER OF
CACHE SEGMENTS field or the CACHE SEGMENT SIZE field, dependent upon the
SIZE bit, to control the caching algorithm rather than the LSISS2520/LSISS2530
device's own adaptive algorithm. The LSISS2520/LSISS2530 device does not
 Abort pre-fetch (ABPF)
This bit set to 1 with the DRA bit set to 0, specifies that the LSISS2520/LSISS2530
device abort a prefetch upon receipt of a new command. An ABPF bit set to 1 takes
precedence over the value specified in the MINIMUM PRE-FETCH field. An ABPF bit
set to 0, with the DRA bit set to 0, specifies that the termination of any active
prefetch is dependent upon Caching mode page bytes 4 through 11 and is
operation and/or vendor-specific. The LSISS2520/LSISS2530 device does not
 Caching Analysis Permitted (CAP)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device perform caching
analysis during subsequent operations. A CAP bit set to 0 specifies that caching
analysis be disabled to reduce overhead time or to prevent vague operations from
impacting tuning values. The LSISS2520/LSISS2530 device does not support this bit
set to 1.
 Discontinuity (DISC)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device continue the prefetch
across time discontinuities (for example, across cylinders) up to the limits of the
buffer, or segment, space available for the prefetch. A DISC bit set to 0 specifies that
prefetches be truncated or wrapped at time discontinuities. The
 Size Enable (SIZE)
This bit set to 1 specifies that the CACHE SEGMENT SIZE field be used to control
caching segmentation. A SIZE bit set to 0 specifies that the NUMBER OF CACHE
SEGMENTS field be used to control caching segmentation. The
 WCE (Write Cache Enable)
This bit set at zero indicates that the LSISS2520/LSISS2530 device must issue GOOD
status for WRITE (6) or WRITE (10) command only after successfully writing the data
to the media. When the WCE bit is set to 1, the LSISS2520/LSISS2530 device can
issue GOOD status for a WRITE (6) or WRITE (10) command after successfully
receiving the data but before writing it to the media. The LSISS2520/LSISS2530
device sends out the ATA_SET_FEATURES command to enable/disable write cache
when the initiator modifies WCE to ON/OFF respectively.

 A Multiplication Factor (MF)

This bit set to 0 specifies that the LSISS2520/LSISS2530 device interprets the
MINIMUM and MAXIMUM PRE-FETCH fields in terms of the number of logical blocks
for each of the respective types of prefetch. The LSISS2520/LSISS2530 device does
not support this bit set to 1.
 Read Cache Disable (RCD)
This bit set to 0 specifies that the LSISS2520/LSISS2530 device returns data
requested by a READ command by accessing either the cache or medium. The
 DEMAND READ RETENTION PRIORITY
This field specifies the LSISS2520/LSISS2530 device the retention priority to assign
for data read into the cache that has also been transferred from the logical unit to
the application client. The LSISS2520/LSISS2530 device does not support this bit set
to 1.
 WRITE RETENTION PRIORITY
This field advises the LSISS2520/LSISS2530 device, the retention priority to assign
for data written into the cache that has also been transferred from the cache
memory to the medium. The LSISS2520/LSISS2530 device supports only the 0h
condition.
Value Description
0h The LSISS2520/LSISS2530 device does not distinguish between retaining the
indicated data and data placed into the cache memory by other means (For
example, prefetch).
1h Demand read retention priority: Data put into the cache through a READ command
is replaced sooner (that is, has lower priority) than data placed into the cache by
other means (for example, prefetch).
Write retention priority: Data put into the cache during a WRITE or WRITE AND
VERIFY command is replaced sooner (that is, has lower priority) than data placed
into the cache by other means (for example, prefetch).
2h - Eh RESERVED
Fh Demand read retention priority: Data put into the cache through a READ command
is not replaced if there is other data in the cache that was placed into the cache by
other means (for example, prefetch) and it is replaced (that is, it is not locked). Write
retention priority: Data put into the cache during a WRITE or WRITE AND VERIFY
command is not replaced if there is other data in the cache that was placed into the
cache by other means (for example, prefetch) and it is replaced (that is, it is not
locked).
 DISABLE PRE-FETCH TRANSFER LENGTH

This field specifies the selective disabling of anticipatory prefetch on long
transfer lengths. The LSISS2520/LSISS2530 device does not support nonzero value
for this field.

 MINIMUM PRE-FETCH
This field specifies either a number of blocks or a scalar multiplier of the TRANSFER
LENGTH, depending upon the setting of the MF bit. In either case, the resulting
number of blocks is the number to prefetch regardless of the delays it might cause
in processing subsequent commands. The LSISS2520/LSISS2530 device keeps the
default value as 0.
 MAXIMUM PRE-FETCH
This field specifies either a number of blocks or a scalar multiplier of the TRANSFER
LENGTH, depending upon the setting of the MF bit. In either case, the resulting
number of blocks is the number to prefetch if the prefetch does not delay
processing of subsequent commands. The MAXIMUM PRE-FETCH field contains the
maximum amount of data to prefetch into the cache as a result of one READ
command. The field is non changeable and the LSISS2520/LSISS2530 device keeps
the default value as 0.
 MAXIMUM PRE-FETCH CEILING
This field specifies an upper limit on the number of logical blocks computed as the
maximum prefetch. The field is non changeable and the LSISS2520/LSISS2530
device keeps the default value as 0.
 Force Sequential Write (FSW)
This bit set to 1 specifies that multiple block writes are to be transferred from the
initiator Data-Out buffer and written to the medium in an ascending, sequential,
logical block order. An FSW bit set to 0 specifies that the LSISS2520/LSISS2530
device is allowed to reorder the sequence of writing addressed logical blocks in
order to achieve a faster command completion. The LSISS2520/LSISS2530 device
does not support this bit set to 1.
 Logical Block Cache Segment Size (LBCSS)
This bit set to 1 specifies that the CACHE SEGMENT SIZE field units is interpreted as
logical blocks. A LBCSS bit set to 0 specifies that the CACHE SEGMENT SIZE field
units is interpreted as bytes. The LSISS2520/LSISS2530 device does not support this
bit set to 1.
 Disable Read-Ahead (DRA)
This bit set to 1 specifies that the LSISS2520/LSISS2530 device does not read into
the buffer any logical blocks beyond the addressed logical blocks. A DRA bit set to 0
specifies that the LSISS2520/LSISS2530 device continues to read logical blocks into
the buffer beyond the addressed logical blocks. The LSISS2520/LSISS2530 device
supports this bit set to both 0 and 1. The LSISS2520/LSISS2530 device sends out the
command ATA_SET_FEATURES with look ahead disabled/enabled depending on
whether DRA is set to 0 or 1 respectively.
 NV_DIS
This bit set to 1 specifies that the LSISS2520/LSISS2530 device disables a
non-volatile cache and indicates that a non-volatile cache is supported but
disabled. An NV_DIS bit set to 0 specifies that the LSISS2520/LSISS2530 device uses
a non-volatile cache and indicates that a non-volatile cache is present and enabled.
The LSISS2520/LSISS2530 device does not support this bit set to 0.

 NUMBER OF CACHE SEGMENTS

This field specifies the number of segments into which the LSISS2520/LSISS2530
device divides the cache. The LSISS2520/LSISS2530 device does not support this field.
 CACHE SEGMENT SIZE
This field specifies the segment size in bytes. The CACHE SEGMENT SIZE field is valid
only when the SIZE bit is set to 1. The LSISS2520/LSISS2530 device does not support
this field.
5.1.7 Mode Page 0Ah (Control Mode This section describes Mode Page 0Ah.
Page Parameters)
Table 145: Mode Page 0Ah
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0b) PAGE CODE = 0Ah 8Ah
2 TST = 000b TMF_ONLY = 0 RESERVED D_SENSE GLTSD = 0 RLEC 00h
3 QUEUE ALGORITHM MODIFIER = 1h RESERVED QErr = 00b OBSOLETE 10h
4 VS RAC = 0 UA_INTLCK_CTRL = 00b SWP = 0b OBSOLETE 00h
5 ATO TAS = 1 RESERVED AUTOLOAD MODE = 000b C0h
6:7 OBSOLETE 00h
00h
8:9 (MSB) FFh
BUSY TIMEOUT PERIOD = FF FFh
(LSB)
10:11 (MSB) 00h
EXTENDED SELF-TEST ROUTINE COMPLETION TIME = 0X00 03h
(LSB)

Following are the parameter options for Page 0A of MODE SELECT.

 QUEUE ALGORITHM MODIFIER
This field specifies restrictions on the algorithm used for re-ordering commands
that are tagged with the SIMPLE QUEUE TAG task attribute.
— 0h: Restricted re-ordering: The target re-orders the actual execution sequence of
the queued commands from each initiator such that data integrity is maintained
for that initiator. The LSISS2520/LSISS2530 device does not support this field set
to 0.
— 1h: Unrestricted re-ordering allowed: The target re-orders the actual execution
sequence of the queued commands in any manner it selects. Any data integrity
exposures related to command sequence order are explicitly handled by the
initiator through the selection of appropriate commands and queue task codes.
The LSISS2520/LSISS2530 device supports this unrestricted re-ordering.
— 2h-7h: RESERVED
— 8h-Fh: RESERVED
 Queue Error Management (QErr)
This field specifies how the LSISS2520/LSISS2530 device handles blocked tasks
when another task receives a CHECK CONDITION status. The LSISS2520/LSISS2530
device supports QErr=0 and QErr =1 only.
Table 146: QErr Values
QErr Value Description

00b All tasks other than the task that received the CHECK CONDITION status is processed as if no error occurred.
01b When TAS bit = 1, all the affected tasks in the task set for I_T NEXUSs (other than the I_T NEXUS for which the CHECK CONDITION
status was sent) are completed with TASK ABORTED status and no unit attention is established. For the I_T NEXUS to which the
CHECK CONDITION status is sent, no status is sent for the tasks that are aborted.
 BUSY TIMEOUT PERIOD

This field is set to 0xFFFF by LSISS25x0 and is ignored by the LSISS2520\LSISS2530
device.
 EXTENDED SELF-TEST ROUTINE COMPLETION TIME
This field is an advisory parameter that an initiator uses to determine the time in
seconds that the target requires to complete self-test routine when the target is not
interrupted by an initiator and no errors occur during execution of the self-test
routine. The LSISS2520/LSISS2530 device currently keeps the default value for this as
3. This value needs to be calculated for drives that have the SMART feature. In case of
mode select, this field is Don’t care and is valid only on the SMART enabled device.

 Task Set Type (TST)

This field specifies the type of task set in the logical unit. Task set type (TST) field
Code Description
000b The logical unit maintains one task set for all I_T NEXUSs
001b The logical unit maintains separate task sets for each I_T NEXUS
010b -111b RESERVED
The LSISS2520/LSISS2530 device supports 000b condition for TST.

 TMF_ONLY
This bit set to 0 specifies that the LSISS2520/LSISS2530 device processes tasks with
the ACA task attribute received on the faulted I_T NEXUS when an ACA condition
has been established. The LSISS2520/LSISS2530 device does not support ACA
condition. Therefore, this field is non changeable and set to 0 by default.
 D_SENSE
This bit set to 0 specifies that the LSISS2520/LSISS2530 device returns the fixed
format sense data when returning sense data in the same I_T_L_Q NEXUS
transaction as a CHECK CONDITION status.
This bit set to 1 specifies that the LSISS2520/LSISS2530 device returns the descriptor
format sense data when returning sense data in the same I_T_L_Q NEXUS
transaction as a CHECK CONDITION status.
 Global Logging Target Save Disable (GLTSD)
This bit set to 0 specifies that the logical unit implicitly saves, at vendor-specific
intervals, each log parameter in which the TSD bit is set to 0. A GLTSD bit set to 1
specifies that the logical unit does not implicitly save any log parameters. The
LSISS2520/LSISS2530 device saves the log parameters at vendor-specific intervals.
The field is non changeable and set to 0 by default.
 Task Aborted Status (TAS)
This bit set to 0 specifies that aborted tasks are terminated by the
LSISS2520/LSISS2530 device without any response to the initiator. A TAS bit set to 1
specifies that tasks aborted by the actions of an I_T NEXUS other than the I_T
NEXUS on which the command was received is terminated with a TASK ABORTED
status. The LSISS2520/LSISS2530 device supports TAS bit condition set to 1 only.
 Report A Check (RAC)
This bit provides control of reporting long busy conditions or CHECK CONDITION
status. A RAC bit set to 1 specifies that the LSISS2520/LSISS2530 device returns
CHECK CONDITION status rather than returning BUSY status if the reason for
returning the BUSY status persists for a longer time than that specified by the BUSY
TIMEOUT PERIOD field. A RAC bit set to 0 specifies that the LSISS2520/LSISS2530
device returns BUSY status regardless of the length of time for returning BUSY
status. The LSISS2520/LSISS2530 device supports bit set to 0 condition.

 Unit Attention Interlocks Control (UA_INTLCK_CTRL)

This field controls the clearing of unit attention conditions reported in the same
I_T_L_Q NEXUS transaction as a CHECK CONDITION status and whether returning a
status of BUSY, TASK SET FULL or RESERVATION CONFLICT results in the
establishment of a unit attention condition. The LSISS2520/LSISS2530 device
supports bit set to 00 condition only.
Table 147: Unit Attention Interlocks Control (UA_INTLCK_CTRL) Field
Code Definition
00b The logical unit clears any unit attention condition reported in the same
I_T_L_Q NEXUS transaction as a CHECK CONDITION status and does not
establish a unit attention condition when a task is terminated with BUSY,
TASK SET FULL, or RESERVATION CONFLICT status.
01b RESERVED
10b The logical unit does not clear any unit attention condition reported in the
same I_T_L_Q NEXUS transaction as a CHECK CONDITION status and does
not establish a unit attention condition when a task is terminated with
BUSY, TASK SET FULL, or RESERVATION CONFLICT status.
11b The logical unit does not clear any unit attention condition reported in
the same I_T_L_Q NEXUS transaction as a CHECK CONDITION status and
establishes a unit attention condition for the initiator port associated with
the I_T NEXUS on which the BUSY, TASK SET FULL, or RESERVATION
CONFLICT status is being returned. Depending on the status, the ASC is
set to PREVIOUS BUSY STATUS, PREVIOUS TASK SET FULL STATUS, or
PREVIOUS RESERVATION CONFLICT STATUS. Until it is cleared by a
REQUEST SENSE command, a unit attention condition is established only
once for a BUSY, TASK SET FULL, or RESERVATION CONFLICT status
regardless to the number of commands terminated with one of those
status values.
 Software Write Protect (SWP)

This bit set to 1 specifies that the logical unit inhibits writing to the medium after
writing all cached or buffered write data, if any. When SWP is 1 and the device type's
command standard defines a write protect (WP) bit in the DEVICE-SPECIFIC
PARAMETER field in the mode parameter header, the WP bit is set to 1 for
subsequent MODE SENSE commands. The LSISS2520/LSISS2530 device does not
support SWP set to 1 condition.

 AUTOLOAD MODE
This field specifies the action to be taken by a removable medium device server
when a medium is inserted. For devices other than removable medium devices, this
field is reserved. The following table shows the usage of the AUTOLOAD MODE field.
The LSISS2520/LSISS2530 device supports 000b mode only.
Table 148: AUTOLOAD MODE field
Code Definition
000b Medium is loaded for full access.
001b Medium is loaded for medium auxiliary memory access only.
010b Medium is not loaded.
011b - 111b RESERVED
 Report log exception condition (RLEC)

This bit set to 1 specifies that The LSISS2520/LSISS2530 device reports log exception
conditions. A RLEC bit set to 0 specifies that the LSISS2520/LSISS2530 device does
not report log exception conditions. The LSISS2520/LSISS2530 device does not
support this bit condition set to 1.
 VS
This is a vendor-specific bit.
 Application tag owner (ATO)
This bit set to 1 specifies that the contents of the LOGICAL BLOCK APPLICATION TAG
field in the protection information, if any, are not be modified by the
LSISS2520/LSISS2530 device. An ATO bit set to 0 specifies that the contents of the
LOGICAL BLOCK APPLICATION TAG field in the protection information is modified by
the LSISS2520/LSISS2530 device. If the ATO bit is set to 0, then the
LSISS2520/LSISS2530 device ignores the contents of the LOGICAL BLOCK
APPLICATION TAG field in the protection information when received from the
initiator. Though the field is changeable, the LSISS2520/LSISS2530 device does not
support this functionality.

5.1.7.1 Mode Page 0Ah – The following section describes Mode Page 0Ah – Subpage 01h.
Subpage 01h
Table 149: Mode Page 0Ah, Subpage 01h – Control Extension Mode Page
Bit
Byte Default
7 6 5 4 3 2 1 0
0 PS (1b) SPF (1b) PAGE CODE (0Ah) CAh
1 SUBPAGE CODE (01h) 01h
2:3 PAGE LENGTH (001Ch) 00h
1Ch
4 RESERVED TCMOS = 0b SCSIP = 1B IALUAE = 0b 02h
5 RESERVED INITIAL COMMAND PRIORITY = 0h 00h
6:31 RESERVED 00h
This is a read-only mode page and the LSISS2520/LSISS2530 device does not support
modification of any of the parameters within this mode page.
 Timestamp Changeable by Methods Outside SPC Standard (TCMOS)
The value of this bit is reported as 0, indicating that the timestamp is not changed
by any method except those defined by the applicable SPC standard.
 SCSI Precedence (SCSIP)
The value of this bit is reported as 1, indicating that the timestamp changed using
SET TIMESTAMP command takes precedence over the methods outside the scope
of the applicable SPC standard.
 Implicit Asymmetric Logical Unit Access Enabled (IALUAE)
The LSISS2520/LSISS2530 device does not support this field. The value of this field is
reported as zero.
 INITIAL COMMAND PRIORITY
The LSISS2520/LSISS2530 device does not support this field. The value of this field is
reported as zero.

5.1.8 Mode Page 18h The mode page is a read-only mode page since the LSISS2520/LSISS2530 device does
(Protocol-Specific Logical Unit Mode not support changing the parameters of this mode page.
Page for SAS SSP)
Table 150: Mode Page 18h - Protocol-Specific Logical Unit Mode Page for SAS SSP
Bit
Byte Default
7 6 5 4 3 2 1 0
1 PAGE LENGTH = 06h 06h
2 RESERVED TRANSPORT LAYER RETRIES PROTOCOL IDENTIFIER (6h) 06h
3:7 RESERVED 00h
The PROTOCOL IDENTIFIER is set to value 6h. This indicates SAS as the underlying
transport protocol.
 TRANSPORT LAYER RETRIES
5.1.9 Mode Page 19h This section describes the Mode page 19 and various subpages within the mode
(Protocol-Specific Port Mode Page for page 19h.
SAS SSP)
5.1.9.1 Mode Page 19 This section describes Mode Page 19.
Table 151: Mode Page 19h - Protocol-Specific Port Mode Page for SAS SSP
BIT
Byte Default
7 6 5 4 3 2 1 0
1 PAGE LENGTH = 0Eh 0Eh
2 RESERVED CONTINUE BROADCAST READY LED PROTOCOL IDENTIFIER (6h) 26h
AWT ASYNCHRONOUS EVENT MEANING
3 RESERVED 00h
4:5 (MSB) 07h
I_T NEXUS LOSS TIME D0h
(LSB)
6:7 (MSB) 00h
INITIATOR RESPONSE TIMEOUT
(LSB)
8:9 (MSB) 00h
REJECT TO OPEN LIMIT
(LSB)
10:15 RESERVED 00h

The Protocol-Specific Port mode page contains parameters that affect the SSP target
port operation.
 A CONTINUE AWT
This bit set to 1 specifies that the SAS port does not stop the Arbitration Wait Time
timer and set the Arbitration Wait Time timer to zero when the SAS port receives an
OPEN_REJECT (RETRY).
A CONTINUE AWT bit set to 0 specifies that the SAS port stops the Arbitration Wait
Time timer and sets the Arbitration Wait Time timer to zero when it receives an
OPEN_REJECT (RETRY).
 A BROADCAST ASYNCHRONOUS EVENT
This bit set to 1 specifies that the device server enables the origin of Broadcast
(Asynchronous Event).
This bit set to 0 specifies that the device server disables the origin of Broadcast
(Asynchronous Event).
 READY LED MEANING
This bit specifies the READY LED signal behavior. Regardless of the mode page
policy, the shared mode page policy applies to the READY LED MEANING bit. Refer
SAS-2 standard.
When the bit is 0, and the device is in a ready state, the LED is usually on, but flashes
on and off when commands are processed. When the bit is 1, the LED is usually off,
but flashes on and off when commands are processed.
The field is set to value 6h. This indicates SAS as the underlying transport protocol.
 I_T NEXUS LOSS TIME
This field contains the time that the SSP target port retries the connection requests
to an SSP initiator port. The rejected responses indicate that the SSP initiator port is
no longer present before recognizing an I_T NEXUS loss. The following table defines
the I_T NEXUS LOSS TIME field values. The port layer enforces I_T NEXUS LOSS TIME
field values. The default time is 2000 ms.
Table 152: I_T NEXUS LOSS TIME field
Code Description
0000h Vendor-specific amount of time.
0001h to FFFEh Time in ms
FFFFh The SSP target port never recognizes an I_T NEXUS loss.
This indicates that it retries the connection requests forever.

 REJECT TO OPEN LIMIT

This field contains the minimum time in 10-μs increments that the target port waits
to establish a connection request with an initiator port on an I_T NEXUS after
receiving an OPEN_REJECT (RETRY), OPEN_REJECT (RESERVED CONTINUE 0), or
OPEN_REJECT (RESERVED CONTINUE 1). This value can be rounded as defined in
SPC-4.
A REJECT TO OPEN LIMIT field set to 0000h indicates that the minimum time is
VENDOR SPECIFIC. This minimum time is enforced by the port layer.
The supported values for this field range from 0 to 128.
 INITIATOR RESPONSE TIMEOUT
5.1.9.2 Mode Page 19 - This section describes Mode Page 19 - Subpage 1.

Subpage 1
Table 153: Mode Page 19h - PHY Control And Discover Mode Page
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE (19h) D9h
2:3 PAGE LENGTH (0064h) 00h
64h
4 RESERVED 00h
5 RESERVED PROTOCOL IDENTIFIER (6h) 06h
6 GENERATION CODE 00h
7 NUMBER OF PHYS (02h) 02h
8:55 SAS PHY MODE DESCRIPTOR for PHY 0. See Table 154. —
56:103 SAS PHY MODE DESCRIPTOR for PHY 1. See Table 154. —
transport protocol.
 NUMBER OF PHYS
The NUMBER OF PHYS indicates the number of SAS PHYs on the
LSISS2520/LSISS2530 device. This field is set to 2.

 GENERATION CODE
The LSISS2520/LSISS2530 device sets the GENERATION CODE to the 0 value.
Table 154: SAS PHY Mode Descriptor
BIT
Byte Default
7 6 5 4 3 2 1 0
0 RESERVED 00h
1 PHY IDENTIFIER —
2:3 RESERVED 00h
4 RESERVED ATTACHED DEVICE TYPE ATTACHED REASON —
5 REASON NEGOTIATED LOGICAL LINK RATE —
6 RESERVED ATTACHED SSP ATTACHED STP ATTACHED RESERVED —
INITIATOR INITIATOR SMP INITIATOR
PORT PORT PORT
7 RESERVED ATTACHED SSP ATTACHED STP ATTACHED RESERVED —
TARGET PORT TARGET PORT SMP TARGET
PORT
8:15 SAS ADDRESS —
16:23 ATTACHED SAS ADDRESS —
24 ATTACHED PHY IDENTIFIER —
25:31 RESERVED 00h
32 PROGRAMMED MINIMUM PHYSICAL LINK HARDWARE MINIMUM PHYSICAL LINK RATE 08h
RATE
33 PROGRAMMED MAXIMUM PHYSICAL LINK HARDWARE MAXIMUM PHYSICAL LINK RATE AAh
RATE
34:41 RESERVED 00h
42:43 VENDOR SPECIFIC 00h
44:47 RESERVED 00h
 ATTACHED DEVICE TYPE

This field indicates the device type attached to this PHY and is defined in the
following table.
Code Description
000 No device attached
001 SAS or SATA device
010 Expander device
All Others RESERVED

 ATTACHED REASON
This field indicates the value of the REASON field received in the IDENTIFY address
frame during the identification sequence.
The REASON field indicates the reason for the link reset sequence and is defined in
following table.
Table 155: REASON Codes
Code Description
0000 Unknown Reason.
0001 Power On.
0010 Hard Reset.
0011 SMP link Reset.
0100 Loss of D-Word Synchronization.
0101 MUX Received.
0110 I_T NEXUS time-out timer expired.
0111 Break time-out timer expired.
1000 PHY test function stopped.
1001 Expender Device Reduced Functionality.
All Others RESERVED
 NEGOTIATED LOGICAL LINK RATE

This field indicates the logical link rate being used by the phy. The value is
negotiated during the link reset sequence.
Table 156: Logical Link Rate Values
Link Rate Value

6 Gbps Ah
3 Gbps 9h
1.5 Gbps 8h
The LSISS2520/LSISS2530 device sets the following six fields to the value obtained
in the IDENTIFY address frame during the identification sequence.
 ATTACHED SSP INITIATOR PORT
 ATTACHED STP INITIATOR PORT
 ATTACHED SMP INITIATOR PORT
 ATTACHED SSP TARGET PORT
 ATTACHED STP TARGET PORT
 ATTACHED SMP TARGET PORT
 SAS ADDRESS
The address of the PHY is populated by LSISS2520/LSISS2530 device.

 ATTACHED SAS ADDRESS

This field contains the value of the SAS ADDRESS field received in the IDENTIFY
address frame during the identification sequence.
 PROGRAMMED MINIMUM PHYSICAL LINK RATE
This field specifies the minimum physical link rate that the PHY supports during a
link reset sequence. See the following table.
 The PROGRAMMED MAXIMUM PHYSICAL LINK RATE
This field specifies the MAXIMUM PHYSICAL LINK RATEs that the PHY supports
during a link reset sequence. See the following table.
Table 157: PROGRAMMED MINIMUM\MAXIMUM PHYSICAL LINK RATE
Code Description
0x0 Do not change current value
0x1 to 0x7 Reserved
0x8 1.5Gb/s
0x9 3Gb/s
0xA 6Gb/s
0xB to 0xF Reserved for future physical link rates
 HARDWARE MINIMUM PHYSICAL LINK RATE

This field is set to 1.5 Gbps (Value 8h) for the LSISS2520/LSISS2530 device.
 HARDWARE MAXIMUM PHYSICAL LINK RATE
This field is set to 6 Gbps (Value Ah) for the LSISS2520/LSISS2530 device.
 VENDOR SPECIFIC
This field is populated by zero value in the LSISS2520/LSISS2530 device.


Subpage 2
Table 158: Mode Page 19h - Shared Port Control Mode Page
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE (19h) D9h
0Ch
4 RESERVED 00h
6:7 POWER LOSS TIMEOUT 00h
8:15 RESERVED 00h
The page is a read-only mode page and the LSISS2520/LSISS2530 device does not
support modifying parameters of this page.
transport protocol.
 POWER LOSS TIMEOUT
The POWER LOSS TIMEOUT field contains the maximum time, in one millisecond
increments, that a target port responds to connection requests with OPEN_REJECT
(RETRY) after receiving NOTIFY (POWER LOSS EXPECTED).
If this field is set to 0x0000, the default timeout value is 2 seconds. This field is
rounded up to the nearest 10 millisecond value. (i.e. values of 1 to 10 are set to 10
milliseconds, and values of 11 to 20 are set to 20 milliseconds, etc.).

Subpage 3
Table 159: Mode Page 19h - ENHANCED PHY CONTROL Mode Page
BIT Default
Byte
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE (19h) 59h
2Ch
4 RESERVED 00h
6 GENERATION CODE 00h

Table 159: Mode Page 19h - ENHANCED PHY CONTROL Mode Page (Continued)
BIT Default
Byte
7 6 5 4 3 2 1 0
7 NUMBER OF PHYS (02h) 02h
8:27 ENHANCED PHY CONTROL MODE DESCRIPTOR for PHY 0. See Table 160. —
28:47 ENHANCED PHY CONTROL MODE DESCRIPTOR for PHY 1. See Table 160. —
transport protocol.
 NUMBER OF PHYS
The NUMBER OF PHYS indicates Number of SAS Phys on the LSISS2520/LSISS2530
device. The field is set to 2.
 GENERATION CODE
The LSISS2520/LSISS2530 device sets the GENERATION CODE to the zero value.
Table 160: ENHANCED PHY CONTROL MODE DESCRIPTOR
BIT
Byte Default
7 6 5 4 3 2 1 0
0 RESERVED 00h
1 PHY IDENTIFIER 00h
01h
2:3 DESCRIPTOR LENGTH 00h
10h
4:7 PROGRAMMED PHY CAPABILITIES —
8:11 CURRENT PHY CAPABILITIES —
12:15 ATTACHED PHY CAPABILITIES —
16:17 RESERVED 00h
18 RESERVED NEGOTIATED SSC NEGOTIATED PHYSICAL LINK RATE —
19 RESERVED HW MUXing 00h

SUPPORT
 PROGRAMMED PHY CAPABILITIES

This field indicates the SNW-3 PHY capabilities bits transmitted in the next link reset
sequence containing SNW-3.
 CURRENT PHY CAPABILITIES
This field indicates the outgoing SNW-3 PHY capabilities bits transmitted in the last
link reset sequence. If the last link reset sequence did not include SNW-3 or was a
SATA link reset sequence, the CURRENT PHY CAPABILITIES field is set to 0.

 The ATTACHED PHY CAPABILITIES

This field indicates the incoming SNW-3 PHY capabilities bits received in the last
SNW-3. If the last link reset sequence did not include SNW-3 or was a SATA link reset
sequence, the ATTACHED PHY CAPABILITIES field is set to 0.
 A NEGOTIATED SSC
This field set to 1 indicates that SSC is enabled. A NEGOTIATED SSC field set to 0
indicates that SSC is disabled. The NEGOTIATED SSC field is valid only when the
NEGOTIATED PHYSICAL LINK RATE field is greater than or equal to 8h.
 NEGOTIATED PHYSICAL LINK RATE
If the PHY is a physical PHY, this field indicates the physical link rate negotiated
during the link reset sequence. If the PHY is a virtual PHY, set this field to the
MAXIMUM PHYSICAL LINK RATE supported by the expander device.
If the programmed PHYSICAL LINK RATE changes after the last link reset sequence,
the NEGOTIATED PHYSICAL LINK RATE is less than the PROGRAMMED MINIMUM
PHYSICAL LINK RATE. It can be greater than the PROGRAMMED MAXIMUM
PHYSICAL LINK RATE. For details, refer to the SAS-2 spec.
 HW MUXing SUPPORT
The LSISS2520/LSISS2530 device does not support this field and it is always set to 0.

5.1.10 Mode Page 1Ah (Power This section describes Mode Page 1Ah.
Condition)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF Page Code = 1Ah 1Ah
1 Page Length = 0Ah 0Ah
2 RESERVED = 0 00h
3 RESERVED Idle Standby 00h
4:5 (MSB) Idle Condition Timer = 0 00h
6:7 (LSB) Idle Condition Timer = 0 00h
8:9 (MSB) Standby Condition Timer FFh
10:11 (LSB) Standby Condition Timer FFh
The Power Condition mode pages allow changing of the ATA APM mode setting and
the ATA STANDBY timer value. They also provide information about the current power
condition settings.
 Idle
If Idle is set to 1during Mode Select, the LSISS2520/LSISS2530 device terminates the
command with check condition status, sense key set to Illegal request, and
additional sense code set to INVALID FIELD IN PARAMETER LIST. Idle is set to 0
during Mode Sense command.
 Idle Condition Timer
Value is ignored by the LSISS2520/LSISS2530 device and sets the value 0.
 Standby
If the STANDBY bit is set to 1, then the standby condition timer is enabled by
sending the ATA STANDBY command to the ATA device with the value in the
Standby condition timer. If the STANDBY bit is set to 0, the device server ignores the
standby condition timer. Standby is only supported if the ATA device connected to
the LSISS2520/LSISS2530 device supports the STANDBY feature. If the drive does
not support STANDBY, the LSISS2520/LSISS2530 device terminates the mode select
command with a check condition status, the sense key set to ILLEGAL REQUEST, and
additional sense code set to INVALID FIELD IN PARAMETER LIST. If the ATA device
does not support the Standby feature, the value of Standby is set to 0 during the
mode sense command.
 Standby Condition Timer
Specifies the inactivity time in 100 millisecond increments.
NOTE: The fields within the mode page 1Ah are not saved to a nonvolatile memory. The
value of the Standby Condition timer is set to 0xFFFFFFFF (Invalid value) after power
recycle/reboot.

5.1.10.1 ModePage 1Ah Subpage This section describes ModePage 1Ah Subpage F1h.
F1h: ATA Power Condition
ModePage
Table 162: ModePage 1Ah Subpage F1h
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF Page Code = 1Ah DAh
1 SUBPAGE CODE = F1h F1h
2 (MSB)PAGE LENGTH = 0 00h
3 (LSB)PAGE LENGTH = 0Ch 0Ch
4 RESERVED 00h
5 RESERVED APMP 00h
6 APM Value 00h
7:15 RESERVED 00H
 APMP
This bit set to 1 indicates that the LSISS2520/LSISS2530 device alters the APM Mode by
issuing the ATA SET FEATURES command, depending on the value contained in the
APM Value field. When this bit is set to 0, the LSISS2520/LSISS2530 device ignores the
value contained in the APM Value field.
 APM Value
If the APM VALUE field contains a nonzero value, the ATA SET FEATURES –
Enable/disable the APM feature set (subcommand 05h) command is sent and the APM
VALUE field is used to set the power management level (COUNT field). If the APM VALUE
field contains a zero, the ATA SET FEATURES – Disable the APM feature set
(subcommand 85h) command is sent.
5.1.11 Mode Page 1Ch (Informational This section describes Mode Page 1Ch.
Exceptions Control)
Table 163: Mode Page 1Ch
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF PAGE CODE = 1Ch 9Ch
2 PERF RSVD EBF EWASC = 0 DEXCPT = 0 TEST = 0 EBACKERR = 0 LOGERR = 1 81h
3 RESERVED Method of Reporting 06h

Table 163: Mode Page 1Ch (Continued)
BIT
Byte Default
7 6 5 4 3 2 1 0
(MSB)
4:7 INTERVAL TIMER 00h
(LSB)
(MSB)
8:11 REPORT COUNT 00h
(LSB)
The Informational Exceptions Control mode page defines the methods used by the
LSISS2520/LSISS2530 device to control the reporting and the operations of specific
informational exception conditions.
This page only applies to informational exceptions that report additional sense codes
with the ASC field set to 5Dh such as FAILURE PREDICTION THRESHOLD EXCEEDED or
0Bh such as WARNING to the application client.
Informational exception conditions occur as the result of background scan errors,
background self-test errors.
 PERF (Performance)
If the performance (PERF) bit is set to 0, informational exception operations that are
the cause of delays are acceptable. If the PERF bit is set to 1, the device server does
not cause delays while doing informational exception operations. The
LSISS2520/LSISS2530 device does not support this field, and the PERF field is set to
1 in a Mode Sense data.
 EBF (Enable Background Function)
This bit is not used and is ignored by the LSISS2520/LSISS2530 device.
 EWASC (Enable Warning ASC)
This bit set to 0 indicates that Temperature Warning is not reported. An EWASC bit
of 1 allows Temperature Warning to be reported when DEXCPT bit is set to 0. If the
temperature reading inside of the disk enclosure exceeds the threshold (default or
set by MODE SELECT Page 0), Recovered Error (Sense Key 01h, ASC 0Bh, ASCQ 01h)
is reported. The LSISS2520/LSISS2530 device does not support this bit set to 1.
 DEXCPT (Disable Exception Control)
This bit set to 0 indicates information exception operations is enabled. The reporting
of information exception conditions when the DEXCPT bit is set to 0 is determined
from the Method of Reporting field. A DEXCPT bit of 1 indicates the Target disable all
information exception operations including the LSISS2520/LSISS2530 device idle
time function which saves the LOG SELECT counters. If this bit is set these counters
are not written to disk and so is lost at the next power cycle. The LSISS2520/LSISS2530
device does not support this bit set to 1.

 TEST
This bit of 1 instructs the LSISS2520/LSISS2530 device to generate false
LSISS2520/LSISS2530 device notifications at the next interval time, as determined
by the INTERVAL TIMER field, if the DEXCPT bit is 0. When the TEST bit is set to 1, the
MRIE and REPORT COUNT fields apply as if the TEST bit is zero. The false
LSISS2520/LSISS2530 device failure is reported as sense qualifier 5DFFh. The TEST
bit of 0 instructs the LSISS2520/LSISS2530 device to stop generating any false
LSISS2520/LSISS2530 device notifications. The LSISS2520/LSISS2530 device does
not support this bit, set to 1 condition.
 Enable Background Error (EBACKERR)
This bit set to 0 indicates the target disables reporting of background self-test errors
and background scan errors. An EBACKERR bit set to 1 indicates reporting of
background self-test errors and background scan errors is enabled. The
LSISS2520/LSISS2530 device supports this bit set to both 0 and 1.
 LOGERR (Log Errors)
This field is not used and is ignored internally by the LSISS2520/LSISS2530 device.
 METHOD OF REPORTING INFORMATIONAL EXCEPTIONS
This field indicates the methods used by the Target to report informational
Table 164: METHOD OF REPORTING INFORMATIONAL EXCEPTIONS Descriptions
Code Description
2h The device server reports informational exception conditions by establishing a unit attention condition for the initiator port
associated with every I_T NEXUS, with the ASC set to indicate the cause of the informational exception condition.
4h The device server reports informational exception conditions, regardless of whether the reporting of recovered errors is
allowed, by returning a CHECK CONDITION status. If the TEST bit is set to 0, the status can be returned after the informational
exception condition occurs on any command for which GOOD status is returned. The sense key is set to RECOVERED ERROR and
the ASC indicates the cause of the informational exception condition.
The command that returns the CHECK CONDITION for the informational exception completes without error before any
informational exception condition can be reported.
6h Only report informational exception conditions on request: This method instructs the target to preserve the informational
exceptions information. To find out about informational exception conditions the initiator polls the target by issuing an
unsolicited REQUEST SENSE command. The Sense Key is set to NO SENSE and the ASC indicates the cause of the informational
exception conditions. The LSISS2520/LSISS2530 device supports this mode.
 INTERVAL TIMER
This field indicates the period in 100 millisecond increments for reporting that an
informational exception condition has occurred. The target does not report
informational exception conditions more frequently than the time specified by the
INTERVAL TIMER field and as soon as possible after the time interval has elapsed.
After the informational exception condition has been reported, the INTERVAL TIMER
is restarted. A value of 0 in the INTERVAL TIMER field indicates that the target does
not poll the SATA device. The LSISS2520/LSISS2530 device supports values from 0 to
6000. That is, for 0 ms to 600 seconds for this field.

 REPORT COUNT
This field indicates the number of times the target reports an informational
exception condition. A REPORT COUNT of 0 indicates no limits on the number of
times the target reports an informational exception condition. The
LSISS2520/LSISS2530 device does not support a nonzero value for this field.
5.1.12 Mode Page 25h (Logging This section describes Mode Page 25h.
Configuration Parameters)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF PAGE CODE = 25h A5h
1 PAGE LENGTH = 06h 06h
2:3 RESERVED 00h
4 LOGGING SYSTEM LEVEL 02h
5:7 FLASHING TIMER CONFIGURATION 00h
This page is used to change the behavior of logging. It can change the types of
messages that are saved, or how soon after a log message is generated the flush to the
flash begins.
There are four different log levels.
Table 166: Log Levels
Value Description
00 Informational Message
01 Low Priority Error/Warning
10 Error (Default): Errors are considered to be disruptive but recoverable
11 Severe: these are unrecoverable errors that results in a reset
 LOGGING SYSTEM LEVEL

The Logging feature is configured at the system level of logging. This value is one of
the four levels. When an log request is made, the logging module first checks for the
priority of the log. If it is less than the system level, the log message is dropped.
 FLASHING TIMER CONFIGURATION
The LSISS2520/LSISS2530 device periodically flushes the logs to flash. This timer
provides the 100ms interval to control the period. A value of zero allows the
LSISS2520/LSISS2530 device to chose the interval. LSISS25x0 does not support this
field set to nonzero value.

5.1.13 Mode Page 32h (Firmware This mode page is a vendor-specific mode page for clearing vendor-specific mode and
Parameter Control) log parameters, and contains firmware parameters.
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0b) PAGE CODE = 32h B2h
1 PAGE LENGTH = 2Dh 2Dh
2 PANIC ON DISABLE WRITE AS ALTERNAT DISABLE DPO INITIALIZE CLEAN ENABLE 00h
SAS LINK WATCHDOG WRITE ESCT CHECK DRIVE ON REBOOT ACTIVE
LOSS REFRESH VERIFY TIMEOUT TARGET
BEHAVIOU RESET WAIT
R
3 DISABLE QUEUE DEPTH C0h
NON512
ANDDIF
4 LEGACY READYLED MAX ALLOWED INITIATOR PER PORT 4h
INITIATOR ACTIVESTATE
DISABLE
5 REBOOT ON RESERVED WWN GEN. REPORT REBOOT RESTORE TO DISABLE DISABLE 00h
PANIC TYPE FORMAT LSISS2520/LS FRESH HOST PORT HOST PORT
CORRUPT ISS2530 MANUFACT 1 0
URING
6 RESERVED FIELD VARIABLE NUMBER OF BLOCKS TO BE INITIALIZED AT ONCE 08h
RESERVED COMMAN DURING A FORMAT UNIT OPERATION
FOR DTIMEOUT
FUTURE
FEATURE
7 DEVICE SPIN-UP ALGORITHM IGNORE REBOOT OPTIONS RESTORE 00h
CHANGABLE
AFTER FW UPGRADE _DEFAUL
VALUES
TS
8 FIELD RESERVED FOR FUTURE FEATURE 00h
9 WATCH DOG TIMEOUT VALUE (IN UNITS OF 250 MS) 04h
10 COMMAND TIMEOUT FOR PACKAGE UPGRADE (in sec) 0Eh
11:18 (MSB) —
WORLD WIDE NAME PROGRAMMED
(LSB)
19:26 (MSB) —
WORLD WIDE NAME IN USE
(LSB)
27:34 (MSB) —
WORLD WIDE NAME FROM DEVICE
(LSB)
35 RESERVED 00h
36 RESERVED 00h
37:38 CUSTOMER 00h

Table 167: Mode Page 32h (Continued)
BIT
Byte Default
7 6 5 4 3 2 1 0
39:42 DEVICE QUALIFICATION FLAGS 00000005h
43:44 DSM SPINUP TIMEOUT 006Eh
45-46 RESERVED 00h
 CLEAN REBOOT
This flag specifies whether to clean reboot the LSISS2520/LSISS2530 device or not.
If this flag is set, the firmware sends an Aborted by Device Server status for the
commands which are present in queue, and then restarts. If this flag is not set, the
firmware does nothing.
NOTE: Mode sense for this flag always returns 0.
 DISABLE DPO CHECK

This flag specifies whether to check the DPO field value within the
READ/WRITE/VERIFY/WRITE AND VERIFY command CDB. If set to 1, the LSISS25x0
device disables checking of the DPO field value.
 INITIALIZE DRIVE ON TARGET RESET
This flag is used to transition the Device State Machine from the SSD4 –
SATA_DRIVE_DOWN state to the SSD3 – SATA_DRIVE_RESET state, when the device
receives a SAS Target Reset (SAS Hard Reset primitive). See Section B.1, Device State
Machine for a description of the Device State Machine.
If this flag is set and the Device State Machine is in the SATA_DRIVE_DOWN state,
the LSISS2520/LSISS2530 device issues a Reset to the Device and transitions the
Device State Machine to SATA_DRIVE_RESET state (wait for a Device Signature)
when it receives a SAS Target Reset.
 ENABLE ACTIVE WAIT
This flag, with the Drive Spin-up Algorithm field, controls the transition to the
Active_Wait power condition state from the Stopped/Standby power condition
state. If set to 1 (and Drive Spin-up Algorithm set to SPINUP ON NOTIFY PRIMITIVE –
DRIVEPOWER or SPINUP ON NOTIFY PRIMITIVE – DRIVEPHY), the transition to the
Active_Wait power condition state is enabled.

 ALTERNATESCTTIMEOUTBEHAVIOUR
This flag identifies the behavior for the LSISS2520/LSISS2530 device to program SCT
time-out on the device.
— If TRUE, the LSISS2520/LSISS2530 device attempts to configure Mode page 35h
SCT time-out values to the device if they are nonzero. Else the
LSISS2520/LSISS2530 device attempts to configure Recovery timeout -1 sec value
to the device.
— If FALSE, the LSISS2520/LSISS2530 device attempts to configure Mode page 35h
SCT time-out values to the device if they are nonzero.
 WRITE AS WRITE AND VERIFY
This flag specifies the firmware to treat a WRITE command as WRITE AND VERIFY
command with BYTCHK set to 1. This is applicable only to WRITE (10), WRITE (12),
and WRITE (16) commands and is translated as WRITE AND VERIFY (10), WRITE AND
VERIFY (12), and WRITE AND VERIFY (16) commands.
 DISABLE WATCHDOG REFRESH
This field instructs the LSISS2520/LSISS2530 device to disable refreshing the
Watchdog timer.
NOTE: This field is used ONLY for debug purpose and disabling the watchdog refresh
results in Firmware Panic/Reboot depending upon the Reboot on Panic flag. This field is
added for critical event simulation.
 PANIC ON SAS LINK LOSS

This firmware flag specifies whether to panic on SAS LINK LOSS event. If set to 1b,
the LSISS2520/LSISS2530 device panics when SAS Link goes down else it brings up
the SAS Links and continues execution normally.
 LEGACYINITIATORDISABLE
This bit flag disables the support for Legacy Initiators. When this flag is set, the
Check Condition - ILLEGAL REQUEST, and the ASC set to INVALID FIELD in CDB is
sent out for READ CAPACITY 10 command. READ CAPACITY 16 works as it is.
 DISABLENON512ANDDIF
It signifies Disable the Non 512 sector block size and DIF information. The Flag is set
by default to disable Non-512 byte mode and DIF.
 READYLEDACTIVESTATE
When this bit field is set to 0, the LSISS2520/LSISS2530 device drives 0 to turn on the
ready LED. When the bit is set to 1, the LSISS2520/LSISS2530 device drives 1 to turn
on the ready LED.
 MAX ALLOWED INITIATOR PER PORT
This field specifies Max Initiators per Port for the LSISS2520/LSISS2530 device. This
field ranges from 1 to 4. The default value is set to 04h by default.

 QUEUE DEPTH
This parameter specifies the command queue depth that the LSISS2520/LSISS2530
device supports. The maximum and minimum allowable queue depth is 64 and 1
respectively. The LSISS2520/LSISS2530 device requires a reboot for changes in the
Queue Depth to take effect.
 RESTORE TO FRESH MANUFACTURING
When this bit field is set to 1 and SP is enabled, the LSISS2520/LSISS2530 device
resets itself to fresh manufacturing config data values. No other field values are
saved in this mode page, because it loads the customer-specific default values for
all values. In addition, all logs and crash dumps are purged. This purge reconfigures
the LSISS2520/LSIS2530 device as if it were a new device. The LSISS2520/LSISS2530
device loads these new values the next time it boots.
 DISABLE HOST PORT 0
When this bit field is set to 1, the Host Port 0 is disabled. This bit value cannot be
saved. Upon reboot, this value is cleared to zero. When this bit is set to 0, then the
Host Port 0 is enabled.
 DISABLE HOST PORT 1
When this bit field is set to 1, the Host Port 1 is disabled. This bit value cannot be
saved. Upon reboot, this value is cleared to zero. When this bit is set to 0, then the
Host Port 1 is enabled.
NOTE: The LSISS2520/LSISS2530 device does not allow both the host ports together in
a disabled state. Therefore, both DISABLE HOST PORT 1 and DISABLE HOST PORT 0 set
to 1 (11) is not valid. LSISS25x0 does not allow port 1 to be disabled if port 0 is already
disabled and vice-versa. LSISS25x0 sends out a CC status with
INVALID_FIELD_IN_PARAMETER_LIST for such request.
 WWN GEN. TYPE

This field specifies the WWN generation algorithm that is used by the
Table 168: WWN GEN. TYPE Field Values
Field Description
0 As specified in SAT 2.0 specification (that is, using the WWN field of IDENTIFY DEVICE
data). Port numbering is performed in bit 0 and bit 1 as determined by the OUI in the
device's WWN. This setting is not recommended.
1 Vendor-specific method (using the node name provided in the WWN field). In this
mode, the port number field is bits 0 and 1 where bits 0 and 1 cleared are the node
WWN and bit 0 is set for port 0, bit 1 is set for port 1. When WNN Gen. Type set to 1,
the Target Port Identifiers, Device Name, and Logical Unit Name are derived from the
programmed WWN value.

 REBOOT ON PANIC
This field specifies whether to reboot on a Panic condition. If set, the
LSISS2520/LSISS2530 device restarts on panic. If clear, it enters into diagnostic
mode where diagnostics / management commands are performed through the
console interface.
 REPORT FORMAT CORRUPT
This field specifies whether to report a Format Corrupt condition.
 VARIABLE COMMAND TIMEOUT
Command time-out could be configured if the LSISS2520/LSISS2530 device uses
Mode page 01h. This flag indicates whether or not the LSISS2520/LSISS2530 device
recalculates the command time-out.
Table 169: VARIABLE Command Timeout Field Descriptions
Field Description
0 Stick to command time-out specified in Mode page 01 for all commands
1 Internally re-calculate the time-out for the commands having bigger transfer lengths
so that they won't time out on the LSISS2520/LSISS2530 device.
For the TIMEOUTVALUE calculation, when the Variable command time-out is set to
TRUE, the command time-out is calculated using the following equations:
— For READ commands, TimeoutValue = (TransferLength / 64) + command
timeout specified in mode page 01.
— For WRITE/WRITESAME/FORMAT commands, TimeoutValue = (TransferLength /
32) + command timeout specified in mode page 01.
 REBOOT LSISS2520/LSISS2530
When this field is set to 1, the LSISS2520/LSISS2530 device restarts itself. This is a
vendor-specific method for re-booting the LSISS2520/LSISS2530 device. This field is
used in conjunction with Reboot Type.
 NUMBER OF BLOCKS TO BE INITIALIZED AT ONCE DURING FORMAT UNIT OPERATION
This field specifies the block count that is used for initializing the device. When a
FORMAT UNIT command is received, the LSISS2520/LSISS2530 device initializes the
blocks in the device with a user-defined pattern (if provided) or with a
vendor-specific pattern. This operation results in more than one command to the
device depending upon the size of the device. This parameter defines the number
of blocks to be initialized in one stretch. This is measured in the units of powers of 2.
For example, a value of 4 specifies 2 ^ 4 = 16 blocks to be written at once. The
default value is set to 8 (that is, 256 blocks).
NOTE: When the LSISS2520/LSISS2530 device is configured in Sector Skewing Mode

with Stripe Size set to 116 blocks and Skew Mode set to Sparse Mode, or Block Length
set to 4104 bytes and Skew Mode set to Packed Mode, this field is not considered and
maximum possible blocks are initialized per command.

 DEVICE SPIN-UP ALGORITHM

This parameter controls how the SATA device spins after the LSISS2520/LSISS2530
device is powered up.
Table 170: DEVICE SPIN-UP ALGORITHM Values
Value Acronym Meaning

0x0 SPINUP ON NOTIFY PRIMITIVE -DRIVEPOWER Apply device power on Notify Spinup primitive from initiator.
0x1 SPINUP ON STARTSTOP - DRIVEPOWER Apply device power on Start stop unit command from initiator.
0x2 SPINUP IMMEDIATE Spinup as soon as the device is powered.
0x3 SPINUP ON STARTSTOP-DRIVEPHY Start OOB to device on Start stop unit command from initiator
0x4 SPINUP ON NOTIFY PRIMITIVE – DRIVEPHY Start OOB to device on reception of Notify primitive from initiator
0x5 to 0xF RESERVED RESERVED
 IGNORECHANGABLEVALUES
If this bit is set to 1, the LSISS2520/LSISS2530 device ignores the changeable values
mask while processing a mode select command.
 REBOOT OPTIONS AFTER FW UPGRADE
This field specifies the action taken by the LSISS2520/LSISS2530 device after a
firmware upgrade. The field is two bits long. The following table shows the possible
values for the field:
Table 171: REBOOT OPTIONS AFTER FW UPGRADE Field Values
Field Description
00 Deferred Reboot (The initiator has to do an explicit mode select /console
command to reboot the LSISS2520/LSISS2530 device after completing the
firmware upgrade.) This is the default value for the field.
01 Immediate reboot after the firmware upgrade (Firmware restarts on its own as
soon as the firmware upgrade completes.)
10 Clean reboot after firmware upgrade (Firmware sends an aborted by device
server status for the commands in queue and then restarts).
11 RESERVED

This parameter controls the reset behavior of the LSISS25x0 device after the
following actions take place:
— Package firmware upgrade (Write Buffer mode 5 buffId 0xA and
mode 7 buffId 0xA):
This parameter controls the reset behavior of the LSISS25x0 device in
conjunction with the options_reset flag present in the package.
The following table illustrates the LSISS25x0 devices’ s reset behavior:
Table 172: LSISS25x0 Reset Behavior
Options Reset Flag in Mode Page 32 – Reboot After

Behavior
Package Firmware Upgrade Flag
0 0 No reboot
0 nonzero Deferred reboot/Clean
reboot/Immediate reboot as per
Mode Page 32 - Reboot After
firmware upgrade flag
1 0 Clean reboot/Immediate reboot
as per Mode Page 32 - Reboot
After firmware upgrade flag
1 nonzero Deferred reboot/Clean
reboot/Immediate reboot as per
Mode Page 32 - Reboot After
firmware upgrade flag
— An LSISS25x0 firmware upgrade (Write Buffer mode 7 buffId 1):

The LSISS25x0 reset undergoes deferred reboot/clean reboot/immediate reboot
based upon the setting of this flag.
 RESTORE_DEFAULTS
When this bit is set, the LSISS2520/LSISS2530 device restarts and comes up with all
the items in the configuration data set to defaults (erase followed by restore
followed by reboot).
 WATCH DOG TIMEOUT VALUE
This field is specified in units of 250 milliseconds. The default value is 4 (which is 1
second). The range for this field is 250 ms to 4 seconds.
 COMMAND TIMEOUT FOR PACKAGE UPGRADE (in sec)
The command time-out values are specified in seconds for Package upgrade. The
default time-out is 14 sec.
 WORLD WIDE NAME PROGRAMMED
This field specifies the world wide node name, which the LSISS2520/LSISS2530
device uses when reporting the Node Name in Inquiry data (that is, VPD page 83h -
Device Identification Page).

NOTE: The user has to select the WWN Gen Type to 1 if the node name specified in this
field to be used by the LSISS2520/LSISS2530 device. Otherwise the
LSISS2520/LSISS2530 device uses the node name from its nonvolatile memory that has
been constructed from the device's WWN.
 WORLD WIDE NAME IN USE

This is the World Wide Name that the LSISS2520/LSISS2530 device is using to
connect to the SAS Side. This field is read-only. The field is Don't Care when a mode
select operation is performed.
 WORLD WIDE NAME FROM DEVICE
This is the World Wide Name supplied by the device. This field is read -only. The field
is Don't Care when a mode select operation is performed.
 CUSTOMER
This field is a customer specific value. Setting this value to a nonzero changes the
behavior of the LSISS2520/LSISS2530 device for a specific customer. Each bit is
meaningful for a different customer. Which bit has meaning for which customer is
defined elsewhere.
 DEVICE QUALIFCATION FLAGS
This field determines which features a device must support in order to come ready on
the LSISS2520/LSISS2530 device. If the device does not support those features, it
enters the DRIVE_DOWN state in the device state machine and logs an error message.
Table 173: Supported Features
Bit Feature
0 Device Supports NCQ
1 Device Supports SCT
2 Device Supports ATA7
3 Device Supports ATA8
4 Device Supports SMART
5 Device has a Valid WWN
 DSM SPINUP TIMEOUT

This field specifies the Spinup time-out for LSISS2520/LSISS2530 device's drive state
machine in seconds. The value programmed in this field is also used as the
command time-out value for the Start Stop Unit command when, in the Start Stop
Unit CDB, the Start bit is set and the Immediate bit is reset.

5.1.13.1 Mode Page 32 – The following section describes Mode Page 32 - Subpage 1.
Subpage 1
Table 174: Mode Page 32h Subpage 1 – Firmware Parameter Control Subpage 1
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE = 32h F2h
2:3 PAGE LENGTH (0014h) 00h
14h
4:5 READ COMMAND TIMEOUT 0000h
6:7 WRITE COMMAND TIMEOUT 0000h
8:9 WRITE VERIFY COMMAND TIMEOUT 00h
10 RESERVED CUSTOMER ENABLE DEBUG 00h
SPECIFIC SENSE
BEHAVIOUR INFORMATION
11:12 DRIVE INITIALIZATION TIMEOUT 00FAh
13:14 DRIVE HARD RESET TIME DELAY 00FAh
15:16 DRIVE POWER DOWN RESET TIME DELAY 03E8h
17:23 RESERVED 00h
 READ COMMAND TIMEOUT

This field indicates the command time-out value for all Read Commands in
milliseconds. The default time-out is 0 ms. When this value is 0, the default Read
commands time-out value is considered as the RECOVERY TIME LIMIT value in Mode
page 1h.
 WRITE COMMAND TIMEOUT
This field indicates the command time-out value for all Write or Write as Write Verify
Commands in milliseconds. The default time-out is 0 ms. When this value is 0, the
default Write or Write as Write Verify commands time-out value is considered as the
RECOVERY TIME LIMIT value in Mode page 1h.
 WRITE VERIFY COMMAND TIMEOUT
This field indicates the command time-out value for all Write Verify Commands in
milliseconds. The default time-out is 0 ms. When this value is 0, the default Write
Verify commands time-out value is considered as the RECOVERY TIME LIMIT value in
Mode page 1h.
 ENABLE DEBUG SENSE INFORMATION
This field controls the transmission of vendor-specific debug sense information in
the sense data sent back by the LSISS25x0 device for the commands that end up in
non-unit-attention check condition status. When this flag is set, the LSISS25x0
device sends out the vendor-specific debug sense information in the sense data in
the format specified in Section 3.16, Error Reporting Codes.

 DRIVE INITIALIZATION TIMEOUT

This field indicates the time-out in milliseconds for the Drive Initialization Sequence.
The minimum and maximum supported values are 250 and 8000 milliseconds
respectively.
 CUSTOMER SPECIFIC BEHAVIOUR
If this field is set, the LSISS2520/LSISS2530 device exhibits customer-specific behavior.
 DRIVE HARD RESET TIME DELAY
This field indicates the time-out in milliseconds for the device hard reset to
complete. The LSISS2520/LSISS2530 device must receive the attached device’s
signature by this time from where it initiated the hard reset of the device. The
minimum supported values and maximum supported values are 250 milliseconds
and 8000 milliseconds respectively.
 DRIVE POWER DOWN RESET TIME DELAY
This field indicates the time-out in milliseconds that the LSISS2520/LSISS2530
device switches off the device power while performing a device power cycle. The
minimum supported values and maximum supported values are 1000 milliseconds
and 8000 milliseconds respectively.
5.1.14 Mode Page 33h (Sector This mode page is a vendor-specific mode page for configuring the sector skewing
Skewing Support Parameter Page) capabilities of the LSISS2520/LSISS2530 device. The mode page is accessible only if the
DISABLENON512ANDDIF field within mode page 32h is set to 0. Otherwise, the
LSISS2520/LSISS2530 device terminates the command with a Check Condition status
with SENSE KEY set to ILLEGAL REQUEST and ASC set to INVALID FIELD IN PARAMETER
LIST.
BIT
Byte Default
7 6 5 4 3 2 1 0
1 PAGE LENGTH = o6h 06h
2 RESERVED SkewAlgori 70h
thm
3 Stripe Size 08h
4 RESERVED 00h
5 RESERVED 00h
6 RESERVED 00h
7 RESERVED 00h

 Skew Algorithm – This field specifies the mode for sector skewing. The
LSISS2520/LSISS2530 device supports the following two modes:
— Packed Mode (0) – logical blocks (as seen by the initiator) are placed in
consecutive physical blocks on the drive without leaving any space or gaps.
— Sparse Mode (1) – logical blocks (as seen by the initiator) are not placed in
consecutive physical blocks in the drive.
 Stripe Size – This field is applicable only in Sparse Mode. This field specifies the
count of logical blocks after which the LSISS2520/LSISS2530 device leaves the
remaining bytes (in the physical sector) unused.
If an initiator changes any of these parameters using the MODE SELECT command and
the REPORT FORMAT CORRUPT field within mode page 32h is set to 1, then the
following commands are terminated with the Check Condition status, with SENSE KEY
set to MEDIUM ERROR and ASC set to MEDIUM FORMAT CORRUPTED:
 READ
 READ LONG
 REASSIGN BLOCK
 VERIFY
 WRITE
 WRITE AND VERIFY
 WRITE LONG
 WRITE SAME
The initiator must issue the FORMAT UNIT command to clear the Format Corrupt
condition. Once the Format Corrupt condition is cleared, theses commands are
processed normally.
The LSISS2520/LSISS2530 device supports the following sector skewing configurations:
 Packed Mode
— 520/528 bytes Logical Blocks on 512 bytes sector sized SATA device.
— 4104 bytes Logical Blocks on 4096 bytes sector sized SATA device.
 Sparse Mode
— 520 bytes Logical Blocks with 8/16/32/64/116 blocks stripes on 512 bytes sector
sized SATA device.
— 528 bytes Logical Blocks with 8/16/32/64 blocks stripes on 512 bytes sector
sized SATA device.
— 4104 bytes Logical Blocks with 8/16/32/64/116 blocks stripes on 4096 bytes
sector sized SATA device.
Mode Select commands with any other sector skewing combinations are terminated
with a Check Condition status, with SENSE KEY set to ILLEGAL REQUEST and ASC set to
INVALID FIELD IN PARAMETER LIST.

5.1.15 Mode Page 34h (SATA Link This mode page is a vendor-specific mode page for configuring the SATA Link present
Configuration) in the LSISS2520/LSISS2530 device.
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0B) PAGE CODE = 34H B4h
1 PAGE LENGTH = 12H 12h
2 SATA LINK RETRY LIMIT 00h
3 RESERVED 00h
4 SATA MAX RETRY (ON R_ERR) 0x02
5 SATA DATA FIFO THRESHOLD 30h
6 SATA LINK TRANSMIT TIMEOUT 20h
7 SATA LINK RECEIVE TIMEOUT 20h
8 RESERVED RESET LINK RESET LINK 03h
ON RECEIVE ON
TIMEOUT TRANSMIT
TIMEOUT
9:19 RESERVED 00h
 SATA LINK RETRY LIMIT

This field specifies the maximum number of Link Retries. The Field is
non-changeable field and the value is set to 0.
 SATA MAX RETRY (On R_ERR)
This field indicates the maximum number of attempts to send the same FIS to the
device. The legal values for this field range between 0 to 3.
 SATA DATA FIFO THRESHOLD
This field specifies the Command Buffer Manager's FIFO limit. The legal values for
this field range between 0x14 and 0x3F. This setting determines the threshold value
of available space in SATA Data FIFO in DWORDs such that SATA Port Link Layer
starts sending HOLDs to the device to avoid received data from overflowing SATA
Data FIFO.
Table 177: SATA DATA FIFO THRESHOLD Field Descriptions
Field Description
00h-13h Not a valid value. FW does not program a value in this range.
14h Free space at 20 DWORDs

Table 177: SATA DATA FIFO THRESHOLD Field Descriptions (Continued)
Field Description
..... ....
3Eh Free space at 62 DWORDs
3Fh Free space at 63 DWORDs
 SATA LINK TRANSMIT TIMEOUT

This field specifies the SATA Link Transmit\Receive State Machine time-out. The
value needs to be configured in terms of 32msec steps.
Table 178: SATA LINK TRANSMIT TIMEOUT Field Descriptions
Field Description
0 Disabled
1 32msec
0xff 8.16 sec
 SATA LINK RECEIVE TIMEOUT

This field specifies the SATA Link Receive State Machine time-out. The value needs
to be configured in terms of 32msec steps.
Table 179: SATA LINK RECEIVE TIMEOUT Field Descriptions
Field Description
0 Disabled
1 32msec
0xff 8.16 sec
NOTE: For these parameters to take effect, the SATA Link Reset is required and hence,
the SATA link is reset after successful mode select to this page.
 RESET LINK ON TRANSMIT TIMEOUT

This field specifies that the SATA Link is reset upon expiration of SATA LINK
TRANSMIT TIMEOUT.
 RESET LINK ON RECEIVE TIMEOUT
This field specifies that the SATA Link be reset upon expiration of SATA LINK RECEIVE
TIMEOUT. Setting of this flag is not recommended, since the SATA link might time
out because of SAS congestion.

5.1.16 Mode Page 35h (SATA Queuing This mode page is a vendor-specific mode page for configuring SATA Queuing behavior
and Error Recovery) and Error Recovery Timeout.
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0B) PAGE CODE = 35H B5h
1 PAGE LENGTH = 0AH 0Ah
2 RESERVED RESERVED ALLOW SKIP POWER SKIP HARD SKIP SOFT STAY IN STAY IN SYS 27h
STANDBY CYCLE RESET RESET DEVICE DOWN
DOWN
3:4 SCT READ ERROR RECOVERY TIMEOUT 00h
5:6 SCT WRITE ERROR RECOVERY TIMEOUT 00h
7:11 RESERVED 00h
 STAY IN SYS DOWN FLAG

This parameter specifies if the LSISS2520/LSISS2530 device enters a system down
state, then it remains until the LSISS2520/LSISS2530 device is power cycled.
 STAY IN DEVICE DOWN FLAG
This flag specifies that if the device enters device down state, stay there until chip
reset or console command is received.
 SKIP SOFT RESET
This parameter instructs the LSISS2520/LSISS2530 device not to issue Soft Reset
when doing error handling.
 SKIP HARD RESET
This parameter instructs the LSISS2520/LSISS2530 device not to issue hard resets
when doing error handling.
 SKIP POWER CYCLE
This parameter instructs the LSISS2520/LSISS2530 device not to power cycle the
device when doing error handling.
 ALLOW STANDBY
This flag allows the LSISS2520/LSISS2530 device to enter a low power state.
 SCT READ ERROR RECOVERY TIMEOUT
The LSISS2520/LSISS2530 device provides a mechanism to configure the SCT READ
ERROR RECOVERY TIMEOUT of the SATA device through this parameter. This is in the
units of 100 milliseconds. (1 = 100 ms, 2 = 200 ms). SCT Read Error recovery timer is
disabled if the value is zero.

 SCT WRITE ERROR RECOVERY TIMEOUT

This parameter configures the SCT WRITE ERROR RECOVERY TIMEOUT of the SATA
device. This is in the units of 100 milliseconds (1=100 ms, 2=200 misc.). SCT Write
Error recovery timer is disabled if the value is zero.
NOTE: In order to exercise the Read Error Recovery Timeout and Write Error Recovery
Timeout, the connected SATA device must support Smart Command Transfer (SCT), and
is ATA8 compliant. Else, LSISS2520/2530 device sends a check condition with the sense
key, INVALID FIELD IN CDB PARAMETER LIST.
5.1.17 Mode Page 36h (SAS Link This mode page is a vendor-specific mode page for configuring the SAS Links in the
Configuration) LSISS2520/LSISS2530 device.
BIT
Byte Default
7 6 5 4 3 2 1 0
1 PAGE LENGTH = 0CH 0Ch
2 RESERVED 00h
3 SAS MAX TRANSMIT FRAME COUNT 00h
4:5 RESERVED 00h
6 0x00h
7:8 00h
9:12 PHY EVENT SOURCE SELECTION 00h
13 RESERVED 00h
 SAS MAX TRANSMIT FRAME COUNT

This parameter specifies the Maximum frames to transmit per connection. The legal
values for this field range between 0 to 64 (Decimal).
 PHY EVENT SOURCE SELECTION
The LSISS2520/LSISS2530 device contains 10 PHY Event sources, of which only 4 are
active at one time. This parameter is composed of 4 one-byte fields, where each
byte corresponds to a specific PHY Event Source.
The legal values for this field are described in the following table.
Table 182: PHY EVENT SOURCE SELECTION Values
PHY Event Source Field Description

0x00 No PHY Event Source
0x06 Received Error Count
0x20 Received Address Frame Error Count
0x21 Transmitted Abandon-Class OR Count

Table 182: PHY EVENT SOURCE SELECTION Values (Continued)
PHY Event Source Field Description

0x22 Received Abandon-Class OR Count
0x23 Transmitted Retry-Class OR Count
0x24 Received Retry-Class OR Count
0x25 Received AIP (WAITING ON PARTIAL) count
0x26 Received AIP (WAITING ON CONNECTION) count
0x40 Transmitted SSP frame count
0x41 Received SSP frame count
For example, to select Transmitted Abandon-Class OR Count, Received Abandon-Class

OR Count, Transmitted SSP frame count, and Received SSP frame count, PHY Event
Source Selection is set to 0x21224041.
5.1.18 Mode Page 37h (Firmware This section describes Mode Page 37h.
Debug Mode Page)
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF PAGE CODE = 37h B7h
1 PAGE LENGTH = 0Eh 0Eh
2 RESERVED 00h
3 RESERVED PARAMETER COUNT 02h
4:7 (MSB) 00h
LOG CODE
(LSB)
8:11 (MSB) 00h
PARAMETER 1
(LSB)
12:15 (MSB) 00h
PARAMETER 2
(LSB)

The Firmware Debug Mode Page is used for informing the firmware to add a log entry
to its log database. This mode page facilitates the LSISS2520/LSISS2530 device test
automation, where the test scripts uses this page to log the starting and ending of a
test case. This also helps them to correlate the sequence of events across test script logs
and firmware log. This mode page is used in conjunction with Mode Select command
only. Reading this mode page results in all the data set to 0.
 Parameter Count
This field specifies whether PARAMETER 0 and PARAMETER 1 are valid. A value of 0
indicates no parameter, value of 1 indicates PARAMETER 1 alone is valid and value of
2 indicates both the parameters are valid.
 LOG CODE
This field specifies the unique logging code.
 PARAMETER 0
The Log messages takes a maximum of two arguments. Depending upon the LOG
CODE, PARAMETER 0 and PARAMETER 1 field contains log code specific information.
 PARAMETER 1
5.1.19 Mode Page 39h (PHY Control This is a vendor-specific mode page that allows the initiators to configure the PHY
Mode Page) parameters such as TX Swing amplitude, Tx Pre-emphasis, Tx Post-emphasis, and Tx
Slew rate for all the three ports (SAS Port 0, SAS Port 1, and SATA Port 0).
NOTE: For mode page 39h the parameters must be programmed with caution and it is
not recommended to change the default settings for these parameters. The Phys might
become unusable if programmed to improper values. This is applicable both to Mode
Page 39h and Mode Page 39 Subpage1.
5.1.19.1 Mode Page 39h The section describes Mode Page 39h.
BIT
Byte
7 6 5 4 3 2 1 0 Default
0 PS SPF=0 PAGE CODE = 39h 0xB9
1 PAGE LENGTH 0x22
2 RESERVED 0x0
3 NUMBER OF SAS PHYS 0x2
4:19 PHY SPECIFIC SETTINGS FOR SAS PHY 0 —
20:35 PHY SPECIFIC SETTINGS FOR SAS PHY 1 —

The following table shows the PHY Specific Settings for SAS PHYs.
Table 185: PHY Specific Settings for SAS PHYS
BIT
Byte Default
7 6 5 4 3 2 1 0
0 RESERVED 0x00
1 RESERVED TX AMPLITUDE ALL SPEEDS 0x0D
2 RESERVED 0x00
3 ENABLESSC FORCESSC RESERVED TX POST-EMPHASIS FOR ALL SPEEDS 0x84
4 RESERVED TXCTRLI TX PRE-EMPHASIS REF50T REF50R RESERVED TERM_SEL 0x4C
5 TERMT_REG TERMR_REG RESERVED TZ 0xA1
6 RESERVED TP 0x00
7 RESERVED LOSADJ RESERVED RISEFALL 0x20
8 RESERVED RX CT-DFE RX EQ. PD 0x03
RATE
9 RX CT-DFE RX POLE/GAIN RX ZERO/POLE RX EQ. 0x13
SEL. MODE
10:15 RESERVED 0x00
Table 186: Field Descriptions for SAS PHYS
Field Description Reference

TX AMPLITUDE ALL SPEEDS Transmit driver peak-to-peak differential voltage swing. For further reading, refer to Section A.1.2.1 of
the LSISS2520 SAS-SATA Bridge Reference
Manual V1.1 (April 2009).
ENABLESSC Enable SSC. For further reading, refer to Section A.1.2.8 of
FORCESSC Force SSC.
TXCTRLI TX emphasis/de-emphasis selection. For further reading, refer to Section A.1.2.2 of
TX POST-EMPHASIS FOR TX post-emphasis.
ALL SPEEDS
TX PRE-EMPHASIS TX pre-emphasis.
REF50T TX termination selection. For further reading, refer to Section A.1.2.7 of
REF50R RX termination selection.
TERM_SEL Termination trimming mode selection.
TERMT_REG TX Termination Trimming Program.
TERMR_REG RX Termination Trimming Program.
TZ Tx PLL Zeros For further reading, refer to Section A.1.2.3 of
TP Tx PLL Poles
LOSADJ The receiver loss of signal input amplitude adjustment control For further reading, refer to Section A.1.2.6 of
sets the threshold at which the receiver detects a Receiver Loss of the LSISS2520 SAS-SATA Bridge Reference
Signal status. Manual V1.1 (April 2009).

Table 186: Field Descriptions for SAS PHYS (Continued)

RISEFALL The transmitter (TX) slew rate (rise/fall times). For further reading, refer to Section A.1.2.4 of
RX EQ MODE RX Equalizer Mode. For further reading, refer to Section A.1.2.5 of
RX EQ. PD Equalizer Adaptation Powerdown.
RX CT-DFE SEL RX CT-DFE Adaptive Equalization Select.
RX CT-DFE RATE RX CT-DFE Adaptive Equalization Rate.
RX POLE/GAIN RX Linear EQ Poles.
RX ZERO/POLE RX Linear EQ Zeros.
5.1.19.2 Mode Page 39 Subpage1 The following table shows the Mode Page 39 Subpage 1 Format for SATA Phys.
Table 187: Mode Page 39 Subpage 1 Format for SATA PHYS
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE (39h) F9h
2:3 PAGE LENGTH 00h
12h
4:5 RESERVED 00h
6:21 PHY SPECIFIC SETTINGS FOR SATA PHY
The following table shows the PHY Specific Settings for SATA Phys.
Table 188: PHY Specific Settings for SATA PHYS
BIT
Byte Default
7 6 5 4 3 2 1 0
0 RESERVED TX AMPLITUDE FOR 6G 0x0C
1 TX AMPLITUDE FOR 3G TX AMPLITUDE FOR 1.5G 0xDB
2 RESERVED TX POST-EMPHASIS FOR 6G SATA 0x04
3 RESERVED TX POST-EMPHASIS FOR 3G SATA RESERVED TX POST-EMPHASIS FOR 1.5G SATA 0x42
4 ENSSC TXCTRLI TX PRE-EMPHASIS REF50T REF50R TERMT_SEL TERMR_SEL 0x4C
5 TERMT_REG TERMR_REG RESERVED TZ 0xA1
6 RESERVED TP 0x00
7 RESERVED LOSADJ RESERVED RISEFALL 0x20

Table 188: PHY Specific Settings for SATA PHYS
BIT
Byte Default
7 6 5 4 3 2 1 0
8 RESERVED RX CT-DFE RX EQ. PD 0x03
RATE
9 RX CT-DFE RX POLE/GAIN RX ZERO/POLE RX EQ. 0x13
SEL. MODE
10:15 RESERVED 0x00
The following table shows the Mode Page 39 Subpage1 field descriptions
Table 189: Mode Page 39 Subpage1 Field Descriptions

TX AMPLITUDE FOR 6G Transmit driver peak-to-peak differential voltage For further reading, refer to Section A.1.1.1 of the
TX AMPLITUDE FOR 3G swing for the specified Link Speed. LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
TX AMPLITUDE FOR 1.5G
TXCTRLI TX emphasis/de-emphasis selection. For further reading, refer to Section A.1.1.2 of the
TX PRE-EMPHASIS TX pre-emphasis. LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
TX POST-EMPHASIS FOR 6G SATA TX post-emphasis for a given link speed
TX POST-EMPHASIS FOR 3G SATA
TX POST-EMPHASIS FOR 1.5G SATA
TZ Tx PLL Zeros For further reading, refer to Section A.1.1.3 of the
TP Tx PLL Poles LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
RISEFALL The transmitter (TX) slew rate (rise/fall times). For further reading, refer to Section A.1.1.4 of the
LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
RX EQ MODE RX Equalizer Mode. For further reading, refer to Section A.1.1.5 of the
RX EQ. PD Equalizer Adaptation Powerdown. LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
RX CT-DFE SEL RX CT-DFE Adaptive Equalization Select.
RX CT-DFE RATE RX CT-DFE Adaptive Equalization Rate.
RX POLE/GAIN RX Linear EQ Poles.
RX ZERO/POLE RX Linear EQ Zeros.
LOSADJ The receiver loss of signal input amplitude For further reading, refer to Section A.1.1.6 of the
adjustment control sets the threshold at which the LSISS2520 SAS-SATA Bridge Reference Manual V1.1
receiver detects a Receiver Loss of Signal status. (April 2009)
REF50T TX termination selection. For further reading, refer to Section A.1.1.7 of the
REF50R RX termination selection. LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)
TERMT_SEL TX Termination trimming mode selection.
TERMR_SEL RX Termination trimming mode selection
TERMT_REG TX Termination Trimming Program.
TERMR_REG RX Termination Trimming Program.
ENSSC Enable SSC. For further reading, refer to Section A.1.1.8 of the
LSISS2520 SAS-SATA Bridge Reference Manual V1.1
(April 2009)

5.1.19.3 Mode Page 39 Subpage 2 The following table shows the Mode Page 39 Subpage 2 format for PHY testing.
Table 190: Mode Page 39 Subpage 2 Format for PHY Testing
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(1b) PAGE CODE (39h) 79h
2:3 PAGE LENGTH 0024h
4:35 PHY SPECIFIC TEST PATTERN SETTINGS —
The following table shows the PHY Test Specific settings.
Table 191: PHY Test Specific Settings
BIT
Byte Default
7 6 5 4 3 2 1 0
0:3 RESERVED 00h
4 PhyIdentifier 00h
5 PhyTestFunction 00h
6 PhyTestPattern 00h
7 RESERVED PhyTestFuncSSC PhyTestFunctionRate 00h
8:10 RESERVED 00h
11 PhyTestPatternDwordControl 00h
12 PhyTestPatternDword0 00h
28 PhyTestControl 00h
29:31 RESERVED 00h

NOTE: You cannot save Mode Page 39h Subpage 2. When the LSISS2520/LSISS2530
device receives a Mode Select command with the Save Pages bit set to 1 for changing
any parameters in Mode Page 39h Subpage 2, the LSISS2520/LSISS2530 device
terminates the Mode Select command with Check Condition status, with Sense Key set
to ILLEGAL REQUEST, and the Additional Sense Code set to INVALID FIELD IN CDB.
Following are the descriptions of the fields within this mode page:
 PhyIdentifier
This field specifies which PHY to start a pattern test on.
— 0x00 – SAS Port 0
— 0x01 – SAS Port 1
— 0x02 – SATA Port
 PhyTestFunction
This field specifies the action to perform on the selected PHY.
— 0x00 – Stop. The selected PHY stops performing a PHY test function and
originates a chip reset.
— 0x01 – Transmit Pattern. The selected PHY transmits the PHY test pattern
specified by the PhyTestPattern field at the physical link rate specified by the
PhyTestFunctionRate field.
 PhyTestPattern
When the PhyTestFunction field is set to 01h this field determines the PHY test
pattern to be transmitted:
— 0x01 – JTPAT
— 0x02 – CJTPAT
 PhyTestFuncSSC
This field specifies the SSC modulation type.
0x00 - No SSC. This is the only currently supported value for this field is 0x00.
 PhyTestFunctionRate
This field specifies the physical link rate at which the phy test function is performed:
— 0x08 – 1.5Gb/s
— 0x09 – 3.0Gb/s
— 0x0A – 6.0Gb/s
 PhyTestPatternDwordControl
When the PhyTestPattern field is set to 0x01 (JTPAT), this field controls the disparity
of the JTPAT pattern.
— 0x55 – Negative Disparity (JTPAT-)
— 0xAA – Positive Disparity (JTPAT+)

 PhyTestPatternDWord(0 to 15)
These fields are not used for the currently implemented functionality.
 PhyTestControl
This field is not used for the currently implemented functionality.
5.1.20 Mode Page 3Ah (SATA Link This is a vendor-specific mode page to control the SATA Link present in the
Control) LSISS2520/LSISS2530 device.
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0B) PAGE CODE = 3AH BAh
2 DISABLE COM-RESET RESERVED 00h
SATA LINK
3 SATA MAX LINK SPEED 01h
4 SATA MIN LINK SPEED 00h
5 SATA NEGOTIATED SPEED 00h
6:7 RESERVED 00h
Following are the meanings of the various fields within this mode page:
 DISABLE SATA LINK
If set, the SATA link is disabled otherwise enabled. This field is saved to a
nonvolatile memory.
 COM-RESET
If set, the SATA link undergoes the reset cycle. This field is not saved to the
nonvolatile memory and read to this bit always returns zero.
 SATA MAX and MIN LINK SPEED
These fields are saved to the nonvolatile memory and define the maximum and
minimum SATA link speeds.:
Table 193: SATA MAX and MIN LINK SPEED Values
Value of Field Speed

0 1.5G
1 3.0G
2 6.0G
The field values from 2 to 7 are reserved.

 SATA NEGOTIATED SPEED

This field indicates the negotiated SATA link speed. This is valid only for Mode Sense
and ignored in case of Mode Select. The values are returned as per the previous table.
NOTE: If the SATA Link fails to negotiate a speed equal to or greater than the set SATA
Min Link Speed then the SATA Link undergoes a reset cycle. This is attempted for three
times and if the failure still persists then the LSISS2520/LSISS2530 device defaults to the
negotiated speed and generates a Unit Attention condition for all initiators with an ASC
set to 82h and ASC qualifier set to 00h.
5.1.21 Mode Page 3Bh (Device This is a vendor-specific mode page to control the device connected to the
Control) LSISS2520/LSISS2530 device.
Table 194: Mode Page 3Bh
BIT
Byte Default
7 6 5 4 3 2 1 0
0 PS SPF(0B) PAGE CODE = 3BH 3Bh
2 POWER SOFT RESET HARD RESET RESERVED 80h
ON/OFF
3:7 RESERVED 00h
The fields within this mode page are not saved to a nonvolatile memory.
Following are the meanings of the various fields within this mode page.
 POWER ON/OFF
This bit is set/cleared by using a MODE SELECT command to power ON or power
OFF the device respectively. While doing a MODE SENSE, this bit indicates whether
the device is ON or OFF; if set, device in ON and vice versa.
 SOFT RESET
If set, a soft reset to the device is initiated and read to this bit always returns zero.
 HARD RESET
If set, a COMRESET to the device is initiated and read to this bit always returns zero.
The MODE SELECT to this mode page is processed in the following order:
— If the device Power OFF is requested then the device is powered OFF and the
command is completed.
— If the device Power ON is requested and the device was powered OFF previously
then the device is powered ON and the command gets completed. Else the
device resets if any are processed.
— The hard reset takes a higher priority than the soft reset. If both the hard reset
and soft reset or only the hard reset is requested then the hard reset to the
device is processed and the command gets completed. Else the soft reset if any
is processed.

Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
5.2 Log Parameters This section describes the Log Pages.
5.2.1 Log Page 00h (Supported Log Page 0 indicates the supported LOG SENSE pages. This page determines the additional
Pages) pages an initiator can request.
Table 195: Supported Log pages
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE = 00h
1 RESERVED
2:3 (MSB)
(LSB)
PAGE LENGTH = 0015H
(NUMBER OF PAGES SUPPORTED)
4 FIRST SUPPORTED PAGE 00H
5 SECOND SUPPORTED PAGE 02H
6 THIRD SUPPORTED PAGE 03H
7 FOURTH SUPPORTED PAGE 05H
8 FIFTH SUPPORTED PAGE 06H
9 SIXTH SUPPORTED PAGE 0DH
10 SEVENTH SUPPORTED PAGE 0EH
11 EIGHTH SUPPORTED PAGE 0FH
12 NINTH SUPPORTED PAGE 10H
13 TENTH SUPPORTED PAGE 15H
14 ELEVENTH SUPPORTED PAGE 16H
15 TWELVTH SUPPORTED PAGE 18H
16 THIRTEENTH SUPPORTED PAGE 2FH
17 FOURTEENTH SUPPORTED PAGE 30H
18 FIFTEENTH SUPPORTED PAGE 31H
19 SIXTEENTH SUPPORTED PAGE 32H
20 SEVENTEENTH SUPPORTED PAGE 33H
21 EIGHTEENTH SUPPORTED PAGE 34H
22 NINETEENTH SUPPORTED PAGE 35H
23 TWENTIETH SUPPORTED PAGE 36H
24 TWENTY FIRST SUPPORTED PAGE 37H

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters
5.2.2 Log Page 02h (Write Error This log page contains the counters for write errors.
Counter)
Table 196: Write Error Counter Log Page
Bit
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE = 02H
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 38H
(LSB)
4:5 (MSB)
PARAMETER CODE = 0000H
ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY
(LSB)
6 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0
7 PARAMETER LENGTH (04H)
8:11 ERROR CORRECTED WITHOUT SUBSTANTIAL DELAY = 0000
12:13 (MSB)
ERRORS CORRECTED WITH POSSIBLE DELAYS
(LSB)
16:19 DELAYED ERROR CORRECTED COUNT = 0000
20:21 (MSB)
TOTAL REPEATED COMMANDS
(LSB)
24:27 TOTAL REPEATED COMMANDS = 0000
28:29 (MSB)
TOTAL ERRORS CORRECTED
(LSB)
32:35 TOTAL ERRORS CORRECTED = 0000
36:37 (MSB)
TOTAL TIMES CORRECTION ALGORITHM PROCESSED
(LSB)

Table 196: Write Error Counter Log Page (Continued)
Bit
Byte
7 6 5 4 3 2 1 0
40:43 TOTAL TIMES CORRECTION ALGORITHM PROCESSED = 0000
44:45 (MSB)
TOTAL BYTES PROCESSED
(LSB)
48:51 TOTAL BYTES PROCESSED = 0000
52:53 (MSB)
TOTAL UNCORRECTED ERRORS
(LSB)
56:59 TOTAL UNCORRECTED ERRORS = 0000
Currently, the LSISS2520/LSISS2530 device does not support these PARAMETER CODE
fields and hence the LSISS2520/LSISS2530 device returns default values 0000h for
these fields.
 ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY
This field specifies the number of Errors corrected without any delay for write type
commands.
 ERRORS CORRECTED WITH POSSIBLE DELAYS
This field specifies the number of Errors corrected with substantial delay for write
type commands.
 TOTAL REPEATED COMMANDS
This field specifies the total commands that are repeated for processing (Rewrites).
 TOTAL ERRORS CORRECTED
This field specifies the total number of Errors corrected for write type commands.
 TOTAL TIMES CORRECTION ALGORITHM PROCESSED
This field specifies the total number of times the correction algorithm part was
processed by the firmware for write type commands.

 TOTAL BYTES PROCESSED

This field specifies the total number of bytes processed for the write type
commands.
 TOTAL UNCORRECTED ERRORs
This field specifies the total number of uncorrected error for the write type
commands.
5.2.3 Log Page 03h (Read Error This log page contains the counters for read errors.
Counter)
Table 197: Read Error Counter Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 38H
(LSB)
4:5 (MSB)
(LSB)
12:13 (MSB)
(LSB)
20:21 (MSB)
PARAMETER CODE= 0002H
(LSB)
28:29 (MSB)
(LSB)

Table 197: Read Error Counter Log Page (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
36:37 (MSB)
(LSB)
44:45 (MSB)
(LSB)
52:53 (MSB)
(LSB)
56:59 TOTAL UNCORRECTED ERRORs = 0000
these fields.
 ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY
This field specifies the number of Errors corrected without any delay for read type
commands.
This field specifies the number of Errors corrected with substantial delay for read
type commands.
This field specifies the total commands that are repeated for processing (Rereads).
This field specifies the total number of Errors corrected for read type commands.


processed by the firmware for read type commands.
This field specifies the total number of bytes processed for the read type
commands.
 TOTAL UNCORRECTED ERRORS
This field specifies the total number of uncorrected error for the read type commands.
5.2.4 Log Page 05h (Verify Error This log page contains the counters for verify errors.
Counter)
Table 198: Verify Error Counter Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 38H
(LSB)
4:5 (MSB)
(LSB)
12:13 (MSB)
(LSB)
20:21 (MSB)
(LSB)

Table 198: Verify Error Counter Log Page (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
28:29 (MSB)
(LSB)
36:37 (MSB)
(LSB)
44:45 (MSB)
(LSB)
52:53 (MSB)
(LSB)
56:59 TOTAL UNCORRECTED ERRORs = 0000
these fields.
 ERROR CORRECTED WITHOUT SUBSTANTIAL DELAY
This field specifies the Number of Errors corrected without any delay for verify
type commands.
This field specifies the Number of Errors corrected with substantial delay for verify
type commands.


This field specifies the total verify commands that are repeated for processing.
This field specifies the total number of Errors corrected for Verify Type commands.
processed by the firmware for verify type commands.
This field specifies the total number of bytes processed for the verify type
commands.
 TOTAL UNCORRECTED ERRORS
This field specifies the total number of uncorrected errors for the verify
type commands.
5.2.5 Log Page 06h (Non-Medium The Non-Medium Error log page provides for summing the occurrences of recoverable
Error Log page) error events other than write, read, or verifies failures. No discrimination among the
various types of events is provided by PARAMETER CODE.
Table 199: Non-Medium Error Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 06H
(LSB)
4:5 (MSB)
NON MEDIUM ERROR COUNT
(LSB)
8:9 NON MEDIUM ERROR COUNT= 0000
 NON MEDIUM ERROR COUNT

This field specifies the total number of Non-medium errors occurred. Currently, the
LSISS2520/LSISS2530 device does not support this field. The LSISS2520/LSISS2530
device sends default value (0000h) for this field.

5.2.6 Log Page 0Dh (Temperature Page 0Dh indicates the Temperature Log Page for the device connected to the
Log page) LSISS2520/LSISS2530 device. To get the temperature information of the
LSISS2520/LSISS2530 device, use the log page 33h.
Table 200: Temperature Log Page Format
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE(0DH)
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 0CH
(LSB)
4:5 (MSB)
(LSB)
TEMPERATURE
8 RESERVED
9 TEMPERATURE (°C)
10:11 (MSB)
(LSB)
REFERENCE TEMPERATURE
13 PARAMETER LENGTH(02H)
14 RESERVED
15 REFERENCE TEMPERATURE (°C)
 TEMPERATURE
This field contains a one-byte binary value that indicates the temperature of the
device connected to the LSISS2520/LSISS2530 device in degrees Celsius at the time
the LOG SENSE command is performed. Temperatures equal to or less than zero
degrees Celsius is indicated by a value of zero. If the LSISS2520/LSISS2530 device
cannot detect a valid temperature because of a sensor failure or other condition,
then the value returned is FFh. No comparison is performed between the
temperature value specified in parameter 0000h and the reference temperature
specified in parameter 0001h.
 REFERENCE TEMPERATURE
The REFERENCE TEMPERATURE for the connected device might be returned by the
LSISS2520/LSISS2530 device as follows:
— If the reference temperature is returned then it indicates the maximum
recommended continuous operating temperature for the connected device.
— It returns value FFh in PARAMETER CODE 0001h to indicate an invalid
reference temperature.

5.2.7 Log Page 0Eh (Start Stop Cycle This log page defines the Start Stop Cycle Counter.
Counter Log page)
Table 201: Start Stop Cycle Counter Log Page Format
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE(0Eh)
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 24h
(LSB)
4:5 (MSB)
(LSB)
DATE OF MANUFACTURE
8:11 (MSB)
YEAR OF MANUFACTURING (4 ASCII CHARACTERS)
(LSB)
12:13 (MSB)
WEEK OF MANUFACTURING(2 ASCII CHARACTERS)
(LSB)
14:15 (MSB)
(LSB)
PARAMETER CODE
ACCOUNTING DATE
18:21 (MSB)
ACCOUNTING DATE YEAR (4 ASCII CHARACTERS)
(LSB)
22:23
ACCOUNTING DATE WEEK (2 ASCII CHARACTERS)
24:25 (MSB)
(LSB)
PARAMETER CODE
SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME

Table 201: Start Stop Cycle Counter Log Page Format (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
28:31 (MSB)
SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME (4-BYTE BINARY NUMBER)
(LSB)
32:33 (MSB)
(LSB)
ACCUMULATED START STOP CYCLE
36:39 (MSB)
ACCUMULATED START STOP CYCLE(4 BYTE BINARY NUMBER)
(LSB)
 DATE OF MANUFACTURE
The year and week in the year that the LSISS2520/LSISS2530 device was
manufactured is contained in the parameter value of the log parameter in which
the PARAMETER CODE is 0001h. The date is expressed in numeric ASCII characters
(30h - 39h) in the form YYYYWW. This field cannot be changed using the LOG
SELECT command.
 ACCOUNTING DATE
The ACCOUNTING DATE specified by PARAMETER CODE 0002h can be modified and
saved using a LOG SELECT command to indicate when the LSISS2520/LSISS2530
device was placed in service. If the parameter is not yet set or cannot be set, the
default value placed in the parameter field is six ASCII space characters (20h).
 SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME
This field contains a four-byte binary value that indicates how many stop-start
cycles can typically be performed during the lifetime of the LSISS2520/LSISS2530
device without degrading the LSISS2520/LSISS2530 device's operation or reliability
outside the limits specified by the manufacturer of the LSISS2520/LSISS2530 device.
This field cannot be changed using the LOG SELECT command.
 ACCUMULATED START-STOP CYCLES
This field contains a four-byte binary value that indicates how many stop-start
cycles the LSISS2520/LSISS2530 device has detected since its date of manufacture.
This field cannot be changed using the LOG SELECT command. The time at which
the count is incremented during a start-stop cycle is vendor specific.

5.2.8 Log Page 0Fh (Application The intended use for this information is to aid in describing the system configuration
Client Log page) and system problems.
Table 202: Application Client Log Page
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE = 0FH
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 4000H
(LSB)
APPLICATION CLIENT LOG PARAMETERS
4 FIRST APPLICATION CLIENT LOG PARAMETER
: :
259 :
16132 LAST APPLICATION CLIENT LOG PARAMETER
: :
16387 :
Table 203: General Usage Application Client Log Parameter Data
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE
(LSB)
2 DU = 1 DS = 0 TSD=0 ETC=0 TMC=0 LBIN = 1 LP = 1
3 PARAMETER LENGTH (FCH)
4:255 GENERAL USAGE PARAMETER BYTES
GENERAL USAGE PARAMETER BYTES represent data sent to the LSISS2520/LSISS2530

device in a previous LOG SELECT command. If a previous LOG SELECT command has
not occurred, the data is vendor specific. The LSISS2520/LSISS2530 device supports the
PARAMETER CODEs from 0000h to 01FFh.
The Application Client data is stored in the connected SATA device using WRITE LOG
EXT command. The PARAMETER LIST LENGTH in case of LOG SELECT command and
allocation length in case of LOG SENSE command must be in multiples of 256 bytes
plus 4 bytes for the header. Also the log parameters must be sent in sequentially
ascending order in the LOG SELECT data.

5.2.9 Log Page 10h (Self-Test Results This log page contains the self-test results of the underlying device present in the
Log Page) LSISS2520/LSISS2530 device system. The results of the twenty most recent self-tests are
stored in this Log page. If fewer than 20 self-tests have occurred, the unused self-test
log parameter entries is 0.
Table 204: Self-Test Results Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 190H
(LSB)
SELF-TEST RESULTS LOG PARAMETERS
4 FIRST SELF-TEST RESULTS LOG PARAMETER
: :
23 :
384 LAST SELF-TEST RESULTS LOG PARAMETER
: :
403 :
The following table describes the self-test results log parameter structure.
Table 205: LOG Sense Page 10h Log Parameter Structure
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE
(LSB)
4 SELF TEST CODE RESERVED SELF TEST RESULTS VALUE
5 EXTENDED SEGMENT NUMBER
6:7 (MSB)
ACCUMULATED POWER ON HOURS
(LSB)
8:15 (MSB)
ADDRESS OF FIRST FAILURE
(LSB)
16 RESERVED SENSE KEY

Table 205: LOG Sense Page 10h Log Parameter Structure (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
17 ASC
18 ASC QUALIFIER
19 RESERVED
 PARAMETER CODE
This field identifies the log parameter for the log page. The PARAMETER CODE field
for the results of the most recent test is 0001h. The parameter for the next most
recent is 0002h.
 SELF-TEST CODE
This field contains the content of the Function Code field in the SEND DIAGNOSTIC
command that initiated this self-test. Currently, the LSISS2520/LSISS2530 device
returns zero value in this field.
The Self-Test Results Value for this field is described in the following table.
Table 206: Self-Test Results Value
Value Description
0h The self-test routine completed without error.
1h The background self-test routine was aborted by the initiator using a SEND DIAGNOSTIC command with the Abort Background
self-test function.
2h The initiator aborted the self-test routine by a Task Management function of a reset.
3h An unknown error occurred while the target was executing the self-test routine and the target was unable to complete the self-test
routine.
4h The self-test completed having a test element that failed and the test element that failed is not known.
5h The first segment of the self-test failed.
6h The second segment of the self-test failed.
7h The third or greater segment of the self-test failed.
8h to Eh RESERVED
Fh The self-test is in progress.
 EXTENDED SEGMENT NUMBER

This field identifies the number of the segment that failed during self-test. If no
segment failed, this field is 00h. Currently, the LSISS2520/LSISS2530 device return
zero value in this field.
 ACCUMULATED POWER ON HOURS
This field contains the total accumulated power-on hours of the drive at the time
the self-test completed.

 ADDRESS OF FIRST FAILURE

This field contains the LBA of the first logical block where a self-test error occurred. If
no errors occurred during the self-test or the error is not related to a LOGICAL
BLOCK ADDRESS, then the field is FFFF FFFF FFFF FFFFh.
 SENSE KEY, ASC and ASC QUALIFIER
These fields contains the additional information relating to the error or exception
conditions during self-test.
Table 207: Extended Segment Number
Extended Segment Number Foreground Test Background Test

0h NA NA
1h LSISS2520/LSISS2530 device ready check LSISS2520/LSISS2530 device ready check
2h RAM Test NA
3h Spin Check Spin Check
4h Write/Read/Compare Write/Read/Compare
5h ECC Test ECC Test
6h Random Seek Random Seek
7h SMART Check SMART Check
8h Low Level Format Check Low Level Format Check
9h Physical Head Check Physical Head Check
Ah Read Scan Read Scan
Bh SMART Check SMART Check
— — —
5.2.10 Log Page 15h (Background This log page contains the Background Scanning Status parameter and Background
Scan Results Log page) Medium Scan parameters for the underlying device present in the
LSISS2520/LSISS2530 device system. The Background Scanning Status parameter
provides information about background pre-scan and background medium scan
operations. Each Background Medium Scan parameter corresponds to a logical block
where an error was detected.
Table 208: Background Scan Results log page PARAMETER CODEs
PARAMETER CODE Description

0000h Background Scanning Status
0001h to 0013h Background Medium Scan

The following table shows the Background Scan Results Log Page.
Table 209: Background Scan Results Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 1D8H
(LSB)
BACKGROUND SCAN RESULTS LOG PARAMETER
4:19 BACKGROUND SCANNING STATUS PARAMETER
BACKGROUND MEDIUM SCAN PARAMETER LIST
20:43 BACKGROUND MEDIUM SCAN PARAMETER (FIRST)
: :
452:475 BACKGROUND MEDIUM SCAN PARAMETER (NINETEENTH)
The following table shows the Background Scanning Status Parameter format.
Table 210: Background Scanning Status Parameter Format
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE (LSB) = 0000H
(LSB)
3 PARAMETER LENGTH (0CH)
4:7 (MSB)
ACCUMULATED POWER ON MINUTES
(LSB)
8 RESERVED
9 BACKGROUND SCANNING RESULTS
10:11 (MSB)
NUMBER OF BACKGROUND SCANS PERFORMED
(LSB)
12:13 (MSB)
BACKGROUND MEDIUM SCAN PROGRESS
(LSB)
14:15 RESERVED

 ACCUMULATED POWER ON MINUTES

This field indicates the number of minutes the device connected to the
LSISS2520/LSISS2530 device is powered on since manufacturing. The
LSISS2520/LSISS2530 device returns zero value in this field.
 NUMBER OF BACKGROUND SCANS PERFORMED
This field indicates the number of background scans been performed since the
device connected to the LSISS2520/LSISS2530 device was originally shipped by the
manufacturer. The LSISS2520/LSISS2530 device returns zero value in this field.
 BACKGROUND MEDIUM SCAN PROGRESS
This field is a percent complete indication of background indication.
Table 211: Background Scanning Status
Code Description
00h No background scans active
01h Background medium scan is active
02h Background pre-scan is active
03h Background medium scan halted because of a fatal error
04h Background medium scan halted because of a vendor-specific pattern of errors
05h Background medium scan halted because of medium formatted without P-list
06h Background medium scan halted - vendor-specific cause
07h Background medium scan halted because of temperature out of allowed range
08h Background medium scan halted, waiting for Background Medium Interval timer expiration
09h to FFh RESERVED
The following table shows the Background Medium Scan Parameter format.
Table 212: Background Medium Scan Parameter Format
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE = 0001H - 0013H
(LSB)
4:7 (MSB)
ACCUMULATED POWER ON HOURS
(LSB)
8 REASSIGN STATUS SENSE KEY
9 ASC
10 ASC QUALIFIER

Table 212: Background Medium Scan Parameter Format
BIT
Byte
7 6 5 4 3 2 1 0
11:15 RESERVED
16:23 (MSB)
(LSB)
 BACKGROUND MEDIUM SCAN PARAMETER

This field describes a defect location on the medium encountered by
background scanning.
 REASSIGN STATUS VALUE
The LSISS2520/LSISS2530 device returns zero value in this field.
 ACCUMULATED POWER ON HOURS
This field indicates the number of Hours the device connected to the
LSISS2520/LSISS2530 device has been powered on since manufacturing at the time
the background scan error occurred.
This field indicates the LBA associated with the medium error.
 SENSE KEY, ASC and ASC QUALIFIER
These fields contains the additional information relating to the error or exception
conditions during background scans.
Table 213: Reassign Status Values
Code Reported Description

0h No RESERVED
1h Yes The logical block specified by the LOGICAL BLOCK ADDRESS field failed and reassignment is pending receipt of
the following commands:
• A command performing a Write operation, if auto write reallocation is allowed;
• REASSIGN BLOCKS command.
2h No The logical block specified by the LOGICAL BLOCK ADDRESS field failed and was successfully reassigned by
the SCSI target device with recovered data.
3h RESERVED RESERVED
4h Yes The logical block specified by the LOGICAL BLOCK ADDRESS field failed and is reassignment by the SCSI
target device failed and the logical block does or does not have an error that is corrected.
5h No The logical block specified by the LOGICAL BLOCK ADDRESS field failed and was recovered by the SCSI target
device through a rewrite in-place.
6h Yes The logical block specified by the LOGICAL BLOCK ADDRESS field failed, was successfully reassigned by the
initiator, and contains valid data (For example, by a REASSIGN BLOCKS command that successfully recovered
the data, or by command performing a write operation).

Table 213: Reassign Status Values (Continued)
Code Reported Description

7h Yes Logical block specified by the LOGICAL BLOCK ADDRESS field was successfully reassigned by the initiator but
not contain valid value. (For example, Reassign block command that did not successfully recover the data.)
8h Yes Logical block specified by the LOGICAL BLOCK ADDRESS field was not successfully reassigned by the
initiator. (For example, Reassign block command that failed)
9h RESERVED RESERVED
Fh
5.2.11 Log Page 16h (ATA Log Page 16h reports descriptor format sense data for ATA PASS-THROUGH commands
PASS-THROUGH Results Log page) that were terminated with a CHECK CONDITION status by the SATA device that returned
Fixed format sense data and was not able to return the complete set of register
information for the SATA device connected to the LSISS2520/LSISS2530 device.
Table 214: ATA PASS-THROUGH Results Log page Format
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH
(LSB)
ATA PASS THROUGH RESULTS
4:29 FIRST ATA PASS THROUGH RESULTS LOG PARAMETERS
.. ..
368:393 LAST ATA PASS THROUGH RESULTS LOG PARAMETERS
The number of log parameters reported is less than or equal to 15.
Table 215: ATA PASS-THROUGH Results Log Parameter Format
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE
(LSB)
PARAMETER CONTROL
2 DU= 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1
DESCRIPTOR FORMAT SENSE DATA
4 RESPONSE CODE
5 RESERVED = 0 SENSE KEY

Table 215: ATA PASS-THROUGH Results Log Parameter Format (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
8:10 RESERVED = 0
11 ADDITIONAL SENSE LENGTH
ATA RETURN DESCRIPTOR
12 DESCRIPTOR CODE (09h)
13 ADDITIONAL DESCRIPTOR LENGTH (0Ch)
14 RESERVED EXTEND
15 ERROR
18 LBA_LOW (15:8)
19 LBA_LOW (7:0)
20 LBA_MID (15:8)
21 LBA_MID (7:0)
22 LBA_HIGH (15:8)
23 LBA_HIGH (7:0)
24 DEVICE
25 STATUS
 PARAMETER CODE
This field indicates the value of the LOG INDEX field minus one, returned in fixed
format sense of ATA Pass through results command. The device server supports log
parameter codes 0h through Eh.
 ATA RETURN DESCRIPTOR
See Section 4.2.3.1, ATA PASS THROUGH Status Return – Descriptor Format Sense Data.

5.2.12 Log Page 18h The Log Sense Page 18h (Protocol-Specific Port log page) provides SCSI transport
(Protocol-Specific Port Log page) protocol-specific parameters associated with the SCSI targets ports present in the
Table 216: Protocol Specific Port Log Page for SAS SSP
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE=18h
1 RESERVED
2:3 PAGE LENGTH = F0H
4:123 PROTOCOL SPECIFIC PORT LOG PARAMETER – PORT A
124:243 PROTOCOL SPECIFIC PORT LOG PARAMETER – PORT B
The following table shows Protocol Specific Port Log Parameter for SAS.
Table 217: Protocol Specific Port Log Parameter for SAS
BIT
Byte
7 6 5 4 3 2 1 0
0:1 (MSB)
PARAMETER CODE (0001H FOR PORT A AND 0002H FOR PORT B)
(LSB)
2 DU =0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1
3 PARAMETER LENGTH = 74H
4 RESERVED PROTOCOL IDENTIFIER (6H)
5 RESERVED
6 GENERATION CODE
7 NUMBER OF PHYS (01H)
8:119 SAS-2 PHY LOG DESCRIPTOR
The following table shows the SAS-2 PHY Log Descriptor.
Table 218: SAS-2 PHY Log Descriptor
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED
1 PHY IDENTIFIER = 00h
2 RESERVED
3 SAS PHY LOG DESCRIPTOR LENGTH = 6Ch
4 RESERVED ATTACHED DEVICE TYPE ATTACHED REASON
5 REASON NEGOTIATED LOGICAL LINK RATE

Table 218: SAS-2 PHY Log Descriptor
BIT
Byte
7 6 5 4 3 2 1 0
6 RESERVED ATTACHED SSP ATTACHED STP ATTACHED SMP RESERVED
INITIATOR PORT INITIATOR PORT INITIATOR PORT
7 RESERVED ATTACHED SSP ATTACHED STP ATTACHED SMP RESERVED
TARGET PORT TARGET PORT TARGET PORT
8:15 SAS ADDRESS
16:23 ATTACHED SAS ADDRESS
24 ATTACHED PHY IDENTIFIER
25:31 RESERVED
32:35 (MSB)
INVALID DWORD COUNT
(LSB)
36:39 (MSB)
RUNNING DISPARITY ERROR COUNT
(LSB)
40:43 (MSB)
LOSS OF DWORD SYNCHRONIZATION
(LSB)
44:47 (MSB) PHY RESET PROBLEM (LSB)
48:50 RESERVED
51 NUMBER OF PHY EVENT DESCRIPTORS = 5
52:63 PHY EVENT DESCRIPTOR (FIRST)
…
100:111 PHY EVENT DESCRIPTOR (FIFTH)
See Mode Page 36h (SAS Link Configuration) for details on selecting the PHY Event
Sources reported.
Table 219: SAS PHY Event Descriptor
BIT
Byte
7 6 5 4 3 2 1 0
0:2 RESERVED
3 PHY EVENT INFORMATION SOURCE
4:7 PHY EVENT INFORMATION
8:11 PEAK VALUE DETECTOR THRESHOLD

5.2.13 Log Page 2Fh (Informational This log page contains the SMART status and the Temperature reading of the
Exceptions Log page) underlying device present in the LSISS2520/LSISS2530 device system.
Table 220: Informational Exceptions Log Page
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED PAGE CODE = 2Fh
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 08H
(LSB)
4:5 (MSB)
(LSB)
6 DU= 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1
8 INFORMATIONAL EXCEPTION ASC
9 INFORMATIONAL EXCEPTION ASC QUALIFIER
10 MOST RECENT TEMPERATURE READING
11 RESERVED
 MOST RECENT TEMPERATURE READING

This field indicates the temperature in degrees Celsius of the device connected to
the LSISS2520/LSISS2530 device at the time the LOG SENSE command is performed.
Temperatures equal to or less than 0 degrees Celsius is indicated by a value of 0. If
the LSISS2520/LSISS2530 device cannot detect a valid temperature because of a
sensor failure or other condition, the value returned is FFh.
 INFORMATIONAL EXCEPTION ASC
If this field contains 0, no informational exception condition is pending and
contents of the INFORMATIONAL EXCEPTION ASC QUALIFIER field are unspecified.
If the INFORMATIONAL EXCEPTION ASC field contains any value other than 0, an
informational exception condition exists that has an ASC indicated by
INFORMATIONAL EXCEPTION ASC field and an ASC QUALIFIER indicated by the
INFORMATIONAL EXCEPTION ASC QUALIFIER field.

5.2.14 Log Page 30h (SATA Link This Log page is a vendor-specific log page for providing error details of underlying
Errors) device present in the LSISS2520/LSISS2530 device system.
All counters saturate at their maximum field value.
Table 221: SATA Link Errors Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 PAGE LENGTH = 20H
4:5 PARAMETER CODE = 0000H
7 PARAMETER LENGTH = 1CH
8:9 RESERVED
10:11 RECEIVE ERROR COUNT
12:13 RESERVED
14:15 TRANSMIT ERROR COUNT
16:19 LINK DOWN COUNT
20:21 RESERVED
22:23 DISPARITY ERROR COUNT
24:25 RESERVED
26:27 INVALID DWORD COUNT
28:29 RESERVED
30:31 LOSS OF DWORD SYNC COUNT
32:33 RESERVED
34:35 SPEED NEGOTIATION ERROR COUNT
 RECEIVE ERROR COUNT

SATA receive error count information. It counts for each error detected such that
R_ERR is returned to the device for a FIS received from the device.
 TRANSMIT ERROR COUNT
SATA transmit error count information. It increments when the device returns R_ERR
for a FIS transmitted by the LSISS2520/LSISS2530 device.
 LINK DOWN COUNT
This field indicates the number of times the SATA link went down.
 DISPARITY ERROR COUNT
SATA disparity error count. Specifies the number of running disparity errors
detected in a DWORD.

 INVALID DWORD COUNT

This field specifies the number of invalid DWORD detected by the
LSISS2520/LSISS2530 device on the SATA side.
 LOSS OF DWORD SYNC COUNT
This field specifies the number of loss of DWORD synchronizations on the SATA side.
 SPEED NEGOTIATION ERROR COUNT
This field specifies the number of SATA speed negotiation failures.
5.2.15 Log Page 31h - SMART Data This Log page is a vendor-specific log page for providing the SMART data structure of
the device present in the LSISS2520/LSISS2530 device system.
Table 222: SMART Data Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
4:515 SMART DATA
5.2.16 Log Page 32h - System This is a vendor-specific log page for providing the LSISS2520/LSISS2530 device
Statistics system statistics.
Table 223: Log Page 32h - System Statistics
BIT
BYTE
7 6 5 4 3 2 1 0
1 RESERVED
2:3 PAGE LENGTH = 3CH
6 DU=0 DS=1 TSD=0 ETC=0 TMC=0 TMC=0 LBIN=0 LP=0
8:11 NUMBER OF SCSI RESPONSES SENT
12:15 NUMBER OF SCSI READ/WRITE REQUESTS
16:19 NUMBER OF READS COMPLETED
20:23 NUMBER OF WRITES COMPLETED
24:27 NUMBER OF SATA I/O ERRORS
28:31 NUMBER OF PHY RESETS (SATA)
32:35 NUMBER OF PHY RESETS (SAS PORT A)
36:39 NUMBER OF PHY RESETS (SAS PORT B)
40:41 RESERVED

Table 223: Log Page 32h - System Statistics (Continued)
BIT
BYTE
7 6 5 4 3 2 1 0
42:43 NUMBER OF DISPARITY ERRORS (SATA PHY)
44:47 NUMBER OF DISPARITY ERRORS (SAS PHY A)
48:51 NUMBER OF DISPARITY ERRORS (SAS PHY B)
52:55 NUMBER OF CRC ERRORS (SATA PHY)
56:59 NUMBER OF CRC ERRORS (SAS PHY A)
60:63 NUMBER OF CRC ERRORS (SAS PHY B)
All counter within this log page saturate at their maximum field value. Also, these
counters are not stored in a nonvolatile memory.
Following are the meanings of the various fields within this log page:
 NUMBER OF SCSI RESPONSES SENT
This counter specifies the number of SCSI command responses sent.
 NUMBER OF SCSI READ/WRITE REQUESTS
This counter specifies the number of SCSI I/O requests processed by the
LSISS2520/LSISS2530 device. This is the sum of number of reads and writes received
by the LSISS2520/LSISS2530 device.
 NUMBER OF READS COMPLETED
This counter specifies the number of SCSI Read commands completed by the
 NUMBER OF WRITES COMPLETED
This counter specifies the number of SCSI Write commands completed by the
 NUMBER OF SATA I/O ERRORS
This counter specifies the number of SATA I/O errors. It considers the responses
received from the SATA device (for the I/O type of commands).
 NUMBER OF PHY RESETS (SATA PHY)
This field specifies the number of SATA PHY resets.
 NUMBER OF PHY RESETS (SAS PHY A)
This field specifies the number of SAS PHY A resets.
 NUMBER OF PHY RESETS (SAS PHY B)
This field specifies the number of SAS PHY B resets
 NUMBER OF DISPARITY ERRORS (SATA PHY)
This field specifies the number of Disparity errors detected at the SATA PHY.

 NUMBER OF DISPARITY ERRORS (SAS PHY A)

This field specifies the number of Disparity errors detected at the SAS PHY A.
 NUMBER OF DISPARITY ERRORS (SAS PHY B)
This field specifies the number of Disparity errors detected at the SAS PHY B.
 NUMBER OF CRC ERRORS (SATA PHY)
This field specifies the number of CRC errors detected at the SATA PHY.
 NUMBER OF CRC ERRORS (SAS PHY A)
This field specifies the number of CRC errors detected at the SAS PHY A.
 NUMBER OF CRC ERRORS (SAS PHY B)
This field specifies the number of CRC errors detected at the SAS PHY B.
The following counters in this log page do not support the Read-Clear feature.
 NUMBER OF DISPARITY ERRORS (SAS PHY A)
 NUMBER OF DISPARITY ERRORS (SAS PHY B)
 NUMBER OF CRC ERRORS (SAS PHY A)
 NUMBER OF CRC ERRORS (SAS PHY B)
In addition, the following counters are wrapping:
 NUMBER OF PHY RESETS (SAS PORT A)
 NUMBER OF PHY RESETS (SAS PORT B)
5.2.17 Log Page 33h This log page provides die temperature information of the LSISS2520/LSISS2530 device.
(LSISS2520/LSISS2530 Device
Temperature)
Table 224: LSISS2520/LSISS2530 Device Temperature Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 12H
(LSB)
4:5 (MSB)
TEMPERATURE
(LSB)
8 RESERVED
9 CURRENT TEMPERATURE (IN °C)

Table 224: LSISS2520/LSISS2530 Device Temperature Log Page (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
10:11 (MSB)
MAXIMUM TEMPERATURE
(LSB)
14 RESERVED
15 MAXIMUM TEMPERATURE (IN °C)
16:17 (MSB)
MINIMUM TEMPERATURE
(LSB)
20 RESERVED
21 MINIMUM TEMPERATURE (IN °C)
 TEMPERATURE
This field specifies the current temperature of the LSISS2520/LSISS2530 device. The
temperature equal to or less than zero degrees Celsius is indicated by a value of zero.
 MAXIMUM TEMPERATURE
This field specifies the maximum temperature and operating the device above this
temperature causes physical damage to the LSISS2520/LSISS2530 device.
 MINIMUM TEMPERATURE
This field specifies the minimum temperature and operating the device below this
temperature causes physical damage to the LSISS2520/LSISS2530 device.
The Maximum and Minimum temperatures indicated by the PARAMETER CODEs 0001h
and 0002h respectively can be modified and saved using a Log Select command. The
Minimum temperature value is less than or equal to the maximum temperature value
and the temperature values equal to or less than zero degrees Celsius are indicated by a
value of zero.
5.2.18 Log Page 34h This log page is used to retrieve the LSISS2520/LSISS2530 firmware logs. For details, see
(LSISS2520/LSISS2530 device Log Page) Log Retrieval.

5.2.19 Log Page 35h (Versions Page) This section describes Log Page 35h.
Table 225: Versions Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2:3 (MSB)
PAGE LENGTH = 9EH
(LSB)
7 PARAMETER LENGTH = 9AH
8:11 CHIP IDENTIFIER = 2520
12:15 CHIP REVISION = AB00
16:31 SERIAL NUMBER
32:39 WWN
40:47 SAS PORT A IDENTIFIER
48:55 SAS PORT B IDENTIFIER
56 BOARD FORM FACTOR HEIGHT
57 BOARD FORM FACTOR WIDTH
58:73 PART NUMBER
74:89 OEM NAME
90:101 REVISION
102:109 DATE OF MANUFACTURE
110:117 LOCATION OF MANUFACTURE
118:125 REFURBISH DATE
126:137 FIRMWARE VERSION
138:149 BOOT LOADER VERSION
150:157 CONFIGURATION DATA VERSION
158:161 PACKAGE VERSION
The following are the various fields within this log page.
 CHIP IDENTIFIER (4 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device CHIP IDENTIFIER.
 CHIP VERSION (4 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device chip revision as AB00 for the
B0 chips.

 SERIAL NUMBER (16 ASCII characters)

This field specifies the LSISS2520/LSISS2530 device SERIAL NUMBER.
 WWN (8 bytes)
This field specifies the LSISS2520/LSISS2530 device World Wide Name.
 PORT A IDENTIFIER (8 bytes)
This field specifies the LSISS2520/LSISS2530 device port A SAS address.
 PORT B IDENTIFIER (8 bytes)
This field specifies the LSISS2520/LSISS2530 device port B SAS address.
 BOARD FORM FACTOR HEIGHT (1 byte):
This field specifies the height of the LSISS2520/LSISS2530 device.
 BOARD FORM FACTOR WIDTH (1 byte)
This field specifies the width of the LSISS2520/LSISS2530 device.
 PART NUMBER (16 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device part number.
 OEM NAME (16 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device OEM name.
 REVISION (12 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device hardware revision.
 DATE OF MANUFACTURE (8 ASCII characters) (mm,dd,yyyy)
This field specifies the LSISS2520/LSISS2530 device manufacturing date.
 LOCATION OF MANUFACTURe (8 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device manufacturers location.
 REFURBISH DATE (8 ASCII characters) (mm,dd,yyyy)
This field specifies the LSISS2520/LSISS2530 device refurbish date.
 FIRMWARE VERSION (12 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device firmware version.
 BOOT LOADER VERSION (12 ASCII characters)
This field specifies the LSISS2520/LSISS2530 device Boot Loader version.
 CONFIGURATION DATA VERSION (8 Bytes)
This field specifies the LSISS2520/LSISS2530 device configuration data version.
 PACKAGE VERSION (4 Bytes)
This field specifies the LSISS2520/LSISS2530 device package version.

NOTE: The LOG SELECT command can modify and save only the Serial number, Part
number, Date of manufacture and Refurbish date fields. Ignore the other fields in the
LOG SELECT data. The Date of manufacture and Refurbish date fields must be set with
correct values in the mm,dd,yyyy format. The LSISS2520/LSISS2530 device does not
validate these fields.
5.2.20 Log Page 36h (Nonvolatile The log page 36h (nonvolatile scratch page) request that the Logical Unit read / write
scratch page) 4096 bytes to nonvolatile memory. The user has to supply their own checksum
algorithm to validate data integrity of this 4096 byte space. The LSISS2520/LSISS2530
device only validates that the data written is the same as the data it received.
Table 226: Log Page 36h
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
2 (MSB) PAGE LENGTH = 4096 (LSB)
3
4:4099 DATA TO NV
 PAGE LENGTH
This field indicates the length of data to be written to nonvolatile memory. This
value is equal to 4096.
 DATA TO NV
This field indicates the data to be written to the nonvolatile memory.
5.2.21 Log Page 37h - Firmware This Log page is a vendor-specific log page for providing the LSISS2520/LSISS2530
Statistics device firmware statistics. All counters saturate at their maximum field value.
Table 227: LSISS2520/LSISS2530 Device Firmware Statistics Log Page
BIT
Byte
7 6 5 4 3 2 1 0
1 RESERVED
6 DU=0 DS = 1 TSD=0 ETC=0 TMC=0 LBIN = 0 LP = 0
8:9 COMMAND TIMEOUTS ERROR COUNT

Table 227: LSISS2520/LSISS2530 Device Firmware Statistics Log Page (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
10:11 COMMAND ABORT ERROR COUNT
12:13 CHECK CONDITIONS ERROR COUNT
14:15 SOFTWARE RESET ISSUED COUNT
16:17 READ LOG EXT COUNT
18:21 READ LOG EXT-10 COUNT
22:25 RESERVED
 COMMAND TIMEOUTS ERROR COUNT

This field specifies the number of SCSI commands timed out.
 COMMAND ABORT ERROR COUNT
This field specifies the number of SCSI commands aborted.
 CHECK CONDITIONS ERROR COUNT
This field specifies the number of check conditions occurred.
 SOFTWARE RESET ISSUED COUNT
This field specifies the number of times SATA SRST has been performed.
 READ LOG EXT COUNT
This field specifies the number of READ LOG EXT command issued to SATA device.
This counter does not count for the READ LOG EXT commands issued in case of NCQ
errors.
 READ LOG EXT-10 COUNT
This field specifies the number of READ LOG EXT command issued to the connected
SATA device to read the NCQ Command Error log.

Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
5.3 VPD Parameters This section describes the VPD pages.

When the Offline Drive Change feature is enabled, if an INQUIRY command for a VPD
page (including VPD page 00) is received before the LSISS2520/LSISS2530 device has
received the IDD from drive, the inquiry command returns a CC status with ASC/ASCQ =
Becoming ready.
5.3.1 VPD Page 00 - List of pages The following table lists the VPD pages that the LSISS2520/LSISS2530 device supports:
Supported
Table 228: VPD Supported Page
BIT
Byte
7 6 5 4 3 2 1 0
1 PAGE CODE 00h
2 RESERVED
3 PAGE LENGTH 07h
4 SUPPORTED PAGE CODE 00h
10 SUPPORTED PAGE CODE B1h
 PAGE CODE
This field is set to 0. This field has the same value as in the page code field of the
INQUIRY command descriptor block.
 PAGE LENGTH
This field specifies the length of the following page data.
 SUPPORTED PAGE CODE
This field contains the PAGE CODEs supported by the target. The list is in
ascending order.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters
5.3.2 VPD Page 80 - Unit Serial This section describes the VPD Page 80 - Unit Serial Number.
Number
Table 229: Unit Serial Number VPD Page
Byte BIT
7 6 5 4 3 2 1 0
1 PAGE CODE 80h
2 RESERVED
3 PAGE LENGTH 14h
4 :23 PRODUCT SERIAL NUMBER
 PRODUCT SERIAL NUMBER

This field contains a representation of the Serial number field in the SATA IDENTIFY
DEVICE data (that is, words 19:10) last retrieved from the SATA device. Swap each
pair of bytes in the Serial number field to create a valid ASCII string format in the
PRODUCT SERIAL NUMBER field as described in following table.
Table 230: PRODUCT SERIAL NUMBER Translation
Byte Contents
0 IDENTIFY DEVICE word 10 bits 15:8 (that is, byte 1)
: ……………
5.3.3 VPD Page 83 - Device This section describes the VPD Page 83 - Device Identification Page.
Identification Page
Table 231: Device Identification VPD Page
Byte BIT
7 6 5 4 3 2 1 0
1 PAGE CODE 83h
2:3 PAGE LENGTH
4 DESIGNATION DESCRIPTOR IDENTIFYING THE LOGICAL UNIT NAME
n

Table 231: Device Identification VPD Page
Byte BIT
7 6 5 4 3 2 1 0
n+1:n+12 DESIGNATION DESCRIPTOR IDENTIFYING THE TARGET PORT IDENTIFIER
n+13:n+24 DESIGNATION DESCRIPTOR IDENTIFYING THE RELATIVE TARGET PORT IDENTIFIER
n+25:n+36 DESIGNATION DESCRIPTOR IDENTIFYING THE TARGET DEVICE NAME
The following table describes the Identification Descriptor Format.
Table 232: Identification Descriptor Format
BIT
Byte
7 6 5 4 3 2 1 0
0 PROTOCOL IDENTIFIER CODE SET
1 PIV RESERVED ASSOCIATION DESIGNATORTYPE
2 RESERVED
3 DESIGNATOR LENGTH
4:N DESIGNATOR
 LOGICAL UNIT NAME DESCRIPTOR

If the SATA device returns the IDENTIFY DEVICE data word 87 bit 8 set to 1 indicating
that the ATA device supports the World wide name field, the Logical unit name is
derived from the world wide name as shown in the following table.
Table 233: Logical Unit Name derived from World Wide Name
BIT
Byte
7 6 5 4 3 2 1 0
0 PROTOCOL IDENTIFIER (0h) CODE SET (1h)
1 PIV (0b) RESERVED ASSOCIATION (00b) IDENTIFIER TYPE (3h)
2 RESERVED
3 IDENTIFIER LENGTH (08h)
4 NAA IEEE COMPANY_ID
5:6 IEEE COMPANY_ID
7
8:11 VENDOR SPECIFIC IDENTIFIER

 VENDOR SPECIFIC IDENTIFIER

This field is based on the SATA IDENTIFY DEVICE data World wide name field as
described in the following table.
Table 234: Fields in the Logical Unit Name
Field
Contents
Field Name Specific bits
NAA Byte 4 bits 7:4 IDENTIFY DEVICE word 108 bits 15:12
IEEE COMPANY_ID Byte 4 bits 3:0 IDENTIFY DEVICE word 108 bits 11:8
Byte 5 IDENTIFY DEVICE word 108 bits 7:0
Byte 7 bits 7:4 IDENTIFY DEVICE word 109 bits 7:4
VENDOR SPECIFIC Byte 7 bits 3:0 IDENTIFY DEVICE word 109 bits 3:0
IDENTIFIER Byte 8 IDENTIFY DEVICE word 110 bits 15:8
If the SATA IDENTIFY DEVICE data returned by the SATA device word 87 bit 8 is set to 0,
indicating that the SATA device does not support the World wide name field, then the
Logical unit name is derived from the model number and serial number as shown in the
following table.
Table 235: Logical Unit Name Derived from the Model Number and Serial Number
BIT
Byte
7 6 5 4 3 2 1 0
0 PROTOCOL IDENTIFIER (0h) CODE SET (2h)
1 PIV (0b) RESERVED ASSOCIATION (00b) IDENTIFIER TYPE (1h)
2 RESERVED
3 IDENTIFIER LENGTH (68)
4:11 VENDOR IDENTIFICATION (ATA)
12:71 VENDOR SPECIFIC IDENTIFIER

 VENDOR SPECIFIC IDENTIFIER

This field is set to a representation of the ATA IDENTIFY DEVICE data Model number
field concatenated with a representation of the ATA IDENTIFY DEVICE data Serial
number field as described in the following table.
Table 236: VENDOR SPECIFIC IDENTIFIER Field for Logical Unit Name
Field
Contents
Field Name Specific bits
0 Model Number field IDENTIFY DEVICE word 27 bits 15:8
1 IDENTIFY DEVICE word 27 bits 7:0
... ...
40 Serial Number field IDENTIFY DEVICE word 10 bits 15:8
... ...
 TARGET PORT IDENTIFIER DESCRIPTOR

This field returns the port identifier value by which the target port can be referenced.
Table 237: TARGET PORT IDENTIFIER DESCRIPTOR
BIT
Byte
7 6 5 4 3 2 1 0
0 PROTOCOL IDENTIFIER = 6h CODE SET = 1h
1 PIV =1 RESERVED ASSOCIATION = 1 DESIGNATORTYPE = 3h
2 RESERVED
3 DESIGNATOR LENGTH = 8h
4 TARGET PORT IDENTIFIER DESIGNATOR
11

 RELATIVE TARGET PORT IDENTIFIER DESCRIPTOR

This field returns the identifier which is unique within the ports of
Table 238: RELATIVE TARGET PORT IDENTIFIER DESCRIPTOR
Byte BIT
7 6 5 4 3 2 1 0
0 PROTOCOL IDENTIFIER = 6h CODE SET = 1h
1 PIV = 1 RESERVED ASSOCIATION = 1 DESIGNATORTYPE = 4h
2 RESERVED
4:7 RELATIVE TARGET PORT IDENTIFIER DESIGNATOR
 TARGET DEVICE NAME DESCRIPTOR

The target device name in NAA format is returned.
Table 239: TARGET DEVICE NAME DESCRIPTOR
Byte BIT
7 6 5 4
0 PROTOCOL IDENTIFIER = 6 CODE SET = 1
1 PIV = 1 RESERVED ASSOCIATION = 2 DESIGNATORTYPE = 3h
2 RESERVED
4:11 TARGET DEVICE NAME DESIGNATOR
5.3.4 VPD Page 86 - Extended This following table describes VPD Page 86 - Extended Inquiry Data .
Inquiry Data
Table 240: Extended Inquiry Data VPD Page
Byte BIT
7 6 5 4 3 2 1 0
1 PAGE CODE 86h
2 RESERVED
3 PAGE LENGTH 3Ch
4 RESERVED SPT = 7 GRD_CHK APP_CHK REF_CHK
5 RESERVED GRP_SUP = 0 PRIOR_SUP = 0 HEADSUP = 1 ORDSUP = 1 SIMPSUP = 1
6 RESERVED COR_D_SUP = 0 NV_SUP = 0 V_SUP
7:63 RESERVED

 PAGE LENGTH
This field specifies the length of the following VPD page data and set it to 3Ch.
 SPT (Supported Protection Type)
This field indicates the type of protection the logical unit supports. Ignore the SPT
field if the PROTECT bit in the Standard Inquiry Data is set to 0. For the
LSISS2520/LSISS2530 device, this field returns 0x7, which indicates support for all
three protection types.
 GRD_CHK (Guard check)
This bit set to 0 indicates that the device server does not check the LOGICAL BLOCK
GUARD field in the protection information (Refer SBC-3), if any.
This bit set to 1 indicates that the device server checks the LOGICAL BLOCK GUARD
field in the protection information, if any.
 APP_CHK (Application tag check)
APPLICATION TAG field in the protection information (refer SBC-3), if any. The
LSISS2520/LSISS2530 device does not support Logical Block Application Tag
checking.
This bit set to 1 indicates that the device server checks the LOGICAL BLOCK
APPLICATION TAG field in the protection information, if any.
 REF_CHK (Reference tag check)
REFERENCE TAG field in the protection information (refer SBC-3), if any.
This bit set to 1 indicates that the device server checks the LOGICAL BLOCK
REFERENCE TAG field in the protection information, if any.
 GROUP_SUP (Grouping function supported)
This bit set to 1 indicates that the grouping function (refer SBC-3) is supported by
the device server.
This bit set to 0 indicates that the grouping function is not supported. The
LSISS2520/LSISS2530 device does not support Grouping. It is considered a reserved
case.
 PRIOR_SUP (Priority supported)
This bit set to 1 indicates that task priority (Refer SAM-4) is supported by the logical
unit.
This bit set to 0 indicates that task priority is not supported. The
LSISS2520/LSISS2530 device does not support task priority.
 HEADSUP (Head of queue supported)
This bit set to 1 indicates that the HEAD OF QUEUE task attribute (Refer SAM-4) is
supported by the logical unit.
This bit set to 0 indicates that the HEAD OF QUEUE task attribute is not supported.
The LSISS2520/LSISS2530 device Supports Head of queue task attribute.

 ORDSUP (Ordered supported)

This bit set to 1 indicates that the ORDERED task attribute (Refer SAM-4) is
supported by the logical unit. The LSISS2520/LSISS2530 device supports Ordering.
 SIMPSUP (Simple supported)
This bit set to 1 indicates that the SIMPLE task attribute (Refer SAM-4) is supported
by the logical unit. The LSISS2520/LSISS2530 device supports Simple.
 COR_D_SUP (Correction disable supported)
This bit set to 0 indicates that the device server does not support application clients
disabling read error checking on a logical block written using a WRITE LONG
command (refer SBC-3).
This bit set to 1 indicates that the device server supports application client disabling
read error checking on a logical block written using a WRITE LONG command. The
LSISS2520/LSISS2530 device does not support the correction disable attribute and
sets it to 0.
 NV_SUP
This bit set to 1 indicates that the device server supports a non-volatile cache and
that the applicable command standard defines features using this cache
(for example, the FUA_NV bit in SBC-3).
This bit set to 0 indicates that the device server does or does not support a
non-volatile cache. The LSISS2520/LSISS2530 device always returns the NV_SUP bit
set to 0.
 V_SUP
This bit set to 1 indicates that the device server supports a volatile cache and that
the applicable command standard defines features using this cache (for example,
the FUA bit in SBC-3).
This bit set to 0 indicates that the device server does or does not support a volatile
cache. The LSISS2520/LSISS2530 device support FUA. The LSISS2520/LSISS2530
device receives the underlying device's FUA data and sends the data to the initiator.
5.3.5 VPD Page 87 - Mode Page This following table describes the VPD Page 87 - Mode Page Policy.
Policy
Table 241: Mode Page Policy VPD Page
Byte BIT
7 6 5 4 3 2 1 0
1 PAGE CODE 87h
2:3 PAGE LENGTH (n-3)h
4:7 MODE PAGE POLICY DESCRIPTOR (first)
: ….
n-3:n MODE PAGE POLICY DESCRIPTOR (last)

The following table describes the MODE PAGE POLICY DESCRIPTOR Format.
Table 242: MODE PAGE POLICY DESCRIPTOR Format
Byte BIT
7 6 5 4 3 2 1 0
0 RESERVED POLICY PAGE CODE
1 POLICY SUBPAGE CODE
2 MLUS RESERVED MODE PAGE POLICY = 0
3 RESERVED
 The POLICY PAGE CODE and POLICY SUBPAGE CODE fields are set according to the
following table.
Table 243: POLICY PAGE CODE and POLICY SUBPAGE CODE Field Settings
POLICY PAGE CODE POLICY SUBPAGE CODE Description

3Fh FFh Retrieve all policy pages
02h 00h Disconnect-Reconnect mode page
19h 00h Protocol specific port mode page
19h 01h Protocol specific port mode page - subpage 01h
36h 00h Vendor Specific Mode Page: SAS Link
Configuration
 MLUS
This field is set to 1 for Policy PAGE CODE set to 02h, 19h (all SUBPAGE CODEs) and 36h.
 MODE PAGE POLICY
This field is set to Shared (0h) for POLICY PAGE CODE 3Fh, POLICY PAGE CODE 02h
and POLICY PAGE CODE 19h (all SUBPAGE CODEs - 00h, 01h 02h, 03h), and set to Per
Target Port (1h) for POLICY PAGE CODE 36h.

5.3.6 VPD Page 89 -SATA This following table describes the VPD Page 89 -SATA Information VPD Page.
Information VPD Page
Table 244: SATA Information VPD Page
Byte BIT
7 6 5 4 3 2 1 0
1 PAGE CODE 89h
2:3 PAGE LENGTH 238h
4:7 RESERVED
8:15 SAT VENDOR IDENTIFICATION
16:31 SAT PRODUCT IDENTIFICATION
32:35 SAT PRODUCT REVISION LEVEL
36:55 SATA DEVICE SIGNATURE
56 COMMAND CODE
57:59 RESERVED
60:571 SATA IDENTIFY DEVICE DATA
 SAT VENDOR IDENTIFICATION

This field contains an 8-byte ASCII string identifying the vendor of the
LSISS2520/LSISS2530 device. The data is left aligned within the field. The vendor
identification string is assigned by INCITS for use in the Standard INQUIRY data
VENDOR IDENTIFICATION field. The LSISS2520/LSISS2530 device sets this field to the
ASCII string LSI followed by ASCII spaces.
 SAT PRODUCT IDENTIFICATION
This field contains 16 bytes of ASCII data. The LSISS2520/LSISS2530 device sets this
field to the ASCII string LSISS25x0 followed by ASCII spaces.
 SAT PRODUCT REVISION LEVEL
This field contains four bytes of ASCII data.

 COMMAND CODE
This field contains the of the SATA command used to retrieve the data in the
IDENTIFY DEVICE for the LSISS2520/LSISS2530 device.
Table 245: SATA DEVICE SIGNATURE
Byte BIT
7 6 5 4 3 2 1 0
0 TRANSPORT IDENTIFIER
1 RESERVED INTERRUPT/ RESERVED PM PORT/RESERVED
RESERVED
2 STATUS (00 – 70h) any value in between (Setting of 6:4 bits is device specific)
3 ERROR = 01
4 LBA LOW = 01
5 LBA MID = 00
6 LBA HIGH = 00
7 DEVICE
8 LBA LOW EXP = (00)
9 LBA MID EXP = (00)
10 LBA HIGH EXP = (00)
11 RESERVED
12 SECTOR COUNT = 01
13 SECTOR COUNT EXP (00)
14:19 RESERVED
 TRANSPORT IDENTIFIER
This field is set to 34h indicating SATA as TRANSPORT layer.
 INTERRUPT
This bit and the PM PORT field are defined only if the TRANSPORT IDENTIFIER field is
set to 34h.
 INTERRUPT
This bit is set to 1.
For the remaining field description within the SATA DEVICE SIGNATURE, refer to
ATA8-APT and SATA-2.6 specs.

5.3.7 VPD Page B1 - Block Device The Block Device Characteristics VPD page contains parameters indicating the
Characteristics characteristics of the logical unit.
Table 246: Block Device Characteristics VPD Page
BIT
Byte
7 6 5 4 3 2 1 0
1 PAGE CODE B1h
2 RESERVED
3 PAGE LENGTH 3Ch
4:5 MEDIUM ROTATION RATE
6 RESERVED
7 RESERVED NOMINAL FORM FACTOR
8:63 RESERVED
 PAGE LENGTH
This field specifies the length of the following VPD page data and is set to 3Ch.
 MEDIUM ROTATION RATE
This field is set to the value of SATA IDENTIFY DEVICE data word 217.
 NOMINAL FORM FACTOR
This field indicates the nominal form factor of the device containing the logical unit
is set to the value of SATA IDENTIFY DEVICE data word 168 bits 3:0.


LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix A: | Boot Loader
Appendix A
System Initialization
This appendix describes the firmware initialization.
A.1 Boot Loader The main responsibilities of the Boot Loader are to identify, validate, and start
execution of the firmware image stored in flash. The flash contains up to two different
firmware images, two copies of boot flags, two copies of configuration data, and logs
and/or a crash dump.
When the Boot Loader is first executed, it runs a full memory test on all the internal
memories used to store code and data. If any of the memory tests fail, the Boot Loader
indicates this failure by blinking the Fault LED. Upon successful completion of the
memory test, the Boot Loader proceeds to identifying which image is to be executed.
The Boot Loader assumes that there is at least one known good image available in flash
memory. A known good image is defined as an image that allows enough functionality
to perform an in-band upgrade of the firmware image. The Boot Loader identifies the
image to be executed by examining the boot flags. The boot flags contain age
information (through a counter) and validity information about each image. The Boot
Loader first checks the validity of both images. If there is only one valid image, then the
Boot Loader continues to the validate stage. If both images are valid, then the Boot
Loader selects the image that is the newest based on the age of the image.
The Boot Loader validates the image by reading it from flash and calculating a CRC. If
the calculated CRC matches the CRC present in flash, the check is successful. The Boot
Loader then executes the image by jumping to the image's first instruction in flash.
The Boot Loader only invalidates an image where the boot flags show both images as
being valid and failure case occurs. There are two failure cases, one is if the image fails
the CRC check and the other is if there is a boot failure. A boot failure occurs when the
image is loaded and verified, but once execution is started, the image does not
complete initialization. The Boot Loader attempts to load this image for a fixed number
of times before marking it as invalid.
A.2 Firmware Initialization When the firmware executes, it runs the modules in the following order:
1. BSP Subsystem
2. Hardware Abstraction Subsystem
3. Console
4. Timer Subsystem
5. Configuration Manager
6. Log Manager
7. SCSI Engine
8. Transport Protocol Layer- SAS Driver
9. Device Layer-SATA Driver

Appendix A: | Device Spin-Up LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
A.3 Device Spin-Up In the LSISS2520/LSISS2530 device, the device spin up is controlled based on the
following configurable options:
 NOTIFY(ENABLE SPINUP) primitive
— The device is powered down initially and then powered up on receipt of this
primitive.
— The device is powered up initially but SATA staggered spin-up is enabled. When
the primitive is received, the SATA PHY is initialized, causing the device to spin
up.
 No Spin-up control at all
The device is powered on and spun-up immediately when power is applied to the
device carrier.
 Start/Stop Unit command
There are two options for the start/stop command.
— Power up device upon receipt of this command.
— Initialize the SATA PHY on receipt of this command.
There is an option to ignore spin-up on this SCSI command if NOTIFY (ENABLE SPIN-UP)
has not yet been received.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix B: | Device State Machine
Appendix B
State Machines
This appendix describes the Various State Machines maintained by the
LSISS25x0 bridge.
B.1 Device State Machine The Device State Machine operations are composed of five states.
B.1.1 Device State Machine The following figures shows the Device State machine operations.
Operations
SSD1 – SATA_DRIVE_INIT SSD4 – SATA_DRIVE_DOWN
Initialization Commands Failed N Times or Drive

not meet minimum standards for this Vendor
SSD3 – SATA_DRIVE_RESET
No Drive Response
Signature Received
SSD5 – SATA_WAITING_FOR_SPINUP_REQUEST
SSD2 – SATA_DRIVE_RDY
Spinup Request Received
Initialization
Commands
Failed under N Times Processor Reset
Error Recovery
Initialization Commands Passed
GRF000553-00
Figure 4: Device State Machine

Appendix B: | Device State Machine LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
B.1.1.1 SSD1: SATA_DRIVE_INIT The signature of the device has been received and the LSISS2520/LSISS2530 device
issues commands to bring the device to the ready state.
B.1.1.2 SSD2: The device is in a ready state suitable for accepting commands from the initiator.
SATA_DRIVE_READY
B.1.1.3 SSD3: The device has been reset (COMRESET, soft reset or a power cycle), and waiting to
SATA_DRIVE_RESET receive a signature.
B.1.1.4 SSD4: The device has failed and is non usable. No further attempt at error recovery is made. As
SATA_DRIVE_DOWN soon as the LSI2520/LSISS2530 device enters drive down state, it queues a Unit
attention condition with ASC/ASCQ set to 81/0. For details on command processing in
this state, see Section 3.2, Priority Commands.
B.1.1.5 SSD5:SATA_WAITING_FOR_ The device has been powered on., but has yet to receive a request from the initiator to
SPINUP_REQUEST spin up the device.
B.1.2 State Machine Initialization This section describes the State Machine Initialization operations.
B.1.2.1 Device Signature When a signature is received in the SSD3 (SATA_DRIVE_RESET) state, the signature is
Validation checked for validity. The cylinder low and cylinder high registers are valid when the
value is zero and Device/Head register is valid when it is either 0xA0 or 0x0. If the
signature is valid, the device State Machine transitions to SSD1 (SATA_DRIVE_INIT).
Otherwise it remains in SSD3 (SATA_DRIVE_RESET) state.
B.1.2.2 Device State Machine The Device State Machine has a number of control flags that determine the commands
Control Flags sent to the device. These commands make the device ready for operations.
The commands are sent to the device in this order:
1. Execute Device Diagnostics
2. Identify Device
3. Check Power Mode
4. Set Features (Set PIO Speed)
5. Set Features (Set Multi DMA Speed)
6. Set Features (Set UDMA Speed)
7. Set Features (Read Cache Enable/Disable)
8. Set Features (Write Cache Enable/Disable)
9. Set Features (Guaranteed In Order Delivery)
10. Set Features (Disable Revert to Power On Defaults on a Reset)
11. Smart (SCT Set Read Timeout), and Smart (SCT Set Write Timeout)
These commands, except Identify Device, can be enabled or disabled through the
Device State Machine Control Flags. If a mode select occurs that changes the value of
read or write cache, or read or write time-out, then those flags are enabled
automatically.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix B: | System State Machine
B.1.2.3 Device Qualification During SSD1 (SATA_DRIVE_INIT) state when the Identify Device Command is sent to the
Flags device. The device is checked for minimum level of support as specified in the device
Qualification flags. The drives ID data can be checked for Support of the following
features: NCQ Mode, SCT Commands, ATA7, ATA8, Smart, and device Based World Wide
Name.
If the Qualification flag is enabled and the device connected does not support the
feature, the device State Machine transitions to the SSD4 (SATA_DRIVE_DOWN) state
and logs the error.
B.2 System State Machine The System State Machine operations are composed of five states. The following figure
shows the System State machine operations.
LSISS2520/ LSISS2520/ LSISS2520/

LSISS2530_01_SYS_INT LSISS2530_02_SYS_RDY LSISS2530_04_SYS_STANDBY
Boot Successful
System Idle
Command Received
LSISS2520/
LSISS2530_05_SYS_DEGRADED
There are no longer LSISS2520/

any log sectors LSISS2530_03_SYS_DOWN
available
Processor Reset
Config or log sectors are

Boot Successful
not available
except no Log
Sectors
Boot Successful except error lookup table is bad or no

valid log and config sectors are left all are bad
3_00074-00
Figure 5: System State Machine
B.2.1 LSISS2520/LSISS2530_01: In the LSISS2520/LSISS2530_01: SYS_INIT state, the device is booting.

SYS_INIT
B.2.2 LSISS2520/LSISS2530_02: In the LSISS2520/LSISS2530_02: SYS_RDY state, the device is in the ready state and is
SYS_RDY being processed in the polling loop.

Appendix B: | System State Machine LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
B.2.3 LSISS2520/LSISS2530_03: In the LSISS2520/LSISS2530_03: SYS_DOWN state, the device has a major problem and
SYS_DOWN cannot continue with the normal operations. Only a crash dump retrieval, log retrieval,
firmware update and a few other important commands are operational. As soon as the
LSISS2520/LSISS2530 device enters this state, It queues a unit attention condition with
ASC/ASCQ = 81/1 and sends out a check condition response with sense key set to
hardware error and ASC/ASCQ set to 81/1 for the commands which are not supported
in this state. This UA and CC could not be overridden by using Error lookup table.
B.2.4 LSISS2520/LSISS2530_04: In the LSISS2520/LSISS2530_04: SYS_STANDBY state, the device is idle for a while and
SYS_STANDBY has lowered the power consumption.
B.2.5 LSISS2520/LSISS2530_05:SYS_ In the LSISS2520/LSISS2530_05:SYS_DEGRADED state, the device is functional but

DEGRADED unable to retrieve logs because of the flash going bad.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix C: | Configuration Data
Appendix C
Additional Information
This appendix describes the configuration data, device replacement algorithm, and
LED behavior.
C.1 Configuration Data Two copies of the configuration data are stored in the flash with each copy protected
by a checksum. The reason for the two copies is to ensure that there is at least one valid
copy of the configuration data in the flash in case a reset occurs while firmware is
attempting to update the flash.
During initialization, firmware scans the configuration and log area looking for valid
configuration data. It knows that it has found valid data if the first few bytes match a
predefined pattern and the CRC right after it passes for the section. If the first sector
checked does not pass this check, it continues to scan until it finds one that does or it
runs out of configuration and logs sectors. In the event of total failure, the firmware
loads the customer specific default data and attempts to rewrite the configuration
data. If this fails, the system enters the system down state.
Upon retrieving a good copy of configuration data, the firmware checks its version
label to determine if its what it is expecting. If the version is different, the device
processes the data using the Firmware Upgrade code to change the configuration data
to the current version. If the current firmware does not understand what the old
configuration version was, it sets the data to the customer specific default data.
When the first copy of configuration data is retrieved successfully, a byte compare of the
first copy with the second copy is performed to ensure that the second copy is good. If
the compare fails, then the second copy is overwritten with the data from the first.
On a configuration update, the first copy is written first and once completed, the
second copy is written. When this operation is a result of a SCSI command, the SCSI
Response is held until both writes are complete.

Appendix C: | Delaying SAS Links Bring Up LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
C.2 Delaying SAS Links Bring With the LSISS2520/LSISS2530 device, you can delay SAS links bring up on Power-On
Up reset until one of the following actions occurs.
 Identify Device Data (IDD) from the drive is received.
 The Drive State Machine enters the Drive Down State.
 The System State Machine enters the System Down State.
To enable this feature, perform the following steps:
1. Set WWN GenType to 0.
2. Set DEVICE SPIN-UP ALGORITHM to SPINUP IMMEDIATE (0x2).
See Section 5.1.13, Mode Page 32h (Firmware Parameter Control) for descriptions of
these fields.
If you do not enable this feature, the SAS links are brought up before the
LSISS2520/LSISS2530 device receives IDD from the drive.
If you do enable this feature, SAS links are not brought up after a Power-On reset until
IDD from the drive has been received. In case the LSISS2520/LSISS2530 device goes to
drive-down or system-down state, SAS links come up irrespective of whether IDD
response from the drive has been received or not (this is required for debugging). This
behavior is not applicable if the LSISS2520/LSISS2530 device is configured for a spin-up
algorithm other than SPINUP IMMEDIATE because the LSISS2520/LSISS2530 device
requires SAS links up for receiving notify spin-up primitive or start/stop unit command
from the initiator. See Section 5.1.13, Mode Page 32h (Firmware Parameter Control) for a
description of the DEVICE SPIN-UP ALGORITHM field.
C.3 Device Replacement The LSISS2520/LSISS2530 device supports the ability to initially connect to a device for
Algorithm the first time given any configuration. The LSISS2520/LSISS2530 device also supports
the ability to change the device while the LSISS2520/LSISS2530 device has no power.
If you wish to change the device when the LSISS2520/LSISS2530 device has no power
you must enable the following three features of the LSISS2520/LSISS2530 device.
 Enable WWN Override
 Program a WWN
 Enable OffLineDriveChangeEnable
If you do not enable these features, the LSISS2520/LSISS2530 device does not support
changing the device from its initially connected SATA device.
If all the three features are enabled, the LSISS2520/LSISS2530 device seamlessly
changes from one SATA device to another. The LSISS2520/LSISS2530 device also
responds to a test unit ready with a check condition of device becoming ready until the
SATA device has been spun up. It also returns the customer specific fake inquiry data
available until this point. Once the SATA device is capable of responding to an Identify
Device command, the actual inquiry data is available.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix C: | LED Behavior
C.4 LED Behavior This section describes the LED behavior.
C.4.1 Ready LED The behavior of the READY LED conforms to the SAS-2 spec.
C.4.2 Fault LED The Fault LED is primarily used by the Boot Loader to indicate status and error
conditions. The main firmware image uses it to indicate a crash. The following table
shows the Fault LED behavior.
Table 247: Fault LED behavior
State Description
Default Hardware State Fault LED is off
Power On Reset or Crash Fault LED is on
Image Loads Successfully Fault LED is off
Fatal Error Fault LED continuously blinks
Debug Mode with no failures Fault LED blinks once per iteration
Memory Test Fails Fault LED blinks twice per iteration
Boot Options CRC Failure Fault LED blinks three times per iteration
Image Boot Failure Fault LED blinks four times per iteration
Image CRC Failure Fault LED blinks five times per iteration
Image Invalid Failure Fault LED blinks six times per iteration
Other Failures Fault LED blinks seven times per iteration

Appendix C: | LED Behavior LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Firmware Upgrade
Appendix D
Firmware Upgrade
This appendix describes the firmware update.
D.1 Firmware Upgrade Use the Write Buffer command, with mode set to Download microcode with offsets and
save (mode 07h) and Buffer ID set to 1hA, to perform a nondisruptive in-band the
LSISS2520/LSISS2530 firmware upgrade. While the LSISS2520/LSISS2530 firmware
upgrade is in process, all I/O commands to the device are nondisruptive. The new
firmware is effective on the next reboot. The LSISS2520/LSISS2530 firmware upgrade
supports an option for immediate, deferred, and clean reset based on the Reboot After
firmware upgrade setting in mode page 0x32.
The LSISS2520/LSISS2530 device can receive one or multiple Write Buffer commands to
upgrade its firmware. The first Write Buffer command has Buffer Offset as zero. If this is
not the case, then the Write Buffer command is check conditioned with the sense key
as an illegal request, an additional sense key as an invalid field in CDB, and an
additional sense key qualifier as an invalid field in CDB.
If the subsequent Write Buffer commands are to be sent out of order (i.e., Write Buffer
commands with buffer offset out of sequence), the payloads of these commands must
be 4-Kb aligned (except for the last Write Buffer command).
After receiving the Write Buffer command with mode set to 7h and Buffer ID set to 1h,
the LSISS2520/LSISS2530 device transmits Transfer Readys with size 512 bytes to the
initiator. When the data is received from the initiator, it is written into the Non-Volatile
Memory. This process continues until all the bytes indicated by the Parameter List
Length field in the Write Buffer command are received from the initiator. If the write to
the Non-Volatile memory fails, the image is marked as bad, a check condition status
with sense key is set to HARDWARE ERROR, and additional sense data set to a
vendor-specific value indicating NVM write failure is sent back to the initiator.
If the initiator does not provide the data mentioned in the Parameter List Length field
of the Write Buffer command, the LSISS2520/LSISS2530 device detects this and
Check-Conditions the command. The initiator must issue all the Write Buffer
commands again for the firmware upgrade.

Appendix D: | Boot Loader Image Upgrade LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
D.2 Boot Loader Image Use the Write Buffer command, with the mode set to Download microcode with offsets
Upgrade and save (mode 07h) and the Buffer ID set to 0xEF, to perform an Inband Boot Loader
image upgrade. The LSISS2520/LSISS2530 Boot Loader Image upgrade is implemented
as a blocked and ordered command. (No other command is processed while Boot
Loader upgrade is in progress.) The new Boot Loader image comes into effect once the
boot image is written successfully in flash and then firmware restarts the
The LSISS2520/LSISS2530 device can receive a single Write Buffer command to upgrade
its Boot Loader. The Write Buffer command has Buffer Offset as zero. If this is not the
case, then the Write Buffer command is check conditioned with sense key as illegal
request, additional sense key as invalid field in CDB, and additional sense key qualifier
as invalid field in CDB.
After receiving the Write Buffer command, with the mode set to 7 and the buffer ID set
to 0xEF, the LSISS2520/LSISS2530 device transmits Transfer Ready's with 512 bytes to
the initiator. Once the data is received from the initiator, it is written into the
Non-Volatile Memory. This process continues until all the bytes indicated by the
Parameter List Length field in the Write Buffer command are received from the initiator.
If the write to the Non-Volatile memory fails, a check condition status is sent to the
initiator with the sense key set to HARDWARE ERROR and an additional sense data set
to a vendor-specific value indicating NVM write failure.
After the complete Boot Loader image successfully writes in flash, the flash is locked to
prevent accidental overwriting and a success status is sent to the initiator.
If the initiator does not provide the data mentioned in the Parameter List Length field
of the Write Buffer command, the LSISS2520/LSISS2530 device detects this and
Check-Conditions the command. The initiator must issue all the Write Buffer
commands again for the firmware upgrade.
NOTE: If the Boot Loader upgrade fails (caused by either a flash write failure or an
Under-run condition) and the Boot Loader on the LSISS25x0 device becomes corrupted,
the LSISS25x0 firmware cannot reboot again and the part becomes unusable. The
LSISS2520/LSISS2530 device must then be sent to the Lab to restore the Boot Loader. To
avoid this, perform the Boot Loader upgrade with extreme caution.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Boot Option Image Upgrade
D.3 Boot Option Image Use the Write Buffer command, with the mode set to Download microcode with offsets
Upgrade and save (mode 07h) with the Buffer ID set to 0x03, to perform an Inband Boot Option
image upgrade. The LSISS2520 Boot Option Image upgrade is implemented as a
blocked and ordered command (no other command is processed while the Boot
Loader upgrade is in progress.) The new Boot Option image comes into effect once the
boot image is written successfully in flash and then firmware restarts the
The LSISS2520/LSISS2530 device can receive a single Write Buffer command to upgrade
its Boot Option. The Write Buffer command has a Buffer Offset of zero. If this is not the
case, then the Write Buffer command is check conditioned with the sense key as an
illegal request, an additional sense key as an invalid field in CDB, and an additional
sense key qualifier as an invalid field in CDB. After receiving the Write Buffer command,
with the mode set to 7 and the buffer ID set to 0x03, the LSISS2520 device transmits
Transfer Readys with the size of Parameter list length bytes to the initiator. Once the
data is received from initiator, it is written into the Non-Volatile Memory. If the write to
the Non-Volatile memory fails, a check condition status is sent to the initiator with the
sense key set to HARDWARE ERROR and an additional sense data set to a
vendor-specific value indicating NVM write failure.
After the complete Boot Loader image successfully writes in flash, the flash is locked to
prevent accidental overwriting and a success status is sent to the initiator.
NOTE: If the Boot Loader upgrade fails (caused by either a flash write failure or an
Under-run condition) and the Boot Loader on the LSISS25x0 device becomes corrupted,
the LSISS25x0 firmware cannot reboot again and the part becomes unusable. The
LSISS2520/LSISS2530 device must then be sent to the Lab to restore the Boot Loader. To
avoid this, perform the Boot Loader upgrade with extreme caution.
D.4 Drive Firmware Upgrade The LSISS25x0 device performs the drive firmware upgrade with a Write Buffer
command with the mode field set to 0x5 (Download Microcode and Save) or
0x7(Download Microcode with Offsets and Save) and the buffer ID set to zero.
When the mode is set to 0x5 (Download Microcode and Save), the LSISS25x0 device
assumes that the complete drive firmware is sent in a single Write Buffer command. The
LSISSS25x0 device sends an ATA DOWNLOAD MICROCODE command to the ATA drive.
The Features field is set to 07h in ATA DOWNLOAD MICROCODE command when it
receives a Write Buffer command with the mode field set to 0x5 and the buffer ID 0.
When the mode is set to 0x7 (Download Microcode with Offsets and Save), the
LSISS25x0 device assumes that the complete drive firmware is being sent through
multiple Write Buffer commands. The LSISSS25x0 device sends an ATA DOWNLOAD
MICROCODE command with the ATA Features field set to 03h to the ATA device when it
receives a Write Buffer command with the mode field set to 0x7 and buffer ID 0.

Appendix D: | Package Firmware Upgrade LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The LSISSS25x0 device checks if the ATA DOWNLOAD MICROCODE command

completes with an error. If the ATA DOWNLOAD MICROCODE command completes with
an error, the LSISSS25x0 device terminates the command with the CHECK CONDITION
status with appropriately populated sense information. For drive error translation see
Section 3.15, Error Translations.
NOTE: After successful completion of a drive firmware upgrade through Write Buffer
Mode 5 buffer ID 0, the LSISS25x0 device performs automatic drive reset. With a Mode 7
buffer ID 0 drive firmware upgrade, the drive reset is left to the initiator.
D.5 Package Firmware The LSISS25x0 device supports the package firmware upgrade feature. In the package
Upgrade firmware upgrade, the LSISS25x0 firmware, boot loader, boot options, and the SATA
drive firmware can be bundled in a single package and all four components can be
upgraded through a single firmware upgrade operation.
The package sent by the host contains the following constituents:
 Package Main header – This is a mandatory part of the package. For more
information on the main package, see Section D.5.1, Main Package Header
Description, on page 256.
 Component headers – This is also a mandatory part of the package. This contains
the four individual component headers for the LSISS25x0 Boot loader, LSISS25x0
boot options, LSISS25x0 firmware, and drive firmware, in order. For more
information on the individual component headers, see Section D.5.2, Individual
Component Header Description, on page 257.
 LSISS25x0 Boot Loader – Optional. This is the first component of the package.
 LSISS25x0 Boot Options – Optional. This is the second component of the package.
 LSISS25x0 firmware image – Optional. This is the third component of the package.
 Drive image – Optional. This is the fourth component of the package.
This order of the components in the package is fixed and cannot be changed. The
header contains the revision for all the components and the package revision.
NOTE: The package must be generated using the lsi_package.exe utility from LSI.
The package firmware upgrade can be done either through multiple Write Buffer
commands (mode 0x7 buffer ID 0xA) or through a single Write Buffer command (mode
0x5 buffer ID 0xA).
If the package firmware upgrade is done using the mode 0x5 buffer ID 0xA, the entire
package must be sent through the single Write Buffer command. In this case, the
LSISS25x0 device responds to the command with the check condition, if the buffer
offset is set to a nonzero value.
If the package firmware upgrade is done using the mode 0x7 buffer ID 0xA, the
firmware upgrade takes place through multiple Write Buffer commands with each
command containing a chunk from a package as payload. In this case, following are the
assumptions made from the initiator perspective.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Package Firmware Upgrade
 The initiator splits the package into chunks, with the size of each chunk a multiple
of one KB, so an implied minimum of one KB. The minimum chunk size does not
apply to the last chunk from the package.
 The initiator sends the chunks of the firmware to the LSISS25x0 device in the correct
order. No repetitions or reordering of chunks is allowed.
 If the package contains LSISS25x0 firmware or Drive firmware as a component, the
following commands receive CC (DOWNLOAD MICROCODE IN PROGRESS) status if
they are sent when the package upgrade using multiple Write Buffers (Mode 0x7
buffId 0xA) is partially completed.
— FORMAT UNIT
— READ
— READ LONG
— REASSIGN BLOCKS
— START STOP UNIT
— SYNCHRONIZE CACHE
— VERIFY
— WRITE
— WRITE LONG
— WRITE SAME
— WRITE VERIFY
The initiators must send only the following commands:
— INQUIRY
— READ CAPACITY
— REPORT LUNs
 If any kind of failure is detected during Write Buffer command processing of a
multiple Write Buffer package upgrade sequence, the LSISS25x0 device exhibits the
following behavior:
— The Corresponding Write Buffer command is terminated with CC (appropriate
ASC/ASCQ) status.
— The package data received before the error was detected (data of the package
received through any previous and current Write Buffer commands) is discarded.
Hence the initiator needs to reinitiate the entire package upgrade sequence.
The package header has the starting offsets to each component. The LSISS25x0 device
parses the header and compares the Package Revision with the revision reported in the
Inquiry Data.
 If the Package Revision is newer that the one reported in the Inquiry Data, or the
Force Upgrade option is set to TRUE, then the contents of the package (Boot Loader,
Boot Options, or LSISS25x0 firmware) are written to non-volatile memory.
 If the package revisions match, then the LSISS25x0 device receives the package,
discards the contents of the package, and returns a SCSI GOOD status.
NOTE: Use the Boot Loader upgrade rarely and cautiously. If the upgrade of one or
more components included in the package is not successful, then the LSISS25x0 device
returns a SCSI Check Condition status for the Write Buffer command. If the Boot Loader
upgrade fails, then the LSISS25x0 device cannot boot successfully.

D.5.1 Main Package Header These are the constituents of the LSISS25x0 device’s package main header.
Description
 Package Signature – The Package Signature is used an identifier of package. The
package identifier value is LSIP.
 Package Revision – The Package Revision field, provides the revision of component
in the package. Before initiating the package update, the LSISS25x0 device
compares the package revision in package header to calculated package revision; if
the revision is different, then update routines are initiated. The package revision is
calculated on every boot by comparing the actual component revision detected
and the expected component revision (stored in the configuration data). If the
revisions of all the components match, then the package revision used during the
previous package upgrade is used as the calculated package revision. However, if a
mismatch is detected, then the calculated package revision is marked as bad (i.e.,
4321).If the package upgrade was partially successful, (i.e, LSISS25x0 firmware is
upgraded and the drive firmware upgrade is unsuccessful) the package revision is
reported as 4321. If no part of the package upgrade was successful, then the
package revision does not change.
 Package Utility Revision – The Package Utility Revision field indicates the revision of
the lsi_package.exe utility that is used to generate the package.
 Component Count – The Component Count field provides the number of
component present in the package.
 Package Option: – The Package Option field provides option for a force upgrade
field. The force upgrade option in the package header indicates that you ignore the
current package revision while deciding whether to update or not. If the force
upgrade bit is set, then the result of the package revision check is ignored, and the
package update is initiated.
 Ignore Flash – The Ignore Flash type flag in the package header is set, then,
irrespective of the value of the flash type field, the FW images included in the
package are used for the upgrade. If ignore flash type is not set LSISS25x0 compares
the flash type in main package header to flash type in the hardware; if flash type
matches, then the FW images included in the package are used for the upgrade.
 Flash type – This field is used to specify the flash type.
flash _type = 0; Image is for Flash of 512 KB
flash _type = 1; Image is for Flash of 2 MB, with 64 KB sector size
flash _type = 2; Image is for Flash of 2 MB, with 4 KB sector size
 pad_length – This field is used to specify the number of bytes added as padding
before the drive firmware (if the drive firmware is present in the package) to make
the position of the drive firmware 512 bytes aligned.
 CRC – The CRC field provides the CRC of the main header.

D.5.2 Individual Component Header These are the constituents of individual component header.
Description
 Signature – The signature identifies the component to be upgraded.
 Revision – The Revision field provides the revision of component in the package. If a
component is not included in the Package, then the corresponding component
revision uses a don't care value for the Package Revision check. The 'don't care
value' is also updated in the configuration data when the Package Update is
partially or completely successful. If the component revision is don't care we ignore
that component revision, while calculating the current package revision by
comparing the actual component revision detected and the expected component
revision (i.e., the revision mentioned in the package).
 Offset – The Offset field provides the offset in bytes of the component from the start
of the package.
 Length – The length field is the length of component in bytes. Length is set to zero if
the corresponding component is not the part of the package.
 Options field – You can use the Options field to specify any options. Currently, only
one option, Option_Reset, is supported.
Use the Option_Reset bit (bit 0 in the Options field) to specify the reset type, i.e.,
Deferred (Bit Reset) or Immediate (Bit Set). Deferred reset indicates that the initiator
initiates a reset. While creating a package using the lsi_package utility Option_Reset is
set by default to Immediate.
The Options_Reset bit controls the reset behavior of the LSISS25x0 device in
conjunction with the Mode Page 0x32 – Reboot After firmware upgrade flag.
See Table 172, LSISS25x0 Reset Behavior, on page 178 for the reset behavior of the
LSISS25x0 device after a package upgrade with various settings of the Options_Reset
bit and the Mode Page 0x32 – Reboot After firmware upgrade flag.
The following table shows the possible combinations of the various components in
package, status of the each component upgrade, and the overall package upgrade
status, when the option reset flag in Package Header is set.
Table 248: Package Firmware Upgrade Status Information
LSISS2520/LSISS
Boot loader Image Boot Option 2530 device Drive Image Package
SR No Successfully Image Successfully FW Image Successfully Upgrade
Upgraded Upgraded Successfully Upgraded Status
Upgraded
1 Y Y Y Y Successful
2 Y Y Y N Failure 1
3 Y Y N N Failure 2
4 Y N N N Failure 2
5 N N N N Failure 2
6 NA Y Y Y Successful
7 NA Y Y N Failure 1
8 NA Y N N Failure 2
9 NA N N N Failure 2

Table 248: Package Firmware Upgrade Status Information (Continued)
LSISS2520/LSISS
Boot loader Image Boot Option 2530 device Drive Image Package
SR No Successfully Image Successfully FW Image Successfully Upgrade
Upgraded Upgraded Successfully Upgraded Status
Upgraded
10 NA NA Y Y Successful
11 NA NA Y N Failure 1
12 NA NA N N Failure 2
13 Y Y NA NA Successful
14 Y N NA NA Failure 2
15 N N NA NA Failure 2
16 NA Y Y NA Successful
17 NA Y N NA Failure 2
18 NA N N NA Failure 2
19 Y NA NA Y Successful
20 Y NA NA N Failure 2
21 N NA NA N Failure 2
22 NA Y NA Y Successful
23 NA Y NA N Failure 2
24 NA N NA N Failure 2
25 NA NA Y NA Successful
26 NA NA N NA Failure 2
27 NA NA NA Y Successful
28 NA NA NA N Failure 2
39 NA Y NA NA Successful
30 NA N NA NA Failure 2
31 Y NA NA NA Successful
32 N NA NA NA Failure 2
 If the Package upgrade status is Successful, then the reported package revision is
the package revision mentioned in the Package Header.
 If the Package upgrade status is Failure1, then the reported package revision is 4321.
 If the Package upgrade status is Failure2, then the currently reported package
revision (i.e., the package revision before the package upgrade) is not changed.
 If the currently running image has revision ABCD and the new package to be
upgraded has package revision WXYZ, then after successful package upgrade, the
package revision reported is WXYZ.

upgraded has package revision WXYZ, and if the LSISS2520/LSISS2530 device
image update is successful in the package and the drive firmware update is
unsuccessful, then the package upgrade is unsuccessful and the package revision
reported after reboot is 4321.
upgraded has package revision WXYZ, and if none of the image upgrades in the
package are successful, then the package upgrade fails and the package revision
reported is ABCD.


LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix E: | Logging
Appendix E
Debug
This appendix describes the logging and crash dump format.
E.1 Logging The LSISS2520/LSISS2530 device provides a log with information about the crash dump
that is available in-band through the SCSI Log Sense command. In the event of a crash,
logs are preserved across resets. The Boot Loader reserves a section of memory
dedicated for these logs. The Boot Loader does not run a memory test in this memory
location if the reset was not caused by a power-on-reset.
E.1.1 Log Format Log entries are in a predefined format indicating the module, sub-module, and any
specific information that is relevant. A typical log entry is 8 to 16 bytes. Strings are only
used for debug images where the parallel flash is used. The following is a diagram of
both the normal and crash logs.
Normal Log
32-bits 32-bits 32-bits 32-bits
Parameter 1 Parameter 2
Timestamp Log Info
(optional) (optional)
Crash Log
32-bits 32-bits 32-bits 32-bits 32-bits
Timestamp Log Info Reason Crash Data Crash Data

Code 0 N
Log Info Details

31 30 29-28 27-26 25-24 23-21 20-17 16 15-0
V C LT R PC Module Sub- R Unique Code/Crash Log Size

Module
V = Valid Bit
C = Crash Log Bit
LT = Log Type
PC = Parameter Count
R = Reserved GRF000040_00
Figure 6: Normal and Crash Log Structure

Appendix E: | Logging LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
The following table lists the contents of each logs entry (each DWORD = 4 bytes).
Table 249: Log Entry Structure
Word Name Definition

0 Timestamp This timestamp has a resolution of 10 milliseconds and it starts from the time the LSISS2520/LSISS2530 device
was booted.
1 Log Info See Table 250.
2 Param1 Optional parameter 1.
3 Param2 Optional parameter 2.
The following table lists the log information.
Table 250: Log Information
Bit Name Definition

31 Valid If this bit is set to 1, then it is a valid log message.
30 Crash Log If this bit is set to 0, then the log entry is a crash dump. (See Table 255). For a crash dump, the Unique Code field
contains the size of the dump in bytes and the parameter count field is invalid.
If this bit is set to 1, then the log entry is a normal log entry.
29:28 Log Type These bits determine the priority of the debug and specify if the message is categorized as information or error. For
these values, see Table 251.
27:26 Reserved —
25:24 Parameter Count These bits contain the number of parameters for this log entry. Valid numbers are 0 to 2.
23:21 Module These bits specify the module from which the log message originated.
20:17 Sub Module These bits specify the sub module from which the log message originated.
16 Reserved —
15:0 Unique Code/ These bits uniquely identify the message that forms the format string.
Crash Log Size
Table 251: Log Type Bit Values
Bits
Log Type
29 28
0 0 Informational – These messages give the status of an
operation or the details about the firmware state at a
particular point of time.
0 1 Warning – These warnings do not halt the operations of
the LSISS2520/LSISS2530 device. Examples are queue
full conditions and check conditions.
1 0 Error – These messages signify that an error has
occurred in the LSISS2520/LSISS2530 device which
might affect normal operation.
1 1 Critical (Fatal) – These messages are for critical errors. In
most cases, the log entry is for a crash dump.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix E: | Logging
E.1.2 Logs Storage The logs generated in the system are placed in a circular buffer. The size of the buffer is
4K (the size of the serial flash sector). This provides room for a header and 968 dwords
to be stored in the buffer. This indicates that 242 to 484 log messages can be stored
depending on their size. Whenever the buffer overflows, the last log entry rolls over to
the start of the circular buffer.
E.1.3 Logging Level There is an option for configuring the logging level for the system. If the logging level is
a warning, then only warnings, fatal and errors are logged in the buffer. The logging
module conducts a run-time check on the logging level to decide if a log message
needs to be written to the buffer. In addition to storing log messages to the buffer, log
information is sent to the console if there is a serial port present. Logs exiting the serial
port are suffixed with LOG:.
E.1.4 Log Retrieval The logs are retrieved through the Log Sense command or through out-of-band
management. Log Sense Command with Page code 34h (vendor specific) is used for
retrieving the logs from the LSISS2520/LSISS2530 device.
Table 252: Log Sense Page 34h, Subpage 00h, LSISS2520/LSISS2530 Device Log
BIT
Byte
7 6 5 4 3 2 1 0
0 DS = 1 SPF = 1 Page Code = 34h
1 Subpage Code = 00h
2:3 (MSB) Page Length (LSB) = 1000h
4:7 Version = 16h
8:9 Size of Header = 8Ch(140)
10:11 Data Sector Data Sector Data Sector RESERVED
Good Empty Type
12:23 LSISS2520/LSISS2530 Firmware Revision
24:27 LSISS2520/LSISS2530 Hardware Revision
28:67 Device Model Number
68:87 Device Serial Number
88:95 Device Firmware Revision
96 Device NCQ Device Write Device SATA Device SATA Device SATA Device SATA RESERVED
Support Cache Enable Cache Enable Cache Support look Ahead Look Ahead
Enable Support
97 Device Queue Depth
98:113 PCB Part Number
114:129 LSISS2520/LSISS2530 Serial Number
130 Number of Boots Since Last Crash Dump
131 RESERVED
132:139 World Wide Name
140:141 Start Log
142:143 End Log
144:4099 Log Messages

Appendix E: | Logging LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Based on the given Log Sense command, appropriate log pages are returned to the
user. The Log Sense page reads log data from the flash. System maintains the current
log sector in flash.
The following table lists the Log Entry structure.
Table 253: Log Sense Page 34h Log Entry Structure
BIT
Byte
7 6 5 4 3 2 1 0
0:3 Time Stamp
4:7 Log Info
8:N Log Specific Data
Mode Select Command with Page code 25h(vender specific) is used to get/set the
logging configuration information.
For details, see Mode Page 25h (Logging Configuration Parameters).
Table 254: Log Sense Page 34h, Subpage 01h, Crash Dump
BIT
Byte
7 6 5 4 3 2 1 0
0 DS = 1 SPF = 1 Page Code = 34h
1 Subpage Code = 01h
2 (MSB)
3 Page Length = 1000h
(LSB)
4:4099 LSISS2520/LSISS2530 Crash Dump
E.1.5 Crash Log Format During firmware panics or other catastrophic failures for certain processor exceptions,
the firmware generates a crash log. This log provides sufficient information to help
identify the cause of the failure in firmware. The contents of the dump information
depend on the type of failure that triggered the dump.
The following is the format for the crash log.
Table 255: Crash Log Format

0 Timestamp This timestamp has a resolution of 10 milliseconds and it starts from the time the LSISS2520/LSISS2530 device was
booted.
1 Log Info For the crash log, bits [15:0] contain the size of the log in words.
2 Reason Code The code that identifies the reason for the log.
3:N Reason Specific These fields contain reason specific information.
Information

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix E: | Crash Dump format
The following is an example crash log. In this example, an ARM data abort exception
has occurred. The exception handler creates this log, saving the ARM® registers (r0 - r15
and the CPSR and SPSR) and the last 64 bytes of the stack.
Table 256: Crash Log Example

0 Timestamp Current timestamp for the crash
1 Log Info Crash Dump of size (M * 4) bytes
2 Reason Code Data Abort Processor Exception
3:N Reason Specific ARM Specific Processor Registers (R0 - R15, CPSR, SPSR…)
Information
N+1:M Reason Specific Stack Trace - Last 64 entries of the stack for the normal operating processor mode
Information
continued
E.2 Crash Dump format The following table shows the crash dump format.
Table 257: Crash Dump format
Section Title Word Index Values

Header 0x0000 – 0x0003 Timestamp, Length, Reason Code, Crash dump
version. The following rows lists the crash
dump format for crash dump version 106.
Firmware 0x0004 – 0x0006 LSISS2520/LSISS2530 FW Version String
CPU Registers 0x0007- 0x0081 ARM Registers
SM Ports 0x0082 – 0x00E9 Hardware Registers
SASAM 0x00EA – 0x00FC Hardware Registers
MPRM 0x00FD – 0x013E Hardware Registers
MPTM 0x013F – 0x017A Hardware Registers
DM 0x017B – 0x01BA Hardware Registers
DBM 0x01BB – 0x01BD Hardware Registers
DMA 0x01BE – 0x01C4 Hardware Registers
CBM 0x01C5 – 0x01D3 Hardware Registers
Subsystem 0x01D4 – 0x01E1 Hardware Registers
SATA Port 0x01E2 – 0x0221 Hardware Registers
MISC 0x0222 – 0x0246 Hardware Registers
Lynx 0x0247 – 0x02B4 Lynx™ Registers
g_STHDGlobal 0x02B5 – 0x02BF Firmware Structure
SE Abort Details 0x02C0 – 0x02C4 Firmware Structure
SE Lun State 0x02C5 Firmware Structure
SE Task Set 0x02C6 – 0x02D0 Firmware Structure
SE Background TD 0x02D1 – 0x02E5 Firmware Structure
SE Misc 0x02E6 Firmware Structure
SAS Port Counts 0x02E7 – 0x030F Error Counters

Appendix E: | Crash Dump format LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 257: Crash Dump format (Continued)
Section Title Word Index Values

FW Init Table 0x0310 – 0x0327 Initiators
Task Descriptors 0x0328 - 0x03F0 Task List
State Machine State 0x03F1 Disk and System State
Log Info 0x03F2 – 0x03F3 Logging Info
NVM Defect 0x03F4 – 0x03FB Bad Sector Map
Timer 0x03FC – 0x03FF Timer Info

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table
Appendix F
Error Lookup Table
This appendix lists the Error lookup table.
F.1 Error Lookup Table This section lists the Error Lookup table.
F.1.1 FRU Code Values To assist in debugging problems, the FIELD REPLACEABLE UNIT CODE field of sense
data that is returned with a check condition is populated with the lower 8 bits of the
Instance ID. This allows easier identification of the particular instance of check
condition being generated from within the LSISS2520/LSISS2530 device firmware. See
Table 259 for the numeric value for the various FRU codes. FRU codes are returned with
both fixed and descriptor format sense data.
F.1.2 Sense Information This section describes the default Sense Information table maintained with the
LSISS2520/LSISS2530 device firmware.
Table 258: Sense Information
ErrorIdx
Skey ASC ASCQ
ErrorIdx Numeric Description
(Hex) (Hex) (Hex)
Value
Unit Attentions
UA_ERROR_CODE_SCSI_BUS_RESET 0 6 29 2 Error code returned when unit attention condition is established
because of a hard reset.
UA_ERROR_CODE_ABRT_TS 1 6 2F 2 Error code returned when unit attention condition is established
because a task management function is in progress.
UA_ERROR_CODE_FLASH_WRITE_F 2 6 3 0 Instance ID reserved, removed from the current implementation.
AILURE
UA_ERROR_CODE_MICROCODE_UP 3 6 3F 1 Instance ID reserved, removed from the current implementation.
DATED
UA_ERROR_CODE_RESERVATIONS_ 4 6 2A 4 Error code returned when unit attention condition is established
CLEARED because persistent reservation with registrants only type or all
registrants type was released.
UA_ERROR_CODE_REGISTRATIONS 5 6 2A 5 Error code returned when unit attention condition is established
_PREEMPTED because the persistent reservation of the I_T NEXUS has been
preempted.
UA_ERROR_CODE_INITIATOR_LOGI 6 6 29 1 Error code returned when unit attention condition is established
N because power on occurred and an initiator logged in.
UA_ERROR_CODE_LOG_PARAMETE 7 6 2A 2 Error code returned when unit attention condition is established
RS_CHANGED because the target device does not support independent states of
log parameters and log parameters which could affect other I_T
NEXUS are changed.

Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 258: Sense Information (Continued)
ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
UA_ERROR_CODE_MODE_PARAME 8 6 2A 1 Error code returned when unit attention condition is established
TERS_CHANGED because mode parameters which affect the I_T NEXUS are changed
on another I_T NEXUS.
UA_ERROR_CODE_BACKGROUND_ 9 6 0B 3 Error code returned when unit attention condition is established
SELF_TEST_FAILED because self test running in the background mode failed.
UA_ERROR_CODE_DRIVE_NON_PO 10 6 29 3 Error code returned when unit attention condition is established
WERON_RESET because logical unit reset occurred.
UA_ERROR_CODE_MEDIUM_CHAN 11 6 28 0 Error code returned when unit attention condition is established
GED because underlying ATA drive returned SATA error MC.
UA_ERROR_CODE_MEDIUM_REMO 12 6 5A 1 Error code returned when unit attention condition is established
VAL_REQUEST because underlying ATA drive returned SATA error MCR.
UA_ERROR_CODE_CRASH_RESET_ 13 6 29 4 Error code returned when unit attention condition is established
OCCURED because reboot due to panic occurred in the LSISS2520/LSISS2530
firmware.
UA_ERROR_CODE_DRIVE_DOWN 14 6 81 0 Error code returned when unit attention condition is established
because the LSISS2520/LSISS2530 device entered drive down state.
UA_ERROR_CODE_SATA_LINKSPEE 15 6 82 0 Error code returned when unit attention condition is established
D_SET_ERR because the LSISS2520/LSISS2530 device was unable to program the
set link speed configured using the mode page interface.
UA_ERROR_CODE_INQ_DATA_CHA 16 6 3F 3 Error code returned when unit attention condition is established to
NGED inform the initiator that the Inquiry data has been changed.
UA_ERROR_CODE_A0_HARDWARE 17 6 83 0 Error code returned when unit attention condition is established to
inform the initiator that the underlying hardware is A0.
UA_ERROR_CODE_CAPACITY_CHA 18 6 2A 9 Error code returned when unit attention condition is established
NGED because the max LBA value has been changed by another initiator
on another I_T NEXUS.
UA_ERROR_CODE_FAILURE_PREDIC 19 6 5D 0 Error code returned when unit attention condition is established
TION_THRESHOLD_EXCEEDED because the device has detected a threshold exceeded condition.
UA_ERROR_CODE_POR_OR_BUS_D 20 6 29 0 Error code returned when unit attention condition is established
EVICE_RESET because of drive reset or SATA link reset.
UA_ERROR_CODE_CMDS_CLRED_B 21 6 2F 1 Error code returned when unit attention condition is established
Y_PWR_LOSS_NOTIFICATION when commands are cleared because Notify Power Loss primitive
has been received.
UA_ERROR_CODE_IT_NEXUS_LOSS 22 6 29 7 Error code returned when unit attention condition is established
_OCCURRED because of IT Nexus Loss occurred.
UA_ERROR_CODE_TIMESTAMP_CH 23 6 2A 10 Error code returned when unit attention condition is established
ANGED when time stamp is changed because of SET TIMESTAMP command.
UA_ERROR_CODE_RESERVED_1 24 6 0 0 Error code reserved for future use.

ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
Other Check Conditions
CC_ERROR_CODE_NO_SENSE_DAT 35 0 0 0 Error code returned when a command is check conditioned but no
A_AVAILABLE sense data is available.
CC_ERROR_CODE_DEFECT_LIST_N 36 0 19 1 Error code returned when a command is check conditioned in case of
OT_FOUND Read Defect Data command because it is not supported.
CC_ERROR_CODE_FAIL_PREDICTIO 46 0 5D 0 Error code returned when a command is check conditioned because
N_THRESHOLD_EXCEEDED of prediction threshold failure.
CC_ERROR_CODE_DATA_PROTECT 38 7 27 0 Error code returned when a command is check conditioned because
writing to medium is prohibited because of software write protect
bit set in control mode page.
CC_ERROR_CODE_BACKGROUND_E 39 2 4 0 Error code returned when a command is check conditioned because
RRRS logical unit is not ready and additional sense info is not available in
case of start stop unit.
CC_ERROR_CODE_SNS_NOT_RDY_I 40 2 4 2 Error code returned when a command is check conditioned because
NIT_CMD_REQUIRED drive is in standby mode and requires an initializing command.
CC_ERROR_CODE_SNS_NOT_RDY_ 41 2 5 0 Error code returned when the Test Unit Ready command is check
NO_RESP_BY_LU conditioned because the logical unit did not respond to selection.
CC_ERROR_CODE_SNS_NOT_RDY_ 42 2 3A 0 Error code returned when a command is check conditioned because
MED_ABSENT information from medium memory is inaccessible because of
absence of medium.
CC_ERROR_CODE_SNS_NOT_RDY_ 43 2 4 4 Error code returned when a command is check conditioned because
FMT_IN_PROG device is being formatted.
CC_ERROR_CODE_SELF_TEST_IN_P 44 2 4 9 Error code returned when a command is check conditioned because
ROGRESS self-test is being performed in foreground mode.
CC_ERROR_CODE_BECOMING_REA 45 2 4 1 Error code returned when a command is check conditioned because
DY the connected SATA drive is being initialized.
CC_ERROR_CODE_INITIATOR_OVER 46 2 55 3 Error code returned when we receive a command from a new
FLOW initiator, and our initiator table is full.
CC_ERROR_CODE_MISCOMP_DURI 47 E 1D 0 Error code returned when a command is check conditioned because
NG_VERIFY CRC check failed during write and verify operation.
CC_ERROR_CODE_HW_ERR_NO_SE 48 4 0 0 Error code returned when a command is check conditioned because
NSE of hardware error but additional sense information is not present.
CC_ERROR_CODE_HW_ERR_INT_TA 49 4 44 0 Error code returned when a command is check conditioned because
RGET_FAILURE of internal target failure.
CC_ERROR_CODE_HW_ERR_DIAG_ 50 4 40 84 Error code returned when a command is check conditioned because
FAIL_COMP_84 the underlying ATA drive resulted in self test execution status 4
FAIL_COMP_85 the underlying ATA drive resulted in self test execution status. 5.
FAIL_COMP_86 the underlying ATA drive resulted in self test execution status 6.

ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
FAIL_COMP_88 the underlying ATA drive resulted in self test execution status 8.
CC_ERROR_CODE_HW_ERR_LU_SE 54 4 3E 3 Error code returned when a command is check conditioned because
LF_TEST_FAILED the self-test being performed by the device in the foreground mode
results in test segment error.
CC_ERROR_CODE_DRIVE_IS_DOWN 55 4 81 0 Error code returned when DSM has gone to a Drive Down State, and
we receive a command that needs the DSM in the ready state.
CC_ERROR_CODE_MEDIUM_ERROR 56 3 0 0 Error code returned when a command is check conditioned because
_NO_SENSE of medium error but additional sense information is not available.
CC_ERROR_CODE_MEDIUM_FORM 57 3 31 0 Error code returned when a command is check conditioned because
AT_CORRUPTED format of the medium is corrupt.
CC_ERROR_CODE_LBA_MARKED_B 58 3 11 14 Error code returned when a write long(10) command is check
AD_APPLCLIENT conditioned because correction is disabled.
CC_ERROR_CODE_MED_ERR_UNRE 59 3 11 0 Error code returned when a command is check conditioned because
COVERED_READ the sector on which read or write operation is being performed is
bad or pseudo un-correctable.
CC_ERROR_CODE_MED_ERR_DIAG 60 3 40 87 Error code returned when a command is check conditioned because
_FAIL_COMP_87 the underlying ATA drive resulted in self test execution status 7.
CC_ERROR_CODE_PERIPHERAL_DE 61 3 3 0 Error code returned when a Write Buffer command is check
VICE_WRITE_FAULT conditioned because firmware upgrade fails or existing firmware
is invalidated.
CC_ERROR_CODE_AUTO_REALLOC 62 3 11 4 Error code returned when a command is check conditioned because
ATE_FAILED auto reallocation of logical blocks fails.
CC_ERROR_CODE_ILLEGAL_REQ_N 63 5 0 0 Error code returned because a command is illegal but additional
O_SENSE sense data is not available.
CC_ERROR_CODE_INV_FIELD_IN_C 64 5 24 0 Error code returned because a command is illegal since a field in CDB
DB of the command is not set correctly.
CC_ERROR_CODE_INV_FIELD_IN_P 65 5 26 0 Error code returned because a command is illegal because a field in
ARAM_LIST the list of parameters provided by the initiator is incorrect.
CC_ERROR_CODE_INV_OPCODE 66 5 20 0 Error code returned because a command is illegal because the no
valid command exists for the given command operation code.
CC_ERROR_CODE_INV_PARAM_LIS 67 5 26 2 Error code returned because a command is illegal because the length
T_LEN of parameter list provided is incorrect.
CC_ERROR_CODE_INSUF_REG_RES 68 5 55 4 Error code returned because a command is illegal because all the
OURCES resources required for registration are not present.
CC_ERROR_CODE_PER_RES_INV_RE 69 5 26 4 Error code returned because a command is illegal because the type
L of reservation provided does not match with actual type. Hence
release of persistent reservation failed.
CC_ERROR_CODE_LUN_NOT_SUPP 70 5 25 0 Error code returned because a command is illegal since report luns
ORTED command was requested for logical unit not supported by the target.
CC_ERROR_CODE_PARAM_LIST_LE 71 5 1A 0 Error code returned because a command is illegal because the length
N_ERR of parameter list provided is incorrect.
CC_ERROR_CODE_LBA_OUT_OF_R 72 5 21 0 Error code returned because a command is illegal because the logical
ANGE block address exceeds the capacity of the medium.

ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
CC_ERROR_CODE_VENDOR_SPECIF 73 5 80 80 Error code returned because a command is illegal because though
IC_FIRST_BURST_SET the first burst feature is not supported by the device, the enable first
burst bit is set.
CC_ERROR_CODE_INVALID_MESSA 74 5 49 0 Error code returned because a command is illegal because task
GE_ERROR attribute is not supported; here ACA attribute when ACA condition
does not exist.
CC_ERROR_CODE_REC_ERR_DEFEC 75 1 19 1 Error code returned when the requested defect list format and returned
T_LIST_NT_FOUND defect list format are not same in case of Read Defect Data command.
CC_ERROR_CODE_REC_ERR_ATAPA 76 1 0 1D Error code returned when ATA pass through command with check
SSTHRU_INFO_AVAILABLE condition bit set completes successfully.
CC_ERROR_CODE_REC_ERR_BGND 77 1 0B 3 Error code returned after condition specified in the MRIE field occurs
_SELFTEST_FAILED after self-test running in the background mode has failed.
CC_ERROR_CODE_ABORTED_NO_S 78 B 0 0 Error code returned when a command is aborted and no appropriate
ENSE additional sense data is available.
CC_ERROR_CODE_ABORTED_LBLK_ 79 B 10 1 Error code returned when a command is aborted because of DIF
GUARD_CHK_FAILED error - Logical guard check fails.
REF_TAG_FAILED error - Refer tag check fails.
APP_TAG_FAILED error - App tag check fails.
CC_ERROR_CODE_ABORTED_CAUS 82 B 4 0 Error code returned when a command is aborted but the cause is
E_NOT_REPORTABLE not reportable.
CC_ERROR_CODE_ABORTED_CMD_ 83 B 2C 0 Error code returned when a command is aborted because the
SEQ_ERROR commands are sent from initiator out of sequence.
CC_ERROR_CODE_ABORTED_MEDI 84 B 53 0 Error code returned when a command is aborted because the load
A_LOAD_EJECT_FAILED eject failed in case of start stop unit.
CC_ERROR_CODE_ABORTED_INF_U 85 B 47 3 Error code returned when a command is aborted because the ATA
INT_CRC_ERROR drive underneath returns command with a CRC error.
CC_ERROR_CODE_ABORTED_ATA_F 86 B 67 B Error code returned when a command is aborted because
EATURE_NT_EN corresponding feature is not enabled on the ATA drive underneath
CC_ERROR_CODE_ABORTED_DIAG 87 B 40 81 Error code returned when a command is aborted because the
_FAIL_COMP_81 underlying ATA drive resulted in self test execution status 1.
CC_ERROR_CODE_ABORTED_DATA 90 B 47 1 Error code returned when a command is aborted because CRC error
_PHASE_CRC_ERROR is present in the frame sent from the initiator.
CC_ERROR_CODE_ABORTED_LU_TI 91 B 8 1 Error code returned when a command is aborted because time-out
MEOUT occurred on the I_T_L nexus.
CC_ERROR_CODE_ABORTED_NAK_ 92 B 4B 4 Error code returned when a command is aborted since NAK was
RECEIVED received from the target.
CC_ERROR_CODE_ABORTED_CMDS 93 B 2F 0 Error code returned when a command is aborted because the
_CLRD_BY_OTHER_INIT command has been cleared by another initiator.

ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
CC_ERROR_CODE_ABORTED_ACK_ 94 B 4B 3 Error code returned when a command is aborted because time-out
NAK_TIMEOUT occurred for receiving ACK or NAK.
CC_ERROR_CODE_ABORTED_INFO 95 B 0E 1 Error code returned when a command is aborted because data frame
_UNT_TOO_SHORT of zero bytes was received from the target.
CC_ERROR_CODE_ABORTED_TOO_ 96 B 4B 2 Error code returned when a command is aborted because data frame
MUCH_WRITE_DATA received from the target contains more data than expected.
CC_ERROR_CODE_ABORTED_DATA 97 B 4B 5 Error code returned when a command is aborted because the data
_OFFSET_ERROR offset in a frame received from the initiator was not as expected.
CC_ERROR_CODE_ABORTED_CMDS 98 B 2F 2 Error code returned when a command is aborted because of side
_CLRD_BY_DEVSRV effect of TMF processing for other initiator.
CC_ERROR_CODE_ABORTED_INTER 99 B 44 0 Error code returned when a command is aborted because of internal
NAL_TGT_FAILURE target failure.
CC_ERROR_CODE_ABORTED_MEDI 100 B 3A 0 Error code returned when a command is aborted because information
UN_NT_PRESENT from medium memory is inaccessible because of absence of medium.
CC_ERROR_CODE_ABORTED_UNRE 101 B 11 0 Error code returned when a command is aborted because the sector
COVERED_RD_ERR on which read or write operation is being performed is bad or
pseudo un-correctable.
CC_ERROR_CODE_ABORTED_LBA_ 102 B 21 0 Error code returned because a command is aborted because the
OUT_OF_RANGE logical block address exceeds the capacity of the medium.
CC_ERROR_CODE_ABORTED_MEDI 103 B 28 0 Error code returned when a command is aborted because underlying
UM_CHANGED ATA drive returned SATA error MC.
CC_ERROR_CODE_HW_ERR_FLASH 104 4 84 0 Error code returned when flash access failed.
_ACCESS_FAILED
CC_ERROR_CODE_ABORTED_INSUF 105 B 55 3 Error code returned when a command is aborted because of
FICIENT_RES insufficient resources.
CC_ERROR_CODE_ABORTED_PARA 106 B 26 1 Error code returned when a command is aborted because of
M_NOT_SUPPORTED unexpected SCT status returned by the drive.
CC_ERROR_CODE_MEDIUM_ERR_R 107 3 14 1 Error code returned when the ATA drive returns IDNF error (To be
ECORD_NOT_FOUND used only if compliance with SAT1 is expected)
CC_ERROR_CODE_HW_IMPENDING 108 0 5d 10 Error code returned when REQUEST SENSE encounters threshold
_FAILURE_GEN_DRV_FAIL exceeded condition.
CC_ERROR_CODE_NOT_RDY_NOTIF 109 2 4 11 Error code returned when LU power condition state set to
Y_SPINUP_REQUIRED Active_Wait.
CC_ERROR_CODE_ATA_SECURITY_ 110 5 74 79 Error code returned when security state conflict is detected.
CONFLICT
CC_ERROR_CODE_LU_STANDBY_C 111 0 5E 4 Error code returned when power condition activated to Standby
ONDITION_ACTIVATED
CC_ERROR_CODE_LU_IDLE_CONDI 112 0 5E 3 Error code returned when power condition activated to Idle.
TION_ACTIVATED
CC_ERROR_CODE_LU_POWER_CON 113 0 5E 43 Error code returned when power condition returned by SATA device
DITION_CHANGE_TO_STANDBY is Standby.
CC_ERROR_CODE_LU_POWER_CON 114 0 5E 42 Error code returned when power condition returned by SATA device
DITION_CHANGE_TO_IDLE is Idle.

ErrorIdx
Skey ASC ASCQ
(Hex) (Hex) (Hex)
Value
CC_ERROR_CODE_SAVING_PARAM 115 5 39 0 Error code returned for mode sense command when requested
S_NOT_SUPPORTED mode page does not support saved values.
CC_ERROR_CODE_RESERVED_0 116 0 0 0 Error code reserved for future use.
F.1.3 List of InstIds Occurrences and This LSISS2520/LSISS2530 device firmware has the following default association of
ErrorIdx Class of Errors InstIds occurrences and ErrorIdx class of errors.
Table 259: InstIds
Numeric
Numeric
Value
InstId Value for Default ErrorIdx Explanation
for default
InstId
ErrorIdx
INST_UA_SCSI_BUS_RESET=0 0 UA_ERROR_CODE_SCSI_BUS_ 0 The UA Instance when unit attention condition is
RESET established because of a hard reset.
INST_UA_ABRT_TS 1 UA_ERROR_CODE_ABRT_TS 1 The UA Instance when unit attention condition is
established because a task management function is in
progress.
INST_UA_FLASH_WRITE_FAIL 2 UA_ERROR_CODE_FLASH_W 2 The UA Instance when unit attention condition is
URE RITE_FAILURE established because new device firmware could not be
written to flash.
INST_NETLIST_UPGRADE_UA_ 3 UA_ERROR_CODE_MICROCO 3 The UA Instance when unit attention condition is
MICROCODE_UPDATED DE_UPDATED established because new microcode - netlist has been
updated as a result of Write Buffer command.
INST_CONFDATA_UPGRADE_ 4 UA_ERROR_CODE_MICROCO 3 The UA Instance when unit attention condition is
UA_MICROCODE_UPDATED DE_UPDATED established because new microcode - configdata has
been updated as a result of Write Buffer command.
INST_DRIVE_FW_UPGRADE_U 5 UA_ERROR_CODE_MICROCO 3 The UA Instance when unit attention condition is
A_MICROCODE_UPDATED DE_UPDATED established because new microcode - configdata has
been updated as a result of Write Buffer command.
INST_UA_RESERVATIONS_CLE 6 UA_ERROR_CODE_RESERVATI 4 The UA Instance when unit attention condition is
ARED ONS_CLEARED established with affected registrants because persistent
reservation with registrants only type or all registrants
type was released.
INST_PREEMPT_UA_REGISTRA 7 UA_ERROR_CODE_REGISTRAT 5 The UA Instance when unit attention condition is
TIONS_PREEMPTED IONS_PREEMPTED established with affected registrants because persistent
reservation are preempted.

Table 259: InstIds (Continued)
Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_CLEAR_UA_REGISTRATIO 8 UA_ERROR_CODE_REGISTRAT 5 The UA Instance when unit attention condition is
NS_PREEMPTED IONS_PREEMPTED established with affected registrants because persistent
reservation are cleared.
INST_UA_INITIATOR_LOGIN 9 UA_ERROR_CODE_INITIATOR 6 The UA Instance when unit attention condition is
_LOGIN established because power on occurred and an initiator
logged in.
INST_DEFLTVAL_UA_LOG_PAR 10 UA_ERROR_CODE_LOG_PARA 7 The UA Instance when unit attention condition is
AMETERS_CHANGED METERS_CHANGED established because the target device does not support
independent states of log parameters and log parameters
which could affect other I_T NEXUS are turned to default.
INST_CLEAR_UA_LOG_PARAM 11 UA_ERROR_CODE_LOG_PARA 7 The UA Instance when unit attention condition is
ETERS_CHANGED METERS_CHANGED established because the target device does not support
independent states of log parameters and log parameters
which could affect other I_T NEXUS are turned to cleared.
INST_UA_MODE_PARAMETER 12 UA_ERROR_CODE_MODE_PA 8 The UA Instance when unit attention condition is
S_CHANGED RAMETERS_CHANGED established because mode parameters which affect the
I_T NEXUS are changed on another I_T NEXUS.
INST_UA_BACKGROUND_SELF 13 UA_ERROR_CODE_BACKGRO 9 The UA Instance when unit attention condition is
_TEST_FAILED UND_SELF_TEST_FAILED established because self test running in the background
mode failed.
INST_UA_LINK_DOWN 14 UA_ERROR_CODE_DRIVE_NO 10 The UA Instance when unit attention condition is
N_POWERON_RESET established because SAS link went down.
INST_UA_CTS_LUN_RESET 15 UA_ERROR_CODE_DRIVE_NO 10 The UA Instance when unit attention condition is
N_POWERON_RESET established because logical unit reset or clear task set
occurred.
INST_UA_DRIVE_DOWN 16 UA_ERROR_CODE_DRIVE_DO 14 The UA Instance when unit attention condition is
WN established because the LSISS2520/LSISS2530 device
entered drive-down state.
INST_UA_SYSTEM_DOWN 17 UA_ERROR_CODE_SYSTEM_D 15 The UA Instance when unit attention condition is
OWN established because the LSISS2520/LSISS2530 device
entered system-down state.
INST_ID_SEQERR_FORMAT_RE 18 NA NA Instance ID reserved, removed from the current
SPONSE implementation.
INST_UA_CRASH_RESET 19 UA_ERROR_CODE_CRASH_RE 13 The UA Instance when unit attention condition is
SET_OCCURED established because reboot due to panic occurred in the
LSISS2520/LSISS2530 device firmware.
INST_UA_SATA_LINK_SPEED_S 20 UA_ERROR_CODE_SATA_LINK 15 The UA Instance when unit attention condition is
ET_ERROR SPEED_SET_ERR established because the LSISS2520/LSISS2530 device was
unable to program the set link speed configured using
the mode page interface
INST_UA_INQ_DATA_CHANGE 21 UA_ERROR_CODE_INQ_DATA 16 The UA Instance when unit attention condition is
D _CHANGED established to inform the initiator that the Inquiry data
has been changed.
INST_UA_ERROR_CODE_A0_H 22 UA_ERROR_CODE_A0_HARD 17 The UA Instance when unit attention condition is
ARDWARE WARE established to inform the initiator that the underlying
hardware is A0

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_ID_CC_BACKGROUND_E 23 CC_ERROR_CODE_BACKGRO 39 The CC-sense not ready instance for Start Stop Unit
RRORS UND_ERRRS command when the operation fails but no additional
information is available.
INST_ATAPASSTHRU_1_CC_N 24 NA NA Instance ID reserved, removed from the current
O_SNS_DATA implementation.
INST_WRBUF_FLASHFAIL_1_C 27 CC_ERROR_CODE_HW_ERR_F 35 The CC-no sense data instance when the
C_HW_ERR LASH_ACCESS_FAILED LSISS2520/LSISS2530 device firmware upgrade fails
because of failure to write data to flash, but no additional
information available.
INST_WRBUF_FLASHFAIL_2_C 28 CC_ERROR_CODE_HW_ERR_F 35 The CC-no sense data instance when Bootloader upgrade
C_HW_ERR LASH_ACCESS_FAILED fails because of failure to write data to flash, but no
additional information available.
INST_WRBUF_FLASHFAIL_3_C 29 CC_ERROR_CODE_HW_ERR_F 35 Instance ID reserved, removed from the current
C_HW_ERR LASH_ACCESS_FAILED implementation.
INST_WRBUF_FLASHFAIL_4_C 30 CC_ERROR_CODE_HW_ERR_F 35 The CC-no sense data instance when Boot Option
C_HW_ERR LASH_ACCESS_FAILED upgrade fails because of failure to write data to flash, but
no additional information available.
INST_NV_SCRATCH_PAGE_WR 31 CC_ERROR_CODE_HW_ERR_F 35 The CC- Hardware error instance for Log Select command
_FLASHFAIL_1_CC_HW_ERR LASH_ACCESS_FAILED to NV Scratch page when the log select command fails
because of memory access failure.
INST_NV_SCRATCH_PAGE_RD 32 CC_ERROR_CODE_HW_ERR_F 35 The CC-Hardware error instance for Log Sense command
_FLASHFAIL_1_CC_HW_ERR LASH_ACCESS_FAILED to NV Scratch page when the log sense command fails
because of memory access failure.
INST_DA_LOGS_CC_ABRTED_I 33 CC_ERROR_CODE_ABORTED_ 35 The CC-aborted command, Log Sense to Log Page 34h
NSF_RES INSUFFICIENT_RES fails because of memory allocation failure.
INST_CC_DEFECT_LIST_NOT_ 34 CC_ERROR_CODE_DEFECT_LI 36 Instance ID reserved, for future planned feature.
FOUND ST_NOT_FOUND
INST_SRT_STP_UNT_CC_BECO 35 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for Start Stop Unit
MING_RDY G_READY command when drive is in the process of becoming ready.
INST_LGSLT_CC_BECOMING_R 36 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for Log Select
DY G_READY command, Application Client Logpage when the drive is
in the process of becoming ready.
INST_LGSNS_CC_BECOMING_ 37 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for Log Sense
RDY G_READY command, when a page which requires the drive to be in
ready state is requested but the drive is in process of
becoming ready.
INST_CHK_LUST_DRIVEDOWN 38 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance when a command checks
_CC_BECOMING_RDY G_READY LU state and the result is that drive is becoming ready.
INST_CHK_LUST_MICROCODE 39 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance when a command
_UPGRD_CC_BECOMING_RDY G_READY checks LU state and the result is that microcode is getting
upgraded.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_CHK_LUST_STARTUP_CC 40 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance when a command
_BECOMING_RDY G_READY checks LU state and the result is that startup operation is
in progress.
INST_MDSNS_CC_BECOMING 41 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance fro Mode Sense
_RDY G_READY command when Control Mode page is requested and
drive is in the process of becoming ready.
INST_RVMDSEL_CC_BECOMIN 42 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for Mode Select
G_RDY G_READY command when drive is in the process of becoming ready.
INST_WRITEBUF_UNT_CC_BEC 43 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for Write Buffer
OMING_RDY G_READY command when the mode requires drive to be in ready
state and drive is in the process of becoming ready.
INST_SND_RECV_DIAG_CC_BE 44 CC_ERROR_CODE_BECOMIN 45 Instance ID reserved, for a feature planned for future.
COMING_RDY G_READY
INST_SRT_STP_UNT_CC_SELF 45 CC_ERROR_CODE_SELF_TEST 44 The CC-self test in progress instance for Start Stop Unit
_TEST_IN_PROG _IN_PROGRESS command when foreground self test is in progress.
INST_CHK_LUST_CC_SELF_TE 46 CC_ERROR_CODE_SELF_TEST 44 The CC-self test in progress instance when a command
ST_IN_PROG _IN_PROGRESS checks LU state and the result is that a self test is in
progress.
INST_SND_RECV_DIAG_BG_TS 47 CC_ERROR_CODE_SELF_TEST 44 Instance ID reserved, for a feature planned for future.
T_CC_SELF_TEST_IN_PROG _IN_PROGRESS
INST_SND_RECV_DIAG_FG_TS 48 CC_ERROR_CODE_SELF_TEST 44 Instance ID reserved, for a feature planned for future.
T_CC_SELF_TEST_IN_PROG _IN_PROGRESS
INST_CC_SNS_NT_RDY_FMT_I 49 CC_ERROR_CODE_SNS_NOT_ 43 The CC-format in progress instance when a command
N_PROG RDY_FMT_IN_PROG checks LU state and the result is that format operation is
in progress.
INST_CHK_LUST_CC_INIT_CM 50 CC_ERROR_CODE_SNS_NOT_ 40 The CC-initializing command required a command checks
D_REQD RDY_INIT_CMD_REQUIRED LU state and the result is that the drive is in standby mode
and requires an initializing command.
INST_TST_UNT_RDY_CC_SNS_ 51 CC_ERROR_CODE_SNS_NOT_ 41 The CC-not ready, LU did not respond to selection
NT_RDY_LU_NORESPOND RDY_NO_RESP_BY_LU instance when the Test Unit Ready command is check
conditioned because the logical unit did not respond to
selection.
INST_WVFY_CC_MISCOMP_D 52 CC_ERROR_CODE_MISCOMP 47 The CC-miscompare during verify instance returned
URING_VFY _DURING_VERIFY when CRC check failed during write and verify operation.
INST_RD_DFECT_DATA_CC_RE 53 CC_ERROR_CODE_REC_ERR_ 75 The CC-defect list not found instance for Read Defect
C_ERR_LST_NOT_FOUND DEFECT_LIST_NT_FOUND Data command when he requested defect list format and
returned defect list format are not same.
INST_CC_REC_ERR_ATAPASST 54 CC_ERROR_CODE_REC_ERR_ 76 The CC-ATA pass through info available instance for the
HRU_INFO_AVAILABLE ATAPASSTHRU_INFO_AVAILA LSISS2520/LSISS2530 device Pass Through command
BLE with CK_COND bit set when the command completes
successfully.
INST_CC_BGND_TST_FAILED 55 NA NA Instance ID reserved, removed from the current
implementation.
INST_MDSEL_RV_CC_HWERR_ 56 CC_ERROR_CODE_HW_ERR_ 48 The CC-hardware error, no sense instance for Mode Select
NOSNS NO_SENSE command when the command fails, but no additional
information is available.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SNDRCV_DIAG_1_CC_H 57 CC_ERROR_CODE_HW_ERR_L 54 Instance ID reserved, for a feature planned for future.
WERR_SLFTST_FAIL U_SELF_TEST_FAILED
INST_CHK_LUST_DRIVEDOWN 60 CC_ERROR_CODE_DRIVE_IS_ 55 The CC-drive is down instance when a command checks
_CC_DRIVE_DOWN DOWN LU state and the result is that the underlying SATA drive is
in a down state.
INST_SET_VER_LGPG_CC_HW 61 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Select command to
_ERR LASH_ACCESS_FAILED Version Logpage when write to nonvolatile memory fails.
INST_START_STOP_CNT_LGPG 62 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Select command to
_CC_HW_ERR LASH_ACCESS_FAILED Start Stop Cycle Counter Logpage when write to
nonvolatile memory fails.
INST_MDSEL_RV_CC_MEDIUM 63 CC_ERROR_CODE_MEDIUM_ NA Instance ID reserved, removed from the current
_ERROR_NOSNS ERROR_NO_SENSE implementation.
INST_MDSEL_DRV_CMD_FAIL 64 CC_ERROR_CODE_HW_ERR_ 48 The CC-Hw error, no sense instance for Mode Select
_CC_HW_ERROR_NOSNS NO_SENSE command when the LSISS2520/LSISS2530 device cannot
post commands to the underlying SATA drive.
INST_SMART_ERRCODE_CC_A 65 CC_ERROR_CODE_ABORTED_ 106 The CC-aborted command, the SCT command returns the
BRTD_PARAM_NOT_SUP PARAM_NOT_SUPPORTED unexpected status.
INST_RWV_LGPG_CC_HW_ER 66 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
R LASH_ACCESS_FAILED Read/Write/Verify Error Counter Logpage when write to
INST_GET_STRT_STP_CNT_LG 67 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
PG_CC_HW_ERR LASH_ACCESS_FAILED Start Stop Cycle Counter Logpage when write to
INST_NON_MED_ERR_LGPG_C 68 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to Non
C_HW_ERR LASH_ACCESS_FAILED Medium Error Counter Logpage when write to
INST_GET_VER_LGPG_CC_HW 69 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
_ERR LASH_ACCESS_FAILED Versions Logpage when write to nonvolatile memory fails.
INST_DA_LGPG_FLASHFAIL_C 70 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
C_HW_ERR_1 LASH_ACCESS_FAILED Drive Attachment Logs Logpage when access to
INST_DA_LGPG_FLASHFAIL_C 71 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
C_HW_ERR_2 LASH_ACCESS_FAILED Drive Attachment Logs Logpage when access to
nonvolatile memory fails (clearing the logs/crash dump).
INST_SET_DA_TEMP_LGPG_C 72 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Select command to
C_HW_ERR LASH_ACCESS_FAILED Drive Attachment Temperature Logpage when write to
INST_GET_DA_TEMP_LGPG_C 73 CC_ERROR_CODE_HW_ERR_F 104 The CC-Hw error, instance for Log Sense command to
C_HW_ERR LASH_ACCESS_FAILED Drive Attachment Temperature Logpage when write to

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_CHK_LUST_CC_MEDIUM 74 CC_ERROR_CODE_MEDIUM_ 57 The CC-fmedium format corrupted instance when a
_ERROR_FMT_CORRUPTED FORMAT_CORRUPTED command checks LU state and the result is that medium
format is corrupted.
INST_WRBUF1_CC_MEDIUM_E 75 CC_ERROR_CODE_PERIPHER 61 The CC-peripheral device write fault instance for Write
RROR_DEV_WT_FAULT AL_DEVICE_WRITE_FAULT Buffer command when firmware image invalidation to
upgrade new image fails.
INST_WRBUF2_CC_MEDIUM_E 76 CC_ERROR_CODE_PERIPHER 61 The CC-peripheral device write fault instance for Write
RROR_DEV_WT_FAULT AL_DEVICE_WRITE_FAULT Buffer command when new firmware image validation
fails.
INST_REASS_BLK1_CC_MEDIU 77 CC_ERROR_CODE_AUTO_REA 62 The CC-auto reallocate failed instance for Reassign Blocks
M_ERR_AUTOREALLOC_FAIL LLOCATE_FAILED command.
INST_REASS_BLK2_CC_MEDIU 78 CC_ERROR_CODE_AUTO_REA 62 The CC-auto reallocate failed instance for Reassign Blocks
M_ERR_AUTOREALLOC_FAIL LLOCATE_FAILED command when the ATA write command sent to the
underlying SATA drive results in failure.
INST_VFY_CC_MEDIUM_ERRO 79 NA NA Instance ID reserved, removed from the current
R_AUTO_RELOC_FAILED implementation.
INST_WT_VFY_CC_MEDIUM_E 80 CC_ERROR_CODE_AUTO_REA 62 The CC-auto reallocate failed instance for Write Verify
RROR_AUTO_RELOC_FAILED LLOCATE_FAILED command.
INST_SEEK_CC_MEDIUM_ERR 81 CC_ERROR_CODE_AUTO_REA 62 The CC-auto reallocate failed instance for Seek command.
OR_AUTO_RELOC_FAILED LLOCATE_FAILED
INST_HDL_RSP_ABT_CMD_CC 82 CC_ERROR_CODE_ABORTED_ 91 The CC-aborted command, LU time-out instance when a
_ABRTD_LU_TIMEOUT LU_TIMEOUT command that was not active on the drive was aborted
because of time-out of logical unit.
INST_DRV_RST_TIMEOUT_CC_ 83 CC_ERROR_CODE_ABORTED_ 91 The CC-aborted command, LU time-out instance when
ABRTD_LU_TIMEOUT LU_TIMEOUT command time-out occurs because of reset of the
underlying ATA drive.
INST_HDL_ABRTD_RSP_CC_A 84 CC_ERROR_CODE_ABORTED_ 91 The CC-aborted command, LU time-out instance when a
BRTD_LU_TIMEOUT LU_TIMEOUT command which was not active on the drive but data
streaming to/from the initiator was in progress; was
aborted because of time-out of logical unit.
INST_SRCV_DIAG_CC_ABRTD_ 85 CC_ERROR_CODE_ABORTED_ 86 Instance ID reserved, for a feature planned for future.
ATA_FT_NT_ENB ATA_FEATURE_NT_EN
INST_HDL_RSP_ABT_CMD_CC 86 CC_ERROR_CODE_ABORTED_ 93 The CC-aborted command, command cleared by another
_ABRTD_CMDS_CLRD_BY_OT CMDS_CLRD_BY_OTHER_INIT initiator instance when a command was aborted because
HER_INIT of TMF from another initiator.
INST_HDL_ABRTD_RSP_CC_A 87 CC_ERROR_CODE_ABORTED_ 93 The CC-aborted command, command cleared by another
BRTD_CMDS_CLRD_BY_OTHE CMDS_CLRD_BY_OTHER_INIT initiator instance when a command that was active on
R_INIT drive got aborted since the drive was reset because of
TMF from another initiator.
INST_HDL_ABRTD_RSP_CC_A 88 CC_ERROR_CODE_ABORTED_ 98 The CC-aborted command, command cleared by device
BRTD_CMDS_CLRD_BY_DEV_ CMDS_CLRD_BY_DEVSRV server instance when the hardware layer returns the
SERVER reason of command being aborted as side effect of TMF
processing for other initiator.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_HDL_ABRTD_RSP_CC_A 89 CC_ERROR_CODE_ABORTED_ 94 The CC-aborted command, ack-nak time-out instance
BRTD_ACK_NAK_TIMEOUT ACK_NAK_TIMEOUT (case 1) when the transport protocol layer returns the
status of aborted command as time-out for receiving ack
or nak. It is recommended that case1 and case 2 for this
ErrorIdx must be customized together.
INST_TPLERR_CC_ABRTD_ACK 90 CC_ERROR_CODE_ABORTED_ 94 The CC-aborted command, ack-nak time-out instance
_NAK_TIMEOUT ACK_NAK_TIMEOUT (case 2) when the transport protocol layer returns the
status of aborted command as time-out for receiving ack
or nak. It is recommended that case1 and case 2 for this
ErrorIdx must be customized together.
INST_HDL_ABRTD_RSP_CC_A 91 CC_ERROR_CODE_ABORTED_ 92 The CC-aborted command, nak received instance (case 1)
BRTD_NAK_RCVD NAK_RECEIVED when the transport protocol layer returns the reason of
aborted command as receipt of nak from the target. It is
recommended that case1 and case 2 for this ErrorIdx
must be customized together.
INST_TPLERR_CC_ABRTD_NA 92 CC_ERROR_CODE_ABORTED_ 92 The CC-aborted command, nak received instance (case 2)
K_RCVD NAK_RECEIVED when the transport protocol layer returns the reason of
aborted command as receipt of nak from the target. It is
INST_HDL_ABRTD_RSP_CC_A 93 CC_ERROR_CODE_ABORTED_ 97 The CC-aborted command, data offset error instance
BRTD_DATA_OFFSET_ERR DATA_OFFSET_ERROR when the hardware layer indicates that the reason of
aborted command was that the data offset in a frame
received from the initiator was not as expected.
INST_HDL_ABRTD_RSP_CC_A 94 CC_ERROR_CODE_ABORTED_ 96 The CC-aborted command, too much write data error
BRTD_TOO_MUCH_WDATA TOO_MUCH_WRITE_DATA instance (case 1) when the transport protocol layer
indicates that the reason of aborted command was that
data frame received from the target contained more data
than expected. It is recommended that case1 and case 2
for this ErrorIdx must be customized together.
INST_TPLERR_CC_ABRTD_TO 95 CC_ERROR_CODE_ABORTED_ 96 The CC-aborted command, too much write data error
O_MUCH_WDATA TOO_MUCH_WRITE_DATA instance (case 2) when the transport protocol layer
data frame received from the target contained more data
than expected. It is recommended that case1 and case 2
for this ErrorIdx must be customized together.
INST_HDL_ABRTD_RSP_CC_A 96 CC_ERROR_CODE_ABORTED_ 95 The CC-aborted command, info unit too short error
BRTD_INFO_UNT_TOO_SHOR INFO_UNT_TOO_SHORT instance (case 1) when the transport protocol layer
T indicates that the reason of aborted command was that
data frame of zero bytes was received from the target. It is
INST_TPLERR_CC_ABRTD_INF 97 CC_ERROR_CODE_ABORTED_ 95 The CC-aborted command, info unit too short error
O_UNT_TOO_SHORT INFO_UNT_TOO_SHORT instance (case 2) when the transport protocol layer
data frame of zero bytes was received from the target. It is

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_HDL_ABRTD_RSP_CC_A 98 CC_ERROR_CODE_ABORTED_ 90 The CC-aborted command, data phase error instance
BRTD_DATA_CRC_ERR DATA_PHASE_CRC_ERROR (case 1) when the transport protocol layer indicates that
the reason of aborted command was that CRC error was
present in the frame sent from the initiator. It is
INST_TPLERR_CC_ABRTD_DAT 99 CC_ERROR_CODE_ABORTED_ 90 The CC-aborted command, data phase error instance
A_CRC_ERR DATA_PHASE_CRC_ERROR (case 2) when the transport protocol layer indicates that
the reason of aborted command was that CRC error was
present in the frame sent from the initiator. It is
INST_NTFY_DIFERR_CC_ABRT 100 CC_ERROR_CODE_ABORTED_ 79 Instance ID reserved, for a feature planned for future.
D_LBLK_GRD_CHK_FAILED LBLK_GUARD_CHK_FAILED
D_APPTAG_CHK_FAILED LBLK_APP_TAG_FAILED
D_REFTAG_CHK_FAILED LBLK_REF_TAG_FAILED
INST_ID_CC_START_STOP_UNI 103 NA NA Instance ID reserved, removed from the current
T implementation.
INST_ID_CC_SAT_SMARTFEAT 104 NA NA Instance ID reserved, removed from the current
URES implementation.
INST_ID_CC_APPCLT_LGPG_L 105 NA NA Instance ID reserved, removed from the current
GSLT implementation.
INST_ID_CC_WRITEBUF 106 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_READBUFF 107 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_INQUIRY 108 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_REQUEST_SENSE 109 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_RD_MDFY_RT 110 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_WRITESAME 111 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_WRITE 112 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_READ 113 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_SYNC_CACHE 114 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_WRITE_VERITY 115 NA NA Instance ID reserved, removed from the current
implementation.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_ID_CC_APPCLT_LGPG_L 116 NA NA Instance ID reserved, removed from the current
GSNS implementation.
INST_ID_CC_SELFTEST_RESUL 117 NA NA Instance ID reserved, removed from the current
T_LGPG implementation.
INST_ID_BG_SCAN_RES_LGPG 118 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_WLONG 119 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_CC_SMARTDATA_LGP 120 NA NA Instance ID reserved, removed from the current
G implementation.
INST_ID_CC_INFO_EXCP_LGP 121 NA NA Instance ID reserved, removed from the current
G implementation.
INST_ID_CC_RLONG 122 NA NA Instance ID reserved, removed from the current
implementation.
INST_SND_STP_UNT_CC_INV_ 123 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In start stop unit
FIELD_IN_CDB _IN_CDB command when control bit in the CDB is set or invalid
combination of start bit and LOEJ bit in the CDB occurs
INST_FMT_UNT_GET_DATA_C 124 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In format unit
C_INV_FIELD_IN_CDB _IN_CDB command when control bit in the CDB is set or LongList
or CmpList bits in the CDB are set.
INST_FMT_UNT_PROCESS_RC 125 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
V_DATA_CC_INV_FIELD_IN_C _IN_CDB
DB
INST_FMT_UNT_CC_INV_BLK_ 126 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
LEN_IN_CDB _IN_CDB
INST_ATAPASSTHRU_CHK_BYT 127 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In ATA pass through
E_XFER_CC_INV_FIELD_IN_CD _IN_CDB command when byte transfer is requested.
B
INST_ATAPASSTHRU_ERROR_P 128 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance in ATA pass through
ATH_RETURN_CC_INV_FIELD_I _IN_CDB command when invalid combination of PROTOCOL and
N_CDB T_DIR or T_LENGTH field in the CDB.
INST_LGSLT_VALIDATE_CDB_C 129 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance in Log Select
C_INV_FIELD_IN_CDB _IN_CDB command when control bit in the CDB is set or an invalid
combination of PC, PCR and transfer length field in the
CDb occurs.
INST_LGSLT_CHK_XFER_LEN_ 130 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance in Log Select
CC_INV_FIELD_IN_CDB _IN_CDB command when transfer length is higher than maximum
and not equal to the size of NV ScratchPage
INST_LGSLT_VALIDATE_NV_SC 131 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Select
RATCH_PAGE_HEADER_CC_IN _IN_CDB command for NV Scratch Page when DS or SPF bit is set or
V_FIELD_IN_CDB if pagelength is incorrect.
INST_LGSNS_CHK_RD_CLEAR 132 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Select
_SUPPORTED_CC_INV_FIELD_ _IN_CDB command when Read Clear is requested but not
IN_CDB supported by the log page.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_LGSNS_VALIDATE_CDB_ 133 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
CC_INV_FIELD_IN_CDB _IN_CDB command when control or PPC bit in the CDB is set or
invalid combination of PC, Page Code and Param Pointer
occurs.
INST_LGSNS_CHK_ALLOCATIO 134 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
N_LEN_CC_INV_FIELD_IN_CD _IN_CDB command when Drive attachment Logpage is requested
B and the allocation length is not equal to standard size of
the LSISS2520/LSISS2530 device Logpage.
INST_LGSNS_INVAILD_PGCOD 135 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
E_CASE_CC_INV_FIELD_IN_CD _IN_CDB command when the page code requested for is not
B supported.
INST_GET_MDPG_INFO_EXCP 136 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Sense
_CC_INV_FIELD_IN_CDB _IN_CDB command when smart support is turned off and
modepage Exceptions control is requested.
INST_MDSNS_CHK_NONZERO 137 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Sense
_CONTROL_CC_INV_FIELD_IN _IN_CDB command when the control field is set to a nonzero value.
_CDB
INST_MDSNS_CHK_MEMORY_ 138 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Sense
REQD_CC_INV_FIELD_IN_CDB _IN_CDB command when the page code requested is not
supported.
INST_MDSNS_CHK_MODE_PG 139 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Sense
_DATA_FILL_1_CC_INV_FIELD _IN_CDB command when the drive cannot return data, when task
_IN_CDB descriptor is in wait ordered state.
INST_MDSNS_CHK_MODE_PG 140 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Sense
_DATA_FILL_2_CC_INV_FIELD _IN_CDB command when the drive cannot return data, when task
_IN_CDB descriptor is in wait for drive response state.
INST_MDSEL_CC_INV_FIELD_I 141 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Select
N_CDB _IN_CDB command when the control field in the CDB is set to a
nonzero value.
INST_MDSEL_CC_INV_BLK_LE 142 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Mode Select
N_IN_CDB _IN_CDB command when the block length field in the block
descriptor is not equal to SATA block size.
INST_WRBUF_MODE_SUPPOR 143 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
TING_NONZER0_BUFID_CC_IN _IN_CDB command if the mode is Download and save Offset and
V_FIELD_IN_CDB either the field Buffer ID or Buffer offset field in the CDB is
set to a nonzero value.
INST_WRBUF_MODE2_PARAM 144 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
_LEN_NON512_CC_INV_FIELD _IN_CDB command when in Data mode and the fields Buffer ID
_IN_CDB and Buffer offset are set to a nonzero value and the value
of the field Parameter list length in the CDB is not equal to
the size of SATA Read Buffer.
INST_WRBUF_MODE2_BUFID_ 145 NA NA Instance ID reserved, removed from the current
NONZERO_CC_INV_FIELD_IN_ implementation.
CDB

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_WRBUF_MODE7_DRV_F 146 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
W_BUFFOFFSET_CC_INV_FIEL _IN_CDB command if the mode is Download and save Offset,
D_IN_CDB buffer ID is zero and the lower 8 bits of Buffer offset fields
in the CDB are nonzero.
INST_WRBUF_PARAMLEN_GRE 147 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
ATER_ID_DATA_BYTE235_CC_I _IN_CDB command when the Identify Device Byte 235 is nonzero
NV_FIELD_IN_CDB and Parameter length is greater than the same.
INST_WRBUF_PARAMLEN_LES 148 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
S_ID_DATA_BYTE234_CC_INV _IN_CDB command when the Identify Device Byte 234 is nonzero
_FIELD_IN_CDB and Parameter length is lesser than the same.
INST_WRBUF_MODE7_BUF_ID 149 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance when the first Write
1_FIRST_WB_BUFFOFFSET_N _IN_CDB Buffer command for the LSISS2520/LSISS2530 device
ONZERO_CC_INV_FIELD_IN_C firmware upgrade has buffer offset field in the CDB set to
DB a nonzero value.
INST_RDBUF_ILLEGAL_CMD_ 150 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Buffer
CC_INV_FIELD_IN_CDB _IN_CDB command when the Mode field in the CDB refers to an
unsupported mode or if buffer ID field in the CDB is set to
a nonzero value and the mode field in CDB is not set to
Descriptor mode.
INST_RDBUF_CHK_ALLOCATI 151 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in read Buffer
ON_LEN_CC_INV_FIELD_IN_C _IN_CDB command when in Descriptor mode and the allocation
DB length field in the CDB is set to a value less than the
minimum allowed for SATA Read Descriptor.
INST_REASS_BLK_CC_INV_FIE 152 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Reassign Blocks
LD_IN_CDB _IN_CDB Command when control byte in the CDB is nonzero or the
LongLBA bit is set in the CDB and underlying drive does
not support the 48 bit addressing.
INST_RD_DEFECT_DATA_CC_I 153 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Defect Data
NV_FIELD_IN_CDB _IN_CDB command when the Control field in the CDB is set or the
allocation length is lesser than the size required for Read
Defect Data Response.
INST_RD_CAPACITY10_CDB_C 154 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Capacity 10
HK_CC_INV_FIELD_IN_CDB _IN_CDB command when one of the LBA, PMI or Control field in
the CDB is set to a nonzero value.
INST_RD_CAPACITY16_CDB_C 155 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Capacity 16
HK_CC_INV_FIELD_IN_CDB _IN_CDB command when one of the LBA, PMI or Control field in
the CDB is set to a nonzero value.
INST_RD_CAPACITY_UNSUPP 156 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Capacity 16
ORTED_SRV_ACTION_CC_INV _IN_CDB command when the service action field in the CDB is set
_FIELD_IN_CDB to an unsupported value.
INST_REZERRO_UNIT_CC_INV 157 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature deprecated.
_FIELD_IN_CDB _IN_CDB
INST_RESERVE_REL10_CC_INV 158 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature deprecated.
_FIELD_IN_CDB _IN_CDB
INST_RESERVE_REL6_CC_INV_ 159 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature deprecated.
FIELD_IN_CDB _IN_CDB

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_PER_RESERVE_OUT_CC_ 160 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
INV_FIELD_IN_CDB _IN_CDB Out command when the service action code is one of
Reserve, Release, Prempt, Prempt and Abort and Register
and Move; and the type is not of one Write Exclusive,
Exclusive, Write Exclusive Registrants Only and Exclusive
Registrants Only.
INST_PER_RESERVE_IN_CC_IN 161 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
V_FIELD_IN_CDB _IN_CDB In command when the control field in CDB is set or the
service action code is set to an unsupported value.
INST_PRI_RD_KEYS_CC_INV_F 162 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
IELD_IN_CDB _IN_CDB In command when the service action code is Read Keys
and the allocation length provided is insufficient to
transfer the required data.
INST_PRI_RD_RESERVATION_C 163 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
C_INV_FIELD_IN_CDB _IN_CDB In command when the service action code is Read
Reservation and the allocation length provided is
insufficient to transfer the required data.
INST_PRI_REPORT_CAPABILITI 164 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
ES_CC_INV_FIELD_IN_CDB _IN_CDB In command when the service action code is Report
Capabilities and the allocation length provided is
insufficient to transfer the required data.
INST_PRI_RD_FULL_STATUS_C 165 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Persistent Reserve
C_INV_FIELD_IN_CDB _IN_CDB In command when the service action code is Read Full
Status and the allocation length provided is insufficient to
transfer the required data.
INST_REPORT_LUNS_CC_INV_ 166 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Report LUNS
FIELD_IN_CDB _IN_CDB command when the control bit in the CDB is set or the
select report field has an unsupported value or the
allocation length field has a value less than the minimum
allowed.
INST_REQUEST_SENSE_CC_IN 167 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Request Sense
V_FIELD_IN_CDB _IN_CDB command when the control bit or DESC bit in the CDB is
set to a nonzero value.
INST_TST_UNT_RDY_CC_INV_ 168 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Test Unit Ready
FIELD_IN_CDB _IN_CDB command when the control bit in the CDB is set to a
nonzero value.
INST_VALIDATE_RW6_CDB_CC 169 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read/Write 6
_INV_FIELD_IN_CDB _IN_CDB command when control field in the CDB is set to a
nonzero value.
INST_VALIDATE_RW10_CDB_V 170 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read/Write 10
ALIDATION_CC_INV_FIELD_IN _IN_CDB command when control, FUA_NV or DPO field in CDB is
_CDB set to nonzero value.
INST_VALIDATE_RW10_CDB_I 171 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
NVAILD_PROTECTION_CC_INV _IN_CDB
_FIELD_IN_CDB
ALIDATION_CC_INV_FIELD_IN _IN_CDB command when control, FUA_NV or DPO field in CDB is

Numeric
Numeric
Value
for default
InstId
ErrorIdx
_FIELD_IN_CDB
AILADTION_CC_INV_FIELD_IN _IN_CDB command when control, FUA_NV or DPO field in CDB is
_FIELD_IN_CDB
AILADTION_CC_INV_FIELD_IN _IN_CDB command when control, FUA_NV or DPO field in CDB is
INST_VALIDATE_PROTECTION 177 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
_DIF_CHK_CC_INV_FIELD_IN_ _IN_CDB
CDB
INST_VALIDATE_PROTECTION 178 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
_MODEL_CHK_CC_INV_FIELD _IN_CDB
_IN_CDB
INST_VALIDATE_WR_PROTECT 179 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
ION_CHK_CC_INV_FIELD_IN_ _IN_CDB
CDB
INST_VALIDATE_RD_PROTECTI 180 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
ON_CHK_CC_INV_FIELD_IN_C _IN_CDB
DB
INST_VALIDATE_WS10_CDB_V 181 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Same 10
ALIDATION_CC_INV_FIELD_IN _IN_CDB command when the control field in the CDB is set to a
_CDB nonzero value.
INST_VALIDATE_WS10_CDB_L 182 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Same 10
B_PB_DATA_SUPPORT_CC_IN _IN_CDB command when LBDATA and PBDATA fields in the CDB
V_FIELD_IN_CDB are both set to 1.
INST_VALIDATE_WS10_CDB_I 183 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
NVALID_PROTECTION_CC_INV _IN_CDB
_FIELD_IN_CDB
_CDB nonzero value.
B_PD_DATA_SUPPORT_CC_IN _IN_CDB command when LBDATA and PBDATA fields in the CDB
_FIELD_IN_CDB
_CDB nonzero value.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
B_PD_DATA_SUPPORT_CC_IN _IN_CDB command when LBDATA and PBDATA fields in the CDB
_FIELD_IN_CDB
INST_VALIDATE_VERIFY10_CD 190 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write and Verify
B_VALIDATION_CC_INV_FIELD _IN_CDB 10/Verify 10 commands if control or DPO bit is set or in
_IN_CDB Verify 10 command if BYTECHK field is set to a nonzero
value.
INST_VALIDATE_VERIFY10_CD 191 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
B_INVALID_PROTECTION_CC_I _IN_CDB
NV_FIELD_IN_CDB
value.
NV_FIELD_IN_CDB
value.
NV_FIELD_IN_CDB
value.
NV_FIELD_IN_CDB
INST_SYNC_CACHE_CC_INV_F 198 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Synchronize Cache
IELD_IN_CDB _IN_CDB command when control or sync_nv field in the CDb is set
to a nonzero value.
INST_SND_RECV_DIAG_VALID 199 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
ATE_CDB_CC_INV_FIELD_IN_C _IN_CDB
DB
INST_SND_RECV_DIAG_LED_C 200 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
NTRL_PG_CC_INV_FIELD_IN_ _IN_CDB
CDB
INST_SND_RECV_DIAG_ALTA_ 201 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
SELF_TEST_PG_CC_INV_FIELD _IN_CDB
_IN_CDB

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SND_RECV_DIAG_SUPP 202 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
ORT_PG_CC_INV_FIELD_IN_C _IN_CDB
DB
INST_SND_RECV_DIAG_INVAI 203 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
D_DIAG_PG_CC_INV_FIELD_I _IN_CDB
N_CDB
INST_SND_RECV_DIAG_PARA 204 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
MLEN_CHK_1_CC_INV_FIELD_ _IN_CDB
IN_CDB
INST_SND_RECV_DIAG_PARA 205 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
MLEN_CHK_2_CC_INV_FIELD_ _IN_CDB
IN_CDB
INST_SND_RECV_DIAG_RESUL 206 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
T_VALIDATE_CDB_CC_INV_FIE _IN_CDB
LD_IN_CDB
INST_SND_RECV_DIAG_RESUL 207 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
T_GET_DIAG_PG_CC_INV_FIEL _IN_CDB
D_IN_CDB
INST_WRITE_LONG_CHK_XFE 208 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Long
R_LEN_CC_INV_FIELD_IN_CD _IN_CDB command when control bit in the CDB is set or byte
B transfer length is not equal to the size of data available to
be transferred.
INST_WRITE_LONG_CC_INV_FI 209 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Long
ELD_IN_CDB _IN_CDB command when the service action code is set to an
unsupported value.
INST_WRITE_LONG_VALIDATE 210 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Long
_CDB_CC_INV_FIELD_IN_CDB _IN_CDB command when Write Uncorrectable Ext is not supported
by the underlying drive or the control, pblock or byte
transfer length is set to a nonzero value or an invalid
combination of cor_dis and wr_uncor fields is set.
INST_READ_LONG_CHK_CDB_ 211 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Long
CC_INV_FIELD_IN_CDB _IN_CDB command when control, pblock or corrct field in the CDB
is set to a nonzero value.
INST_READ_LONG_CHK_XFR_ 212 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Long
LEN_CC_INV_FIELD_IN_CDB _IN_CDB command when byte transfer length is not equal to the
size of data available to be transferred.
INST_SEEK_CHK_SEEK6_CMD_ 213 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Seek 6 command
CC_INV_FIELD_IN_CDB _IN_CDB when the control field in the CDB is set to a nonzero
value.
INST_SEEK_OTHER_SEEK_CM 214 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Seek 10 command
D_CC_INV_FIELD_IN_CDB _IN_CDB when the control field in the CDB is set to a nonzero value.
INST_DRV_ATTACHMENT_LG_ 215 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
PG_INAVALID_SUBPAGE_CC_I _IN_CDB command when an invalid subpage for Drive
NV_FIELD_IN_CDB AttachmentLogs Log Page is requested.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_APP_CLIENT_LG_PG_CH 216 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
K_LEN_CC_INV_FIELD_IN_CD _IN_CDB command when Application Client Logpage is requested
B and the allocation length or parameter code field in the
CDB has an invalid value.
INST_APP_CLIENT_LG_PG_CH 217 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Log Sense
K_ADDR_RANGE_CC_INV_FIEL _IN_CDB command when Application Client Logpage is requested
D_IN_CDB and the parameter code field leads to an invalid Log
address value.
INST_WRBUF_MODE7_BUFFID 218 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Write Buffer
_EF_BUFFOFFSET_NONZERO_ _IN_CDB command when Buffer ID is set to Bootlader Upgrade and
CC_INV_FIELD_IN_CDB the buffer offset field is set to a nonzero value.
INST_RDCAP_CUST_CC_INV_F 219 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance in Read Capacity 10
IELD_IN_CDB _IN_CDB command when Legacy Initiator table is disabled.
INST_ADD_CMD_CC_INVALID 220 CC_ERROR_CODE_INVALID_ 74 The CC-invalid message error instance when a task
_MESSAGE_ERROR MESSAGE_ERROR attribute is not supported; here ACA attribute when ACA
condition does not exist.
INST_NTFY_CMD_QD_CC_VE 221 CC_ERROR_CODE_VENDOR_ 73 The CC-vendor specific first burst set instance when,
NDOR_SPECIFIC_FIRST_BURST SPECIFIC_FIRST_BURST_SET though the first burst feature is not supported by the
_SET device, the enable first burst bit is set.
INST_CHK_LBA_CC_LBA_OUT 222 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance when the sum of LBA
_OF_RANGE OF_RANGE and transfer length exceeds the disk range.
INST_RD_CHK_LBA_CC_LBA_ 223 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance for Read command
OUT_OF_RANGE OF_RANGE when HW CDB check indicates that logical block address
field has an address that exceeds the disk range.
INST_WR_CHK_LBA_CC_LBA_ 224 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance for Write command
OUT_OF_RANGE OF_RANGE when HW CDB check indicates that logical block address
field has an address that exceeds the disk range.
INST_CHK_TRANSLEN_CC_LB 225 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance when the transfer
A_OUT_OF_RANGE OF_RANGE length field is higher than the maximum number of RCTC
blocks allowed.
INST_RD_CHK_TRANSLEN_CC 226 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance for Read command
_LBA_OUT_OF_RANGE OF_RANGE when HW CDB check indicates that the transfer length
has an invalid value.
INST_WR_CHK_TRANSLEN_CC 227 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance for Write command
_LBA_OUT_OF_RANGE OF_RANGE when HW CDB check indicates that the transfer length
has an invalid value
INST_CHK_TRANSLEN_BYTES_ 228 CC_ERROR_CODE_LBA_OUT_ 72 The CC-LBA out-of-range instance when the transfer
CC_LBA_OUT_OF_RANGE OF_RANGE length field is higher than the maximum number of RCTC
blocks allowed.
INST_WR_CC_LBA_OUT_OF_R 229 NA NA Instance ID reserved, removed from the current
ANGE implementation.
INST_RD_CC_LBA_OUT_OF_R 230 NA NA Instance ID reserved, removed from the current
ANGE implementation.
INST_REASS_BLK_CC_INV_PAR 231 CC_ERROR_CODE_INV_PARA 67 The CC-invalid parameter list length instance for Reassign
AM_LIST_LEN M_LIST_LEN Blocks command when the initiator sends insufficient data.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SMART_WR_SAME_CC_I 232 CC_ERROR_CODE_INV_PARA 67 The CC-invalid parameter list length instance for Smart
NV_PARAM_LIST_LEN M_LIST_LEN Write Same command when the initiator sends
insufficient data.
INST_WR_LONG_CC_INV_PAR 233 CC_ERROR_CODE_INV_PARA 67 The CC-invalid parameter list length instance for Write
AM_LIST_LEN M_LIST_LEN Long command when the initiator sends insufficient data.
INST_REPORT_LUN_CC_LUN_ 234 CC_ERROR_CODE_LUN_NOT_ 70 The CC-LUN not supported instance when report luns
NOT_SUPPORTED SUPPORTED command is requested for logical unit not supported by
the target.
INST_REQ_SENSE_CC_LUN_N 235 CC_ERROR_CODE_LUN_NOT_ 70 The CC-LUN not supported instance when request sense
OT_SUPPORTED SUPPORTED command is requested for logical unit not supported by
the target.
INST_NTFY_CMD_QD_CC_LU 236 CC_ERROR_CODE_LUN_NOT_ 70 The CC-LUN not supported instance from the function
N_NOT_SUPPORTED SUPPORTED SENotifycommandqueued when a command is
requested for logical unit not supported by the target.
INST_NTFY_CMD_QD_CC_INIT 237 CC_ERROR_CODE_INITIATOR 46 The CC-initiator overflow instance when a command is
_TBL_OVERFLOW _OVERFLOW received from a new initiator, and the initiator table is full.
INST_PRO_REL_CC_PER_RES_I 238 CC_ERROR_CODE_PER_RES_I 69 The CC-Invalid release of persistent reservation instance
NV_REL NV_REL when type of reservation provided does not match with
actual type.
INST_PRO_REG_CC_INSUF_RE 239 CC_ERROR_CODE_INSUF_RE 68 The CC-insufficient registration sources instance for
G_RESOURCES G_RESOURCES Persistent Reserve Out command, service action Register
when an initiator has not registered and
SEReleaseMemory index has the value FF, i.e., reservation
resources (PR table) are full,
INST_PRO_REG_IGNORE_CC_I 240 CC_ERROR_CODE_INSUF_RE 68 The CC-insufficient registration sources instance for
NSUF_REG_RESOURCES G_RESOURCES Persistent Reserve Out command, service action Register
and ignore key when SEReleaseMemory index has the
value FF, i.e., reservation resources (PR table) are full.
INST_PRO_RAMV_CC_INSUF_ 241 CC_ERROR_CODE_INSUF_RE 68 The CC-insufficient registration sources instance for
REG_RESOURCES G_RESOURCES Persistent Reserve Out command, service action Register
and Move when an initiator has not registered and
SEReleaseMemory index has the value FF, i.e., reservation
resources (PR table) are full.
INST_FMT_UNIT_CC_PARAM_ 242 CC_ERROR_CODE_PARAM_LI 71 The CC-parameter list length error instance for Format
LIST_LEN_ERR ST_LEN_ERR Unit command when the initiator sends insufficient data.
INST_ATAPASSTHRU_CC_PARA 243 CC_ERROR_CODE_PARAM_LI 71 The CC-parameter list length error instance for
M_LIST_LEN_ERR ST_LEN_ERR ATAPassthrough command when insufficient data is sent
by initiator.
INST_LGSLT_CC_PARAM_LIST_ 244 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Log
LEN_ERR ST_LEN_ERR Select command when the initiator sends insufficient data.
INST_VERSION_LGPG_CC_PAR 245 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Log
AM_LIST_LEN_ERR ST_LEN_ERR Select command for Versions Logpage when the initiator
sends insufficient data.
INST_START_STOP_CNT_LGPG 246 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Log
_CC_PARAM_LIST_LEN_ERR ST_LEN_ERR Select command for Start Stop Cycle Counter Logpage
when the initiator sends insufficient data.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_DA_TEMP_LGPG_CC_PA 247 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Log
RAM_LIST_LEN_ERR ST_LEN_ERR Select command for Drive Attachment Temp Logpage
when the initiator sends insufficient data.
INST_MDSEL_CC_PARAM_LIST 248 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Mode
_LEN_ERR ST_LEN_ERR Select command when the initiator sends insufficient data.
INST_WRBUF_1_CC_PARAM_L 249 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Write
IST_LEN_ERR ST_LEN_ERR Buffer command when the initiator sends insufficient data.
INST_WRBUF_2_CC_PARAM_L 250 CC_ERROR_CODE_PARAM_LI 71 Instance ID reserved, removed from the current
IST_LEN_ERR ST_LEN_ERR implementation.
INST_WRBUF_INVALID_ALTA_I 251 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for the
MAGE_LEN_CC_PARAM_LIST_ ST_LEN_ERR LSISS2520/LSISS2530 device firmware upgrade when the
LEN_ERR length of image provided by initiator is greater than the
maximum LSISS2520/LSISS2530 device firmware image
size allowed.
INST_REASS_BLK_1_CC_PARA 252 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Reassign
M_LIST_LEN_ERR ST_LEN_ERR Blocks command when length of LBA header list is equal
to zero.
INST_REASS_BLK_2_CC_PARA 253 CC_ERROR_CODE_INV_FIELD 71 The CC-invalid parameter list length instance for Reassign
M_LIST_LEN_ERR _IN_PARAM_LIST Blocks command when the longlba bit in the CDB is set
and length of LBA header list is not a multiple of 8.
INST_REASS_BLK_3_CC_PARA 254 CC_ERROR_CODE_PARAM_LI 71 Instance ID reserved, for a feature planned for future.
M_LIST_LEN_ERR ST_LEN_ERR
INST_REASS_BLK_4_CC_PARA 255 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Reassign
M_LIST_LEN_ERR ST_LEN_ERR Blocks command when the number of LBAs transferred
gets calculated as zero.
INST_RES_REL_CC_PARAM_LI 256 CC_ERROR_CODE_PARAM_LI 71 Instance ID reserved, for a feature deprecated.
ST_LEN_ERR ST_LEN_ERR
INST_PER_RES_OUT_1_CC_PA 257 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for
RAM_LIST_LEN_ERR ST_LEN_ERR Persistent Reserve Out command when the parameter list
length field in the CDB does not correspond to the size of
standard parameter list for Persistent Reserve Out or for
the Register and Move mode.
INST_PER_RES_OUT_2_CC_PA 258 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for
RAM_LIST_LEN_ERR ST_LEN_ERR Persistent Reserve Out command when the initiator
sends insufficient data.
INST_WR_SAME_CC_PARAM_ 259 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Write
LIST_LEN_ERR ST_LEN_ERR Same command when the initiator sends insufficient data.
INST_SND_DIAG_CC_PARAM_ 260 CC_ERROR_CODE_PARAM_LI 71 Instance ID reserved, for a feature planned for future.
LIST_LEN_ERR ST_LEN_ERR
INST_NV_SCRTACH_PAGE_CC 261 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Log
_PARAM_LIST_LEN_ERR ST_LEN_ERR Select command for NV Scratchpage when the value of
the field parameter list length in the CDB is not equal to
the length of NV Scratchpage.
INST_WRBUF_1_CC_INV_FIEL 262 CC_ERROR_CODE_INV_FIELD 66 The CC-invalid operation code instance for command
D_IN_CDB _IN_CDB Write Buffer when the value of the mode field in CDB
indicates an unsupported mode.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_WRBUF_2_CC_INV_OPC 263 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command
ODE DE Write Buffer because of an invalid combination of mode
and buffer ID fields in the CDB.
INST_RDBUF_CC_INV_OPCOD 264 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command
E DE Read Buffer when the word 82 of Identify device data
indicates that the drive does not support the command.
INST_TYPE1_PROTECT_CC_IN 265 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
V_OPCODE DE
V_OPCODE DE
V_OPCODE DE
INST_VALID_RW6CDB_CC_INV 268 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
_OPCODE DE
INST_VALID_PROTECT_CHK_C 269 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
C_INV_OPCODE DE
INST_SMART_WR_SAME_CC_I 270 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
NV_OPCODE DE
INST_WR_LONG_CC_INV_OPC 271 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
ODE DE
INST_RD_LONG_CC_INV_OPC 272 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
ODE DE
INST_SELF_TEST_LGPG_CC_IN 273 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command Log
V_OPCODE DE Sense when Self Test Results Log Page is requested but
smart feature is not enabled or smart self test is not
supported by the drive.
INST_BACKGRND_SCAN_LGPG 274 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command Log
_CC_INV_OPCODE DE Sense when Background Scan Results Log Page is
requested but smart feature is not enabled or smart self
test is not supported by the drive.
INST_PROCESS_USING_SAT_C 275 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance returned when a
C_INV_OPCODE DE command with invalid operation code is sent to the drive.
INST_VALIDATE_RW32_CDB_I 276 CC_ERROR_CODE_INV_OPCO 66 Instance ID reserved, for a feature planned for future.
NVAILD_PROTECTION_CC_INV DE
_OPCODE
INST_SMART_DATA_LGPG_CC 277 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command Log
_INV_OPCODE DE Sense when SATA Firmware Statistics Page is requested
but smart feature is not enabled or smart self test is not
INST_APP_CLNT_LGPG_CC_IN 278 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command Log
V_OPCODE DE Sense when Application Clients Log Page is requested
but smart feature is not enabled or smart self test is not

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SET_APP_CLNT_LGPG_C 279 CC_ERROR_CODE_INV_OPCO 66 The CC-invalid operation code instance for command Log
C_INV_OPCODE DE Select when Application Clients Log Page is sent but
smart feature is not enabled or smart self test is not
INST_FMT_PRO_REC_CC_INV_ 280 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Format
FIELD_IN_PARAM_LIST _IN_PARAM_LIST Unit command when any one of the fields DCRT, FOV,
STPF or IP in the short parameter list header is set to a
nonzero value.
INST_LGSLT_CC_INV_FIELD_IN 281 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log
_PARAM_LIST _IN_PARAM_LIST Select command when the parameter list contains an
unsupported page code.
INST_APP_CLNT_LGPG_1_CC_ 282 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log
INV_FIELD_IN_PARAM_LIST _IN_PARAM_LIST Select command for ApllicationClient Logpage, when the
parameter code exceeds the supported range (0-1FF) or
because of incorrect pagelength.
INST_APP_CLNT_LGPG_2_CC_ 283 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log
INV_FIELD_IN_PARAM_LIST _IN_PARAM_LIST Select command for ApllicationClient Logpage, when the
log parameters in parameter list are out of order.
INST_VERSION_LGPG_CC_INV 284 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log Select
_FIELD_IN_PARAM_LIST _IN_PARAM_LIST command for Version Logpage, when the parameter code
in the parameter list is set to a nonzero value.
INST_START_STOP_CNT_LGPG 285 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log
_CC_INV_FIELD_IN_PARAM_LI _IN_PARAM_LIST Select command for Start Stop Cycle Counter Logpage,
ST when the log parameters in parameter list are out of order.
INST_DA_TEMP_LGPG_CC_IN 286 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Log
V_FIELD_IN_PARAM_LIST _IN_PARAM_LIST Select command for Drive Attachment Temp Logpage,
when the log parameters in parameter list are out of
order or if minimum temperature is higher than the
maximum temperature.
INST_MDPG_SECTOR_SKEW_ 287 CC_ERROR_CODE_INV_FIELD 65 Instance ID reserved, for a feature planned for future.
CC_INV_FIELD_IN_PARAM_LIS _IN_PARAM_LIST
T
INST_PRO_RETRN_MDSEL_CC 288 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for Mode
_INV_FIELD_IN_PARAM_LIST _IN_PARAM_LIST Select command when a field in the parameter list
provided is not within the limits supported.
INST_RES_REL_CC_INV_FIELD 289 CC_ERROR_CODE_INV_FIELD 65 Instance ID reserved, for a feature deprecated.
_IN_PARAM_LIST _IN_PARAM_LIST
INST_PER_RES_OUT_CC_INV_ 290 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for
FIELD_IN_PARAM_LIST _IN_PARAM_LIST Persistent Reserve Out command when the scope specific
address or reserved field in the parameter list is set to a
nonzero value.
INST_PRO_RAMV_CC_INV_FIE 291 CC_ERROR_CODE_INV_FIELD 65 The CC-invalid field in parameter list instance for
LD_IN_PARAM_LIST _IN_PARAM_LIST Persistent Reserve Out command when Target Port
Identifier is greater than maximum number of ports; or
Protocol Identifier field of transport ID is not equal to SAS
transport ID; or SAS address field of transport ID has the
address of the initiator; or Service Action reservation key
in the parameter list is set to 0.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_NTFY_CMD_QD_CC_ILL 292 CC_ERROR_CODE_ILLEGAL_R 63 The CC-illegal request, no sense instance because of a
EGAL_REQ_NO_SENSE EQ_NO_SENSE failure to queue a command when system state machine
is not in ready state; but no additional information is
available.
INST_SRT_STP_UNT_CC_ILLEG 293 CC_ERROR_CODE_ILLEGAL_R 63 Instance ID reserved, removed from the current
AL_REQ EQ_NO_SENSE implementation.
INST_MDSNS_INSUFF_TL_CC_ 294 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in cdb instance for Mode Sense
INV_FIELD_IN_CDB _IN_CDB command when the allocation length or size of data to be
transferred is less than the size of header.
INST_INV_SERVICE_ACTION_C 295 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in cdb instance for a 32 byte
C_INV_FIELD_IN_CDB _IN_CDB command when the service action field in the cdb
contains an unsupported service action code.
INST_CAPACITY_CHANGED_DI 296 UA_ERROR_CODE_CAPACITY 18 The Unit Attention condition when a format command
F _CHANGED forces a change in the maximum logical block.
INST_WRBUF_CC_INVAID_PAC 297 CC_ERROR_CODE_INV_FIELD 65 The CC-Invalid field in parameter list instance for Write
K_IMAGE _IN_PARAM_LIST Buffer command when an invalid image is sent by the
initiator.
INST_WRBUF_CC_DRV_NOT_S 298 CC_ERROR_CODE_INV_OPCO 66 The CC-Invalid operation code instance for Write Buffer
UPPORT_MICROCODE_DNLD DE command, data mode when the command is not
supported by the underlying ATA drive.
INST_MDPG_INFOE_EXCEP_U 299 UA_ERROR_CODE_FAILURE_P 19 The UA instance when unit attention condition is
A_REPORT_INFO_EXCEP_CON REDICTION_THRESHOLD_EXC established when the device detects a threshold
D EEDED exceeded condition.
INST_MDPG_INFOE_EXCEP_C 300 CC_ERROR_CODE_FAIL_PRED 46 The CC-prediction threshold exceeded instance for
C_REPORT_INFO_EXCEP_CON ICTION_THRESHOLD_EXCEED threshold exceed condition.
D ED
INST_MDSEL_CC_INV_FIELD_I 301 CC_ERROR_CODE_INV_FIELD 64 The InstID used when a mode select command is arrived
N_CDB _IN_CDB for a mode page with SavePage bit set and page does not
support saving the values
INST_DEVFAULT_CC_HWERR 302 CC_ERROR_CODE_HW_ERR_I 49 Instance ID to use when the target sets the DF bit in a FIS
NT_TARGET_FAILURE other than the SDB FIS for a NCQ command
INST_RVMDSEL_CC_FLASHWT 303 CC_ERROR_CODE_HW_ERR_F 104 The CC-Instance for Mode Select command for if save
_FAIL LASH_ACCESS_FAILED page is set to TRUE and write to flash fails.
INST_ID_MDSEL_SCTRW_PGM 304 NA NA Instance ID reserved, removed from the current
implementation.
INST_ID_MDSEL_WCACHE_PG 305 NA NA Instance ID reserved, removed from the current
M implementation.
INST_ID_MDSEL_LOOKAHEAD 306 NA NA Instance ID reserved, removed from the current
_PGM implementation.
INST_WRITEBUF_UNT_CC_DR 307 NA NA Instance ID reserved, removed from the current
V_NOT_RDY implementation.
INST_WSAME_CC_LBA_OUT_ 308 CC_ERROR_CODE_LBA_OUT_ 72 The CC-Instance for Mode Select command for if drive err
OF_RANGE OF_RANGE is encountered while write same command is executed
on the drive.The erorIdx and sense Information returned
depends upon the error status returned by underlying
ATA drive.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SSU_FCACHE_STDBY_C 309 CC_ERROR_CODE_ABORTED_ 83 The CC-Sequence error for Start Stop Unit command
C_ERR_ABRT_CSEQ_ERR CMD_SEQ_ERROR when drive returns error for Immediate response and
flush cache response.
INST_SSU_MEJ_RSP_CC_ERR_ 310 CC_ERROR_CODE_ABORTED_ 83 The CC-Sequence error for Start Stop Unit command
ABRT_CSEQ_ERR CMD_SEQ_ERROR when drive returns error for Media eject error.
INST_INQ_INVPMS_CDB_CC_E 311 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In INQUIRY
RR_CODE_INV_FIELD_IN_CDB _IN_CDB command.
INST_INQ_VPD_DC_PG_CC_E 312 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for INQUIRY
RR_CODE_BECMG_RDY G_READY command (DC page) when drive is in the process of
becoming ready.
INST_INQ_VPD_F0_F1_PG_CC 313 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In INQUIRY command
_ERR_CODE_INV_FIELD_IN_C _IN_CDB (Page Converter) when the page is not supported for a
DB customer.
INST_INQ_VPD_DC_PG_CC_E 314 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In INQUIRY command
RR_CODE_INV_FIELD_IN_CDB _IN_CDB (DC Page) when the page is not supported for a customer.
INST_INQ_UNSUP_VPD_PG_C 315 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance In INQUIRY command
C_ERR_CODE_INV_FIELD_IN_ _IN_CDB (Unsupported Page) when the page is not supported for a
CDB customer.
INST_SSU_DRV_ERR_BASE 316 NA NA The CC error code depends upon the error code returned
by drive - Refer to Table 260.
INST_FMTRESP_DRV_ERR_BAS 331 NA NA The CC error code depends upon the error code returned
E = INST_SSU_DRV_ERR_BASE by drive - Refer to Table 260.
+ DRV_ERR_MAX
INST_SMARTFEATURES_DRV_ 346 NA NA The CC error code depends upon the error code returned
ERR_BASE = by drive - Refer to Table 260.
INST_FMTRESP_DRV_ERR_BAS
E + DRV_ERR_MAX
INST_ATAPASSTHRU_DRV_ERR 361 NA NA The CC error code depends upon the error code returned
_BASE = by drive - Refer to Table 260.
INST_SMARTFEATURES_DRV_
ERR_BASE + DRV_ERR_MAX
INST_APPCLT_LGPG_DRV_ERR 376 NA NA The CC error code depends upon the error code returned
INST_ATAPASSTHRU_DRV_ERR
_BASE + DRV_ERR_MAX
INST_SCT_RWERR_MDPG_DR 391 NA NA The CC error code depends upon the error code returned
V_ERR_BASE = by drive - Refer to Table 260.
INST_APPCLT_LGPG_DRV_ERR
_BASE + DRV_ERR_MAX
INST_WCE_MDPG_DRV_ERR_ 406 NA NA The CC error code depends upon the error code returned
BASE = by drive - Refer to Table 260.
INST_SCT_RWERR_MDPG_DR
V_ERR_BASE + DRV_ERR_MAX
INST_DRA_MDPG_DRV_ERR_B 421 NA NA The CC error code depends upon the error code returned
ASE = by drive - Refer to Table 260.
INST_WCE_MDPG_DRV_ERR_
BASE + DRV_ERR_MAX

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_RMW_RSP_DRV_ERR_BA 436 NA NA The CC error code depends upon the error code returned
SE = by drive - Refer to Table 260.
INST_DRA_MDPG_DRV_ERR_B
ASE + DRV_ERR_MAX
INST_WT_DRV_ERR_BASE = 451 NA NA The CC error code depends upon the error code returned
INST_RMW_RSP_DRV_ERR_BA by drive - Refer to Table 260.
SE + DRV_ERR_MAX
INST_RD_DRV_ERR_BASE = 466 NA NA The CC error code depends upon the error code returned
INST_WT_DRV_ERR_BASE by drive - Refer to Table 260.
+ DRV_ERR_MAX
INST_WT_BUFF_DRV_ERR_BA 481 NA NA The CC error code depends upon the error code returned
SE = INST_RD_DRV_ERR_BASE by drive - Refer to Table 260.
+ DRV_ERR_MAX
INST_RD_BUFF_DRV_ERR_BAS 496 NA NA The CC error code depends upon the error code returned
E= by drive - Refer to Table 260.
INST_WT_BUFF_DRV_ERR_BA
SE + DRV_ERR_MAX
INST_REQ_SNS_DRV_ERR_BAS 511 NA NA The CC error code depends upon the error code returned
E= by drive - Refer to Table 260.
INST_RD_BUFF_DRV_ERR_BAS
E + DRV_ERR_MAX
INST_WSAME_DRV_ERR_BASE 526 NA NA The CC error code depends upon the error code returned
= by drive - Refer to Table 260.
INST_REQ_SNS_DRV_ERR_BAS
E + DRV_ERR_MAX
INST_SYNC_CACHE_DRV_ERR 541 NA NA The CC error code depends upon the error code returned
INST_WSAME_DRV_ERR_BASE
+ DRV_ERR_MAX
INST_VFY_DRV_ERR_BASE 556 NA NA The CC error code depends upon the error code returned
INST_SYNC_CACHE_DRV_ERR
_BASE + DRV_ERR_MAX
INST_WT_VFY_DRV_ERR_BAS 571 NA NA The CC error code depends upon the error code returned
E = INST_VFY_DRV_ERR_BASE by drive - Refer to Table 260.
+ DRV_ERR_MAX
INST_WLONG_DRV_ERR_BASE 586 NA NA The CC error code depends upon the error code returned
= by drive - Refer to Table 260
INST_WT_VFY_DRV_ERR_BAS
E + DRV_ERR_MAX
INST_RLONG_DRV_ERR_BASE 601 NA NA The CC error code depends upon the error code returned
INST_WLONG_DRV_ERR_BASE
+ DRV_ERR_MAX
INST_APPCLT_LGSNS_DRV_ER 616 NA NA The CC error code depends upon the error code returned
R_BASE = by drive - Refer to Table 260.
INST_RLONG_DRV_ERR_BASE
+ DRV_ERR_MAX

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SELFTEST_LGPG_DRV_E 631 NA NA The CC error code depends upon the error code returned
RR_BASE = by drive - Refer to Table 260.
INST_APPCLT_LGSNS_DRV_ER
R_BASE + DRV_ERR_MAX
INST_BGTEST_LGPG_DRV_ERR 646 NA NA The CC error code depends upon the error code returned
_BASE = by drive - Refer: Refer to Table 260.
INST_SELFTEST_LGPG_DRV_E
RR_BASE + DRV_ERR_MAX
INST_SMART_DATA_LGPG_DR 661 NA NA The CC error code depends upon the error code returned
V_ERR_BASE = by drive - Refer to Table 260.
INST_BGTEST_LGPG_DRV_ERR
_BASE + DRV_ERR_MAX
INST_INQ_DRV_ERR_BASE = 676 NA NA The CC error code depends upon the error code returned
INST_SMART_DATA_LGPG_DR by drive - Refer to Table 260.
V_ERR_BASE + DRV_ERR_MAX
INST_REQSNS_CC_ERROR_CO 691 CC_ERROR_CODE_HW_IMPE 108 Instance ID for Request sense when drive detects
DE_HW_IMPENDING_FAILURE NDING_FAILURE_GEN_DRV_F threshold exceed condition.
_GEN_DRV_FAIL = AIL
INST_INQ_DRV_ERR_BASE
+ DRV_ERR_MAX
INST_INQ_DRIVEDOWN_CC_B 692 CC_ERROR_CODE_BECOMIN 45 The CC-becoming ready instance for INQUIRY command
ECOMING_RDY G_READY for VPD page for Fake Inquiry data when drive is in the
process of becoming ready.
INST_RW_10_12_16_CDB_FU 693 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for RD/WR 10,12, and
ANV_VAL_CC_INV_FLD_IN_C _IN_CDB 16 CDB when FUANV bit is set in CDB.
DB
INST_VALIDATE_WS_10_16_C 694 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for WS 10 and 16
DB_VALIDATION_CC_INV_FIEL _IN_CDB commands when control field is nonzero.
D_IN_CDB
INST_VALIDATE_WS_10_16_C 695 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for WS 10 and 16
DB_LB_PB_DATA_SUPPORT_C _IN_CDB commands when PBDATA or LBDATA is nonzero.
C_INV_FIELD_IN_CDB
INST_RD_CTL_DPO_CHK_CC_ 696 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for RD command (All
LBA_OUT_OF_RANGE _IN_CDB variants) control field is nonzero or DPO is nonzero.
INST_WR_CTL_DPO_CHK_CC_ 697 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for WR command (All
LBA_OUT_OF_RANGE _IN_CDB variants) control field is nonzero or DPO is nonzero.
INST_VALIDATE_WS_3264_WR 698 CC_ERROR_CODE_INV_FIELD 64 Instance ID reserved, for a feature planned for future.
KRD_CC_INV_FIELD_IN_CDB _IN_CDB
INST_COMMAND_NOT_ACTIV 699 CC_ERROR_CODE_ABORTED_ 98 The CC-Command Aborted by Device Server. This is
E_ON_DRIVE_ABORTED_FOR_ CMDS_CLRD_BY_DEVSRV returned when the commands that are not active on the
CLEAN_REBOOT Drive are aborted by the LSISS2520/LSISS2530 device for
a clean reboot.
INST_PREEMPT_UA_RESERVAT 700 UA_ERROR_CODE_RESERVATI 4 UA-Reservations cleared Instance. This is returned for the
IONS_CLEARED ONS_CLEARED registered and nonaffected initiator when PR type
changes as a result of PREEMPT service action.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_UNREGISTER_UA_RESER 701 UA_ERROR_CODE_RESERVATI 4 UA-Reservations cleared Instance. This is returned for the
VATIONS_CLEARED ONS_CLEARED registered initiators in REGISTER/REGISER AND IGNORE
EXISTING KEY when existing PR type is any of the RO
types PR holder unregisters.
INST_NO_PROTECTION_CHK_ 702 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance for READ, WRITE, etc.
CC_INV_FIELD_IN_CDB _IN_CDB commands with Protect field set to a nonzero value.
INST_MDIO_ACCESS_INV_DAT 703 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance for MDIO access
A_OR_ADDR _IN_CDB command, if MDIO Register is not 4-byte aligned or the
data field is not zero for a read type command.
INST_MDIO_ACCESS_INV_DEV 704 CC_ERROR_CODE_INV_FIELD 64 The CC-invalid field in CDB instance for MDIO access
_TYPE _IN_CDB command, if Dev Type is not set to the Dev Type when FW
Control was enabled.
INST_WRBUF_MULTIPLE_PKG_ 705 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Write Buffer
UPG_INVALID_BUFFOFFSET _IN_CDB command where multiple Write Buffer package upgrade
is going on and out of sequence Write Buffer command is
received.
INST_WRBUF_MULTIPLE_PKG_ 706 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Write Buffer
UPG_INVALID_PLL _IN_CDB command where multiple Write Buffer package upgrade
is going on and parameter list length is less than 1k or not
multiple of 1k.
INST_WRBUF_CC_DRV_NT_SU 707 CC_ERROR_CODE_INV_FIELD 65 The CC-Invalid field in Parameter list length instance for
PPRT_MULTI_DNLD_OR_WRO _IN_PARAM_LIST Write Buffer command where multiple Write Buffer
NG_LENGTH package upgrade is going on and drive does not support
multiple download microcode firmware download or
non-512 chunk is detected.
INST_WRBUF_CC_INV_FLD_C 708 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Write Buffer
DB_BOOT_OPT_UPGRADE_N _IN_CDB command Boot option upgrade using Mode 7 buffer ID 3
ONZERO_BUFOFFSET and buffer offset is nonzero.
INST_SECURITY_IN_OUT_CC_I 709 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Security IN OUT
NV_OPCODE _IN_CDB Protocol for trusted command not supported.
INST_SECURITY_IN_OUT_CHK 710 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Security IN OUT
_ALLOC_LEN_CC_INV_FIELD_I _IN_CDB Protocol for invalid allocation length.
N_CDB
INST_TRUSTED_CMD_DRV_ER 711 NA NA The CC error code depends upon the error code returned
R_BASE by drive - Refer to Table 260.
INST_WRBUF_CC_ALTA_IMAG 726 CC_ERROR_CODE_PARAM_LI 71 The CC-Parameter List Length error when the
E_SMALL_SIZE = ST_LEN_ERR LSISS2520/LSISS2530 device firmware size is beyond flash
INST_TRUSTED_CMD_DRV_ER capacity.
R_BASE + DRV_ERR_MAX
INST_UA_WB_DFW_UPGRADE 727 UA_ERROR_CODE_MICROCO 3 The UA-Microcode updated instance for mode 0x5
_MICROCODE_CHANGED DE_UPDATED bufferId 0x0 drive firmware upgrade in Write Buffer.
INST_WRBUF_MD7_INV_BUFI 728 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for WriteBuffer when
D_CC_INV_FLD_IN_CDB _IN_CDB Invalid BuffId is received for mode 0x7.
INST_WRBUF_CC_MODE7_BU 729 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for WriteBuffer when
FID0_CDB_VALIDATION _IN_CDB Invalid parameter list length/buffer offset is received for
mode 7 buffer Id 0 drive firmware upgrade.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_CAPACITY_CHANGED_F 730 UA_ERROR_CODE_CAPACITY 18 The Unit Attention condition when a format command
MT_CMD _CHANGED forces a change in the maximum logical block.
INST_STDBY_PCMDPG_DRV_E 731 NA NA The CC error code depends upon the error code returned
RR_BASE by drive - Refer to Table 260.
INST_APMP_PCMDPG_DRV_E 746 NA NA The CC error code depends upon the error code returned
RR_BASE = by drive - Refer to Table 260
INST_STDBY_PCMDPG_DRV_E
INST_LUN_NOT_RDY_NOTIFY_ 761 CC_ERROR_CODE_NOT_RDY_ 109 The CC error code Not ready returned for media access
SPINUP_REQUIRED = NOTIFY_SPINUP_REQUIRED commands when lun state is waiting for spinup or active
INST_APMP_PCMDPG_DRV_E wait state.
INST_SND_STP_UNT_CC_ABR 762 CC_ERROR_CODE_ABORTED_ 105 The CC-Start Stop Unit command aborted by device
TED_INSF_RES INSUFFICIENT_RES server as previous Start Stop Unit command still in
progress.
INST_STP_UNT_CC_LUN_NOT 763 CC_ERROR_CODE_NOT_RDY_ 109 The CC-Start Stop Unit command terminated because of
_RDY_NOTIFY_SPINUP_REQUI NOTIFY_SPINUP_REQUIRED Drive State Machine not ready and waiting for spin-up.
RED
INST_CAPACITY_CHANGED_S 764 UA_ERROR_CODE_CAPACITY 18 The Unit Attention condition when Mode Page 0x33
ECTOR_SKEW _CHANGED forces a change in the maximum logical block.
INST_CAPACITY_CHANGED_B 765 UA_ERROR_CODE_CAPACITY 18 The Unit Attention condition when a Mode Page Block
LK_DESC _CHANGED Descriptor forces a change in the maximum logical block.
INST_UA_SATA_LINK_OR_DRI 766 UA_ERROR_CODE_POR_OR_ 20 The Unit Attention condition when drive reset occurs or
VE_RESET BUS_DEVICE_RESET SATA link reset occurs.
_INC_512_NON_EF_CC_INV_F _IN_CDB Protocol for trusted command is supported and INC 512
IELD_IN_CDB is not set.
_MAX_ALLOC_LEN_CC_INV_FI _IN_CDB Protocol for trusted command is supported allocation
ELD_IN_CDB length is greater than 0xFFFF than send a send a CC
invalid field in CDB.
_INC_512_EF_CC_INV_FIELD_I _IN_CDB Protocol for Device server security support and INC_512
N_CDB is set.
INST_SECURITY_IN_OUT_CHK 770 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Security OUT
_ALLOC_LEN_SEC_OUT_CC_I _IN_CDB Protocol for Device server security support and Allocation
NV_FIELD_IN_CDB length is invalid.
INST_SECURITY_IN_OUT_CHK 771 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Security IN
_ALLOC_LEN_SEC_IN_CC_INV _IN_CDB Protocol for Device server security support and Allocation
_FIELD_IN_CDB length is invalid.
_INV_SEC_PROTOCOL_MODE _IN_CDB Protocol for invalid security protocol mode.
_CC_INV_FIELD_IN_CDB
INST_CHK_LUST_CC_ATA_SEC 773 CC_ERROR_CODE_ATA_SECU — The CC-Invalid field in CDB instance for Security IN OUT
_CONFLICT RITY_CONFLICT Protocol for security state conflict while LU state checking.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_SECURITY_IN_OUT_CC_ 774 CC_ERROR_CODE_PARAM_LI 71 The CC-invalid parameter list length instance for Security
PARAM_LIST_LEN_ERR ST_LEN_ERR IN/OUT command when insufficient data is sent by the
initiator.
INST_SECURITY_IN_OUT_CC_I 775 CC_ERROR_CODE_ATA_SECU — The CC-Invalid field in CDB instance for Security IN OUT
NV_SECURITY_STATE RITY_CONFLICT Protocol for invalid security state while validating LUN
state for Security In/Out Command.
INST_SSU_ACTIVE_IDLE_VERIF 776 CC_ERROR_CODE_ABORTED_ 83 The CC-Start Stop Unit command (power condition field
Y_CC_ERR_ABRT_CSEQ_ERR CMD_SEQ_ERROR set to ACTIVE) aborted by device server as error response
received from the drive.
INST_SSU_LU_CNTRL_CC_ERR 777 CC_ERROR_CODE_ABORTED_ 83 The CC-Start Stop Unit command (power condition field
_ABRT_CSEQ_ERR CMD_SEQ_ERROR set to LU_CONTROL) aborted by device server as error
response received from the drive
INST_SSU_IDLE_CC_ERR_ABR 778 CC_ERROR_CODE_ABORTED_ 83 The CC-Start Stop Unit command (power condition field
T_CSEQ_ERR CMD_SEQ_ERROR set to IDLE) aborted by device server as error response
received from the drive.
INST_SSU_STANDBY_CC_ERR_ 779 CC_ERROR_CODE_ABORTED_ 83 The CC-Start Stop Unit command (power condition field
ABRT_CSEQ_ERR CMD_SEQ_ERROR set to STANDBY) aborted by device server as error
response received from the drive.
INST_SSU_FORCE_STANDBY_ 780 CC_ERROR_CODE_ABORTED_ 83 The CC-Start Stop Unit command (power condition field
CC_ERR_ABRT_CSEQ_ERR CMD_SEQ_ERROR set to FORCE_STANDBY_0) aborted by device server as
error response received from the drive.
INST_REQUEST_SENSE_CC_ST 781 CC_ERROR_CODE_LU_STAND 111 The CC-Request sense command instance, power
ANDBY_CONDITION_ACTIVAT BY_CONDITION_ACTIVATED condition activated to Standby.
ED
INST_REQUEST_SENSE_CC_ID 782 CC_ERROR_CODE_LU_IDLE_C 112 The CC-Request sense command instance, power
LE_CONDITION_ACTIVATED ONDITION_ACTIVATED condition activated to Idle.
INST_REQUEST_SENSE_CC_PO 783 CC_ERROR_CODE_LU_POWE 113 The CC-Request sense command instance, power
WER_CONDITION_CHANGE_T R_CONDITION_CHANGE_TO_ condition returned by SATA device as Standby.
O_STANDBY STANDBY
INST_REQUEST_SENSE_CC_PO 784 CC_ERROR_CODE_LU_POWE 114 The CC-Request sense command instance, power
WER_CONDITION_CHANGE_T R_CONDITION_CHANGE_TO_ condition returned by SATA device as Idle.
O_IDLE IDLE
INST_UA_LOG_PARAMETERS_ 785 UA_ERROR_CODE_LOG_PARA 7 The UA Instance when unit attention condition is
CHANGED METERS_CHANGED established because log parameters which affect the I_T
NEXUS are changed on another I_T NEXUS.
INST_UA_CMDS_CLRED_BY_ 786 UA_ERROR_CODE_CMDS_ 21 The UA Instance when unit attention condition is
PWR_LOSS_NOTIFICATION CLRED_BY_PWR_LOSS_ established because commands were cleared because of
NOTIFICATION a power loss notification.
INST_WRBUF_INCOMPATIBLE_ 787 CC_ERROR_CODE_INV_FIELD 65 The CC-Invalid field in Parameter list length instance for
IMG_CC_INV_FLD_IN_PARAM _IN_PARAM_LIST WB command where the firmware image being loaded
_LIST on a given flash part is not compatible for the flash part.
INST_UA_IT_NEXUS_LOSS_ 788 UA_ERROR_CODE_IT_NEXUS 22 The UA Instance when unit attention condition is
OCCURRED _LOSS_OCCURRED established because a IT Nexus Reset TMF was processed.
INST_WRBUF_INCOMPATIBLE_ 789 CC_ERROR_CODE_INV_FIELD 65 The CC-Invalid field in Parameter list length instance for
BL_VER _IN_PARAM_LIST WB command where the bootloader image being loaded
on a given flash part is not compatible for the flash part.

Numeric
Numeric
Value
for default
InstId
ErrorIdx
INST_WR_SAME_HW_BUFF_ 790 CC_ERROR_CODE_HW_ERR_ 49 The CC Instance when there are failures when allocating
CC_ERROR_INT_TARGET_ INT_TARGET_FAILURE or accessing internal HW buffers.
FAILURE
INST_ID_QUEUEFULL_STATUS 791 CC_ERROR_CODE_BECOMIN 45 The CC-instance ID specific to customer to override
_OVERRIDE G_READY queue full status.
INST_SND_RECV_DIAG_BGND 792 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Send diagnostic
_SLF_TEST_COMPLETED_CC_ _IN_CDB command when background self test is finished and
INV_FIELD_IN_CDB Abort background self test is send.
INST_SND_RECV_DIAG_ABRT_ 793 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Send diagnostic
TEST_FAILED_CC_INV_FIELD_I _IN_CDB command when Abort background self test fails.
N_CDB
INST_MDSEL_CC_SAVING_PAR 794 CC_ERROR_CODE_SAVING_P 115 The CC_Saving Parameters not supported instance for
AMS_NOT_SUPPORTED ARAMS_NOT_SUPPORTED Mode Sense command when requested mode page does
not support saved values.
INST_REPORT_TIMESTAMP_CC 795 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Report
_INV_FEILD_IN_CDB _IN_CDB Timestamp command for invalid field in CDB.
INST_SET_TIMESTAMP_CC_IN 796 CC_ERROR_CODE_INV_FIELD 64 The CC-Invalid field in CDB instance for Set Timestamp
V_FEILD_IN_CDB _IN_CDB command for invalid field in CDB.
INST_SET_TIMESTAMP_CC_PA 797 CC_ERROR_CODE_PARAM_LI 71 The CC-parameter list length error instance for Set
RAM_LIST_LEN_ERR ST_LEN_ERR Timestamp command when the initiator sends
insufficient data.
INST_SET_TIMESTAMP_CC_IN 798 CC_ERROR_CODE_PARAM_LI 71 The CC-parameter list length error instance for Set
V_FIELD_IN_PARAM_LIST ST_LEN_ERR Timestamp command when time stamp value exceeds
maximum allowable value.
INST_SET_TIMESTAMP_UA_TI 799 UA_ERROR_CODE_TIMESTAM 23 The UA instance when unit attention condition is
MESTAMP_CHANGED P_CHANGED established because the time stamp is changed using the
SET TIMESTAMP command.
MAX_INST_ID 800 — — —

Table 260: DRIVE ERROR LOOKUP DATA
Numeric Value of
ERROR OFFSET OFFSET Drive Errors ErrorIdx
Default ErrorIdx
DRV_ERR_DF 0 DF bit 49 CC_ERROR_CODE_HW_ERR_INT_TARGET_FAILURE
DRV_ERR_NM 1 NM bit 42 CC_ERROR_CODE_SNS_NOT_RDY_MED_ABSENT
DRV_ERR_UNC 2 UNC bit 59 CC_ERROR_CODE_MED_ERR_UNRECOVERED_READ
DRV_ERR_DP 3 DP bit 38 CC_ERROR_CODE_DATA_PROTECT
DRV_ERR_IDNF 4 IDNF bit 72 CC_ERROR_CODE_LBA_OUT_OF_RANGE
DRV_ERR_MC 5 MC bit 11 UA_ERROR_CODE_MEDIUM_CHANGED
DRV_ERR_MCR 6 MCR bit 12 UA_ERROR_CODE_MEDIUM_REMOVAL_REQUEST
DRV_ERR_ICRC 7 ICRC bit 85 CC_ERROR_CODE_ABORTED_INF_UINT_CRC_ERROR
DRV_ERR_ABRT 8 ABRT bit 78 CC_ERROR_CODE_ABORTED_NO_SENSE
DRV_ERR_UNHANDELED 9 UNHANDLED Drive error 63 CC_ERROR_CODE_ILLEGAL_REQ_NO_SENSE
DRV_ERR_RSVD1 10 Reserved for future use NA NA
DRV_ERR_MAX 15 Reserved for future use NA NA


LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix G: | SCSI Commands with Long Logical Sector SATA Drive
Appendix G
Long Logical Sector SATA Drive Support
This appendix describes the LSISS25x0 device’s Long Logical Sector SATA drive support.
The LSISS25x0 device supports 520, 528, 4096, 4104, and 4160 bytes sector size SATA
drives. The LSISS25x0 device does not support sector skewing (except with 4096 bytes
sector sized SATA drives) and READ LONG/WRITE LONG data type command with the
Long Logical Sector SATA drive. The READ LONG/WRITE LONG data type command is
check conditioned with a sense key set to ILLEGAL REQUEST and ASC set to INVALID
COMMAND OPERATION CODE.
The LSISS25x0 device follows ATA8-ACS specifications to differentiate the Long Logical
Sector and 512-bytes sector size commands with the Long Logical Sector SATA drive.
G.1 SCSI Commands with The following SCSI commands transfer Long Logical Sector size data per block:
Long Logical Sector SATA Drive
 FORMAT UINT
 READ (6)/(10)/(12)/(16)
 REASSIGN BLOCKS
 WRITE (6)/(10)/(12)/(16)
 WRITE AND VERIFY (10)/(12)/(16)
 WRITE SAME (10)/(16)
The following SCSI commands transfer 512 bytes of data per block:
 READ BUFFER
 WRITE BUFFER
Additionally, lengths of Log Parameter Data and Smart Data within log page 0Fh and
log page 31h, respectively, do not change with the Long Logical Sector SATA drive.
G.2 ATA PASS THROUGH The following ATA commands transfer 512 bytes per block:
Commands with Long Logical
 ADD LBA(S) TO NV CACHE PINNED SET
Sector SATA Drive
 DEVICE CONFIGURATION IDENTIFY
 DEVICE CONFIGURATION SET
 DOWNLOAD MICROCODE
 IDENTIFY DEVICE
 IDENTIFY PACKET DEVICE
 QUERY NV CACHE MISSES
 QUERY NV CACHE PINNED SET
 READ BUFFER

Appendix G: | ATA PASS THROUGH Commands with Long Logical Sector SATA Drive LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 READ LOG DMA EXT

 READ LOG EXT
 REMOVE LBAs FROM NV CACHE PINNED SET
 SECURITY DISABLE PASSWORD
 SECURITY ERASE UNIT
 SECURITY SET PASSWORD
 SECURITY UNLOCK
 SET MAX SET PASSWORD
 SET MAX UNLOCK
 SMART READ DATA
 SMART READ LOG
 SMART WRITE LOG
 TRUSTED RECEIVE
 TRUSTED RECEIVE DMA
 TRUSTED SEND
 TRUSTED SEND DMA
 WRITE BUFFER
 WRITE LOG DMA EXT
 WRITE LOG EXT
The following ATA commands transfer Long Logical Sector size data per block:
 CFA TRANSLATE SECTOR
 CFA WRITE MULTIPLE WITHOUT ERASE
 CFA WRITE SECTORS WITHOUT ERASE
 READ DMA
 READ DMA EXT
 READ FPDMA QUEUED
 READ MULTIPLE
 READ MULTIPLE EXT
 READ SECTOR(S)
 READ SECTOR(S) EXT
 READ STREAM DMA EXT
 READ STREAM EXT
 WRITE DMA
 WRITE DMA EXT
 WRITE DMA FUA EXT
 WRITE FPDMA QUEUED
 WRITE MULTIPLE
 WRITE MULTIPLE EXT
 WRITE MULTIPLE FUA EXT
 WRITE SECTOR(S)

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix G: | ATA PASS THROUGH Commands with Long Logical Sector SATA Drive
 WRITE SECTOR(S) EXT

 WRITE STREAM DMA EXT
 WRITE STREAM EXT

Appendix G: | ATA PASS THROUGH Commands with Long Logical Sector SATA Drive LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix H: | Packed Mode Non-512 Byte Mapping
Appendix H
Sector Skewing Support
This appendix describes the LSISS25x0 device’s Sector Skewing feature.
The LSISS25x0 device supports Packed and Sparse Mode Sector Skewing
configurations. The calculations performed in these modes to support SCSI command
requests are described in the following sections.
H.1 Packed Mode Non-512 The following figure shows the Packed Mode non-512 byte mapping.
Byte Mapping
Figure 7: Packed Mode Non-512 Byte Mapping
H.1.1 Read Case For a SCSI read request for k blocks starting from SCSI LBA n, where each block is not
512 bytes in length (see the previous figure), the firmware must perform the following
calculations:
 Calculate m, the equivalent starting LBA on the SATA device, and j, the number of
512 byte sectors needed to cover the entire SCSI read request.
 Calculate the First Sector Offset (FSO). The FSO is defined from the beginning of
SATA LBA m to the start of SCSI LBA n.
 Calculate the Last Sector Offset (LSO). The LSO is defined from the ending of SCSI
LBA n + k to end of SATA LBA m + j.
The LSISS25x0 device’s hardware handles the data transfer between SATA and SAS
interfaces and excludes the bytes as indicated by the FSO and LSO fields while
transferring on the SAS side.
H.1.2 Write Case For a SCSI write request for k blocks starting from LBA n, where each block is not 512
bytes in length (see the previous figure), the firmware must perform the following
calculations:
 Calculate m, the equivalent starting LBA on the SATA device, and j the number of
512 byte sectors needed to cover entire SCSI write request, FSO and LSO as
described in the previous read case.
 Run a single sector read command to the SATA device for SATA LBA m if FSO is a
nonzero value.

Appendix H: | Sparse Mode Non-512 Byte Mapping LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 Run a single sector read command to the SATA device for SATA LBA (m + j) if LSO is a
nonzero value.
 Run a write command with the FSO and LSO fields as shown in Figure 7 and
described in Section H.1.1.
The LSISS25x0 device’s hardware handles the merging of the data received from the
initiator with the data read from the SATA device.
H.2 Sparse Mode Non-512 The Sparse Mode is similar to Packed Mode except that the bytes remaining on the
Byte Mapping SATA device sector after the end of the stripe, if any, are not used. The LSISS25x0 device
skips this space in case of multistripe accesses. Therefore, this space is unavailable to
the initiators.
Figure 8: Sparse Mode Non-512 Byte Mapping

The LSISS25x0 device’s firmware calculates the Next Sector Offset (NSO) (see the
previous figure) for the particular Sparse Mode configuration and programs the same
to the hardware.
H.3 Important Notes Note the following information:

 The LSISS25x0 device does not support READ LONG and WRITE LONG data type
commands when configured in sector skewing mode. These commands are check
conditioned with a sense key set to ILLEGAL REQUEST and ASC set to INVALID
COMMAND OPERATION CODE, when issued in sector skewing configurations.
 The LSISS25x0 device calculates maximum supported SCSI LBA for the configured
sector skewing mode. The same gets recalculated if the SATA device is changed.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix I: | Supported T10 DIF Features
Appendix I
T10 DIF Features
This appendix describes the LSISS25x0 device’s T10 DIF feature.
I.1 Supported T10 DIF The LSISS25x0 device supports the following T10 DIF features:
Features
 User Data Sizes of 512 and 520 bytes for SATA drive’s with 512 byte sector sizes
 FORMAT UNIT Command Support:
— Protection Types 1, 2, and 3 (FMPTINFO)
— Protection Interval Exponent = 0
 Support by the following media access commands:
— READ 6/10/12/16/32
— WRITE 6/10/12/16/32
— WRITE SAME 10/16/32
 Protect Modes 0 – 5 for all of the supported media access commands mentioned in
this list.
Strip or Generation of DIF data for Protect Mode = 0
 INQUIRY Command Support:
Reports PROTECT = 1
 Extended INQUIRY Data VPD Page (0x86) Support:
— Reports the SPT = 7 which indicates support for all three protection types
— Reports GRD_CHK, APP_CHK, and REF_CHK = 1
 READ CAPACITY(16) Command Support. PROT_EN and P_TYPE fields are updated
after a FORMAT for DIF completes.
I.2 Unsupported T10 DIF The LSISS25x0 device does NOT support the following T10 DIF features:
Features
 User Data Sizes other than 512 or 520 bytes.
 SATA drives with non-512 byte sector sizes.
 The following media access commands:
— VERIFY 10/12/16/32
— WRITE AND VERIFY 10/12/16/32
 Protection Interval Exponent != 0
 All 32 Byte CDBs: LOGICAL BLOCK APPLICATION TAG MASK set to any value other
than 0xFFFF.

Appendix I: | Unsupported T10 DIF Features LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix J: | ATA Device Server Password Security Protocol
Appendix J
SAT-Specific Security Protocol Parameters
This appendix describes the LSISS25x0 device’s SAT-Specific Security Protocol support.
J.1 ATA Device Server The LSISS2520/LSISS2530 device supports the ATA Device Server Password Security
Password Security Protocol Protocol when the SECURITY PROTOCOL field is set to EFh in the SECURITY PROTOCOL
IN/OUT command.
J.1.1 SECURITY PROTOCOL IN The SECURITY PROTOCOL IN command is used by the application client to cause the
Command LSISS2520/LSISS2530 device to return ATA Security feature set data extracted from the
ATA IDENTIFY DEVICE data from the ATA device.
If the SECURITY PROTOCOL field is set to EFh in a SECURITY PROTOCOL IN command,
the SECURITY PROTOCOL SPECIFIC field is set to 0. All other values of the SECURITY
PROTOCOL SPECIFIC field are reserved.
The INC_512 bit is set to 0. If a SECURITY PROTOCOL IN command is received with the
INC_512 bit set to 1, the SECURITY PROTOCOL IN command is terminated with CHECK
CONDITION status, sense key set to ILLEGAL REQUEST, and the additional sense code
set to INVALID FIELD IN CDB.
J.1.1.1 SECURITY PROTOCOL IN The following table defines the parameter data sent in response to a SECURITY
Parameter Data PROTOCOL IN command with the SECURITY PROTOCOL field set to EFh. The value in the
SECURITY ERASE TIME field indicates the time required by the ATA device to complete
its security erase procedure in normal mode.
 SECURITY ERASE TIME
The LSISS2520/LSISS2530 device sets the least significant byte of the SECURITY
ERASE TIME field to the ATA IDENTIFY DEVICE data word 89 bits (0:7) and the most
significant byte of the SECURITY ERASE TIME field to 00h.
 ENHANCED SECURITY ERASE TIME
The value in the ENHANCED SECURITY ERASE TIME field indicates the time required
by the ATA device to complete its security erase procedure in enhanced mode. The
LSISS2520/LSISS2530 device sets the least significant byte of the ENHANCED
SECURITY ERASE TIME field to the ATA IDENTIFY DEVICE data word 90 bits (0:7) and
the most significant byte of the ENHANCED SECURITY ERASE TIME field to 00h.
 MASTER PASSWORD IDENTIFIER
The LSISS2520/LSISS2530 device sets the MASTER PASSWORD IDENTIFIER field to
the ATA IDENTIFY DEVICE data word 82.

Appendix J: | ATA Device Server Password Security Protocol LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
 MAXSET
This bit is the master password capability setting. If the ATA IDENTIFY DEVICE data
word 128 bit 8 is set to 0, the LSISS2520/LSISS2530 device sets this bit to 0. If the ATA
IDENTIFY DEVICE data word 128 bit 8 is set to 1, the LSISS2520/LSISS2530 device
sets this bit to 1.
 EN_ER_SUP
This is the enhanced erase mode supported bit. If the ATA IDENTIFY DEVICE data
sets this bit to 1.
Table 261: SECURITY PROTOCOL IN Parameter Data
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED
1 PARAMETER LIST LENGTH (0Dh)
(MSB)
2:3 SECURITY ERASE TIME
(LSB)
(MSB)
4:5 ENHANCED SECURITY ERASE TIME
(LSB)
(MSB)
6:7 MASTER PASSWORD IDENTIFIER
(LSB)
8 RESERVED
9 RESERVED EN_ER_SUP PWCNTEX FROZEN LOCKED S_ENABLD S_SUPRT
10:15
 PWCNTEX
This is the password attempt counter exceeded bit. If the ATA IDENTIFY DEVICE data
sets this bit to 1.
 FROZEN
This is the frozen state bit. If the ATA IDENTIFY DEVICE data word 128 bit 3 is set to 0,
the LSISS2520/LSISS2530 device sets this bit to 0. If the ATA IDENTIFY DEVICE data
word 128 bit 3 is set to 1, the LSISS2520/LSISS2530 device sets this bit to 1.
 LOCKED
This is the locked state bit. If the ATA IDENTIFY DEVICE data word 128 bit 2 is set to 0,
the LSISS2520/LSISS2530 device sets this bit to 0. If the ATA IDENTIFY DEVICE data
word 128 bit 2 is set to 1, the LSISS2520/LSISS2530 device sets this bit to 1.

 S_ENABLD
This is the ATA Security feature set enabled bit. If the ATA IDENTIFY DEVICE data
IDENTIFY DEVICE data word 85 bit 1 is set to 1, the LSISS2520/LSISS2530 device sets
this bit to 1. Enabling of this bit is based on setting of the user password via a set
password function.
 S_SUPRT
This is the ATA Security feature set supported bit. If the ATA IDENTIFY DEVICE data
IDENTIFY DEVICE data word 82 bit 1 is set to 1, the LSISS2520/LSISS2530 device sets
this bit to 1.
J.1.2 SECURITY PROTOCOL OUT The SECURITY PROTOCOL OUT command is used by an application client to send ATA
Command Security feature set commands and data to the ATA device. See ATA8-ACS for a
description of the ATA Security feature set and all of the functions defined in this
standard. When the SECURITY PROTOCOL field is set to EFh in a SECURITY PROTOCOL
OUT command, the SECURITY PROTOCOL SPECIFIC field specifies the ATA command
that the LSISS2520/LSISS2530 device sends to the ATA device. The following table
shows the fields for this command.
Table 262: SECURITY PROTOCOL SPECIFIC Field
SECURITY PROTOCOL
Description ATA Command Processing Reference
SPECIFIC Field
0000h Reserved
0001h Set password ATA SECURITY SET PASSWORD
0002h Unlock ATA SECURITY UNLOCK
0003h Erase prepare ATA SECURITY ERASE PREPARE
0004h Erase unit ATA SECURITY ERASE UNIT
0005h Freeze lock ATA SECURITY FREEZE LOCK
0006h Disable password ATA SECURITY DISABLE PASSWORD
0007h through FFFFh Reserved
The INC_512 bit is set to 0. If a SECURITY PROTOCOL OUT command is received with the
INC_512 bit is set to 1, the SECURITY PROTOCOL OUT command is terminated with
CHECK CONDITION status, the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.

J.1.2.1 Set Password Parameter If the SECURITY PROTOCOL SPECIFIC field is set to 0001h in the SECURITY PROTOCOL
List OUT CDB, the TRANSFER LENGTH field in the CDB is set to 24h. The following table
defines the parameter list for the SECURITY PROTOCOL OUT command when the
SECURITY PROTOCOL SPECIFIC field is set to 0001h (set password).
Table 263: Set Password Parameter List
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED MAXLVL
1 RESERVED MSTRPW
(MSB)
2:33 PASSWORD
(LSB)
(MSB)
34:35 MASTER PASSWORD IDENTIFIER
(LSB)
 MAXLVL
The LSISS2520/LSISS2530 device copies the contents of the MAXLVL bit to word 0,
bit 8 of the ATA SECURITY SET PASSWORD data.
 MSTRPW
The LSISS2520/LSISS2530 device copies the contents of the MSTRPW bit to word 0,
bit 0 of the ATA SECURITY SET PASSWORD data. If the MSTRPW field is set to 1, the
LSISS2520/LSISS2530 device copies the contents of the MASTER PASSWORD
IDENTIFIER field to the ATA SECURITY SET PASSWORD data.
 PASSWORD
The LSISS2520/LSISS2530 device copies the contents of the PASSWORD field to
words (16:1) of the ATA SECURITY SET PASSWORD data.
J.1.2.2 Unlock Parameter List If the SECURITY PROTOCOL SPECIFIC field is set to 0002h in the SECURITY PROTOCOL
OUT CDB, the TRANSFER LENGTH field in the CDB is set to 24h. The following table
SECURITY PROTOCOL SPECIFIC field is set to 0002h (unlock).
Table 264: Unlock Parameter List
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED
1 RESERVED MSTRPW

Table 264: Unlock Parameter List (Continued)
BIT
Byte
7 6 5 4 3 2 1 0
(MSB)
2:33 PASSWORD
(LSB)
34:35 RESERVED
 MSTRPW
The LSISS2520/LSISS2530 device copies the MSTRPW bit to word 0, bit 0 of the ATA
SECURITY UNLOCK data.
 PASSWORD
The LSISS2520/LSISS2530 device copies the PASSWORD field to words 16:1 of the
ATA SECURITY UNLOCK data.
J.1.2.3 Erase Unit Parameter List If the SECURITY PROTOCOL SPECIFIC field is set to 0004h in the SECURITY PROTOCOL
OUT CDB, the TRANSFER LENGTH field in the CDB is set to 24h. The following table
SECURITY PROTOCOL SPECIFIC field is set to 0004h (erase unit).
Table 265: Erase Unit Parameter List
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED EN_ER
1 RESERVED MSTRPW
(MSB)
2:33 PASSWORD
(LSB)
34:35 RESERVED
 EN_ER
The LSISS2520/LSISS2530 device copies the EN_ER bit to word 0, bit 1 of the ATA
SECURITY ERASE UNIT data.
 MSTRPW
 PASSWORD
The LSISS2520/LSISS2530 device copies the password field to words 16:1 of the ATA

J.1.2.4 Disable Password If the SECURITY PROTOCOL SPECIFIC field is set to 0006h in the SECURITY PROTOCOL
Parameter List OUT CDB, the TRANSFER LENGTH field in the CDB is set to 24h. The following table
SECURITY PROTOCOL SPECIFIC field is set to 0006h (disable password).
Table 266: Disable Password Parameter List
BIT
Byte
7 6 5 4 3 2 1 0
0 RESERVED
1 RESERVED MSTRPW
(MSB)
2:33 PASSWORD
(LSB)
34:35 RESERVED
 MSTRPW
SECURITY DISABLE PASSWORD data.
 PASSWORD
The LSISS2520/LSISS2530 device copies the PASSWORD field to words 16:1 of the
ATA SECURITY DISABLE PASSWORD data.
J.1.2.5 Erase Prepare For Erase Prepare, the SECURITY PROTOCOL SPECIFIC field is set to 0003h in the
SECURITY PROTOCOL OUT CDB. Erase Prepare is issued immediately before the Erase
Unit command.
J.1.2.6 Freeze Lock The FREEZE LOCK command sets the device to Frozen mode when the SECURITY
PROTOCOL SPECIFIC field is set to 0005h. After command completion, any other
commands that update the device Lock mode are command aborted. Frozen mode is
disabled by power-off or hardware reset. If FREEZE LOCK is issued when the device is in
Frozen mode, the command executes and the device remains in Frozen mode.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix K: Revision Information | Previous Versions Revision History
Appendix K
Revision Information
This appendix lists all changes made to each version of this specification guide prior to
the current version since its original publication in December 2008.
K.1 Previous Versions The revision history table on the second page of this document lists only the changes
Revision History made to the current version of the document.
Table 267: Revision Information
Version/Date Description of Changes

Version 2.2, Updated Section 2.1, Features, on page 13.
July 2010 Updated Section 3.18, Task Management Functions, on page 35.
Added Table 108 on page 115 and Table 109 on page 116.
Updated Section 5.1.9.3, Mode Page 19 - Subpage 2, on page 164.
Updated Section 5.3.6, VPD Page 89 -SATA Information VPD Page, on
page 237.
Added Section F.1.1, FRU Code Values, on page 267.
Updated Table 259, InstIds, on page 273.
Version 2.1, Added Appendix I, T10 DIF Features.
April 2010 Added Appendix J, SAT-Specific Security Protocol Parameters.
Version/Date Added the following sections:
• Section 3.7, Sense Data, on page 22
• Section 3.16, Error Reporting Codes, on page 33
• Section 4.18, READ (32), on page 87
• Section 4.34, SEND DIAGNOSTIC, on page 109
• Section 4.46, WRITE (32), on page 124
• Section 4.55, WRITE SAME (32), on page 136
• Section 5.1.13.1, Mode Page 32 – Subpage 1, on page 180
• Section D.4, Drive Firmware Upgrade, on page 253
Updated the following sections:
• Section 4.2.3, ATA PASS THROUGH Status Return, on page 47
• Section 4.32, SECURITY IN PROTOCOL, on page 106
• Section 4.29, REQUEST SENSE, on page 101
• Section 4.37, SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16), on
page 117
• Section 5.2.11, Log Page 16h (ATA PASS-THROUGH Results Log page), on
page 214
Updated the following tables:
• Table 258, Sense Information, on page 267
• Table 259, InstIds, on page 273
Updated Appendix F, Error Lookup Table.
Description of Changes

Appendix K: Revision Information | Previous Versions Revision History LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual
Table 267: Revision Information (Continued)
Version/Date Description of Changes

Version 2.0, Added Appendix G, Long Logical Sector SATA Drive Support
February 2010 Added Appendix H, Sector Skewing Support
Added following sections:
• Section 4.6, MDIO ACCESS COMMAND, on page 61
• Section 4.7, MDIO ACCESS RESPONSE, on page 63
• Section 4.37, SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16), on
page 117
• Section 4.26, RELEASE (10), on page 97
• Section 4.27, REPORT LUNS, on page 98
• Section 4.31, RESERVE (10), on page 105
• Section 4.32, SECURITY IN PROTOCOL, on page 106
• Section 4.33, SECURITY OUT PROTOCOL, on page 108
• Section 5.1.19.3, Mode Page 39 Subpage 2, on page 192
• Section C.2, Delaying SAS Links Bring Up, on page 248
• Section 5.1.14, Mode Page 33h (Sector Skewing Support Parameter Page),
on page 181
Updated following sections:
• Section 4.19, READ BUFFER, on page 89.
• Section 4.29, REQUEST SENSE, on page 101.
• Section 4.50, WRITE BUFFER, on page 129.
• Section 5.1.13, Mode Page 32h (Firmware Parameter Control), on page 172.
• Section 5.2.19, Log Page 35h (Versions Page), on page 224.
Updated Appendix D, Firmware Upgrade.
Updated following tables:
• Table 4, Command Processing During Persistent Reservation, on page 20
• Table 5, PERSISTENT RESERVE OUT Service Actions Allowed in the Presence
of Various Reservations, on page 21
• Table 258, Sense Information, on page 267
• Table 259, InstIds, on page 273
Version 1.3 Fixed minor bugs in the document.
October 2009
Version 1.2, Made several technical changes throughout the document.
August 2009
Version 1.1, Technical changes throughout the document.
July 2009
Version 1.0, Initial release of the preliminary document.
December 2008

Alta SARM Release8

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Alta SARM Release8

Încărcat de

Drepturi de autor:

Formate disponibile

LSISS2520/LSISS2530

Version and Date Description of Changes

Corporate Headquarters Email Website

Document Number: DB15-000413-08

Chapter 2: SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Chapter 3: Command Processing and Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

LSI Corporation Confidential | October 2010 Page 3

Chapter 4: SCSI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Page 4 LSI Corporation Confidential | October 2010

4.27 REPORT LUNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

LSI Corporation Confidential | October 2010 Page 5

Chapter 5: SCSI Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Page 6 LSI Corporation Confidential | October 2010

Appendix A: System Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Appendix B: State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Appendix C: Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Appendix D: Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Appendix E: Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Appendix F: Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

LSI Corporation Confidential | October 2010 Page 7

Appendix G: Long Logical Sector SATA Drive Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Appendix H: Sector Skewing Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Appendix I: T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Appendix J: SAT-Specific Security Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Appendix K: Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Page 8 LSI Corporation Confidential | October 2010

1.1 Features The LSISS2520/LSISS2530 device has the following features:

LSI Corporation Confidential | October 2010 Page 9

1.2 Technology The LSISS2520/LSISS2530 device employs the following technologies:

Table 1: Supported Commands

Page 10 LSI Corporation Confidential | October 2010

Reset HDD Power

Figure 1: Hardware Block Diagram

LSI Corporation Confidential | October 2010 Page 11

ADC Adaptive Data Compression

1.6 References This document uses the following references.

Page 12 LSI Corporation Confidential | October 2010

2.1 Features The LSISS2520/LSISS2530 device supports the following features:

LSI Corporation Confidential | October 2010 Page 13

 NOTIFY (POWER LOSS EXPECTED)

Table 2: SSP Target Port Mode pages

For mode page description, see Section 5.1, Mode Parameters.

Page 14 LSI Corporation Confidential | October 2010

Table 3: CONTROL BYTE

NACA (Normal ACA)

LSI Corporation Confidential | October 2010 Page 15

NOTE: Although REQUEST SENSE is listed as a priority command, it requires access to

Page 16 LSI Corporation Confidential | October 2010

LSI Corporation Confidential | October 2010 Page 17

— READ CAPACITY (16)

Page 18 LSI Corporation Confidential | October 2010

LSI Corporation Confidential | October 2010 Page 19

Table 4: Command Processing During Persistent Reservation

Type of Persistent Reservation

Addressed Logical Unit Held by Another Initiator

Page 20 LSI Corporation Confidential | October 2010

Table 4: Command Processing During Persistent Reservation (Continued)

Type of Persistent Reservation

Addressed Logical Unit Held by Another Initiator

Type of Persistent Reservation

Addressed Logical Unit Held by Another Initiator

LSI Corporation Confidential | October 2010 Page 21