LSISS2520/LSISS2530 SAS-SATA Bridge

System Application Reference Manual

Version 2.3 October 2010

Revision History
Version and Date
Version 2.3, October 2010

Description of Changes
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 Milpitas, CA 800-372-2447 Document Number: DB15-000413-08 Copyright © 2010 LSI Corporation All Rights Reserved Email globalsupport@lsi.com Website www.lsi.com

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table of Contents

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50.1 Data (Mode 02h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50.2 Download Microcode and Save (Mode 05h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50.3 Download Microcode with Offsets and Save (Mode 07h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 130 130 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

LSI Corporation Confidential | October 2010

Page 5

Table of Contents

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

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

Page 6

LSI Corporation Confidential | October 2010

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 LSISS2520/LSISS2530_03: SYS_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 C. . . . . . . . . . . . . . . . . . . .4 Drive Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. .1 LSISS2520/LSISS2530_01: SYS_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . .3 Boot Option Image Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Ready LED . . . E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 List of InstIds Occurrences and ErrorIdx Class of Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 D. . . . . . . . . . . . . . . . 261 E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 D. . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . .1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . 257 Appendix E: Debug . . . . . . . . . . . . . . . . . . . . . .1 Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 LSISS2520/LSISS2530_02: SYS_RDY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Device State Machine . . . . . . . . . . . . . . . . . . . . . . . . 251 D. . . . . . . . . . . . . . . . . . . . . . . . . . . 243 B. . . . . . . . . . 247 C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 D. . . . . . . . . . . . . . . . . . . . . . . . . . . .2 State Machine Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 D. . . . . . . . . . . . . . . . . . . . . . . . . . .3 Device Spin-Up . . . . . . . . . . . . B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . .1 Device State Machine Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Logging Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Boot Loader Image Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 System State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 C. . . . . . .2. . . . . . . .1 Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . B. . . . . . . . . . . . . . . . . . . . . . . . . . . 267 F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 D. . . . . . . . . . . . . . . . . . F. . . . . .2. . . . . . . . . . . . . . . . . . . . 241 A. . . . . . . . . . . . . . . . . . . . . . . . . 248 C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. . . . . . . . . . . . . . . . . . . . . . . 249 C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 261 263 263 263 264 E. . . . . . . . . . .5 Crash Log Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . 244 B. . . . . . . . . . . . . . . . . . . . . . . . . . . F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . .1. . . . . . . . . . . . . . . . . . . . E. . . . . . . . . . . . .2 Individual Component Header Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Log Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Delaying SAS Links Bring Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table of Contents Appendix A: System Initialization . . . . . . . . . . . . . . . . . . . . . . . 265 Appendix F: Error Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 LSISS2520/LSISS2530_04: SYS_STANDBY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Log Retrieval . . . . . . . . . . . . 253 D. . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . 267 267 267 273 LSI Corporation Confidential | October 2010 Page 7 . . . . . . . . . . . . . .2 Logs Storage . . . . . . . . . . . . . . . . . . . . .2 Crash Dump format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Configuration Data . . . . . . . . . . . . . . . . 245 245 245 246 246 246 Appendix C: Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 FRU Code Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Device Replacement Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. . . . . . . . . . . . . .2 Fault LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Appendix D: Firmware Upgrade . . .1. . . . . . . . . . . . . . . . 243 B. . . . . . B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 LSISS2520/LSISS2530_05:SYS_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 B. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Sense Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Appendix B: State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 LED Behavior . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Package Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Main Package Header Description . . . . . . . . . . . . . . . . . .2 Firmware Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . 303 G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 SCSI Commands with Long Logical Sector SATA Drive . . . 311 J. . . . . . . . . . . . . . . . . . . . . 317 K. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 I. . . . . . . . 309 Appendix J: SAT-Specific Security Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Previous Versions Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Sparse Mode Non-512 Byte Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Supported T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Appendix H: Sector Skewing Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 H. 308 Appendix I: T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . 317 Page 8 LSI Corporation Confidential | October 2010 . . . . . . . . . . . . . . . . . . . . . . . . . .1 SECURITY PROTOCOL IN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Appendix K: Revision Information . . . . . . . . . . . . . . . . . 307 H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 ATA PASS THROUGH Commands with Long Logical Sector SATA Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 J. . . . . . . . . . . . . . .1 Read Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . .2 SECURITY PROTOCOL OUT Command . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Unsupported T10 DIF Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 I. . . . . .1 ATA Device Server Password Security Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 J. . . . . . . . .1 Packed Mode Non-512 Byte Mapping . . . . . . . . . . . . 307 H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Write Case . . . . . . . . . . .1. . . . . . . . . . .Table of Contents LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix G: Long Logical Sector SATA Drive Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS backplane signaling. Sector Skewing Support for a detailed description. The LSISS2520/LSISS2530 device brings dual-port Serial Attached SCSI accessibility to a SATA device. Multiple commands. See Appendix H. command translation. Support of T10 DIF (Protection Information) for User Data Sizes 512 bytes and 520 bytes for SATA devices that have 512-byte sector sizes.1 Features The LSISS2520/LSISS2530 device has the following features:     Dual independent SAS Target Interfaces that are compliant with SAS 2. and the SCSI commands. Support of Long Logical Sector SATA drive. 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. See Appendix I. configuration. and 4104 bytes block lengths on 4096 bytes sector sized SATA devices). T10 DIF Features. Single SATA host interface that is compliant with SATA 2.5. 6Gb/s Store and Forward data flow architecture. Long Logical Sector SATA Drive Support for details. supporting a maximum of 64 commands. 1.0 SSP interface protocol. Embedded ARM966 processor for initialization. See Appendix G. response generation and exception handling. Support of sector skewing (520/528 bytes block lengths on 512 bytes sector sized SATA devices.          LSI Corporation Confidential | October 2010 Page 9 .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. for full details on the supported and unsupported DIF features. Speed matching. including multiple SAS initiator support. Multiple Initiator Small Computer System Interface (SCSI) access on each path that supports four initiators per SAS port. Error status and reporting. Power and spin-up control.

PERSISTENT RESERVE OUT READ (6). SECURITY OUT PROTOCOL SEND DIAGNOSTIC TEST UNIT READY VERIFY (10). WRITE (10). WRITE (16). READ LONG (16) REASSIGN BLOCK REPORT LUNS REPORT TIMESTAMP REQUEST SENSE SECURITY IN PROTOCOL SET TIMESTAMP SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16). WRITE (32) WRITE AND VERIFY(10). WRITE SAME (32) Page 10 LSI Corporation Confidential | October 2010 . Table 1: Supported Commands SCSI Command ATA PASS THROUGH (12). MODE SENSE (10) PERSISTENT RESERVE IN. WRITE AND VERIFY (12).Chapter 1: Introduction | Technology LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 1. READ (12). WRITE (12). RELEASE (10) RESERVE (10) SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) SECURITY IN PROTOCOL. READ (10). VERIFY(16) WRITE (6). 1. WRITE SAME (16). WRITE LONG (16) WRITE SAME (10). READ CAPACITY (16) READ LONG (10).2 Technology The LSISS2520/LSISS2530 device employs the following technologies:   Implements the LSI™ 90-nm technology. READ (32) READ BUFFER READ CAPACITY (10). MDIO ACCESS RESPONSE MODE SELECT (6). as listed in the following table. Uses the ARM966E-S onboard processor. ATA PASS THROUGH (16) FORMAT UNIT INQUIRY LOG SELECT LOG SENSE MDIO ACCESS COMMAND. WRITE AND VERIFY (16) WRITE BUFFER WRITE LONG (10). MODE SELECT (10) MODE SENSE (6). VERIFY (12).3 Supported SCSI Commands The LSISS2520/LSISS2530 device supports the following SCSI commands. READ (16).

1. 5V.8V.0V Reset Circuit SAS Connector HDD Power Control Circuit SATA Connector Host 0 Device Host 1 LSISS2520/LSISS2530 25 MHz XTAL Flash Memory 3_00075-00 Figure 1: Hardware Block Diagram LSI Corporation Confidential | October 2010 Page 11 .3V.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 1: Introduction | Hardware Block Diagram 1.0V) Filter 3. 12V 12V Power Supplies (3. 1.3V 1.8V 1.4 Hardware Block Diagram The following diagram shows an example of a hardware block diagram.

ADC ASC ASCQ LBA LSB LUN MSB RSVD SAS SAT SATA SCSI SCT SSC SSP TMF VU Adaptive Data Compression Additional Sense Code Additional Sense Code Qualifier Logical Block Address Least Significant Byte Logical Unit Number Most Significant Byte Reserved Serial-Attached SCSI SCSI/ATA Translation Serial Advanced Technology Attachment Small Computer System Interface SMART Command Transport Spread Spectrum Clocking Serial SCSI Protocol Task Management Function Vendor Unique Bits 1.ATA8-ACS Serial ATA 2 Serial Attached SCSI 2 SCSI/ATA Translation . V1.5 Acronyms The following acronyms are used throughout the document.6 References This document uses the following references.4 ATA 8 Command Set .1 (April 2009) Page 12 LSI Corporation Confidential | October 2010 .2 (SAT-2) LSISS2520 SAS-SATA Bridge Reference Manual.Chapter 1: Introduction | Acronyms LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 1.          SCSI Primary Commands 4 SCSI Block Commands 3 ATA Translation 2 SCSI Architecture Model .

0 Draft Compliant — Serial SCSI Protocol (SSP) — Break Reply Capable  Dual-port operation — Full duplex operation — G1 (1. 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 .1. mode pages.SUBPAGE CODE 0x03 — — — — — — Programmable PHY capabilities CURRENT PHY CAPABILITIES ATTACHED PHY CAPABILITIES NEGOTIATED SSC NEGOTIATED PHYSICAL LINK RATE SAS-2 Port Log Page 0x18 LSI Corporation Confidential | October 2010 Page 13 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 2: SAS | Features Chapter 2 SAS This chapter describes the SAS features.5Gb/s).3.SUBPAGE CODE 0x01 SAS-2 Shared Port Control Mode Page 0x19 . 2.1 Features The LSISS2520/LSISS2530 device supports the following features:  SAS 2.9. Mode Page 19 .Subpage 2 for restrictions on this field)  SAS-2 PHY Mode Page 0x19 .SUBPAGE CODE 0x02 — POWER LOSS TIMEOUT (see Section 5. and log pages.

2.1. see Log Page 18h (Protocol-Specific Port Log page). the LSI22520/LSISS2530 device attempts to close the SSP connection as soon as possible. 2. For the description.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.3 Table 2: Mode Pages SSP Target Port Mode pages SUBPAGE Code 00h 00h 01h to DFh E0h to FEh FFh 19h 00h 01h 02h 03h 04h to DFh E0h to FEh FFh The following table describes the SAS mode pages.3 of the SAS-2 Revision 16 Specification with the following exception.4 Log Pages LSISS25x0 supports the Protocol Specific Port Log Page.5. The LSI22520/LSISS2530 device does not send BREAK if in a SSP connection after the NOTIFY (POWER LOSS EXPECTED) primitive is received. Page 14 LSI Corporation Confidential | October 2010 . Instead. see Section 5. Mode Page Code 02h 18h Description Mode Page 02h (Disconnect/Reconnect Parameters) Mode Page 18h (Protocol-Specific Logical Unit Mode Page for SAS SSP) Reserved VENDOR SPECIFIC Return all subpages for this mode page Mode Page 19h (Protocol-Specific Port Mode Page for SAS SSP) PHY Control and Discover Shared Port Control SAS-2 PHY Reserved VENDOR SPECIFIC Return all subpages for this mode page LSISS2520/LSISS2530 device Support Yes Yes N/A No Yes Yes Yes Yes Yes N/A No Yes For mode page description.2 Unsupported Features The LSISS2520/LSISS2530 device does not support the following features:        SAS 2.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. Mode Parameters.

If the LSISS2520/LSISS2530 device receives a command with the NACA bit set to 1. The location of this field varies from command to command. The LSISS2520/LSISS2530 device supports Smart Command Transfer (SCT) commands if the underlying device supports SCT. 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.     3. For details. The LSISS2520/LSISS2530 device does not support the FUA_NV (READ and WRITE type commands) bit. 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. LSI Corporation Confidential | October 2010 Page 15 .1 Table 3: Control Byte Overview CONTROL BYTE Each SCSI CDB contains a CONTROL byte.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. Bit 7 Vendor Specific 6 5 4 Reserved 3 2 NACA 1 OBSOLETE 0 NACA (Normal ACA) The LSISS2520/LSISS2530 device does not support the NACA bit when set to 1. The LSISS2520/LSISS2530 device does not support the Disable Page Out (DPO) bit for Read and Write commands. Ignore this field. The LSISS2520/LSISS2530 device does not support any XOR type commands. refer to SCSI Architecture Model-4 (SAM-4). it returns a CHECK CONDITION with the sense key set to ILLEGAL REQUEST and ASC set to INVALID FIELD IN CDB. The LSISS2520/LSISS2530 device supports the Free Unit Access (FUA) if the underlying SATA device supports the FUA bit.

the new command is added to the task queue.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. If a command is added to the task queue. wait for the response. the order of the queue is preserved. a RESERVATION CONFLICT status is returned. If one of these situations occurs when there are queued commands. the LSISS2520/LSISS2530 device treats the REQUEST SENSE command as a nonpriority command. the LSISS2520/LSISS2530 device might not be able to respond to this command immediately. If an active I/O process exists when the LSISS2520/LSISS2530 device receives a new command. If a Unit Attention exists.3 Command Processing During Execution of Active I/O Process When the LSISS2520/LSISS2530 device is not executing any I/O processes. the command is run. It must issue a SATA command. a new I/O process is then permitted to run (unless another internal target condition prevents its execution). and then transmit the SCSI response. NOTE: Although REQUEST SENSE is listed as a priority command. These commands are never queued. then the QUEUE FULL status is returned. If the LOGICAL UNIT is not ready. CHECK CONDITION status is returned. For this reason.Chapter 3: Command Processing and Error Handling | Priority Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 3. Deferred Error Condition) at the time the command is added to the task queue. then the LSISS2520/LSISS2530 device performs the following checks:      If the command is a priority command. 3.   Priority commands Commands for an invalid Logical Unit Number In these situations.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. If these checks pass. CHECK CONDITION status is returned. the queue is bypassed and the received command runs immediately. execution occurs when the command becomes an active I/O process. Page 16 LSI Corporation Confidential | October 2010 .13. Because of this dependency. This occurs if another internal target condition prevents the execution (See Section 3. The following commands are never queued. The INQUIRY command and the REPORT LUNS command run regardless of the SATA device's state. 3. If the command is not allowed to run because of a Persistent Reservation. it requires access to the SATA device. If the queue is FULL.

All queue slots are returned to the free pool on a reset. the target examines the attribute to determine how to position the new command. 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. — — — — — — — FORMAT UNIT READ (10) READ (12) READ (16) READ (6) READ BUFFER READ CAPACITY (10) LSI Corporation Confidential | October 2010 Page 17 .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. See Section 5.5 Command Processing When Underlying ATA Device not Ready If the target receives a command from an initiator when the underlying ATA device is not ready. Multiple commands of this type run Last-In First-Out (LIFO).1. See Section 5. When a command is added to the queue. Mode Page 0Ah (Control Mode Page Parameters). it selects the command at the head of the queue. Mode Page 32h (Firmware Parameter Control) for drive qualification flags.  The target has maximum of 64 slots. 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.13. It runs before any command that is subsequently received with the Ordered attribute or the Simple attribute. 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. additional sense key qualifier ASCQ_BECOMING_READY(0x1) is returned when the LSISS2520/LSISS2530 device is attempting to bring up the device during startup. 3. The relative ordering of multiple commands with the Simple attribute is determined by the queue algorithm that is in effect. the LSISS2520/LSISS2530 device's response for various commands is as follows:  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).   Head of Queue places the command so that it is the next to run.1. Commands are queued in the slots. 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. additional sense key BECOMING READY (0x4).7.

LOG SELECT. 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. SATA PASS THROUGH (16) MODE SELECT (6). and LOG SENSE might work or might not work. SATA PASS THROUGH (12). MODE SELECT (10). MODE SENSE (6). even when the SATA device is not ready.Chapter 3: Command Processing and Error Handling | Command Processing When Underlying ATA Device not Ready 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 AND VERIFY (12) WRITE AND VERIFY (16) WRITE LONG (10) WRITE LONG (16) WRITE SAME (10) WRITE SAME (16) The commands WRITE BUFFER. Page 18 LSI Corporation Confidential | October 2010 . — — — — — — — 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. if the particular Mode Select command does not require sending an ATA command to the SATA device. 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. The following mode pages do not support the Mode Select command when the device is not ready. MODE SENSE (10). based on the command options/parameters.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Command Processing When Underlying ATA Device not Ready 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 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) LSI Corporation Confidential | October 2010 Page 19 . — — — — 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.

Allowed Allowed Allowed Conflict Conflict Allowed Allowed Allowed Allowed Conflict Conflict Allowed Allowed Conflict Allowed Conflict Allowed Conflict Conflict Allowed Conflict Conflict Allowed Conflict Conflict Allowed Allowed Allowed Conflict Conflict Conflict Allowed Conflict Conflict Allowed Conflict Conflict Conflict Conflict Conflict Allowed Conflict Conflict Conflict a.6 Command Processing During Persistent Reservation Table 4: The following table describes command processing during persistent reservation. Page 20 LSI Corporation Confidential | October 2010 . Command Processing During Persistent Reservation Type of Persistent Reservation Addressed Logical Unit Held by Another Initiator Command From Any Initiator From Registered From Initiator Not Registered Initiator (Registrants Only and All Write Exclusive Exclusive Access Exclusive Access Registrants Registrants Only Registrants Only Access Types) Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Conflict Allowed Conflict Allowed Conflict Allowed Allowed Allowed Allowed Allowed Conflict Conflict Allowed Allowed Allowed Allowed Conflict Conflict Allowed Allowed Conflict Allowed Conflict Allowed Conflict Conflict Allowed Conflict Conflict Allowed Conflict Conflict Allowed Allowed Allowed Conflict Conflict Conflict Allowed Addressed Logical Unit Reserved by Another Initiatora Allowed Conflict Allowed Conflict Conflict Conflict Conflict Conflict Conflict Conflict Allowed Conflict Conflict Allowed Allowed Allowed Conflict Conflict Conflict Allowed Write Exclusive SATA PASSTHROUGH FORMAT UNIT INQUIRY LOG SELECT LOG SENSE MODE SELECT (6) MODE SELECT (10) MODE SENSE (6) MODE SENSE (7) PERSISTENT RESERVATION IN PERSISTENT RESERVATION OUT READ (6) READ (10) READ BUFFER READ CAPACITY READ LONG REASSIGN BLOCKS REPORT LUN REPORT TIMESTAMP REQUEST SENSE SECURITY PROTOCOL IN SECURITY PROTOCOL OUT SET TIMESTAMP START/STOP UNIT START = 1 or POWER CONDITION = 0 START/STOP UNIT START = 0 or POWER CONDITION <> 0 SYNCHRONIZE CACHE Allowed Conflict Allowed Conflict Allowed Conflict Allowed Allowed See Table 5.Chapter 3: Command Processing and Error Handling | Command Processing During Persistent Reservation LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 3. The reservation is not released by the RESERVED/RELEASE method.

all the persistent reservations are cleared off.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) Type of Persistent Reservation Addressed Logical Unit Held by Another Initiator Command From Any Initiator From Registered From Initiator Not Registered Initiator (Registrants Only and All Write Exclusive Exclusive Access Exclusive Access Registrants Registrants Only Registrants Only Access Types) Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed Conflict Conflict Conflict Conflict Conflict Allowed Conflict Conflict Conflict Conflict Conflict Conflict Addressed Logical Unit Reserved by Another Initiatora Conflict Conflict Conflict Conflict Conflict Conflict Conflict Write Exclusive TEST UNIT READY VERIFY (10). Allowed Allowed Allowed Allowed Allowed Conflict Alloweda Conflict Command From Unregistered Initiator Conflict Conflict Conflict Allowed Allowed Conflict Conflict Conflict Addressed Logical Unit Reserved by Another Initiator a Conflict Conflict Conflict Conflict Conflict Conflict Conflict Conflict The reservation is not released by the RESERVED/RELEASE method. the LSISS25x0 device maintains the persistent reservations (use APTPL functionality to write into the nonvolatile memory). The following table describes PERSISTENT RESERVE OUT service actions allowed in the presence of various reservations. but during firmware downgrade. NOTE: During the firmware upgrade. The reservation is not released by the RESERVED/RELEASE method. Table 5: PERSISTENT RESERVE OUT Service Actions Allowed in the Presence of Various Reservations Type of Persistent Reservation Command Service Action Addressed Logical Unit Held by Another Initiator Command From Registered Initiator CLEAR PREEMPT PREEMPT and ABORT REGISTER REGISTER and IGNORE EXISTING KEY REGISTER and MOVE RELEASE RESERVE a. (16) WRITE (6) WRITE (10) WRITE AND VERIFY WRITE BUFFER WRITE LONG WRITE SAME Allowed Allowed Conflict Conflict Conflict Conflict Conflict Allowed Conflict Conflict Conflict Conflict Conflict Conflict a. LSI Corporation Confidential | October 2010 Page 21 . (12).

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

8. on page 27. 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. and the ADDITIONAL SENSE CODE QUALIFIER field provide information relating to the error and exception conditions. To assist in debugging problems. The SENSE KEY field. This allows easier identification of the particular instance of check condition being generated from within the LSISS2520/LSISS2530 device firmware. The COMMAND SPECIFIC INFORMATION field contains information that depends on the command on which the exception condition occurred.7. The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow. See Table 259 for the numeric value for the various FRU codes. the RESPONSE CODE field is set to 72h or 73h.    LSI Corporation Confidential | October 2010 Page 23 . The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow.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 Descriptor format sense data. the ADDITIONAL SENSE CODE field. SCSI Status Byte.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. For a list of the various status codes reported by the LSISS2525/LSISS2530 device.      3. The contents of the INFORMATION field are device type or command specific. The ADDITIONAL SENSE BYTES carry the additional sense information. Table 7: Byte Descriptor Format Sense Data for REQUEST SENSE Bit 7 6 5 4 3 2 1 0 0 1 2 3 4:6 7 8 n RESERVED = 0 RESERVED = 0 RESPONSE CODE = 72h or 73h SENSE KEY ADDITIONAL SENSE CODE ADDITIONAL SENSE CODE QUALIFIER RESERVED = 0 ADDITIONAL SENSE LENGTH N-7 Sense Data Descriptor 0 Sense Data Descriptor X  The contents of the RESPONSE CODE field indicate the error type and format of the sense data. See Section 3. Sense data descriptors provide specific sense information.

on page 95. READ LONG (16). and Section 4. The ADDITIONAL LENGTH field indicates the number of sense data descriptor specific bytes that follow in the sense data descriptor.1 Information Sense Data Descriptor Table 9: Byte 7 0 1 2 3 4:11 VALID 6 5 4 3 2 1 0 DESCRIPTOR TYPE (00H) ADDITIONAL LENGTH (0AH) RESERVED = 0 RESERVED = 0 INFORMATION The information sense data descriptor provides information that is device type or command specific.2.Chapter 3: Command Processing and Error Handling | Sense Data LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual The following table shows the format of the sense data descriptor format.7. Section 4. See Section 4. Table 8: Byte 7 0 1 2:N 6 5 4 3 2 1 0 DESCRIPTOR TYPE ADDITIONAL LENGTH Sense Data Descriptor Specific Sense Data Descriptor Format Bit   The DESCRIPTOR TYPE field identifies the type of sense data descriptor. Section 4.22. WRITE LONG (10).23. WRITE LONG (16). Information Sense Data Descriptor Format Bit The contents of the INFORMATION field are command specific.52. The following descriptor types are supported by the LSISS2520/LSISS2530 device. 3. on page 133.51. READ LONG (10). Page 24 LSI Corporation Confidential | October 2010 . on page 94. on page 131.

REASSIGN BLOCK.7. Bit Byte 7 0 1 2 3 4:11 6 5 4 3 2 1 0 DESCRIPTOR TYPE (01H) ADDITIONAL LENGTH (0AH) RESERVED = 0 COMMAND-SPECIFIC INFORMATION The COMMAND-SPECIFIC INFORMATION field contains information that depends on the command on which the exception condition occurred. 3. LSI Corporation Confidential | October 2010 Page 25 .2 Command-Specific Information Sense Data Descriptor The command specific information sense data descriptor provides information that depends on the command on which the exception condition occurred.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Sense Data 3.7. Table 10: Block Commands Sense Data Descriptor Format Bit Byte 7 0 1 2 3 RESERVED = 0 ILI 6 5 4 3 2 1 0 DESCRIPTOR TYPE (05H) ADDITIONAL LENGTH (02H) RESERVED = 0 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.2.24.3 Block Commands Sense Data Descriptor The following table shows the block commands sense data descriptor format.2. on page 95. See Section 4.

Page 26 LSI Corporation Confidential | October 2010 .2.7.7.2.4 Progress Indication Sense Data Descriptor The progress-specific information sense data descriptor provides progress indication data. on page 47.3.2. Error Reporting Codes.Chapter 3: Command Processing and Error Handling | Sense Data LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 3. Table 11: Progress Indication Sense Data Descriptor Format Bit Byte 7 0 1 2 3 4 5 6:7 6 5 4 3 2 1 0 DESCRIPTOR TYPE (0AH) ADDITIONAL LENGTH (06H) SENSE KEY ADDITIONAL SENSE CODE ADDITIONAL SENSE CODE QUALIFIER RESERVED = 0 PROGRESS INDICATION The PROGRESS INDICATION field indicates a percent completion.7 Debug Sense Descriptor See Section 3.2. FRU codes are returned with both fixed and descriptor format sense data.5 ATA Return Sense Data Descriptor 3.6 Field Replaceable Unit Sense Data Descriptor See Section 4.2. Table 12: Field Replaceable Unit Sense Data Descriptor Format Bit Byte 7 0 1 2 3 6 5 4 3 2 1 0 DESCRIPTOR TYPE (03h) ADDITIONAL LENGTH (02h) RESERVED Field Replaceable Unit Code 3. on page 33.7. The field replaceable unit sense data descriptor provides information about the location in the LSISS2520/LSISS2530 firmware where a check condition occurred. See Table 259 for the numeric value for the various FRU codes.7.16. 3.1. ATA PASS THROUGH Status Return – Descriptor Format Sense Data.

18h 28h 30h 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. Table 13: Status Bytes Value 00h Meaning GOOD status Description This status indicates that the target has successfully completed the command. For this status. GOOD status INTERMEDIATE/ The LSISS2520/LSISS2530 device does not support this status. CONDITION MET status RESERVATION CONFLICT status QUEUE FULL status ACA ACTIVE status This status indicates that the LUN is reserved for a different initiator and cannot run the command received from the current initiator. or abnormal condition has caused a sense data with SKey. Sense data is not valid and the Sense Key and the ASC are set to 0. This status indicates that an error. This status indicates that the target does not have enough resources to enter the I/O process into the queue. Sense data is not valid and the Sense Key and the ASC are set to 0.1. 02h CHECK CONDITION status CONDITION MET status BUSY status 04h 08h 10h 14h INTERMEDIATE/ The LSISS2520/LSISS2530 device does not support this status. The LSISS2520/LSISS2530 device does not support this status. See Section F. Error Lookup Table for a complete list of errors returned by the LSISS25x0 device. exception. For this status. such as ABORT TASK SET or CLEAR TASK SET. ASC and ASCQ is sent out with this status. 3. The LSISS250/LSISS2530 device does not support this status. The LSISS2520/LSISS2530 device does not support this status.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | SCSI Status Byte 3.9 Priority of SCSI Status Reporting Following is the sequence in which the LSISS2520/LSISS2530 device checks the 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.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. and the Device State Machine is in the Device Down state CHECK CONDITION status when the command is received during a Format operation LSI Corporation Confidential | October 2010 Page 27 . The following table shows a description of the status represented by each Status Byte.

2. The REQUEST SENSE command returns the sense data with the Sense Key set to ILLEGAL REQUEST. When the SATA device State Machine reaches the device DOWN state (ASC/ASCQ = 0x81/0x00). Device State Machine. See Section B. When the LSISS2520/LSISS2530 device enters system-down state (ASC/ASCQ = 81/1). INQUIRY data is changed.10 Unit Attention Condition The LSISS2520/LSISS2530 device generates a unit attention condition whenever one of the following events occurs:        A Hard Reset. and returns GOOD status.    3. Disk capacity changes because of change in block descriptor by another I_T NEXUS. 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). See Section B. When the Persistent Reservation from an initiator is preempted. System State Machine. Page 28 LSI Corporation Confidential | October 2010 . Logical Unit Reset or I_T NEXUS loss occurs.1. The LSISS2520/LSISS2530 device restarts after a crash (ASC/ASCQ = 0x29/0x04). All other bytes are valid. and returns GOOD status.11 Invalid LUN Processing The target's response to an invalid LUN varies according to the command. the ASC/ASCQ set to LOGICAL UNIT NOT SUPPORTED. The INQUIRY command to an invalid LUN returns INQUIRY data indicating an unknown device type (byte 0 = 7Fh). The mode parameters and/or log parameters associated with an I_T NEXUS are changed by a command received on another I_T NEXUS. 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).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.

  Sense Information table Instance Override table The Error lookup tables are a part of Configuration data. 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.1. The Sense Key is set to ILLEGAL REQUEST and the ASC/ASCQ is set to LOGICAL UNIT NOT SUPPORTED. Using Configuration data update method. LSI Corporation Confidential | October 2010 Page 29 . See Section F. 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.2. ASC and ASCQ) that the LSISS2520/LSISS2530 firmware sends out. The LSISS2520/LSISS2530 device does not return deferred errors for the Inquiry and Report LUNS commands. the SenseKey. The ErrorIdx specifies a class of errors. 3. 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. If multiple deferred errors have accumulated for an I_T NEXUS.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.  Sense Information table The Sense Information table has the Sense Information (Sense Key. the Deferred Error is returned for one command received on each I_T NEXUS. 3.13 Deferred Error Condition The LSISS2520/LSISS2530 device generates SCSI Standard Deferred Error Condition. In all cases. 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 . 3. which is an error generated by a background operation. Sense Information for the default Sense Information table used by the LSISS2520/LSISS2530 firmware.12 Queue Full Status The target responds with QUEUE FULL status to a SCSI command when all queue slots are utilized. only the last error is returned.14 Error Lookup Table The LSISS2520/LSISS2530 device performs Error lookup when it returns a SCSI Status of Check Condition. ASC and ASCQ along with the check condition response. ASC and ASCQ.ErrorIdx. ASC and ASCQ for a given class of errors (ErrorIdx) in the Sense Information table could be overridden. Each ErrorIdx is associated with an unique combination of Sense Key. 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. The LSISS2520/LSISS2530 firmware maintains two tables to provide the Error lookup and override functionality.

Each InstId is associated with a unique ErrorIdx in the Sense information table by default. Based upon the condition.1. the table contains only this entry. the default errorIdx is overriden by the errorIdx in the table entry. By default. the first entry needs to be modified to indicate the total number of entries in the table. errorIdx errorIdx errorIdx SKey/ASC/ASCQ SKey/ASC/ASCQ SKey/ASC/ASCQ SKey/ASC/ASCQ Skey/ASC/ASCQ sent back to the initiator Figure 2: Lookup Process Page 30 LSI Corporation Confidential | October 2010 . This default association can be overridden by adding entries in the Instance Override table. See Section F. The following figure depicts the lookup process followed in the LSISS2520/LSISS2530 device firmware. 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. which belongs to the same class of errors. As the entries get added to the table.3. Each instance is identified by a unique instance Id . the default errorIdx is carried forward as it is. The first entry of the Instance Override table is a special entry that contains the number of entries present in the table. a pair of InstId and corresponding default errorIdx is generated. Instld Instld Instld Instld errorIdx errorIdx errorIdx errorIdx errorIdx Instance Override Table If No entry is found. A lookup is performed into the Instance Override table for the InstanceId of the error condition InstId LSISS2520/ LSISS2530 firmware encounters an error condition.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. Each entry of the Instance Override table has two parts: InstId and nondefault ErrorIdx (the modified ErrorIdx for a given InstId). Sense Information Table The second lookup is performed into the Sense Information table and the corresponding Skey/ASC/ ASCQ is sent back to the initiator 3_00070-00 errorIdx If the entry is found for the InstId.InstId.

LSI Corporation Confidential | October 2010 Page 31 . for example. an entry can also be added to Instance Override table. SCSI_SENSE_ILLEGAL_REQUEST ASC_INVALID_FIELD_IN_CDB ASCQ_INVALID_FIELD_IN_CDB (5/24/0) Hence. The following table lists Instance Override table entry. 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. INST_MDSNS_CHK_NONZERO_CONTROL_CC_INV_FIELD_IN_CDB).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. To override a specific instance. Table 14: Instance Override InstId INST_MDSNS_CHK_NONZERO_CONTROL_CC_INV_FIELD_IN_CDB(137) ErrorIdx 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. 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.

Table 15: Translation of SATA Errors to SCSI Errors SATA Error Status DF ERR ERR ERR ERR ERR ERR ERR ERR N/A NM UNC WP IDNF ABRT MC MCR ICRC Error Sense Key HARDWARE ERROR NOT READY MEDIUM ERROR DATA PROTECT ILLEGAL REQUEST ABORTED COMMAND UNIT ATTENTION UNIT ATTENTION ABORTED COMMAND INTERNAL TARGET FAILURE MEDIUM NOT PRESENT UNRECOVERED READ ERROR WRITE PROTECTED LOGICAL BLOCK ADDRESS OUT OF RANGE NO ADDITIONAL SENSE INFORMATION NOT READY TO READY CHANGE. If the driver needs the CC_ERROR_CODE_MEDIUM_ERR_RECORD_NOT_FOUND (0x3/0x14/0x1) error code for the SCSI read command. 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. the LSISS25x0 device generates the CC_ERROR_CODE_LBA_OUT_OF_RANGE (0x5/0x21/0x0) error code. To override a specific drive error. an entry must be added into the Instance Override table. InstId ErrorIdx INST_RD_DRV_ERR_BASE + CC_ERROR_CODE_MEDIUM_ERR_RECORD_NOT_FOUND DRV_ERR_IDNF (0x1D6) (0x6B) Page 32 LSI Corporation Confidential | October 2010 . MEDIUM MAY HAVE CHANGED OPERATOR MEDIUM REMOVAL REQUEST INFORMATION UNIT CRC ERROR DETECTED SCSI Error ASC The LSISS25x0 error lookup table provides flexibility to override the sense data generated by the LSISS25x0 device when the driver encounters the drive error.15 Error Translations The SATA device errors are translated to SCSI errors as shown in the following table.Chapter 3: Command Processing and Error Handling | Error Translations LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 3. For example. The LSISS2520/LSISS2530 device uses the SATA status register and Error register to translate the SATA status to SCSI sense key. 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. ASC and ASC qualifier. for an IDNF error from the drive. an entry must be added in the Instance Override table.

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.16 Error Reporting Codes When the LSISS25x0 device returns a nonunit attention check condition status. Table 16: Debug Sense Information Bit Byte 7 0:1 2 3:5 6 5 4 Instance Id Drive State Machine state RESERVED 3 2 1 0 If the D_SENSE bit in the control mode page is set. Table 17: Debug Sense Information Descriptor Bit Byte 7 0 1 2:7 6 5 4 3 2 1 0 Descriptor type = 0x80 Additional length = 0x6 Debug information (In the form of Table 16) LSI Corporation Confidential | October 2010 Page 33 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 3: Command Processing and Error Handling | Error Reporting Codes 3. If the D_SENSE bit is cleared. the following table depicts the debug descriptor returned by the LSISS25x0 device. 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. the debug sense information is returned in the following table format in the additional sense bytes of fixed format sense data.

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

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

Chapter 3: Command Processing and Error Handling | Command Priority Translation LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 36 LSI Corporation Confidential | October 2010 .

4. Table 21: INQUIRY CDB Bit Byte 7 0 1 2 3:4 5 6 5 4 3 2 1 0 COMMAND CODE = 12h RESERVED PAGE CODE ALLOCATION LENGTH CONTROL OBSOLETE VPD The LSISS2520/LSISS2530 device follows SPC4 for the INQUIRY command. 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. Table 22: Supported VPD PAGE CODEs VPD 0 0 1 1 0 Nonzero Supported Unsupported PAGE Code Description The LSISS2520/LSISS2530 device returns the standard INQUIRY data. 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. LSI Corporation Confidential | October 2010 Page 37 .1 INQUIRY This section describes the INQUIRY command. The INQUIRY command requests the following target parameters to be sent to the initiator. It also describes the translation of SCSI commands. 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. When the VPD bit is set to 0.  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.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. The LSISS2520/LSISS2530 device returns the vital product data of page code requested.

1 Inquiry Data The character fields are alphanumeric and are represented in ASCII. That is. 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 INQUIRY command response is generated by using the saved values. the device has never received a valid Identify Device Data from a SATA device.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. This section describes the Standard Inquiry Data Format. 4. If an INQUIRY command is received from an initiator with a pending unit attention condition (before the target reports CHECK CONDITION status). See Default Inquiry Response Data when the LSISS2520/LSISS2530 device does not have a valid saved Identify Device Data.1. Table 23: Standard Inquiry Data Format Bit Byte 7 0 1 2 3 4 5 6 7 8:15 16:31 32:35 36:43 44:55 56 57 58:59 RESERVED RESERVED VERSION Descriptor 1 : SCCS = 0 BQUE = 0 OBSOLETE ACC = 0 ENC-SERV = 0 OBSOLETE VS WBUS16 = 0 OBSOLETE OBSOLETE NormACA = 0 TPGS = 00 MULTIP = 1 SYNC = 0 RMB = 0 HiSup = 0 ADDITIONAL LENGTH = 9Fh 3PC = 0 OBSOLETE LINKED = 0 OBSOLETE OBSOLETE RESERVED OBSOLETE CMDQUE = 1 PROTECT Addr16 = 0 PORTNUM 6 PERIPHERAL QUALIFIER RESERVED VERSION RESPONSE DATA FORMAT = 2 5 4 3 2 PERIPHERAL DEVICE TYPE 1 0 T10 VENDOR IDENTIFICATION ASCII PRODUCT IDENTIFIER ASCII Product Revision Level SATA DEVICE SERIAL NUMBER RESERVED CLOCKING = 0 QAS = 0 IUS = 0 Page 38 LSI Corporation Confidential | October 2010 . the LSISS2520/LSISS2530 device has received a valid Identify Device Data from a SATA device at least once. whichever is less. The unit attention condition is not cleared by this action. The LSISS2520/LSISS2530 device transfers all available INQUIRY data or the amount specified in the allocation length field. An ALLOCATION LENGTH of 0 implies that no data is to be returned. the LSISS2520/LSISS2530 device processes the INQUIRY command.

 TPGS This field is set to 0 and Groups are not supported 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. a CHECK CONDITION is returned if an invalid LUN is specified. for all the commands.  PERIPHERAL DEVICE TYPE This field is set to 0 to indicate that the device is a direct access.  ACC This bit set to 0 indicates that the no access control coordinator is addressed through this logical unit.  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. LSI Corporation Confidential | October 2010 Page 39 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | INQUIRY Table 23: Standard Inquiry Data Format (Continued) Bit Byte 7 72:73 74:104 105 106:163 6 5 4 3 2 1 0 VERSION Descriptor 8 RESERVED DEVICE STATE MACHINE STATE RESERVED In accordance with SBC-3.  PERIPHERAL QUALIFIER This field is set to 0 to indicate that the LUN specified in the Command Block is supported.  SCCS This bit set to 1 indicates the target device is embedded storage controller array support. except INQUIRY and REQUEST SENSE. The LSISS2520/LSISS2530 device sets this bit to 0. PERIPHERAL QUALIFIER is set to 011b 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. The LSISS2520/LSISS2530 device sets this bit to 0. PERIPHERAL DEVICE TYPE is set to 1Fh when the LUN specified in the Command Block is not present. because this bit does not support embedded storage controller array support.

This field sets to ATA.  Protect When this bit is set to 0.  LINKED This bit is set to 0 to indicate that the LSISS2520/LSISS2530 device does not support linked commands. Table 24: BQUE and CMDQUE Definitions BQUE 0 1 0 1 0 0 1 1 CMDQUE Obsolete Full task management model supported Basic task management model supported Illegal combination of BQUE and CMDQUE bits Description  EncSerV (Enclosure Services) This bit is set to 1 to indicate that the Target can provide access to an Enclosure Services Device. The LSISS2520/LSISS2530 device sets this bit to 0. which executes the SCSI-3 Enclosure Services (SES) command set. the LSISS2520/LSISS2530 device supports Type 1.  BQUE and CMDQUE The LSISS2520/LSISS2530 device supports the Basic Task Management model. identifying the vendor of the product. If set to 1. the LSISS2520/LSISS2530 device does not support protection information.  WBUS16 This bit is set to 0 to indicate that the LSISS2520/LSISS2530 device does not support 16-bit wide data transfers. The LSISS2520/LSISS2530 device does not support this field. Type 2. as the following table shows. which indicates that this is SCSI/ATA translator firmware.  T10 VENDOR IDENTIFICATION This field contains eight bytes of left-aligned ASCII data. and Type 3 protection. Page 40 LSI Corporation Confidential | October 2010 .Chapter 4: SCSI Commands | INQUIRY LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  3PC Extended Copy command is not supported.  Addr16 (Wide SCSI Address 16) This bit is set to 0 to indicate that the Target does not support 16-bit wide SCSI Addresses.  MULTIP (MultiPort) This bit is set to 1 to indicate that the Target is a dual-ported device.

 VERSION DESCRIPTOR These fields provide for identifying up to eight standards to which the SCSI target device claims conformance.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | INQUIRY  PRODUCT IDENTIFICATION This field contains 16 bytes of left-aligned ASCII data. This field represents the Firmware revision field of SATA device.  PRODUCT REVISION LEVEL This field contains four bytes of left-aligned ASCII data defined by the vendor. This field represents the first 16 bytes of the Model number field of the SATA device. The Device states are defined as follows: Device State Value 1 2 3 4 5 SSD1 – SATA_DRIVE_INIT SSD2 – SATA_DRIVE_RDY SSD3 – SATA_DRIVE_RESET SSD4 – SATA_DRIVE_DOWN SSD5 – SATA_WAITING_FOR_SPINUP_REQUEST For details on Device State Machine. see Section B.1. Device State Machine. The standards supported are as follows.1 SAS 2. LSI Corporation Confidential | October 2010 Page 41 .0 SATA /ATAPI 7 SATA/ATAPI-8 ATA8-ACS SATA/ATAPI Command Set 0x0060 0x1EC0 0x0300 0x0400 0x0C00 0x0C20 0x1600 0x1623  DEVICE STATE MACHINE STATE This field returns the Device state. VERSION Descriptor Standard Name SAM-3 SAT-2 SPC3 SBC SAS 1. Refer to the SAT specifications for more information.

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. Table 25: Default Inquiry Response Data Format for Standard Inquiry Command Bit Byte 7 0 1 2 3 4 5 6 7 8:15 16:31 SCCS = 0 BQUE = 0 OBSOLETE ACC = 0 ENC-SERV = 0 OBSOLETE VS WBUS16 = 0 OBSOLETE OBSOLETE NORMACA = 0 TPGS = 00 MULTIP = 1 SYNC = 0 RMB = 0 HISUP = 0 ADDITIONAL LENGTH = 9Fh 3PC = 0 OBSOLETE LINKED = 0 RESERVED OBSOLETE OBSOLETE OBSOLETE CMDQUE = 1 PROTECT ADDR16 = 0 PORTNUM 6 PERIPHERAL QUALIFIER RESERVED VERSION RESPONSE DATA FORMAT = 2 5 4 3 2 PERIPHERAL DEVICE TYPE 1 0 T10 VENDOR IDENTIFICATION ASCII PRODUCT IDENTIFIER = 0 32:35 36:43 44:55 56 57 58:59 72:73 74:104 105 106:163 RESERVED ASCII PRODUCT REVISION LEVEL = 0 SATA DEVICE SERIAL NUMBER = 0 RESERVED CLOCKING = 0 RESERVED VERSION DESCRIPTOR 1 : VERSION DESCRIPTOR 8 RESERVED DEVICE STATE MACHINE STATE RESERVED QAS = 0 IUS = 0 For the field description.Chapter 4: SCSI Commands | INQUIRY LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. Page 42 LSI Corporation Confidential | October 2010 .1. The following table lists the default inquiry response data format for standard inquiry command.1. Inquiry Data. If the LSISS2520/LSISS2530 device detects the SATA device. Inquiry Data is returned.1. see Section 4.1.1. the inquiry response data defined in section Section 4.

1. LSI Corporation Confidential | October 2010 Page 43 . For the other field description.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. Inquiry Data. Fake inquiry data is returned only if the Offline Drive Change feature is enabled. see Section 4. The following table shows the fake inquiry response data format for standard inquiry command. Inquiry Data that is present in the nonvolatile memory) is returned until IDD is received from the drive. Stale inquiry data (that is.1. If Offline Drive Change feature is not enabled.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | INQUIRY 4.1. Table 26: Fake Inquiry Response Data Format for Standard Inquiry Command Bit Byte 7 0 1 2 3 4 5 6 7 8:15 16:31 32P:35 36:43 44:55 56 57 58:59 72:73 74:95 96:104 105 106:163 RESERVED = 0 RESERVED VERSION DESCRIPTOR 1 : VERSION DESCRIPTOR 8 RESERVED SIGNATURE = LSISS25X0 DEVICE STATE MACHINE STATE RESERVED SCCS = 0 BQUE = 0 OBSOLETE ACC = 0 ENC-SERV = 0 OBSOLETE VS WBUS16 = 0 OBSOLETE OBSOLETE NORMACA = 0 TPGS = 00 MULTIP = 1 SYNC = 0 RMB = 0 HISUP = 0 ADDITIONAL LENGTH = 9FH 3PC = 0 OBSOLETE LINKED = 0 RESERVED OBSOLETE OBSOLETE OBSOLETE CMDQUE = 1 PROTECT ADDR16 = 0 PORTNUM 6 PERIPHERAL QUALIFIER RESERVED VERSION RESPONSE DATA FORMAT = 2 5 4 3 2 PERIPHERAL DEVICE TYPE 1 0 T10 VENDOR IDENTIFICATION ASCII PRODUCT IDENTIFIER (ASCII BLANKS) ASCII PRODUCT REVISION LEVEL (ASCII BLANKS) DRIVE SERIAL NUMBER (ASCII BLANKS) RESERVED CLOCKING = 0 QAS = 0 IUS = 0  SIGNATURE The signature field when set to the LSISS2520/LSISS2530 device states that this inquiry data is Fake Inquiry data.

4.2.Chapter 4: SCSI Commands | SATA PASS THROUGH Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4.1 ATA PASS THROUGH (12) The following table lists the ATA PASS THROUGH (12) commands.2 SATA PASS THROUGH Commands SATA PASS THROUGH commands provide a method for the following scenarios:    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. Table 27: ATA PASS THROUGH (12) CDB Bit Byte 7 0 1 2 3 4 5 6 7 8 9 10 11 MULTIPLE_COUNT OFF_LINE CK_COND RESERVED FEATURES (7:0) SECTOR_COUNT (7:0) LBA_LOW (7:0) LBA_MID (7:0) LBA_HIGH (7:0) DEVICE COMMAND RESERVED CONTROL 6 5 4 3 2 1 0 OPERATION CODE (A1H) PROTOCOL T_DIR BYTE_BLOCK RESERVED T_LENGTH The Protocol field can contain one of the following values: Table 28: Protocol Field Definitions Protocol 0 1:2 3 4 5 6 7 8 9 10 11 Description SATA Hardware Reset Reserved Nondata PIO Data In PIO Data Out DMA DMA Queued Device Diagnostic Reserved UDMA Data In UDMA Data Out Page 44 LSI Corporation Confidential | October 2010 .

a WRITE MULTIPLE EXT command. 14 15 Description FPDMA Reserved SATA Return Response NOTE: LSISS25x0 does not support the value of the Protocol field when it is set to 15.      The BYTE BLOCK field specifies the type of data in the T-LENGTH field. — If the BYTE_BLOCK is set to 1. 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. a READ MULTIPLE EXT command.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SATA PASS THROUGH Commands Table 28: Protocol Field Definitions (Continued) Protocol 12 13. If the CK_COND bit is set to 0. the LSISS2520/LSISS2530 device does not implement the functionality related to this field. — T_DIR bit set to 0 – Data transfers from the LSISS2520/LSISS2530 device to device.  If the MULTIPLE_COUNT field is nonzero and the command field is not a READ MULTIPLE command. the LSISS2520/LSISS2530 device reports Check Condition status for the error responses only. a WRITE MULTIPLE command. 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. Currently. — If the BYTE_BLOCK is set to 0. the T_LENGTH refers to the number of bytes transferred to or from the SATA device. — T_DIR bit set to 1 – Data transfers from device to the LSISS2520/LSISS2530 device. the T_LENGTH specifies the number of blocks to be transferred to or from SATA device. T_DIR bit indicates the Data transfer direction. or a WRITE MULTIPLE FUA EXT command. LSI Corporation Confidential | October 2010 Page 45 . 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. This field must be set to 0.

This action results in incorrect parameter values sent during normal command execution. 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. The transfer length is an unsigned integer specified in the TPSIU (Transport Protocol-Specific Information Unit). The transfer length is an unsigned integer specified in the FEATURES (7:0) field. The following table indicates the information of the T_LENGTH field. The LSISS2520/LSISS2530 device has only one device. DEVICE bit is set to 1 or 0 depending on the device number. Not supported in the LSISS2520/LSISS2530 device.Chapter 4: SCSI Commands | SATA PASS THROUGH Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual   T_LENGTH fields specify the field that has the TRANSFER LENGTH of the data.2 ATA PASS THROUGH (16) This section lists the ATA PASS THROUGH (16) commands. You can synchronize LSISS25x0 cache only by restarting the LSISS25x0 device. The transfer length is an unsigned integer specified in the SECTOR_COUNT (7:0) field. caches some drive parameters and updates the cached drive parameter by causing discrepancy in the LSISS25x0 cache. Table 29: T_LENGTH Field Description T_LENGTH 00 01 10 11 No Data transfer occurs. Table 30: ATA PASS THROUGH (16) CDB Bit Byte 7 0 1 2 3 4 5 6 7 MULTIPLE_COUNT OFF_LINE CK_COND RESERVED T_DIR FEATURES (15:8) FEATURES (7:0) SECTOR_COUNT (15:8) SECTOR_COUNT (7:0) LBA_LOW (15:8) 6 5 4 3 2 1 0 OPERATION CODE (85h) Protocol BYTE_BLOCK Extend T_LENGTH Page 46 LSI Corporation Confidential | October 2010 . which bypass normal LSISS25x0 command handling. hence the DEVICE bit does not mean anything. Description NOTE: LSISS25x0 cache commands such as ATA Pass.2.

and the LBA_HIGH (15:8) field. 4. the LBA_LOW (15:8) field. The LSISS2520/LSISS2530 device sends a 28-bit address to the device. If the sense data is for an ATA PASS THROUGH (12) command or for the ATA PASS THROUGH (16) command with the EXTEND bit set to 0. the LSISS2520/LSISS2530 device sends a 48-bit address to the device. the LBA_MID (15:8) field. see Section 4. For descriptor format sense data.3 Return ATA PASS THROUGH Status When the CK_COND bit is set in the ATA PASS THROUGH CDB. the LSISS2520/LSISS2530 device returns the ATA registers in the sense data.2.  For the rest of the fields. LSI Corporation Confidential | October 2010 Page 47 .2. then the FEATURES (15:8) field. the LBA_MID (15:8) field. the LSISS2520/LSISS2530 device returns the 48-bit extended status and sets the EXTEND bit to 1. the LSISS2520/LSISS2530 device returns the 28-bit extended status and sets the EXTEND bit to 0.3.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SATA PASS THROUGH Commands Table 30: ATA PASS THROUGH (16) CDB (Continued) Bit Byte 7 8 9 10 11 12 13 14 15 6 5 4 LBA_LOW (7:0) LBA_MID (15:8) LBA_MID (7:0) LBA_HIGH (15:8) LBA_HIGH (7:0) DEVICE COMMAND CONTROL 3 2 1 0  If the EXTEND bit is set to 0.1. the SECTOR_COUNT (15:8) field. or when the ATA command completes with an error. 4. the ATA Status Return Descriptor is returned.2. the LBA_LOW(15:8) field. ignore the FEATURES (15:8) field. the SECTOR_COUNT (15:8) field. and the LBA_HIGH (15:8) field are valid. 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. If the sense data is for an ATA PASS-THROUGH (16) command with the EXTEND bit set to 1. If the EXTEND bit is set to 1. depending on the D_SENSE bit of Control Mode page. ATA PASS THROUGH (12).1 ATA PASS THROUGH Status Return – Descriptor Format Sense Data Each time the ATA Return descriptor is returned.

Table 32: Fixed Format Sense Data Fields for ATA PASS-THROUGH Commands Bit Byte 7 0 1 2 3 4 5 6 7 8 9 10 EXTEND SECTOR COUNT NONZERO LBA UPPER NONZERO FILE MARK = 0 EOM = 0 ILI = 0 VALID = 0 6 5 4 3 2 1 0 RESPONSE CODE = 70h or 71h OBSOLETE RESERVED INFORMATION ERROR STATUS DEVICE SECTOR COUNT (7:0) ADDITIONAL LENGTH (N – 7) COMMAND SPECIFIC INFORMATION RESERVED LBA_HIGH (7:0) LBA_MID (7:0) LOG INDEX SENSE KEY Page 48 LSI Corporation Confidential | October 2010 .2. Table 31: ATA Return Descriptor Format Bit Byte 7 0 1 2 3 4 5 6 7 8 9 10 11 12 13 6 5 4 3 2 1 0 DESCRIPTOR CODE (09h) ADDITIONAL DESCRIPTOR LENGTH (0Ch) RESERVED ERROR SECTOR_COUNT (15:8) SECTOR_COUNT (7:0) LBA_LOW (15:8) LBA_LOW (7:0) LBA_MID (15:8) LBA_MID (7:0) LBA_HIGH (15:8) LBA_HIGH (7:0) DEVICE STATUS EXTEND 4.3.Chapter 4: SCSI Commands | SATA PASS THROUGH Commands LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual The following table shows the ATA Return Descriptor format.2 ATA PASS-THROUGH Status Return – Fixed Format Sense Data The following table shows the fields returned in the fixed format sense data for the ATA PASS-THROUGH commands.

If the EXTEND bit is set to 1. the LBA_MID (15:8) field. the LBA_MID (15:8) field. and the LBA_HIGH (15:8) field cannot be returned in fixed format sense data. or for an ATA PASS-THROUGH (12) command.    LSI Corporation Confidential | October 2010 Page 49 . If the SECTOR_COUNT UPPER NONZERO bit is set to 0. the LBA_LOW (15:8) field. 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. the SECTOR_COUNT (15:8) field returned by the SATA device is not set to 00h.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SATA PASS THROUGH Commands Table 32: Fixed Format Sense Data Fields for ATA PASS-THROUGH Commands (Continued) Bit Byte 7 11 12 13 14 15 SKSV = 0 MSB SENSE KEY SPECIFIC = 0 LSB 16:17 18:N SENSE KEY SPECIFIC ADDITIONAL SENSE BYTES 6 5 4 LBA_LOW (7:0) ASC ASC QUALIFIER FIELD REPLACEABLE UNIT CODE = 0 3 2 1 0   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. one or more of the LBA_LOW (15:8) field. the LBA_LOW (15:8) field. If the LBA UPPER NONZERO bit is set to 0. and the LBA_HIGH (15:8) field returned by the SATA device are set to 00h. the SECTOR_COUNT (15:8) field. and the LBA_HIGH (15:8) field returned by the SATA device are not set to 00h. the SECTOR_COUNT (15:8) field returned by the SATA device is set to 00h. If the SECTOR_COUNT UPPER NONZERO bit is set to 1. the LBA_MID (15:8) field. If the LBA UPPER NONZERO bit is set to 1.

 CMPLST This bit set to 1 specifies that the defect list sent by the initiator is a complete list of defects. This bit set to 0 specifies that the defect list sent by the initiator is used in addition to the existing list of defects. in combination with the PROTECTION FIELD USAGE field (see Table 34). If this field is set to a nonzero value. specifies whether to use protection information. NOTE: The SPT field is set to 0x7 for the LSISS2520/LSISS2530 device. if any. contains a short parameter list header as defined in the following table. NOTE: The LSISS2520/LSISS2530 device does not support PLIST or GLIST.  FMTDATA This field set to 1 specifies that a Format Unit Parameter List (which includes defect list-DList) is supplied by the Initiator. Table 33: FORMAT UNIT CDB Bit Byte 7 0 1 2 3:4 (MSB) OBSOLETE (LSB) 5 CONTROL FMTPINFO LONGLIST = 0 6 5 4 3 2 1 0 OPERATION CODE = 04h FMTDATA CMPLST = 0 DEFECT LIST FORMAT VENDOR SPECIFIC The FORMAT UNIT command performs a physical formatting of the LSISS2520/LSISS2530 device media. then the FMTDATA field must be set to 1. Refer to the SBC-3 specification for details.Chapter 4: SCSI Commands | FORMAT UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4.  FMTPINFO (Format Protection Information) This field.  LONGLIST This bit set to 0 specifies that the parameter list. Any existing defect list except the PLIST is ignored by the LSISS2520/LSISS2530 device. Page 50 LSI Corporation Confidential | October 2010 . contains a long parameter list header. Set this field to 0 for the LSISS2520/LSISS2530 device. which includes handling of defective sectors and the overwriting of all data areas with a constant data pattern. if any. FmtData set to 0 specifies that no Parameter List is transferred. A LONGLIST bit set to 1 specifies that the parameter list.3 FORMAT UNIT This section lists the FORMAT UNIT commands.

DCRT. LSI Corporation Confidential | October 2010 Page 51 . Table 34: Short Parameter List Header Bit Byte 7 0 1 2:3 FOV = 0 (MSB) DEFECT LIST LENGTH (LSB) DPRY = 0 6 5 RESERVED DCRT = 0 STPF = 0 IP = 0 4 3 2 1 PROTECTION FIELD USAGE OBSOLETE IMMED VENDOR SPECIFIC 0  PROTECTION FIELD USAGE This field in combination with the FMTPINFO field specifies the requested protection type. and IP bits. Refer to the SBC-3 specification for details. 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. GOOD status is returned following CDB validation and the successful transfer and validation of any Dlist supplied by the initiator. and IP bits. The LSISS2520/LSISS2530 device does not support PLIST. An immediate bit set to 1 requests that status be returned immediately.  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.  DPRY This bit is ignored by the LSISS2520/LSISS2530 device. STPF. The LSISS2520/LSISS2530 device does not support CLIST. If the immediate format operation terminates in error.  IMMED (Immediate) This bit set to 0 requests that status be returned at the end of the format operation. Set the FOV bit to 1 when the IP bit is set to 1. This bit set to 0 specifies that the LSISS2520/LSISS2530 device uses its default settings for the DPRY.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | FORMAT UNIT The following table lists the Parameter List Header format. DCRT. 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. STPF. Deferred Error sense data is generated.

The initialization pattern descriptor is sent to the device server as a part of the FORMAT UNIT parameter list.Chapter 4: SCSI Commands | FORMAT UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. and the LSISS2520/LSISS2530 device encounters an error while accessing the defect list.1 Initialization Pattern Descriptor The initialization pattern descriptor specifies that the LSISS2520/LSISS2530 device initializes logical blocks to a specified pattern. Table 35: Initialization Pattern Descriptor Bit Byte 7 0 1 (MSB) 2:3 4:n Initialization Pattern Length (n-3) (LSB) Initialization Pattern IP Modifier 6 5 SI Initialization Pattern Type 4 3 2 RESERVED 1 0 Page 52 LSI Corporation Confidential | October 2010 . Set this field to 0 for the LSISS2520/LSISS2530 device. as shown in the following figure.3. — The LSISS2520/LSISS2530 device has been requested to use the PLIST. 4. The LSISS2520/LSISS2530 device does not support the STPF bit.

are in a defect list).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. If the SI field is not set to 0. the least significant four bytes are written ending with the least significant byte. LSI Corporation Confidential | October 2010 Page 53 . The LSISS2520/LSISS2530 device does not modify the initialization pattern. 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. If the LBA is more than four bytes. 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. The LSISS2520/LSISS2530 device does not support the IP Modifier field set to 01b.  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 lowest numbered logical block (or its part) that occurs within the physical block is used. The LSISS2520/LSISS2530 device does not support the IP Modifier field set to 10b. 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. as shown in the following figure. Table 36: IP Modifier Field Code 00b 01b Description No header. The LSISS2520/LSISS2530 device does not support the SI bit set to 1. including those that may have been reassigned (that is. The LBA is written with the most significant byte first. the least significant four bytes are written ending with the least significant byte. If the LBA is more than four bytes. The LSISS2520/LSISS2530 device overwrites the initialization pattern to write the LBA in the first four bytes of each logical block. The SI bit set to 1 specifies that the LSISS2520/LSISS2530 device attempts to write the initialization pattern to all areas of the medium. The LBA is written with the most significant byte first. Reserved 10b 11b If the Initialization Pattern Modifier field is not set to 0.

02h to FFh Reserved  Initialization Pattern Length The Initialization Pattern Length field specifies the number of bytes contained in the Initialization Pattern field. 4. NOTE: If the INITIALIZATION PATTERN LENGTH field is set to 0. depending upon the size of the disk.2 Sending WRITE FPDMA QUEUED Commands As part of the FORMAT UNIT operation. If the initiator sets the IMMED bit 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. 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. 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. All bytes within a logical block are written with the initialization pattern. NOTE: If the INITIALIZATION PATTERN LENGTH field is not set to 0. This entire operation takes minutes or hours.3. Table 37: Initialization Pattern Type field Code 00h Description Use a default initialization pattern. then the LSISS2520/LSISS2530 device waits for the FORMAT operation to complete and then transmits the SCSI response. 01h Repeat the pattern specified in the Initialization Pattern field as required to fill the logical block. Page 54 LSI Corporation Confidential | October 2010 . then it receives the response immediately upon the target's receipt of the command. 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. If the initiator sets the IMMED bit to 1. the LSISS2520/LSISS2530 device writes 0s or the Initialization Pattern to the entire device.Chapter 4: SCSI Commands | FORMAT UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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.

 SP (Save Parameters) This bit set to 0 indicates that the page parameters are not saved. The LSISS2520/LSISS2530 device does not support sending more than one log page through the Data-Out buffer. the LSISS2520/LSISS2530 device does not support the Initialization Pattern. If this bit is set to 1. and it uses a zero pattern implicitly.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.  PC (Page Control) This field defines the type of parameters to be selected. then the PARAMETER LIST LENGTH field must be set to 0.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). This field must be set to either 01b (cumulative values) or 11b (default cumulative values). The LOG SELECT command provides for sending 0 or more log pages through the Data-Out Buffer. 4. A value of 1 indicates that the parameters that are savable are saved after they have been changed. If this field is set to 11b. 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. NOTE: Currently. A value of 1 indicates that the parameters are cleared. LSI Corporation Confidential | October 2010 Page 55 . The equation used for time-out calculation is: Time out Value = (TRANSFER LENGTH / 32) + command time-out specified in Mode page 0x01h. and a value of 0 (except when PC = 11b) indicates that the parameters are not cleared. then the PARAMETER LIST LENGTH field must be set to 0. Table 38: LOG Select CDB Bit Byte 7 0 1 2 3:6 7:8 (MSB) PARAMETER LIST LENGTH (LSB) 9 CONTROL PC RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 4Ch RESERVED RESERVED PCR SP  PCR (PARAMETER CODE Reset) This field determines whether the Log Parameters are to be cleared and the unit attention posted for all other initiators.

The PARAMETER LIST LENGTH must not be greater than 0x500 and must not truncate any of the log data. The Sense Key is set to Illegal Request and the ASC is set to INVALID FIELD IN PARAMETER LIST. The LSISS2520/LSISS2530 device allows updates to the Start Stop Cycle (0Eh). and NV Scratch (36h) log pages only. Application Client (0Fh). Version (35h). Otherwise the LOG SELECT command is terminated with a CHECK CONDITION status. to indicate that parameters have changed. then the data is sent in an ascending order by the PARAMETER CODE value. the command is terminated with a CHECK CONDITION status. 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) Page 56 LSI Corporation Confidential | October 2010 . for all initiators except the one that issued the LOG SELECT command. The LSISS2520/LSISS2530 device generates a Unit Attention Condition.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. If the Data-Out buffer contains multiple log parameters within a log page. The Sense Key is set to Illegal Request and the ASC is set to Invalid Field in CDB. If one or more fields of the CDB are not set correctly. LSISS2520/LSISS2530 Device Temperature (33h).

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

If this field is set to 1. This condition is not considered an error. and the ASC set to INVALID FIELD in CDB. 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.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. the command terminates with CHECK CONDITION status. No bytes are transferred if the length is 0. with the sense key set to ILLEGAL REQUEST. the LSISS2520/LSISS2530 device returns the requested log page and clears the counters within the requested log page.  PARAMETER POINTER This field specifies the beginning field for the transfer. Table 40: LOG PAGE Parameters Format Bit Byte 7 0 1 2:3 (MSB) PAGE LENGTH (N-3) (LSB) — 4 x+3 — — N-y+1 N LOG PARAMETERS LOG PARAMETER (FIRST) LENGTH (X) — — — LOG PARAMETER (LAST) LENGTH (Y) — RESERVED RESERVED 6 5 4 3 PAGE CODE 2 1 0 Page 58 LSI Corporation Confidential | October 2010 . Each log page begins with a four-byte page header followed by 0 or more variable-length log parameters. then the command is terminated with CHECK CONDITION status. as listed in the following table. This field must be set to 0 if the page code is not 0Fh. 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. with SENSE KEY set to ILLEGAL REQUEST. PARAMETER POINTER is 0 for the LSISS2520/LSISS2530 device.  ALLOCATION LENGTH This field specifies the maximum number of bytes the initiator has allocated for returned LOG SENSE data. and the ASC set to INVALID FIELD IN CDB.

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

then the following counters within these Log Pages are cleared with the other counters within the Log Page specified in the LOG SENSE CDB. 32h and 37h with Read-Clear is requested.  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 Page 60 LSI Corporation Confidential | October 2010 .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 LSISS2520/LSISS2 Support 530 Device Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes No No No No No No No Yes No Yes No Yes No No Yes Page 00h 02h 03h 05h 06h 0Dh 0Eh 0Fh 10h 15h 18h 2Fh 30h 31h 32h 33h 34h 35h 36h 37h Description List of Supported Page Write Error Counter Read Error Counter Verify Error Counter Non-Medium Errors Temperature Start Stop Cycle Counters Application Client Log Self-Test Results Background Scan Results Protocol-Specific Port Informational Exceptions Device Errors SMART Data Systems Statistics LSISS2520/LSISS2530 Device Temperature LSISS2520/LSISS2530 Device Log Page Versions Page NV Scratch Page LSISS2520/LSISS2530 Device Firmware Statistics Yes If a LOG SENSE to any of the Log Pages 30h.

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 0 1 2:3 4:5 (MSB) EyeFinder Register Address (LSB) 6:9 (MSB) Write Data (LSB) RESERVED RESERVED 6 5 4 3 2 1 0 Operation Code (C0h) FW Enable Device Type Direction    Set the Direction bit to indicate a write access. LSI Corporation Confidential | October 2010 Page 61 . Set this bit for all regular MDIO Access commands. This field is only valid when the Direction bit is set. Clear the bit to indicate the SAS EyeFinder register. The Write Data field indicates what the initiator wants to write to the EyeFinder register. It is a 16-bit value that is also 4-byte-aligned.   When the LSISS2520/LSISS2530 device receives the MDIO Access command. When the initiator is done sending the MDIO Access commands. Clear the bit to indicate a read access. The FW Enable bit indicates that firmware may use the internal MDIO interface to access the EyeFinder register. it must call the appropriate MDIO interface functions accordingly. 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. which means the least significant 2 bits of the address must always be 0. Set the Device Type bit to indicate the SATA EyeFinder register must be used.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.

The host starts by sending the MDIO Access commands.6. all with FW Enable bit set. . . .1 I/O Flow The following diagram show the typical I/O flow when the MDIO Access command is used to plot eye diagrams. Figure 3: Typical I/O Flow Page 62 LSI Corporation Confidential | October 2010 . . The host/initiator shall send 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. MDIO Access Command LSISS2520/LSISS2530 SAS-SATA Bridge firmware calls the MDIO interface functions to access the EyeFinder registers. MDIO Access Reply LSISS2520/LSISS2530 SAS-SATA Bridge firmware returns the control of EyeFinder registers back to the external MDIO interface.Chapter 4: SCSI Commands | MDIO ACCESS COMMAND LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. Host Driver/ Initiator LSISS2520/LSISS2530 SAS-SATA Bridge MDIO Access Command MDIO Access Reply The host/initiator sends as many MDIO Access commands as necessary. The host EyeFinder application can access the EyeFinder registers thousands of times to establish the statistical eye. . the host sends one last MDIO Access command with the FW Enable bit cleared. . . At the end of the session. with each field filled out appropriately. .

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

The LSISS2520/LSISS2530 device performs the specified MODE SELECT operation. NOTE: If an initiator sends a MODE SELECT command that changes any parameters that apply to other initiators. The initiator pulls the changeable values and changes only those bits allowed to be changed. but uses them until the power is removed. In this case. The LSISS2520/LSISS2530 device sets the ASC to PARAMETERS CHANGED. in the pages of the MODE SENSE command. 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.Chapter 4: SCSI Commands | MODE SELECT (6) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  SP This field is Save pages. then the LSISS2520/LSISS2530 device returns a CHECK CONDITION status with the Sense Key of Illegal Request. A reset is received or an overriding MODE SELECT command is received. as shown in the following table. Page 64 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device returns. Application Note: The initiator issues a MODE SENSE command requesting all changeable values prior to issuing a MODE SELECT command. The MODE SELECT parameter list contains a four-byte header. 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. Table 46: SP Setting Descriptions Field 0 Description The LSISS2520/LSISS2530 device does not save the pages sent by the initiator. followed by 0 or more pages. and saves to a nonvolatile vendor-specific location all the savable mode pages. then a CC with ASC INVALID FIELD and PARAMETER LIST is generated. This action is necessary to find out which pages are implemented by the LSISS2520/LSISS2530 device and the length of those pages. If the length differs. See Section 5. mode select returns a CHECK CONDITION with an appropriate Sense key. If any bits change that are not changeable. the number of bytes supported for each Page. ASC and ASCQ. the LSISS2520/LSISS2530 device generates a unit attention condition for all initiators except the one that issues the MODE SELECT command. A PARAMETER LIST LENGTH of 0 transfers no data and is not considered an error. 1  PARAMETER LIST LENGTH This specifies the number of bytes to be sent from the initiator. Mode Parameters. followed by a 0 block descriptor or a 1 block descriptor.1.

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

Saved values are one of the following: • Values saved as a result of MODE SELECT command with SP set • Identical to the default values 0 1 1 1 0 1  PAGE CODE This field specifies which page or pages are to be returned. Report saved values. If any part of a field is changeable. Table 49: PCF (Page CONTROL Field) Values PCF Values 0 0 Description Report current values. all bits in that field are set to 1. The LSISS2520/LSISS2530 device returns the current values for the logical unit as presently configured for the page code specified. Table 50: PAGE CODE PAGE CODE 00h 01h 02h 07h 08h 0Ah 0Ah 0Ah 18h 19h 19h 19h 19h SUBPAGE CODE NA NA NA NA NA 00h 01h FFh 00h 00h 01h 02h 03h Description Vendor Unique Parameters (Supported mode pages) Read-Write Error Recovery mode page Disconnect/Reconnect Control Parameters mode page Verify Error Recovery mode page Caching Parameters mode page Control mode page Control Extension mode page Return main page and all the subpages of mode page 0Ah Protocol-specific LUN mode page Protocol-specific port mode page PHY control and discover mode page Shared port control mode page SAS2PHY mode page Page 66 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device returns the changeable values for the page code specified. The LSISS2520/LSISS2530 device returns the default values for the page code specified.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 page requested is returned with information that indicates which fields are changeable. The current values returned are as follows: • The parameters set in the last successful MODE SELECT command. Parameters that are not changeable are set to 0. The bits for parameters that are changeable are set to 1. The PCF values are listed in the following table. • The saved values if a MODE SELECT command has not been executed since the last poweron or TARGET RESET message. The LSISS2520/LSISS2530 device returns the saved values for the page code specified. See the following table for the page codes and their descriptions. Report changeable values. Report default values.

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

4.12 PERSISTENT RESERVE IN This section lists the PERSISTENT RESERVE IN commands. 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.10. The PERSISTENT RESERVATION IN command does not conflict with a reservation established by the PERSISTENT RESERVATION OUT command. Table 52: PERSISTENT RESERVE IN CDB Bit Byte 7 0 1 2:6 7:8 (MSB) ALLOCATION LENGTH (LSB) 9 CONTROL RESERVED RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 5Eh SERVICE ACTION The PERSISTENT RESERVE IN command obtains information about persistent reservations and reservation keys that are active within the LSISS2520/LSISS2530 device. the LSISS2520/LSISS2530 device may return parameter data with the LONGLBA bit equal to 1. This command is used in conjunction with the PERSISTENT RESERVE OUT command.  If the Long LBA Accepted (LLBAA) bit is set to 1. See Section 4. If the LLBAA bit is set to 0. MODE SENSE (6) for description of the fields in this command. Page 68 LSI Corporation Confidential | October 2010 .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 4:6 7:8 (MSB) ALLOCATION LENGTH (LSB) 9 CONTROL 6 5 4 RESERVED 3 2 1 0 The MODE SENSE (10) command lets the LSISS2520/LSISS2530 device report various device parameters to the initiator.

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

 ADDITIONAL LENGTH This field contains the count of number of bytes in the Reservation key list.3 PERSISTENT RESERVE IN PARAMETER DATA FOR READ RESERVATIONS The following table describes the PERSISTENT RESERVE IN PARAMETER DATA FOR READ RESERVATIONS command. Table 55: PERSISTENT RESERVE IN PARAMETER DATA FOR READ RESERVATIONS Bit Byte 7 0:3 (MSB) PRGENERATION (LSB) 4:7 (MSB) ADDITIONAL LENGTH (n-7) (LSB) 8:n (MSB) RESERVATION DESCRIPTORS (LSB) 6 5 4 3 2 1 0 The LSISS2520/LSISS2530 device supports this type of service action. When there is no persistent reservation held. Page 70 LSI Corporation Confidential | October 2010 .  Reservation Keys The reservation key list contains the 8-byte reservation keys for all I_T NEXUS commands that have been registered. 4. Register and Ignore Existing Key.12. The Generation counter is set to 0 as part of the power-on reset process and the hard reset process. or Preempt and Abort completes successfully. the ADDITIONAL LENGTH field is set to 0 and there are no RESERVATION DESCRIPTORS.Chapter 4: SCSI Commands | PERSISTENT RESERVE IN LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  GENERATION The Generation counter increments when a PERSISTENT RESERVATION OUT command with a service action code of Register.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE IN When a persistent reservation is held.  SCOPE The scope field is set to 0h (LU_SCOPE). the Reservation Key is set to 0. 4.12. If the Persistent reservation is of All Registrants access types (Exclusive access . Table 57: PERSISTENT RESERVE IN Parameter Data for REPORT CAPABILITIES Bit Byte 7 0:1 (MSB) LENGTH (08h) (LSB) 2 RESERVED CRH (0h) SIP_C (0h) ATP_C (0h) RESERVED PTPL_C (1h) 6 5 4 3 2 1 0 LSI Corporation Confidential | October 2010 Page 71 . 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 REPORT CAPABILITIES SERVICE ACTION The following table describes the REPORT CAPABILITIES SERVICE ACTION command.All Registrants or Write exclusive access All Registrants). see the following table for the Reservation Descriptor format. Table 56: PERSISTENT RESERVE IN READ RESERVATIONS DESCRIPTOR Bit Byte 7 0:7 (MSB) RESERVATION KEY (LSB) 8:11 (MSB) OBSOLETE (LSB) 12 13 14:15 SCOPE = 0 OBSOLETE = 0 RESERVED TYPE 6 5 4 3 2 1 0  RESERVATION KEY The reservation key field specifies the reservation key of the Persistent reservation holder.

 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.  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.  ALLOWED COMMANDS The allowed commands field indicates if certain commands are allowed through certain types of persistent reservations.  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 supports a value of 000b.  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. A TMV bit set to 0 indicates ignoring the PERSISTENT RESERVATION TYPE MASK field. The LSISS2520/LSISS2530 device supports this bit and hence sets it to 1h. Page 72 LSI Corporation Confidential | October 2010 .  Persist Through Power Loss Active (PTPL_A) This bit indicates that the device server has activated the persist through power loss feature.Chapter 4: SCSI Commands | PERSISTENT RESERVE IN LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 57: PERSISTENT RESERVE IN Parameter Data for REPORT CAPABILITIES (Continued) Bit Byte 7 3 4:5 TMV(1h) (MSB) PERSISTENT RESERVATION TYPE MASK (LSB) 6:7 RESERVED 6 5 4 3 2 RESERVED 1 0 PTPL_A (1h) ALLOWED COMMAND (000h) The LSISS2520/LSISS2530 device supports this service action. which indicates that no additional information is provided. The LSISS2520/LSISS2530 device does not support the RESERVE/RELEASE commands and hence sets the CRH bit to 0. A value of 1 indicates the feature is active. The LSISS2520/LSISS2530 device does not support this bit and hence sets it to 0h. 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. The LSISS2520/LSISS2530 device does not support this bit and hence sets it to 0h.

Table 59: READ FULL STATUS DESCRIPTOR Format Bit Byte 7 0-7 (MSB) RESERVATION KEY (LSB) 8:11 12 13 18:19 20:23 24:n Scope RELATIVE TARGET PORT IDENTIFIER ADDITIONAL DESCRIPTOR LENGTH (n-23) TRANSPORT ID RESERVED RESERVED ALL_TG_PT TYPE R_HOLDER 6 5 4 3 2 1 0 LSI Corporation Confidential | October 2010 Page 73 . The format of the full status descriptors is shown in the following table. as the following table shows.12. Table 58: PERSISTENT RESERVE IN PARAMETER DATA FOR READ FULL STATUS Bit Byte 7 0:3 (MSB) PRGENERATION (LSB) 4:7 (MSB) ADDITIONAL LENGTH (n-7) (LSB) 8 : N FIRST FULL STATUS DESCRIPTOR : LAST FULL STATUS DESCRIPTOR 6 5 4 3 2 1 0 The LSISS2520/LSISS2530 device supports this service action.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE IN  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.5 READ FULL STATUS SERVICE ACTION The READ FULL STATUS SERVICE ACTION requests that the device server return a parameter list that describes the registration and persistent reservation status of each currently registered I_T NEXUS for the logical unit.

 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. 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.  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.  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.  PROTOCOL IDENTIFIER This field specifies the SCSI transport protocol to which this transport ID applies. This value represents the SAS protocol. For the LSISS2520/LSISS2530 device.  SAS ADDRESS This field specifies the SAS address of the initiator port. Page 74 LSI Corporation Confidential | October 2010 .Chapter 4: SCSI Commands | PERSISTENT RESERVE IN LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  All Target Ports (ALL_TG_PT) All targets ports set to 0 indicates that this status descriptor represents a single I_T NEXUS. this value is 6h. The LSISS2520/LSISS2530 device sets this bit to 0. Table 60: Transport ID (Format) Bit Byte 7 0 1:3 4:11 12:23 6 5 RESERVED RESERVED SAS ADDRESS RESERVED 4 3 2 1 0 FORMAT CODE (00B) PROTOCOL IDENTIFIER (6h)  FORMAT CODE This is a reserved field and is set to 00b.

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

Otherwise. Page 76 LSI Corporation Confidential | October 2010 . If the same key is not found registered. increment the Generation counter. 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. 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. If the same key is already found registered on the same port. When a PERSISTENT RESERVATION OUT command with a Register service action completes successfully. If the ReservationKey from the PERSISTENT RESERVE OUT . the LSISS25x0 device assumes the registration key change request is for an existing registrant. the LSISS25x0 device returns a RESERVATION CONFLICT status.REGISTER parameter list (Table 65) is set to 0. The LSISS2520/LSISS2530 device can hold up to four keys at the same time. Change the existing registration key from an initiator or un-register a key from the initiator.  Reserve The PERSISTENT RESERVATION OUT command with a Reserve service action is used to establish a PERSISTENT RESERVATION from a registered initiator.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. 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. When four keys are registered. the LSISS2520/LSISS2530 device returns a RESERVATION CONFLICT status.REGISTER parameter list (Table 65) is set to nonzero value. LSISS25x0 assumes it is a new registration request and performs the registration. 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 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. If the APTL bit is set. the key update is performed or the initiator gets unregistered. If a new PERSISTENT RESERVATION conflicts with a previously established PERSISTENT RESERVATION. If the ReservationKey from the PERSISTENT RESERVE OUT . LSISS25x0 returns RESERVATION CONFLICT status else. the initiator gets registered successfully.

the LSISS2520/LSISS2530 device returns a RESERVATION CONFLICT status.  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. The Sense Key is set to Illegal Request and the Additional Sense data is set to INVALID RELEASE OF ACTIVE PERSISTENT RESERVATION. LSI Corporation Confidential | October 2010 Page 77 . UNIT ATTENTION CONDITION is reported to the initiator. This depends on the type of new reservation once established successfully.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT  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 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. the Generation counter is incremented. 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. a CHECK CONDITION status is returned. 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. The Sense Key is set to UNIT ATTENTION and the additional sense data is set to RESERVATION PREEMPTED. When an initiator is preempted. the LSISS2520/LSISS2530 device returns a RESERVATION CONFLICT status. When the key is found but the scope is different from the registered scope or the type is different from the registered type. which was preempted. 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. 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 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.  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. 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. GOOD status is returned when a key specified in Reservation key field is not found. When a PERSISTENT RESERVATION OUT command with a Preempt service action completes successfully.

a new registration is established. When a PERSISTENT RESERVATION OUT command with a CLEAR service action completes successfully. 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. The LSISS2520/LSISS2530 device can hold up to maximum four keys at the same time. increment the Generation counter. The Sense Key is set to UNIT ATTENTION and the additional sense data is set to RESERVATION PREEMPTED. If the APTL bit is set. with the exception of the initiator that has sent out the PERSISTENT RESERVE OUT command with CLEAR service action. which was preempted. The Sense Key is set to UNIT ATTENTION and the additional sense data is set to RESERVATION PREEMPTED.  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. When a PERSISTENT RESERVATION OUT command with a Register and Ignore Existing Key service action completes successfully. If a PERSISTENT RESERVE OUT with a Register and Ignore Existing Key service action is sent when an established registration key exists. the LSISS2520/LSISS2530 device ensures that the registration details are stored to non-volatile memory so that it is retrieved when the LSISS2520/LSISS2530 device comes up after a power loss. 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. 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. UNIT ATTENTION CONDITION is reported to the initiator. the Generation counter is incremented. the LSISS2520/LSISS2530 device clears all the Registrations and Reservations associated with it. When four keys are registered. A UNIT ATTENTION CONDITION is reported to the initiator. the registration supersedes with the specified SERVICE ACTION RESERVATION KEY.Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual When an initiator is preempted. If a PERSISTENT RESERVE OUT with a Register and Ignore Existing Key service action is sent when there is no established registration key. increment the Generation counter. Page 78 LSI Corporation Confidential | October 2010 . The initiator’s registrations/reservations are cleared because of the Clear service action. When a PERSISTENT RESERVATION OUT command with a Preempt and Abort service action completes successfully.  Clear The PERSISTENT RESERVATION OUT command with a Clear service action is primarily used to clear the registrations and Reservations if any wilt. When a Registered Initiator requests for a Clear service action.

creates a new registration and reservation for the initiator who issued the persistent RESERVE OUT command with Register and move service action. The command releases the original persistent reservation. the LSISS2520/LSISS2530 device ensures that the registration details are stored to non-volatile memory so that it is retrieved when the LSISS2520/LSISS2530 device comes up after a power loss.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT  Register and Move The PERSISTENT RESERVATION OUT command with a Register and move service action requires a successfully established persistent reservation. When a PERSISTENT RESERVATION OUT command with a Register and Move service action completes successfully. If the APTL bit is set.13. the LSISS2520/LSISS2530 device returns a CHECK CONDITION status. un-registers the initiator if UNREG bit is set. 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. increment the Generation counter. The Sense Key is set to Illegal Request and the Additional Sense data is set to Invalid Field in CDB. 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. If a scope code which is not supported or a reserved scope code is specified. In case of PERSISTENT RESERVATION OUT command executing a Register service action. ignore this field. Table 63: Persistent Reservation Scope Code Code 00h 03h to 0Fh LU RESERVED Name Description Persistent Reservation applies to the full logical unit Reserved LSI Corporation Confidential | October 2010 Page 79 . For REGISTER AND MOVE service action.2 SCOPE The following table describes the supported Scope Codes. 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.

PREEMPT AND ABORT.3 TYPE The following table describes the supported Type Codes. and CLEAR Service Actions The section provides two tables that show PERSISTENT RESERVE OUT parameter lists for different service actions. Table 65: PERSISTENT RESERVE OUT Parameter List Bit Byte 7 0:7 (MSB) RESERVATION KEY (LSB) 8:15 (MSB) SERVICE ACTION RESERVATION KEY (LSB) 16:19 20 21 22:23 (MSB) OBSOLETE = 0 (LSB) RESERVED OBSOLETE SPEC_I_PT RESERVED ALL_TG_PT RESERVED APTPL 6 5 4 3 2 1 0 Page 80 LSI Corporation Confidential | October 2010 .13. PREEMPT AND ABORT and CLEAR service actions. PREEMPT. RELEASE. RELEASE. Only Exclusive Access Reg. Table 64: Persistent Reservation Type Codes Code 01h 03h 05h 06h 07h 08h Rest All Name Write Exclusive Exclusive Access Write Exclusive Reg. REGISTER AND IGNORE EXISTING KEY. The SENSE KEY is set to Illegal Request and the Additional Sense data is set to INVALID Field in CDB. PREEMPT. REGISTER AND IGNORE EXISTING KEY. the LSISS2520/LSISS2530 device returns a CHECK CONDITION status. In case of PERSISTENT RESERVATION OUT command executing a Register service action.4 PERSISTENT RESERVE OUT PARAMETER LIST 4. RESERVE. RESERVE.1 REGISTER. If a type code which is not supported or a reserved type code is specified.All Reg Ex .Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4.All Reg NA Support in LSISS2520/LSISS2530 device No No No No Yes No No 4.13.13. Only Wr Ex . this field is ignored.4. The following table shows the PERSISTENT RESERVE OUT parameter list for REGISTER.

RESERVATION CONFLICT status is returned. RELEASE. Table 66: APTPL and Information Held by a LSISS2520/LSISS2530 Device Information held by a LSISS2520/LSISS2530 Device Registration Persistent Reservation Generation Counter The last valid APTPL value 0 all keys are set to 0 all are removed set to 0 retained retained set to 0 1 LSI Corporation Confidential | October 2010 Page 81 . REGISTER AND IGNORE EXISTING KEY.  ALL_TG_PT The LSISS2520/LSISS2530 device does not support this field. and PREEMPT AND ABORT and REGISTER AND MOVE. 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. If the initiator which registered a key is different from the initiator requesting PERSISTENT RESERVATION OUT command. — The REGISTER AND IGNORE EXISTING KEY service action where the RESERVATION KEY field is ignored.  SERVICE ACTION RESERVATION KEY The SERVICE ACTION RESERVATION KEY field contains information needed for the following service actions: REGISTER. Register and move service action.  APTPL The APTPL is valid only for the Register service action. — The REGISTER service action for an unregistered I_T NEXUS where the RESERVATION KEY field contains zero. The following table shows the relationship between the last valid APTPL value and information held by the LSISS2520/LSISS2530 device. PREEMPT. The LSISS2520/LSISS2530 device ignores the APTPL in other service actions. For the REGISTER service action and REGISTER AND IGNORE EXISTING KEY service action.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT  RESERVATION KEY Reservation key is verified in each service action process except when either of the following scenarios occur. and REGISTER AND IGNORE EXISTING KEY service action. The SERVICE ACTION RESERVATION KEY field is ignored for the following service actions: RESERVE. and CLEAR.

and CLEAR Service Actions. REGISTER AND IGNORE EXISTING KEY. see REGISTER. REGISTER AND IGNORE EXISTING KEY.4.23) (LSB) 24:n (MSB) TRANSPORT ID (LSB) RESERVED RESERVED UNREG APTPL 6 5 4 3 2 1 0  RESERVATION KEY For details. PREEMPT AND ABORT.  UNREG If UNREG bit is set.13. RELEASE. see REGISTER. RELEASE. RELEASE. Page 82 LSI Corporation Confidential | October 2010 .Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. PREEMPT AND ABORT. Table 67: Persistent Reserve Out Command Parameter List for Register And Move Service Action Bit Byte 7 0:7 (MSB) RESERVATION KEY (LSB) 8:15 (MSB) SERVICE ACTION RESERVATION KEY (LSB) 16 17 18:19 (MSB) RELATIVE TARGET PORT IDENTIFIER (LSB) 20:23 (MSB) TRANSPORT PARAMETER DATA LENGTH (n . and CLEAR Service Actions.  SERVICE ACTION RESERVATION KEY For details. RESERVE. PREEMPT.  APTPL For details.2 PERSISTENT RESERVE OUT Command Parameter List for Register and Move Service Action The following table shows the Persistent RESERVE OUT command parameter list for the REGISTER AND MOVE service action. RESERVE. the initiator requesting the REGISTER AND MOVE service action is unregistered upon successful establishment of new reservation. PREEMPT AND ABORT. PREEMPT. and CLEAR Service Actions. REGISTER AND IGNORE EXISTING KEY. PREEMPT. see REGISTER. RESERVE.

Table 68: Service Action and parameters and generation counter Parameters Service Action Scope Type Reservation Key (0) Register (1) Reserve (2) Release (3) Clear (4) Preempt (5) Preempt and Abort Ignore Apply Apply Ignore Apply Apply Verify Verify Verify Verify Verify Verify Ignore Verify and Release Service Action Reservation Key Save Ignore Ignore Ignore Save Save Save Generation Counter APTPL Apply Ignore Ignore Ignore Ignore Ignore Apply +1 — — +1 +1 +1 +1 +1 (6) Register and Ignore Ignore Existing Key (7)Register and Move Ignore Register and Reserve Apply LSI Corporation Confidential | October 2010 Page 83 .13.  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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | PERSISTENT RESERVE OUT  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. For details.5 SUMMARY The following table shows the Service action and parameters and generation counter. 4. see Table 60.

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

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.15 READ (10) This following table describes the READ (10) 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)).  LOGICAL BLOCK ADDRESS This field specifies the first logical block of the range of logical blocks for this command. 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. FUA FUA_NV X Description This indicates that LSISS2520/LSISS2530 device can read the requested blocks from volatile cache. 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. If the FUA_NV bit is set to 1. Table 70: READ 10 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 (MSB) TRANSFER LENGTH (LSB) 9 CONTROL RESERVED GROUP NUMBER = 0 RDPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 28h DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE The READ(10) command requests that the LSISS2520/LSISS2530 device transfer data to the initiator.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ (10) 4. 0 1 X LSI Corporation Confidential | October 2010 Page 85 . If the FUA_NV bit is set to 1. then the LSISS2520/LSISS2530 device issues a SATA verify command followed by a SATA read command. Data includes user data. then the LSISS2520/LSISS2530 device returns a CHECK CONDITION. This indicates that the LSISS2520/LSISS2530 device must read the requested blocks from the medium. then the LSISS2520/LSISS2530 device returns a CHECK CONDITION. non-volatile cache and/or the medium.

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. Any other value specifies the number of logical blocks transferred. See Section 4.15. Table 71: READ 12 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6:9 (MSB) TRANSFER LENGTH (LSB) 10 11 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 RDPROTECT 6 5 4 3 2 1 0 COMMAND CODE = A8h DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE The READ (12) command requests that the LSISS2520/LSISS2530 device transfer data to the initiator from the medium. This command also supports the variable command time-out feature described in Read(6) command handler description. it checks the protection information according to Table 44 in SBC3-r21. This command also supports the variable command time-out feature described in the Read(6) command handler description. The LSISS2520/LSISS2530 device does not support this field. For details. READ (10) for description of the fields in this command. 4. Do not collect a group number value of 0 specifies that any attributes associated with the command into any group.  TRANSFER LENGTH This field specifies the number of contiguous logical blocks of data transferred.  RDPROTECT If the LSISS2520/LSISS2530 device is formatted to use DIF.Chapter 4: SCSI Commands | READ (12) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  GROUP NUMBER This field specifies the group into which attributes associated with the command is collected.16 READ (12) This following table describes the READ (12) command. refer to SBC3 (revision 10). A TRANSFER LENGTH field set to 0 specifies that no logical blocks is transferred. Page 86 LSI Corporation Confidential | October 2010 . Data includes user data.

4. This command also supports the variable command time-out feature described in READ(6) command handler description.15. READ (10) for description of the fields in this command. Table 73: READ Command Bit Byte 7 0 1 2:5 6 7 8:9 (MSB) SERVICE ACTION (0009h) (LSB) 10 RDPROJECT DPO = 0 FUA RESERVED FUA_NV RESERVED RESERVED 6 5 4 3 2 1 0 COMMAND CODE (7Fh) CONTROL RESERVED GROUP NUMBER = 0 ADDITIONAL CDB LENGTH (18h) LSI Corporation Confidential | October 2010 Page 87 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ (16) 4. See Section 4.17 READ (16) This following table describes the READ (16) command. Table 72: READ 16 CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:13 (MSB) TRANSFER LENGTH (LSB) 14 15 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 RDPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 88h DPO = 0 FUA RESERVED FUA_NV = 0 RESERVED The READ (16) command requests that the LSISS2520/LSISS2530 device transfer data to the initiator from the medium.18 READ (32) This following table describes the READ (32) command. 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 (10) for descriptions of the other fields in this command.  LOGICAL BLOCK APPLICATION TAG MASK The LSISS2520/LSISS2530 device supports only the value of 0xFFFF for the logical block application tag mask.Chapter 4: SCSI Commands | READ (32) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 73: READ Command Bit Byte 7 11 (MSB) 12:19 (MSB) 20:23 (MSB) 24:25 (MSB) 26:27 (MSB) 28:31 TRANSFER LENGTH (LSB) LOGICAL BLOCK APPLICATION TAG MASK = 0xFFFF (LSB) EXPECTED INITIAL LOGICAL BLOCK APPLICATION TAG (LSB) EXPECTED INITIAL LOGICAL BLOCK REFERENCE TAG (LSB) LOGICAL BLOCK ADDRESS (LSB) 6 5 4 RESERVED 3 2 1 0 The READ (32) command requests that the LSISS2520/LSISS2530 device transfer data to the initiator from the medium.15. This command can also request that the transferred data is checked against the protection information fields in the CDB. Page 88 LSI Corporation Confidential | October 2010 .  EXPECTED LOGICAL BLOCK APPLICATION TAG Defined in SBC3-r21 – 5. See Section 4.12. This command also supports the variable command time-out feature described in READ(6) command handler description.12. depending on the value of the RDPROTECT field.  EXPECTED INITIAL LOGICALBLOCK REFERENCE TAG Defined in SBC3-r21 – 5.

Table 75: Valid Mode Field Values for READ BUFFER Command Mode 00h 01h 02h 03h 0Ah 0Bh 1Ah 04:09h 0C:19h 1B:1Fh Description Combined header and data Vendor Specific Data Descriptor Echo Buffer Echo Buffer Descriptor Enable expander communications protocol and Echo buffer Reserved LSISS2520/LSISS2530 Device Support No No Yes Yes No No No No No No 4. the buffer ID and buffer offset fields must be 0.19. If they are not. the LSISS25x0 device issues the ATA READ BUFFER command and transfers the retrieved data back to the initiator.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 0 1 2 3:5 (MSB) BUFFER OFFSET (LSB) 6:8 (MSB) ALLOCATION LENGTH (LSB) 9 CONTROL RESERVED BUFFER ID 6 5 4 3 2 1 COMMAND CODE = 3Ch MODE The function of this command depend on the contents of the MODE field. 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.1 Data (Mode 02h) In this mode. In this mode. the LSISS25x0 device returns the Check Condition status with the sense key set to ILLEGAL REQUEST and ASC set to INVALID FIELD IN CDB. The following table lists the various values of the MODE field supported by the LSISS25x0 device. LSI Corporation Confidential | October 2010 Page 89 .

19. the following settings result when the buffer ID field is set to 0:   OFFSET BOUNDRY: The LSISS25x0 device sets the OFFSET BOUNDRY to 0x9. the zero-filled descriptor is returned back to the initiator. Table 76: Read Buffer Descriptor Bit Byte 7 0 1:3 (MSB) BUFFER CAPACITY (LSB) 6 5 4 3 2 1 OFFSET BOUNDARY In this mode. Table 77: READ CAPACITY 10 CDB Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS = 0 (LSB) 6:7 8 9 RESERVED RESERVED CONTROL PMI = 0 6 5 4 Bit 3 2 1 0 COMMAND CODE = 25h RESERVED OBSOLETE The READ CAPACITY command returns information regarding the capacity of the device. indicating 512 bytes of buffer capacity. The READ BUFFER descriptor is defined in following table.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. indicating the offsets are at a 512-byte boundary.Chapter 4: SCSI Commands | READ CAPACITY (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. four bytes of READ BUFFER descriptor information are returned. Page 90 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device does not support PARTIAL MEDIUM INDICATOR.2 Descriptor (Mode 03h) In this mode. For all nonzero buffer IDs in this mode. 4. BUFFER CAPACITY: The LSISS25x0 device sets the buffer CAPACITY to 0x200.

If the value is FFFFFFFFh. Table 78: Format of READ CAPACITY 10 Command Reply Bit Byte 7 0:3 (MSB) RETURNED LOGICAL BLOCK ADDRESS (LSB) 4:7 (MSB) BLOCK LENGTH (LSB) 6 5 4 3 2 1 0  BLOCK LENGTH This field contains the number of bytes of user data in the logical block.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. the initiator can chose to use the READ CAPACITY (16) command to retrieve the actual block address.  RETURNED LOGICAL BLOCK This field is the LBA of the last logical block on the direct access block device or FFFFFFFFh.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 79: Byte READ CAPACITY 16 CDB Bit 7 6 5 4 3 2 1 0 0 1 2:9 (MSB) RESERVED COMMAND CODE = 9Eh SERVICE ACTION = 10h LOGICAL BLOCK ADDRESS = 0 (LSB) 10:13 (MSB) ALLOCATION LENGTH (LSB) 14 15 RESERVED CONTROL PMI=0 LSI Corporation Confidential | October 2010 Page 91 . 4.

20. The data returned to the initiator in response to the READ CAPACITY command is shown in the following table. READ CAPACITY (10). The following are the valid cases.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. The LSISS2520/LSISS2530 device does not consider this as an error. Table 80: Format of READ CAPACITY 16 Command Reply Bit Byte 7 0:3 4:7 (MSB) RETURNED LOGICAL BLOCK ADDRESS (MSB) LOGICAL BLOCK ADDRESS (LSB) 8:9 (MSB) LOGICAL BLOCK LENGTH IN BYTES (LSB) 10:11 (MSB) BLOCK LENGTH (LSB) 12 13 14:15 TPE RESERVED P_I_EXPONENT TPRZ (MSB) LOWEST ALIGNED LOGICAL BLOCK ADDRESS (LSB) 16:31 RESERVED P_TYPE PROT_EN LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT 6 5 4 3 2 1 0 Page 92 LSI Corporation Confidential | October 2010 . — LOGICAL BLOCK ADDRESS and PMI set to 0 — LOGICAL BLOCK ADDRESS and PMI not set to 0  PMI For details.  ALLOCATION LENGTH This field specifies the maximum number of bytes that the application client has allocated for returned parameter data. see Section 4.  SERVICE ACTION SERVICE ACTION = 10h indicates a READ CAPACITY (16) command  LOGICAL BLOCK ADDRESS This field is used in conjunction with the PMI field. An allocation length of zero indicates that no data is transferred.

The logical unit is formatted for type 2 protection.  TPE and TPRZ The LSISS2520/LSISS2530 device does not support these fields.  LOGICAL BLOCKS PER PHYSICAL EXPONENT When sector skewing and DIF are not enabled. Table 81: PROT_EN PROT_EN 0 1 1 1 1 P_TYPE xxxb 000b 001b 010b 011b to 111b Description The logical unit is formatted for type 0 protection. the LSISS2520/LSISS2530 device returns 0 in this field. LSI Corporation Confidential | October 2010 Page 93 . The maximum value returned in this field is 0xFFFFFFFF_FFFFFFFE. The logical unit is formatted for type 1 protection.  P_TYPE The protection type field and the protection enable (PROT_EN) bit indicate the logical unit's current type of protection. Reserved  P_I_EXPONENT The LSISS2520/LSISS2530 device does not support this field and returns zero value for the field.20.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | READ CAPACITY (16)  RETURNED LOGICAL BLOCK ADDRESS See Section 4. When sector skewing and DIF are enabled. the LSISS2520/LSISS2530 device returns ATA logical sectors per Physical sector exponent in this field. READ CAPACITY (10).  BLOCK LENGTH This field contains the number of bytes of user data in the logical block.  PROT_EN This bit set to 1 indicates that the medium was formatted with protection information 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 emulates this command using the information obtained using the SATA IDENTIFY DEVICE command. The logical unit is formatted for type 3 protection.  LOWEST ALIGNED LOGICAL BLOCK ADDRESS When sector skewing and DIF are not enabled. A PROT_EN bit set to 0 indicates that the medium was not formatted with protection information enabled. the LSISS2520/LSISS2530 device returns 0 in this field.

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

with sense key set to ILLEGAL REQUEST (0x05) and ASC set to invalid command operation code (0x20).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. READ LONG (10) for the definitions of the fields in this command. If the underlying device does not support the SCT Long Sector Access feature. Table 84: REASSIGN BLOCK CDB Bit Byte 7 0 1 2:4 5 RESERVED RESERVED CONTROL 6 5 4 3 2 1 0 COMMAND CODE = 07h LONGLBA LONGLIST REASSIGN BLOCKS defect list contains a four-byte header followed by one or more address descriptors. 4. The transferred data includes data and ECC field data. The initiator transfers a defect list that contains the LBA to be reassigned. otherwise the LSISS2520/LSISS2530 device translates this command into a SATA SCT READ LONG command to the device.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. then the LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status.22. Table 83: READ LONG 16 CDB Bit Byte 7 0 1 2:9 10:11 (MSB) RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 9Eh SERVICE ACTION (11h) LOGICAL BLOCK ADDRESS RESERVED (LSB) 12:13 (MSB) BYTE TRANSFER LENGTH (LSB) 14 15 RESERVED CONTROL PBLOCK = 0 CORRCT = 0 See Section 4. LSI Corporation Confidential | October 2010 Page 95 .

Eight times the number of LBAs. Table 86: Reassign Blocks Short Parameter List Header Bit Byte 7 0:1 2:3 (MSB) DEFECT LIST LENGTH (LSB) 6 5 4 RESERVED 3 2 1 0 If LONGLIST is set to 1.Chapter 4: SCSI Commands | REASSIGN BLOCK LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual The REASSIGN BLOCKS parameter list. then the parameter list header is defined in the following table. Table 87: Reassign Blocks Long Parameter List Header Bit Byte 7 0:3 (MSB) DEFECT LIST LENGTH (LSB) 6 5 4 3 2 1 0 The DEFECT LIST LENGTH field indicates the total length in bytes of the DEFECTIVE LBA LIST field. contains a four-byte parameter list header followed by a defective LBA list containing one or more 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. if the LONGLBA bit is set to 0. Page 96 LSI Corporation Confidential | October 2010 . Table 85: Reassign Blocks Parameter List Bit Byte 7 0:3 4:n 6 5 4 3 2 1 0 PARAMETER LIST HEADER DEFECTIVE LBA LIST (IF ANY) If LONGLIST is set to 0. if the LONGLBA bit is set to 1. 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. then the parameter list header is defined in the following table. shown in the following table. The DEFECTIVE LBA LIST field contains a list of defective LBAs.

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 . the LSISS2520/LSISS2530 device reissues the SATA verify command on the same block to make sure the LBA has been reassigned. subsequent SATA Write command is issued to the same LBA with 0x00 data. Bit 0 is equal to one. 4. The obsolete method has been replaced by the RESERVE (10) and RELEASE (10). Table 89: RELEASE 10 CDB Bit Byte 7 0 1 2 3 RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 57h 3rdPty Obsolete Third Party Device ID RESERVED LONGID Obsolete LSI Corporation Confidential | October 2010 Page 97 .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. 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. If the SATA Write command succeeds. The first LBA not reassigned is returned in the COMMAND-SPECIFIC INFORMATION field of the sense data. Table 88: RELEASE 6 CDB Bit Byte 7 0 1 2 3 4 5 VU = 0 RESERVED Obsolete RESERVED RESERVED RESERVED = 0 NACA FLAG LINK 6 5 4 3 2 1 0 COMMAND CODE = 17h Obsolete Obsolete Bits 1 through 4 of Byte 1 provide a method. This process occurs for each LBA specified in the DEFECT LIST. 4. and Byte 2 provide an obsolete way to release previously reserved extents within a logical unit. limited to device addresses 0 through 7. if the SATA verify command fails.26 RELEASE (10) The RELEASE (10) command is used to release a previously reserved logical unit. Bit 0 in Byte 1. to handle third-party reservations in earlier versions of the SCSI standard.25 RELEASE (6) The RELEASE (6) command is used to release a previously reserved logical unit.AUTO REALLOCATE FAILED. If the Write command also fails. If Byte 1. The RELEASE (6) command does not release third-party reservations. for each LBA SATA verify command is posted to device.

Chapter 4: SCSI Commands | REPORT LUNS LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 89: RELEASE 10 CDB (Continued) Bit Byte 7 4 5 6 7 8 9 VU = 0 6 5 4 RESERVED RESERVED RESERVED (MSB) Parameter List Length (LSB) Parameter List Length RESERVED = 0 NACA FLAG LINK 3 2 1 0  3rdPty must be 0. Extension is not supported. Reservation Identification field must be set to 0. If the 3rdPty bit is not 0.    4. the Check Condition status is returned with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB. The REPORT LUNS command is always available and is unaffected by any reservations. Extents must be 0. Table 90: REPORT LUNS CDB Bit Byte 7 0 1 2 3:5 6:9 (MSB) ALLOCATION LENGTH (LSB) 10 11 RESERVED CONTROL 6 5 4 3 2 1 0 COMMAND CODE = A0h RESERVED SELECT REPORT RESERVED Page 98 LSI Corporation Confidential | October 2010 .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. Third Party reservations are not supported. This command requests that the target return the known Logical Unit Numbers (LUNS) to the initiator. 3rd Party ID must be 0.

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 00h Description 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 The list contains all logical units accessible to the I_T NEXUS.

02h

ALLOCATION LENGTH 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 0:3 (MSB) LUN LIST LENGTH = 8 (LSB) 4:7 8:15 (MSB) LUN LIST = 0 (LSB) RESERVED 6 5 4 3 2 1 0

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.

LSI Corporation Confidential | October 2010

Page 99

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 0 1 2:5 6:9 10 11 RESERVED RESERVED ALLOCATION LENGTH RESERVED CONTROL 6 5 4 3 2 1 0 COMMAND CODE (A3h) SERVICE ACTION (0Fh)

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.

ALLOCATION LENGTH 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 0:1 2 3 4:9 10:11 6 5 4 3 2 1 0 TIMESTAMP PARAMETER DATA LENGTH (000Ah) RESERVED RESERVED TIMESTAMP RESERVED TIMESTAMP ORIGIN

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

Page 100

LSI Corporation Confidential | October 2010

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 0 1 2:3 4 5 6 5 4 3 2 1 0 COMMAND CODE = 03h RESERVED RESERVED ALLOCATION LENGTH CONTROL DESC = 0

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.

LSI Corporation Confidential | October 2010

Page 101

Chapter 4: SCSI Commands | REQUEST SENSE

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

ALLOCATION LENGTH 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.

Page 102

LSI Corporation Confidential | October 2010

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 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: — 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 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, 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 LSISS2520/LSISS2530 device returns a GOOD status with parameter data containing sense data with the sense key set to MEDIUM ERROR and the ASC/ASCQ set to MEDIUM FORMAT CORRUPTED.

LSI Corporation Confidential | October 2010

Page 103

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 0 1 2 3 4 5 VU = 0 6 5 4 3 2 1 0 COMMAND CODE = 16h RESERVED = 0 RESERVED = 0 (MSB) Extent List Length (LSB) Extent List Length RESERVED = 0 NACA FLAG LINK Ext = 0

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.

Page 104

LSI Corporation Confidential | October 2010

Third Party reservations are not supported. 3rd Party ID must be 0. The 3rdPty bit must be 0. LongID is ignored. This reservation can be either for the initiator sending the command or for a third party as specified by the initiator. they must be set to 0. If the 3rdPty bit is not zero. A hard Reset condition occurs.31 RESERVE (10) The RESERVE command is used to reserve a LUN for an initiator. Note the following information:   Extents are not supported in the LSISS2520/LSISS2530 device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | RESERVE (10) 4. Reservation queuing is not supported by the LSISS2520/LSISS2530 device. The reservation is released by a RELEASE command from the same initiator. a Check Condition status is returned with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB. A power off/on cycle occurs.     LSI Corporation Confidential | October 2010 Page 105 . Reservation Identification field is set to 0. Table 97: RESERVE 10 CDB Bit Byte 7 0 1 2 3 4 5 6 7 8 9 VU = 0 RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 56h 3rdPty RESERVED LONGID Obsolete Reservation Identification = 0 Third Party Device ID = 0 RESERVED RESERVED RESERVED (MSB) Parameter List Length (LSB) Parameter List Length RESERVED = 0 NACA FLAG LINK 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. A Device Reset Task Management Function is received from any initiator.

Table 99: SECURITY PROTOCOL Codes Code 00h 01h – 06h 07h 08h to 1Fh 20h 21h 22h to 3Fh 40h 41h 42h to ECh EDh EEh EFh F0h to FFh Supported by LSISS25x0 Yes Yes No No No No No No No No No No Yes No Description Security protocol information Defined by the Trusted Computing Group (TCG) 07h CbCS Reserved Tape Data Encryption SSC-3 Data Encryption Configuration ADC-3 Reserved Security Associations (SA) Creation Capabilities IKEv2-SCSI Reserved SD Card TrustedFlash specification Authentication in Host Attachments of Transient Storage Devices ATA Device Server Password Security SAT-2 Vendor-specific Page 106 LSI Corporation Confidential | October 2010 . See the following table. Table 98: Security In Protocol Bit Byte Security In Protocol 0 1 2:3 4 5 6:9 (MSB) ALLOCATION LENGTH (LSB) 10 11 RESERVED CONTROL INC_512 OPERATION CODE (A2h) SECURITY PROTOCOL SECURITY PROTOCOL SPECIFIC RESERVED RESERVED  SECURITY PROTOCOL This field specifies the protocol used.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.

the SENSE KEY is set to ILLEGAL REQUEST. 2 means 1024 bytes). If the INC_512 bit is set to 1 and the ALLOCATION LENGTH field is greater than FFFFh. LSI Corporation Confidential | October 2010 Page 107 .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. An ALLOCATION LENGTH of 0 is not supported: the LSISS2520/LSISS2530 device returns a CHECK CONDITION status. the ATA Transfer_Length field is set to ALLOCATION LENGTH (15:0). Pad bytes can be appended to meet this length. and the Additional Sense data is set to INVALID FIELD IN CDB. If the INC_512 bit is set to 0 and if the ALLOCATION LENGTH field is greater than 1FF_FE00h. An INC_512 bit set to 0 specifies that the ALLOCATION LENGTH field expresses the number of bytes to be transferred. Pad bytes have a value of 00h. 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 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.  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. After successful completion of the ATA TRUSTED RECEIVE or ATA TRUSTED RECEIVE DMA command. Otherwise. After 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. the data is transferred to the SCSI application client. 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. a value of 1 means 512 bytes.  ALLOCATION LENGTH This field specifies the number of bytes that the initiator allocates for the Security In Protocol data to be returned.

33 SECURITY OUT PROTOCOL This section describes the Security Out Protocol command. The ATA TRUSTED SEND or ATA TRUSTED SEND DMA command transfer the padded data for ATA Transfer_Length number of data blocks. If the INC_512 is set to 1 and TRANSFER LENGTH is greater than FFFFh. 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 SENSE KEY is set to ILLEGAL REQUEST and the Additional Sense data is set to INVALID FIELD IN CDB. SECURITY IN PROTOCOL for descriptions of the fields in this command. The LSISS2520/LSISS2530 device does not support an INC_512 bit setting of 0. Otherwise. If the INC_512 bit is set to 0 and TRANSFER LENGTH is greater than 1FF_FE00h. Otherwise. 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. See Section 4.32. A TRANSFER LENGTH of 0 is not supported and the LSISS2520/LSISS2530 device returns a CHECK CONDITION status. Table 100: Security Out Protocol Bit Byte Security Out Protocol 0 1 2:3 4 5 6:9 (MSB) TRANSFER LENGTH (LSB) 10 11 RESERVED CONTROL INC_512 OPERATION CODE (B5h) SECURTITY PROTOCOL SECURTITY PROTOCOL SPECIFIC RESERVED RESERVED  TRANSFER LENGTH This field specifies the number of blocks to be transferred for Security Out Protocol. Page 108 LSI Corporation Confidential | October 2010 .Chapter 4: SCSI Commands | SECURITY OUT PROTOCOL LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. 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. The ATA TRUSTED SEND or ATA TRUSTED SEND DMA command transfer the data. the ATA Transfer_Length field is set to ALLOCATION LENGTH (15:0).

This bit must be set to 1 if the Self-Test bit is set to 0. This value is only valid if a previous SEND DIAGNOSTIC command specified a background self-test function and that function has not completed.34 SEND DIAGNOSTIC The SEND DIAGNOSTIC command requests the LSISS2520/LSISS2530 device to perform the diagnostic operation on the target device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SEND DIAGNOSTIC 4. The target starts its short self-test routine in the foreground mode. 101b 110b 111b Foreground Short self-test Foreground Extended self-test The target starts its extended self-test routine in the foreground mode. The target starts its short self-test routine in the background mode. or if the Self-Test bit is set to 0 and the PF bit is set to 1. the device server starts the diagnostic operation specified by SELF-TEST CODE field or in parameter list.   LSI Corporation Confidential | October 2010 Page 109 . 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. The LSISS2520/LSISS2530 device does not support Self-Test set to 1. 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. Table 101: SEND DIAGNOSTIC CDB Bit Byte 7 0 1 2 3 4 5 Self test Code 6 5 4 3 2 1 0 OPERATION CODE = 1Dh PF RSVD = 0 Self-Test DEVOFF LEN UNITOFF LEN RESERVED = 0 (MSB) Parameter List Length (LSB) Parameter List Length CONTROL Table 102: Self-Test Codes Value 000b NA Function Name Specific This value is used when the Self-Test bit is set to 1. If the bit is set to 0. The Self-Test bit set to 1 indicates the device performs its logical unit default self test. The DEVOFFLEN bit is ignored by the target for compatibility. NA Abort Background self-test Reserved Abort the current self-test in the background mode. logical unit or both. This bit is ignored by the Target if the Self-Test bit is set. 001b 010b 011b 100b Background Short self-test Background Extended self-test The target starts its extended self-test in the background mode.

then the SET 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 Page 110 LSI Corporation Confidential | October 2010 . 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. Self-test Code.   4. Table 103: SET TIMESTAMP CDB Bit Byte 7 0 1 2:5 6:9 10 11 RESERVED RESERVED PARAMETER LIST LENGTH RESERVED CONTROL 6 5 4 3 2 1 0 COMMAND CODE (A4h) SERVICE ACTION (0Fh) The SET TIMESTAMP command requests the LSISS2520/LSISS2530 device to initialize the timestamp to a value specified in SET TIMESTAMP parameter data. If this field is not set to a value equal to length of the SET TIMESTAMP Parameter Data or 0. A PARAMETER LIST LENGTH of 0 transfers no data and no change is made to the timestamp value. The Parameter List Length must be 0 when the Self-Test bit is 1.  PARAMETER LIST LENGTH This field specifies the number of bytes to be sent from the initiator. See Table 102. the SET 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. Otherwise. it is set to the length of the page to be transferred.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.35 SET TIMESTAMP The following section describes the SET TIMESTAMP command.  SERVICE ACTION This field set to 0Fh indicates that it is the SET TIMESTAMP command. If this field is not set to 0Fh. 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.

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

If it is set to 1. Place the LSISS2520/LSISS2530 device into the active power condition. then the logical unit unloads the medium if the START bit is set to 0. with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CDB. Also. with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CBD. Place the LSISS2520/LSISS2530 device into the standby power condition. this field must be set to 0.  POWER CONDITION MODIFIER This field is supported only if the Power Condition value is set to IDLE. 1. Page 112 LSI Corporation Confidential | October 2010 . Otherwise the LSISS2520/LSISS2530 device terminates the Start Stop Unit commands with the CHECK CONDITION status. Place the LSISS2520/LSISS2530 device into the standby power condition. then the logical unit takes no action regarding loading or ejecting the medium. and 2. if not then the LSISS2520/LSISS2530 device ignores the values of these bits. the LSISS2520/LSISS2530 device terminates the Start Stop Unit commands with the CHECK CONDITION status. the LSISS2520/LSISS2530 device terminates the Start Stop Unit – FORCE_STANDBY_0 commands with the CHECK CONDITION status. For other Power Condition values. If the underlying device does not support the Removable Media Feature set. Setting the START bit to 0 stops the spindle and causes the LU to transition to Stopped power condition state. Table 106: Power Condition Values Code 00h 01h 02h 03h 0Bh Name START_VALID ACTIVE IDLE STANDBY FORCE_STANDBY_0 Description The START and LOEJ bits are valid. while in the Stopped/Active_Wait power condition state. with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CDB. Place the LSISS2520/LSISS2530 device into the idle power condition. with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD IN CBD. For all other Power Condition values. The LSISS2520/LSISS2530 device does not support the LOEJ and START bit set to 1 and terminates the command with CHECK CONDITION status. Setting the START bit to 1 starts the spindle and causes the LU to transition to the Active/Active_Wait power condition state. then the LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status.  LOEJ (load Eject) If this bit is set to 0. with the SENSE KEY set to ILLEGAL REQUEST and the ASC/ASCQ set to INVALID FIELD in CDB.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. The supported values are 0.

with the START bit set to 1. and the particular Start Stop Unit command changes the LU power condition state to Idle/Standby respectively. with the START bit set to 0.   The following table lists the possible power condition states within the LSISS2520/LSISS2530 device. with the Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. LSI Corporation Confidential | October 2010 Page 113 . 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. 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. Table 107: Possible Power Condition States Power Active Command Processing Capable of processing all the supported commands Next Possible Power Condition State Any supported power 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. with the NO_FLUSH bit set to 0. NOTIFY (ENABLE SPINUP) REQUIRED. all the media access type commands and the TEST UNIT READY command terminated with CHECK CONDITION status.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | START STOP UNIT When the Immediate bit is set to 0 and one of the following is true. and the particular Start Stop Unit command changes the LU power condition state to Active. command processing while in particular power condition state. INITIALIZING COMMAND REQUIRED. Power Condition value set to IDLE/STANDBY/FORCE_STANDBY_0. and next possible power condition states from the particular 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. Power Condition value set to START_VALID. and the particular Start Stop Unit command changes the LU power condition state to Stopped.

Any supported power condition state except Active_Wait Next Possible Power Condition State Any supported power condition state 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. and a START STOP UNIT command with the power condition field set to ACTIVE/START_VALID (START = 1) is processed. the LSISS2520/LSISS2530 device transitions to the Active power condition state before processing the command. When a media access type SCSI command is received. 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. Page 114 LSI Corporation Confidential | October 2010 . Idle Capable of processing all the supported commands. NOTE: If transition to the Active_Wait power condition state is enabled. the LSISS2520/LSISS2530 device transitions to the Active power condition state before processing the command. NOTE: When a media access type SCSI command is received. NOTIFY (ENABLE SPINUP) REQUIRED.Chapter 4: SCSI Commands | START STOP UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 107: Possible Power Condition States (Continued) Power Standby Command Processing Capable of processing all the supported commands (assuming the transition to the Active_Wait power condition state is disabled. 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. with the Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY.

1 Processing of Start Stop Unit Command When DSM is in SATA_WAITING_FOR_SPINUP_REQUEST State Table 108 and Table 109 shows the details for processing of Start Stop Unit command when the Device State Machine is in SATA_WAITING_FOR_SPINUP_REQUEST state. Mode Page 32h (Firmware Parameter Control) and Section B.DRIVEPOWER/DRIVEPHY ENABLE ACTIVE WAIT Within Firmware Parameter Control Mode Page (32h) Enabled/Disabled NA NA Enabled Disabled Current LU Power Condition State ACTIVE_WAIT Start Stop Unit Command Power Condition START_VALID: START = 1 START_VALID: START = 0 ACTIVE Start Stop Unit Command Processing Status Good Status Good Status Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Resultant LU Power Condition State ACTIVE STOPPED ACTIVE_WAIT ACTIVE_WAIT STANDBY/FORCE_STANDBY_0/ NA IDLE/LU_CONTROL ACTIVE_WAIT STOPPED START_VALID: START = 1 START_VALID: START = 0 ACTIVE NA NA NA ACTIVE STOPPED STOPPED STANDBY/FORCE_STANDBY_0/ NA IDLE/LU_CONTROL STOPPED LSI Corporation Confidential | October 2010 Page 115 . NOTIFY (ENABLE SPINUP) REQUIRED Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Good Status Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY.1.36. see Section 5. Device State Machine.1. For more information.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | START STOP UNIT 4. Table 108: DEVICE SPINUP ALGORITHM Set to SPINUP ON STARTSTOP .13.

NOTIFY (ENABLE SPINUP) REQUIRED Good Status Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY.DRIVEPOWER/DRIVEPHY ENABLE ACTIVE WAIT Within Firmware Parameter Control Mode Page (32h) Enabled/Disabled Enabled Disabled Current LU Power Condition State ACTIVE_WAIT Start Stop Unit Command Power Condition START_VALID: START = 1 Start Stop Unit Command Processing Status Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Resultant LU Power Condition State ACTIVE_WAIT ACTIVE_WAIT START_VALID: START = 0 ACTIVE NA Enabled Disabled STOPPED ACTIVE_WAIT ACTIVE_WAIT STANDBY/FORCE_STANDBY_0/ NA IDLE/LU_CONTROL ACTIVE_WAIT STOPPED START_VALID: START = 1 Enabled Disabled ACTIVE_WAIT STOPPED START_VALID: START = 0 ACTIVE NA Enabled Disabled STOPPED ACTIVE_WAIT STOPPED STANDBY/FORCE_STANDBY_0/ NA IDLE/LU_CONTROL STOPPED Page 116 LSI Corporation Confidential | October 2010 . NOTIFY (ENABLE SPINUP) REQUIRED Good Status Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY.Chapter 4: SCSI Commands | START STOP UNIT LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 109: DEVICE SPINUP ALGORITHM Set to SPINUP ON NOTIFY PRIMITIVE . NOTIFY (ENABLE SPINUP) REQUIRED Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY. NOTIFY (ENABLE SPINUP) REQUIRED Good Status Check Condition status with Sense Key set to NOT READY and ASC/ASCQ set to LOGICAL UNIT NOT READY.

Table 110: SYNCHRONIZE CACHE (10) CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 (MSB) NUMBER OF BLOCKS (LSB) 9 CONTROL RESERVED GROUP NUMBER = 0 RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 35h SYNC_NV = 0 IMMED = 0 OBSOLETE Table 111: SYNCHRONIZE CACHE (16) CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:13 (MSB) NUMBER OF BLOCKS (LSB) 14 15 RESERVED GROUP NUMBER = 0 CONTROL RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 91h SYNC_NV = 0 IMMED = 0 RESERVED  LOGICAL BLOCK ADDRESS This field specifies where the operation is to begin. LSI Corporation Confidential | October 2010 Page 117 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) 4.  NUMBER OF BLOCKS This field specifies the total number of contiguous logical blocks within the range. 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.37 SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) The SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16) commands ensure that logical blocks in the cache have their most recent data value recorded on the media.

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. the LSISS2520/LSISS2530 device returns a CHECK CONDITION status. An IMMED bit set to 1 causes the LSISS2520/LSISS2530 device to return a GOOD status as soon as the CDB is validated. 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 0 2:4 5 6 5 4 3 2 1 0 COMMAND CODE = 00h RESERVED CONTROL The LSISS2520/LSISS2530 device maintains the current state of the SATA device in its device state machine. The SENSE KEY is set to ILLEGAL REQUEST and the ASC is set to INVALID FIELD in CDB. If the SYNC_NV bit is set to 1. The SYNC_NV bit must be 0. 4.38 TEST UNIT READY The TEST UNIT READY command provides a mechanism to check the state of a Logical Unit. construct and return a SCSI response to the SAS initiators. Page 118 LSI Corporation Confidential | October 2010 . Alternatively.  GROUP NUMBER The LSISS2520/LSISS2530 device does not support this field. A SYNC_NV bit set to 0 indicates that the SCSI target device synchronizes volatile and nonvolatile caches to the medium. the LSISS2520/LSISS2530 device uses SATA CHECK POWER MODE (SATA) command to check the status of the serial SATA device when required.  SYNC_NV This bit specifies whether the SCSI target device is required to synchronize volatile and nonvolatile caches. Based on the current state of the SATA device.

The LSISS2520/LSISS2530 device does not support DPO bit set to 1 condition. The LSISS2520/LSISS2530 device supports Byte Chk bit set 0 conditions only.  DPO (Disable Page Out) 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)).  GROUP NUMBER The LSISS2520/LSISS2530 device does not support Grouping.39 VERIFY (10) The VERIFY command requests that the LSISS2520/LSISS2530 device verify the data written on the media. It is implemented per SBC3r21.  LOGICAL BLOCK ADDRESS This field specifies the logical block at which the VERIFY operation begins. Table 113: VERIFY 10 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 RESTRICTED FOR MMC-4 (MSB) VERIFICATION LENGTH (LSB) RESERVED GROUP NUMBER = 0 VRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 2Fh DPO = 0 RESERVED BYTCHK = 0 OBSOLETE 9 CONTROL  VRPROTECT This field specifies the protection information to be verified. Data includes user data. LSI Corporation Confidential | October 2010 Page 119 . 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. If an error is detected in the verify process.  BYTCHK This bit set to 0 indicates that the data is verified using SATA Verify command.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | VERIFY (10) 4. if any. CHECK CONDITION status is returned with Sense Key set to MEDIUM ERROR.

4.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. Table 115: VERIFY 16 CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) VRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 8Fh DPO = 0 RESERVED BYTCHK = 0 RESERVED Page 120 LSI Corporation Confidential | October 2010 . Table 114: VERIFY 12 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6:9 (MSB) VERIFICATION LENGTH (LSB) 10 11 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 VRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = AFh DPO = 0 RESERVED BYTCHK = 0 OBSOLETE See Section 4. 4. A verification length of 0 indicates that no logical blocks are verified.39. This condition is not considered as an error.41 VERIFY(16) This section lists the VERIFY (16) commands. VERIFY (10) for the description of fields in this command. 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. If the LOGICAL BLOCK ADDRESS plus the verification exceeds the capacity of the medium.40 VERIFY (12) This section lists the VERIFY (12) commands.

 TRANSFER LENGTH This field specifies the number of blocks to be transferred. LSI Corporation Confidential | October 2010 Page 121 . If the LOGICAL BLOCK ADDRESS plus the TRANSFER LENGTH exceeds the capacity of the medium. VERIFY (10) for the description of fields in this command.42 WRITE (6) The WRITE(6) command requests that the Logical Unit transfer the specified blocks from the Data-Out buffer and write them. 4. 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. logical block reference. Any other value specifies the number of logical blocks transferred. Each logical block transferred includes user data but does not include protection information.39. the DIF fields (logical block guard.28. and logical block application tag) are generated according to SBC3-r21. A TRANSFER LENGTH field set to 0 specifies that 256 logical blocks are written. Section 5. Any other value specifies the number of logical blocks to be written. Table 116: WRITE 6 CDB Bit Byte 7 0 1 2:3 (MSB) LOGICAL BLOCK ADDRESS (LSB) 4 5 TRANSFER LENGTH CONTROL RESERVED 6 5 4 3 2 1 0 COMMAND CODE = 0Ah LBA  LOGICAL BLOCK ADDRESS This field specifies the logical block at which the WRITE operation begins.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE (6) Table 115: VERIFY 16 CDB (Continued) Bit Byte 7 10:13 (MSB) VERIFICATION LENGTH (LSB) 14 15 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 6 5 4 3 2 1 0 See Section 4. If the LSISS2520/LSISS2530 device has been formatted to use protection information.

it follows Table 85 in SBC3-r21 to verify the DIF fields in the incoming data. The LSISS2520/LSISS2530 device does not support this bit.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. Table 118: FUA and FUA_NV Descriptions FUA 0 1 X X FUA_NV Description This indicates that the target can return GOOD status prior to writing the data to volatile cache. nonvolatile cache and/or the medium This indicates that the target must write the data to the media before returning GOOD status. 4. If the FUA_NV bit is set to 1. 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. Page 122 LSI Corporation Confidential | October 2010 . If the LSISS2520/LSISS2530 device is configured such that NCQ is disabled. Table 117: WRITE 10 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 9 RESERVED TRANSFER LENGTH CONTROL GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 2Ah DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE  WRPROTECT When the LSISS2520/LSISS2530 device is formatted to use protection information.  Force unit access bits (FUA and FUA_NV) These bits are defined in the following table.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. then the LSISS2520/LSISS2530 device returns a CHECK CONDITION. 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.  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)).

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE (12)  LOGICAL BLOCK ADDRESS 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. This command also supports the variable command time-out feature described in WRITE(6) command handler description.  TRANSFER LENGTH This field specifies the number of blocks to be transferred. Table 119: WRITE 12 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6:9 (MSB) TRANSFER LENGTH (LSB) WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = AAh DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE 10 11 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 See Section 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. 4. WRITE (10) for details of the fields. This command is processed as per the standard WRITE command except for the longer TRANSFER LENGTH. Any other value specifies the number of logical blocks transferred. The LSISS2520/LSISS2530 device does not support grouping function and hence ignores this field. 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.43. If the LOGICAL BLOCK ADDRESS plus the TRANSFER LENGTH exceeds the capacity of the medium. LSI Corporation Confidential | October 2010 Page 123 . A TRANSFER LENGTH of 0 indicates that no logical blocks are transferred. The data transferred from the initiator includes user data as required by the medium format. Do not consider this condition as an error and do not write any data.

Table 121: WRITE 32 CDB Bit Byte 7 0 1 2:5 6 7 8:9 (MSB) SERVICE ACTION (000Bh) (LSB) 10 11 (MSB) 12:19 LOGICAL BLOCK ADDRESS (LSB) WRPROJECT DPO = 0 RESERVED FUA RESERVED FUA_NV RESERVED RESERVED 6 5 4 3 2 1 0 COMMAND CODE (7Fh) CONTROL RESERVED GROUP NUMBER = 0 ADDITIONAL CDB LENGTH (18h) Page 124 LSI Corporation Confidential | October 2010 .Chapter 4: SCSI Commands | WRITE (16) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4.46 WRITE (32) The following table describes the WRITE (32) command. 4.43. This command is processed as per the standard WRITE (10) command except for the TRANSFER LENGTH Field.45 WRITE (16) The WRITE (16) 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. Table 120: WRITE 16 CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:13 (MSB) TRANSFER LENGTH (LSB) 14 15 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 8Ah DPO = 0 FUA RESERVED FUA_NV = 0 OBSOLETE See Section 4. WRITE (10) for details of the fields.

32  LOGICAL BLOCK APPLICATION TAG MASK The LSISS2520/LSISS2530 device only supports the value of 0xFFFF for the logical block application tag mask. LSI Corporation Confidential | October 2010 Page 125 . See Section 4. WRITE (10) for details of the fields. The data transferred from the initiator includes user data as required by the medium format.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE (32) Table 121: WRITE 32 CDB (Continued) Bit Byte 7 (MSB) 20:23 (MSB) 24:25 (MSB) 26:27 (MSB) 28:31 TRANSFER LENGTH (LSB) LOGICAL BLOCK APPLICATION TAG MASK = 0xFFFF (LSB) EXPECTED INITIAL LOGICAL BLOCK APPLICATION TAG (LSB) EXPECTED INITIAL LOGICAL BLOCK REFERENCE TAG (LSB) 6 5 4 3 2 1 0 The WRITE (32) 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 following fields are defined:  EXPECTED INITIAL LOGICALBLOCK REFERENCE TAG Defined in SBC3-r21 – 5.32  EXPECTED LOGICAL BLOCK APPLICATION TAG Defined in SBC3-r21 – 5.43. When the LSISS2520/LSISS2530 device is formatted to use protection information.

The LSISS2520/LSISS2530 device supports DPO set to 0 conditions only. Page 126 LSI Corporation Confidential | October 2010 . It is implemented per SBC3r21.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.  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)). Table 122: WRITE AND VERIFY 10 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 (MSB) TRANSFER LENGTH (LSB) 9 CONTROL RESERVED GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 2Eh DPO = 0 RESERVED BYTCHK OBSOLETE 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.  WRPROTECT This field specifies the protection information to be verified.

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 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. the LSISS2520/LSISS2530 device writes the initiator's data to the device.  GROUP NUMBER This field specifies the group into which attributes associated with the command is collected. the device server perform a medium verification with no data comparison. The algorithm is as follows: — When BYTCHK = 1. If there is a CRC mismatch. While writing. the LSISS2520/LSISS2530 device does not perform a CRC comparison of the initiator data with the data read from medium. If the BYTCHK = 0. then the LSISS2520/LSISS2530 device transmits a CHECK CONDITION response to the initiator along with the calculated read and write CRC (CC response format). 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 generate any CRC nor does the LSISS2520/LSISS2530 device read the data from the device. The LSISS2520/LSISS2530 device discards the read data after it passes through the CRC generator. the device server returns CHECK CONDITION status with the sense key set to MISCOMPARE with the appropriate ASC for the condition. LSI Corporation Confidential | October 2010 Page 127 . A BYTCHK bit set to 1 specifies that. When the WRITE AND VERIFY command is received with the BYTCHK field set to 1. 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.  LOGICAL BLOCK ADDRESS This field specifies the first logical block of the range of logical blocks for this command. NOTE: The CRC generation is only performed for the BYTCHK = 1 case. The LSISS2520/LSISS2530 device implements a non-standard implementation of the BYTCHK bit set to 1. 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. — Once the read completes. after writing. it also generates a CRC value for the data.  TRANSFER LENGTH This field specifies the number of contiguous blocks of data to be transferred. — When the WRITE DATA phase completes. The LSISS2520/LSISS2530 device does not support Grouping. the LSISS2520/LSISS2530 device reads the data from the device starting at the block where the initiator's data was written.

WRITE AND VERIFY(10) for a description of the fields in this command.47.48 WRITE AND VERIFY (12) This following table describes the WRITE AND VERIFY(12) command. 4. See Section 4.Chapter 4: SCSI Commands | WRITE AND VERIFY (12) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. Table 124: WRITE AND VERIFY 16 CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:13 (MSB) TRANSFER LENGTH (LSB) 14 15 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = 8Eh DPO = 0 RESERVED BYTCHK OBSOLETE Page 128 LSI Corporation Confidential | October 2010 .49 WRITE AND VERIFY (16) This following table describes the WRITE AND VERIFY(16) command. Table 123: WRITE AND VERIFY 12 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6:9 (MSB) TRANSFER LENGTH (LSB) 10 11 RESTRICTED FOR MMC-4 RESERVED CONTROL GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 COMMAND CODE = AEh DPO = 0 RESERVED BYTCHK OBSOLETE WRITE AND VERIFY(12) 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.

47. See Section 4. WRITE AND VERIFY(10) for description of the fields in this command. Table 126: Valid Mode Field Values for LSISS25x0 Mode 00h 01h 02h 04h 05h 06h 07h 0Ah 0Eh 0Fh 1Ah Write combined header and data Vendor specific Write data Download microcode Download microcode and save Download microcode with offsets Download microcode with offsets and save Echo buffer Download microcode with offsets and defer activation Activate deferred microcode Enable expander communications protocol and Echo buffer Description No No Yes No Yes No Yes No No No No LSISS2520/LSISS2530 device Support LSI Corporation Confidential | October 2010 Page 129 .50 WRITE BUFFER The LSISS2520/LSISS2530 device translates the WRITE BUFFER SCSI command as per the SAT specification guidelines. 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. Data transferred from the application client includes user data as required by the medium format. 4.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 4: SCSI Commands | WRITE BUFFER WRITE AND VERIFY(16) 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. Table 125: WRITE BUFFER CDB Bit Byte 7 0 1 2 3:5 (MSB) BUFFER OFFSET (LSB) 6:8 (MSB) PARAMETER LIST LENGTH (LSB) 9 CONTROL RESERVED BUFFER ID 6 5 4 3 2 1 0 COMMAND CODE = 3Bh MODE The following table lists the various mode and buffer ID combinations supported by the LSISS25x0 device.

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

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

NOTE: The LSISS2520/LSISS2530 device reports one logical block per physical block (i.21. This bit set to 1 specifies that.  LOGICAL BLOCK ADDRESS This field specifies the logical block at which the WRITE LONG operation occurs. Ignore the BYTE TRANSFER LENGTH field. Table 128: WR_UNCOR bit and PBLOCK bit COR_DIS (WR_UNCOR) PBLOCK (Correction Disable) Write Uncorrectable error (Physical Block) 0 0 0 1 0 0 Description Write only the specified logical block using the value in the BYTE TRANSFER LENGTH field. when the specified logical block is read. and transfer no data.e. the Sense Key is set to Illegal Request and an ASC set to Invalid Field in CDB. — Performs no automatic reallocation of that logical block including any automatic reallocation enabled by the Read-Write Error Recovery mode page.LBA MARKED BAD BY APPLICATION CLIENT.  BYTE TRANSFER LENGTH This field must exactly specify the number of bytes of data that are available for transfer. Ignore the BYTE TRANSFER LENGTH field. the LSISS2520/LSISS2530 device performs normal error recovery on that logical block. The LSISS2520/LSISS2530 device marks only the specified logical block as containing a flagged error without logging. If a nonzero byte TRANSFER LENGTH does not match the available data length. READ CAPACITY (16)) is set to a zero value). the write uncorrectable error (WR_UNCOR) bit. when the specified logical block is read. Negative values are indicated by two's complement notation. 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. the LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status. and transfer no data. the LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT field in the READ CAPACITY (16) data (see Section 4. — Returns a CHECK CONDITION status with the sense key set to MEDIUM ERROR and the ASC set to READ ERROR .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. and the physical block (PBLOCK) bit are defined in the following table. — Does not consider errors on logical blocks to be informational exception conditions as defined in the Information Exceptions Control mode page (refer SPC-4). The LSISS2520/LSISS2530 device supports this configuration. The correction disabled (COR_DIS) bit. 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.. 1 1 0 Page 132 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device marks only the specified logical block as containing a pseudo unrecovered error with logging.

This command is implemented as a service action of the SERVICE ACTION OUT operation code.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. then the LSISS2520/LSISS2530 device terminates the command with CHECK CONDITION status. The LSISS2520/LSISS2530 device writes the logical block or physical block to the medium. otherwise the LSISS2520/LSISS2530 device translates this command into a SATA SCT WRITE LONG command to the device. WRITE LONG (10) for definitions of the fields in this command.51. with sense key set to ILLEGAL REQUEST (0x05) and ASC set to invalid command operation code (0x20). and does not return GOOD status until the logical block is written on the medium. The following table lists the WRITE LONG 16 CDB. If the underlying device does not support the SCT Long Sector Access feature. LSI Corporation Confidential | October 2010 Page 133 . Table 129: WRITE LONG 16 CDB Bit Byte 7 0 1 2:9 COR_DIS (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:11 12:13 (MSB) BYTE TRANSFER LENGTH (LSB) 14 15 RESERVED CONTROL RESERVED WR_UNCOR PBLOCK 6 5 4 3 2 1 0 OPERATION CODE = 9Fh SERVICE ACTION = 11h See Section 4.

write all the remaining blocks on the specified Logical Unit. The LSISS2520/LSISS2530 device does not support grouping. it follows table 85 in SBC3-r21 to verify the DIF fields in the incoming data.  WRPROTECT When the LSISS2520/LSISS2530 device is formatted to use protection information.Chapter 4: SCSI Commands | WRITE SAME (10) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 4. Page 134 LSI Corporation Confidential | October 2010 . Each logical block address includes user data and can include protection information.  NUMBER OF BLOCKS This field specifies the number of contiguous blocks to be written. to the specified range of LBAs. If the number is 0. This command also supports the variable command time-out feature.  GROUP NUMBER This field specifies the group into which attributes associated with the command is collected. The equation used for time-out calculation is Time-out Value = (TRANSFER LENGTH / 32) + command time-out specified in Mode page 0x01h. See Mode Page 32h (Firmware Parameter Control). based on the WRPROTECT field and the medium format. Table 130: WRITE SAME 10 CDB Bit Byte 7 0 1 2:5 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 7:8 (MSB) NUMBER OF BLOCKS (LSB) 9 CONTROL RESERVED Group Number = 0 WRPROTECT 6 5 4 3 2 1 0 OPERATION CODE = 41h RESERVED PBDATA = 0 LBDATA RESERVED  LOGICAL BLOCK ADDRESS This field specifies the address at which the WRITE begins.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. Do not collect a group number value of 0 specifies that any attributes associated with the command into any group.

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. LSI Corporation Confidential | October 2010 Page 135 . WRITE SAME (10) for the definitions of the fields in this command. 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. This command also supports the variable command time-out feature described in the WRITE SAME (10) command handler description. See Section 4.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 (Logical Block Data) (Physical Block Data) 0 0 Description 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.53. Table 132: WRITE SAME 16 CDB Bit Byte 7 0 1 2:9 (MSB) LOGICAL BLOCK ADDRESS (LSB) 10:13 (MSB) NUMBER OF BLOCKS (LSB) 14 15 RESERVED CONTROL GROUP NUMBER = 0 WRPROTECT 6 5 4 3 2 1 0 OPERATION CODE = 93h RESERVED UNMAP = 0 PBDATA = 0 LBDATA OBSOLETE The LSISS2520/LSISS2530 device does not support the UNMAP field. If the LSISS2520/LSISS2530 device is configured for sector skewing. based on the WRPROTECT field and the medium format. 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. 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. ending with the least significant byte. to the specified range of LBAs. with modifications based on the LBDATA bit. 1 0 0 1 1 1 4. Each logical block address includes user data and can include protection information.

Chapter 4: SCSI Commands | WRITE SAME (32) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 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. Each logical block includes user data and can include protection information. with modifications based on the LBDATA bit. to the specified range of LBAs. based on the WRPROTECT field and the medium format. Table 133: WRITE SAME 32 CDB Bit Byte 7 0 1 2:5 6 7 (MSB) 8:9 10 11 (MSB) 12:19 (MSB) 20:23 (MSB) 24:25 (MSB) 26:27 (MSB) 28:31 NUMBER OF LOGICAL BLOCK (LSB) LOGICAL BLOCK APPLICATION TAG MASK = 0xFFFF (LSB) EXPECTED LOGICAL BLOCK APPLICATION TAG (LSB) EXPECTED INITIAL LOGICAL BLOCK REFERENCE TAG (LSB) LOGICAL BLOCK ADDRESS (LSB) WRPROTECT SERVICE ACTION (000Dh) (LSB) RESERVED UNMAP = 0 PBDATA = 0 LBDATA RESERVED RESERVED RESERVED ADDITIONAL LENGTH (18H) 6 5 4 3 2 1 0 OPERATION CODE (7Fh) CONTROL RESERVED GROUP NUMBER = 0 Page 136 LSI Corporation Confidential | October 2010 .

41.54.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:  EXPECTED INITIAL LOGICALBLOCK REFERENCE TAG As defined in SBC3-r21 – 5.  EXPECTED LOGICAL BLOCK APPLICATION TAG As defined in SBC3-r21 – 5. LSI Corporation Confidential | October 2010 Page 137 .41.  LOGICAL BLOCK APPLICATION TAG MASK The LSISS2520/LSISS2530 device only supports the value of 0xFFFF for the logical block application tag mask. See Section 4. WRITE SAME (16) for the definitions of the other fields in this command.

Chapter 4: SCSI Commands | WRITE SAME (32) LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 138 LSI Corporation Confidential | October 2010 .

1 Mode Parameter Header The LSISS2520/LSISS2530 device mode parameters list format for Mode SENSE/SELECT (6/10) is as follows.1 Mode Parameters The LSISS2520/LSISS2530 device supports various SCSI and SAS mode parameters. 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. This section describes the mode parameters supported by the LSISS2520/LSISS2530 device in detail.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. Table 135: Mode Parameter Header for Mode Sense 6/Mode Select 6 Commands BIT Byte 7 0 1 2 3 6 5 4 MODE DATA LENGTH MEDIUM TYPE DEVICE-SPECIFIC PARAMETER BLOCK DESCRIPTOR LENGTH 3 2 1 0 LSI Corporation Confidential | October 2010 Page 139 . 5.

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. When using the MODE SELECT command. the block descriptors in the following mode parameter data. Being the block device. are in the long LBA format.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.  MEDIUM TYPE The contents of the MEDIUM TYPE field are unique for each device type. For the Mode Select 10 command. the LSISS2520/LSISS2530 device populates a zero value in this field. this field is reserved. if the LONGLBA bit in the block descriptor is set. For Mode Sense 10 commands. The mode data length does not include the number of bytes in the MODE DATA LENGTH field. if any.  LONGLBA The LSISS25x0 device supports both short LBA and long LBA format block descriptors. the LSISS25x0 device terminates the mode select command with a check condition status and ASC/ASCQ set to invalid field in the parameter list. the MODE DATA LENGTH field indicates the length in bytes of the following data that is available to be transferred. if any discrepancy is detected in the LONGLBA bit in the mode parameter header and following block descriptor length. Table 136: Mode Parameter Header for Mode Sense 10/Mode Select 10 Commands BIT Byte 7 0:1 (MSB) MODE DATA LENGTH (LSB) 2 3 4 5 6:7 (MSB) BLOCK DESCRIPTOR LENGTH (LSB) MEDIUM TYPE DEVICE-SPECIFIC PARAMETER RESERVED RESERVED LONGLBA 6 5 4 3 2 1 0  MODE DATA LENGTH When using the MODE SENSE command. Page 140 LSI Corporation Confidential | October 2010 .

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

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

1. WRITE.3 Mode Page 01h (Read-Write Error Recovery Parameters) Table 141: Mode Page 01h This section describes Mode Page 01h. READ.  ARRE ARRE bit set to 0 specifies that the device server disables automatic reallocation of defective logical blocks during read operations. WRITE AND VERIFY). AWRE bit is not changeable. AWRE bit is not changeable. BIT Byte 7 0 1 2 3 4:6 AWRE =1 ARRE=0 TB=0 PS 6 RESERVED RC=0 5 4 3 2 PAGE CODE = 01h PAGE LENGTH = 0AH EER OBSOLETE PER=0 DTE=0 DCR=0 READ RETRY COUNT 1 0 81h 0Ah 88h 08h 00h Default 7 8 9 10:11 (MSB) RESERVED WRITE RETRY COUNT RESERVED RECOVERY TIME LIMIT Restricted for MMC-6 00h 04h 00h 1Fh 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.  AWRE This bit set to 1 specifies that the LSISS2520/LSISS2530 device enables automatic reallocation to be performed during write operations. LSI Corporation Confidential | October 2010 Page 143 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 140: Mode Page 00h (Continued) BIT Byte 7 16 17 18 19 20 6 5 4 3 2 1 0 FIFTEENTH SUPPORTED PAGE 36H SIXTEENTH SUPPORTED PAGE 37H SEVENTEENTH SUPPORTED PAGE 39H EIGHTEENTH SUPPORTED PAGE 3AH NINETEENTH SUPPORTED PAGE 3BH 5.

The LSISS2520/LSISS2530 device allows this field to be changed but the assignment does not translate into any behavior change.  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.  READ RETRY COUNT This field specifies the number of times the recovery algorithm is attempted during the read operation. Error recovery procedures is performed within the limits established by the error recovery parameters. PER is not changeable.  RC This bit set to 0 specifies that error recovery operations that cause delays are acceptable during the data transfer. The LSISS2520/LSISS2530 device does not support this feature and returns a value 4 for it. The LSISS2520/LSISS2530 device does not support this feature and returns a value 8 for it. 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.  Disable correction (DCR) This bit set to 1 specifies that error correction codes is not used for data error recovery.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. Data is not fabricated. A PER bit set to 0 specifies that the LSISS2520/LSISS2530 device does not report recovered errors. The LSISS2520/LSISS2530 device supports 0h condition only. The LSISS2520/LSISS2530 device does not support this bit set to 1. 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. Page 144 LSI Corporation Confidential | October 2010 .  Post Error (PER) This bit set to 1 specifies that the LSISS2520/LSISS2530 device reports recovered errors. 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 does not support this bit set to 1.  WRITE RETRY COUNT This field specifies the number of times the recovery algorithm is attempted during the write operation. The LSISS2520/LSISS2530 device supports 0h condition only. EER is not changeable. A DCR bit set to 0 allows the use of error correction codes for data error recovery.  Enable Early Recovery (EER) This bit set to 1 specifies that LSISS2520/LSISS2530 device uses the most expedient form of error recovery first. 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.

5. The default value is 1F40h (8 seconds). the LSISS2520/LSISS2530 device can time out every command that it receives. if a very small value is used. LSI Corporation Confidential | October 2010 Page 145 . The Disconnect/Reconnect mode page enables the initiator to tune the performance of the transmission medium. since. This is the command time-out for the LSISS2520/LSISS2530 device. and the LSISS2520/LSISS2530 device can become unusable. NOTE: Modify this field with caution.4 Mode Page 02h (Disconnect/Reconnect Parameters) Table 142: Mode Page 02h BIT Byte 7 0 1 2 3 4:5 (MSB) BUS INACTIVITY TIME LIMIT (LSB) 6:7 8:9 (MSB) MAXIMUM CONNECT TIME LIMIT (LSB) 10:11 (MSB) MAXIMUM BURST SIZE (LSB) 12 13 14:15 (MSB) FIRST BURST SIZE (LSB) RESERVED RESERVED 00h 00h 00h 00h RESERVED 00h 00h PS 6 SPF(0b) RESERVED RESERVED 5 4 3 2 1 0 82h 0Eh 00h 00h 00h PAGE CODE = 02h PAGE LENGTH= 0Eh Default This section describes the Mode Page 02h. 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).1.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  RECOVERY TIME LIMIT This field specifies in milliseconds the maximum time duration that the LSISS2520/LSISS2530 device uses for data error recovery procedures.

the SSP target port prepares to close the connection by requesting the link layer transmit DONE. 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 SSP target port completes transferring the frame before closing the connection. Nonzero values less than 64 (32K bytes) results in a burst size of 16K. 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. — The SSP target port has read data to transfer for only one I_T_L_Q nexus. A value of 0000h indicates that there is no MAXIMUM CONNECTION TIME LIMIT.4 (SPC . — The SSP target port has no requests to transfer write data for any I_T_L_Q nexus. Internally. If this time elapses. 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. For write data.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. The port layer enforces the MAXIMUM CONNECTION TIME LIMIT.  MAXIMUM CONNECT TIME LIMIT The value in the MAXIMUM CONNECT TIME LIMIT field contains the maximum duration of a connection in 100-μs increments. The SSP target port prepares to close the connection on transferring the amount of data. when both of these conditions exist. the SSP target port prepares to close the connection.  FIRST BURST SIZE The LSISS2520/LSISS2530 device does not support Enable FIRST BURST for command frames and hence does not support this field. the only values supported are a 32K or a 16K burst size.  MAXIMUM BURST SIZE For read data. This value is in 512-byte increments. the value specifies the maximum amount of data that an SSP target port requests through a single XFER_RDY frame. Round up this value as defined in SCSI Primary Commands .4). A value of 0 in this field indicates that there is no MAXIMUM BURST SIZE. The data transferred during a connection consists of data for a single I_T_L_Q nexus. If the MAXIMUM CONNECTION TIME LIMIT has elapsed while transferring a frame. as specified by the MAXIMUM BURST SIZE field to the SSP initiator port. Page 146 LSI Corporation Confidential | October 2010 . Values greater than or equal to 64 result in a burst size of 32K. If this time elapses.

 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. The LSISS2520/LSISS2530 device does not support this bit set to 1.  Disable correction (DCR) This bit set to 1 specifies that error condition codes are not used for data error recovery.  Post Error (PER) This bit set to 1 specifies that the LSISS2520/LSISS2530 device reports recovered errors.5 Mode Page 07h (Verify Error Recovery Parameters) Table 143: Mode Page 07h This section describes Mode Page 07h. 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.  Enable Early Recovery (EER) This bit set to 1 specifies that the LSISS2520/LSISS2530 device uses the most expedient form of error recovery first. 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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 5. The LSISS2520/LSISS2530 device does not support this bit set to 1. BIT Byte 7 0 1 2 3 4 5:9 10:11 (MSB) VERIFY RECOVERY TIME LIMIT (LSB) RESERVED PS 6 RESERVED 5 4 3 2 PAGE CODE = 07h PAGE LENGTH = 0Ah EER = 0 VERIFY RETRY COUNT = 0 OBSOLETE RESERVED PER = 0 DTE = 0 DCR = 0 1 0 87h 0Ah 00h 00h 00h 00h 1Fh 40h Default 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. 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.1. LSI Corporation Confidential | October 2010 Page 147 . The LSISS2520/LSISS2530 device does not support this bit set to 1. 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 default value is 1F40h (8 seconds).1.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  VERIFY RETRY COUNT This field specifies the number of times that the LSISS2520/LSISS2530 device attempts its recovery algorithm during a verify operation. 5.6 Mode Page 08h (Caching Parameters) Table 144: Mode Page 08h This section describes Mode Page 08h. The LSISS2520/LSISS2530 device returns a zero value for it. This field is not changeable.  VERIFY RECOVERY TIME LIMIT This field specifies in milliseconds the maximum time duration that the LSISS2520/LSISS2530 device uses for data error recovery procedures. BIT Byte 7 0 1 2 3 4:5 (MSB) DISABLE PRE-FETCH TRANSFER LENGTH = 0H (LSB) 6:7 (MSB) MINIMUM PRE-FETCH (LSB) 8:9 (MSB) MAXIMUM PRE-FETCH (LSB) 10:11 (MSB) MAXIMUM PRE-FETCH CEILING (LSB) 12 13 14:15 (MSB) CACHE SEGMENT SIZE = 00H (LSB) 16 17:19 RESERVED OBSOLETE 00H 00H FSW LBCSS=0 DRA VENDOR SPECIFIC NUMBER OF CACHE SEGMENTS RESERVED NV_DIS = 1 01H 00H 00H 00H 00H 00H IC=0 ABPF=0 CAP=0 PS 6 RESERVED PAGE LENGTH DISC SIZE=0 WCE MF=0 RCD=0 DEMAND READ RETENTION PRIORITY= 0H WRITE RETENTION PRIORITY = 0H 5 4 3 2 1 0 88H 12H 00H 00H 00H PAGE CODE = 08H Default Page 148 LSI Corporation Confidential | October 2010 .

LSI Corporation Confidential | October 2010 Page 149 .  Abort pre-fetch (ABPF) This bit set to 1 with the DRA bit set to 0. space available for the prefetch. The LSISS2520/LSISS2530 device does not support this bit set to 1. 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. A SIZE bit set to 0 specifies that the NUMBER OF CACHE SEGMENTS field be used to control caching segmentation. The LSISS2520/LSISS2530 device does not support this bit set to 1.  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.  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. specifies that the LSISS2520/LSISS2530 device abort a prefetch upon receipt of a new command. 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 DISC bit set to 0 specifies that prefetches be truncated or wrapped at time discontinuities. with the DRA bit set to 0. or segment. An ABPF bit set to 0. dependent upon the SIZE bit. An ABPF bit set to 1 takes precedence over the value specified in the MINIMUM PRE-FETCH field. The LSISS2520/LSISS2530 device does not support this bit set to 1. The LSISS2520/LSISS2530 device does not support this bit set to 1. 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.  Size Enable (SIZE) This bit set to 1 specifies that the CACHE SEGMENT SIZE field be used to control caching segmentation. The LSISS2520/LSISS2530 device does not support this bit set to 1.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters The Caching Parameters page defines parameters that affect the use of the cache. When the WCE bit is set to 1.  Discontinuity (DISC) This bit set to 1 specifies that the LSISS2520/LSISS2530 device continue the prefetch across time discontinuities (for example. 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. to control the caching algorithm rather than the LSISS2520/LSISS2530 device's own adaptive algorithm.  Caching Analysis Permitted (CAP) This bit set to 1 specifies that the LSISS2520/LSISS2530 device perform caching analysis during subsequent operations. across cylinders) up to the limits of the buffer.

Value Description 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). has lower priority) than data placed into the cache by other means (for example. it is not locked). The LSISS2520/LSISS2530 device supports only the 0h condition. RESERVED 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. has lower priority) than data placed into the cache by other means (for example. prefetch) and it is replaced (that is. prefetch) and it is replaced (that is. 0h 1h 2h . The LSISS2520/LSISS2530 device does not support this bit set to 1. 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.  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.Eh Fh  DISABLE PRE-FETCH TRANSFER LENGTH This field specifies the selective disabling of anticipatory prefetch on long transfer lengths.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. The LSISS2520/LSISS2530 device does not support nonzero value for this field. The LSISS2520/LSISS2530 device does not support this bit set to 1. Page 150 LSI Corporation Confidential | October 2010 .  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. prefetch).  WRITE RETENTION PRIORITY This field advises the LSISS2520/LSISS2530 device. prefetch). the retention priority to assign for data written into the cache that has also been transferred from the cache memory to the medium. Demand read retention priority: Data put into the cache through a READ command is replaced sooner (that is. Write retention priority: Data put into the cache during a WRITE or WRITE AND VERIFY command is replaced sooner (that is. it is not locked).

The LSISS2520/LSISS2530 device supports this bit set to both 0 and 1.  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. The LSISS2520/LSISS2530 device keeps the default value as 0. 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. the resulting number of blocks is the number to prefetch if the prefetch does not delay processing of subsequent commands. A LBCSS bit set to 0 specifies that the CACHE SEGMENT SIZE field units is interpreted as bytes. 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. In either case. The LSISS2520/LSISS2530 device does not support this bit set to 1. 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.  MAXIMUM PRE-FETCH This field specifies either a number of blocks or a scalar multiplier of the TRANSFER LENGTH. 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 does not support this bit set to 1. LSI Corporation Confidential | October 2010 Page 151 .  MAXIMUM PRE-FETCH CEILING This field specifies an upper limit on the number of logical blocks computed as the maximum prefetch. sequential. depending upon the setting of the MF bit.  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. logical block order. The LSISS2520/LSISS2530 device does not support this bit set to 0.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  MINIMUM PRE-FETCH This field specifies either a number of blocks or a scalar multiplier of the TRANSFER LENGTH. 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. In either case. depending upon the setting of the MF bit.  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. The field is non changeable and the LSISS2520/LSISS2530 device keeps the default value as 0.  Logical Block Cache Segment Size (LBCSS) This bit set to 1 specifies that the CACHE SEGMENT SIZE field units is interpreted as logical blocks.

5.7 Mode Page 0Ah (Control Mode Page Parameters) Table 145: Mode Page 0Ah This section describes Mode Page 0Ah. The CACHE SEGMENT SIZE field is valid only when the SIZE bit is set to 1. BIT Byte 7 0 1 2 3 4 5 6:7 8:9 (MSB) BUSY TIMEOUT PERIOD = FF (LSB) 10:11 (MSB) EXTENDED SELF-TEST ROUTINE COMPLETION TIME = 0X00 (LSB) 00h 03h VS ATO TST = 000b RAC = 0 TAS = 1 QUEUE ALGORITHM MODIFIER = 1h UA_INTLCK_CTRL = 00b RESERVED OBSOLETE PS 6 SPF(0b) TMF_ONLY = 0 5 4 3 2 1 0 8Ah 0Ah D_SENSE GLTSD = 0 OBSOLETE AUTOLOAD MODE = 000b RLEC OBSOLETE 00h 10h 00h C0h 00h 00h FFh FFh QErr = 00b PAGE CODE = 0Ah PAGE LENGTH = 0Ah RESERVED RESERVED SWP = 0b Default Page 152 LSI Corporation Confidential | October 2010 .Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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.1. The LSISS2520/LSISS2530 device does not support this field.

— 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. no status is sent for the tasks that are aborted. In case of mode select. The LSISS2520/LSISS2530 device currently keeps the default value for this as 3. — 1h: Unrestricted re-ordering allowed: The target re-orders the actual execution sequence of the queued commands in any manner it selects. 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. The LSISS2520/LSISS2530 device does not support this field set to 0.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 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. Table 146: QErr Values QErr Value 00b 01b Description All tasks other than the task that received the CHECK CONDITION status is processed as if no error occurred. When TAS bit = 1. For the I_T NEXUS to which the CHECK CONDITION status is sent.  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. this field is Don’t care and is valid only on the SMART enabled device. LSI Corporation Confidential | October 2010 Page 153 .  BUSY TIMEOUT PERIOD This field is set to 0xFFFF by LSISS25x0 and is ignored by the LSISS2520\LSISS2530 device. 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 QErr=0 and QErr =1 only. — 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. This value needs to be calculated for drives that have the SMART feature. The LSISS2520/LSISS2530 device supports this unrestricted re-ordering.

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. this field is non changeable and set to 0 by default. The field is non changeable and set to 0 by default. 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. Page 154 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device saves the log parameters at vendor-specific intervals. Task set type (TST) field Code Description The logical unit maintains one task set for all I_T NEXUSs The logical unit maintains separate task sets for each I_T NEXUS RESERVED 000b 001b 010b -111b The LSISS2520/LSISS2530 device supports 000b condition for TST. The LSISS2520/LSISS2530 device does not support ACA condition. 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. The LSISS2520/LSISS2530 device supports TAS bit condition set to 1 only. at vendor-specific intervals.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  Task Set Type (TST) This field specifies the type of task set in the logical unit.  Global Logging Target Save Disable (GLTSD) This bit set to 0 specifies that the logical unit implicitly saves. A GLTSD bit set to 1 specifies that the logical unit does not implicitly save any log parameters. Therefore. 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.  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.  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.  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. The LSISS2520/LSISS2530 device supports bit set to 0 condition. each log parameter in which the TSD bit is set to 0.  Report A Check (RAC) This bit provides control of reporting long busy conditions or CHECK CONDITION status.

Depending on the status. or RESERVATION CONFLICT status. TASK SET FULL or RESERVATION CONFLICT results in the establishment of a unit attention condition. if any. the WP bit is set to 1 for subsequent MODE SENSE commands. TASK SET FULL. RESERVED 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. or PREVIOUS RESERVATION CONFLICT STATUS.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  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 status is being returned. Table 147: Unit Attention Interlocks Control (UA_INTLCK_CTRL) Field Code 00b Definition 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. PREVIOUS TASK SET FULL STATUS. TASK SET FULL. the ASC is set to PREVIOUS BUSY STATUS. 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. Until it is cleared by a REQUEST SENSE command. or RESERVATION CONFLICT status. LSI Corporation Confidential | October 2010 Page 155 . 01b 10b 11b  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. TASK SET FULL. The LSISS2520/LSISS2530 device does not support SWP set to 1 condition. The LSISS2520/LSISS2530 device supports bit set to 00 condition only. or RESERVATION CONFLICT status regardless to the number of commands terminated with one of those status values. 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. a unit attention condition is established only once for a BUSY.

RESERVED  Report log exception condition (RLEC) This bit set to 1 specifies that The LSISS2520/LSISS2530 device reports log exception conditions. this field is reserved. Page 156 LSI Corporation Confidential | October 2010 . Though the field is changeable. are not be modified by the LSISS2520/LSISS2530 device.  Application tag owner (ATO) This bit set to 1 specifies that the contents of the LOGICAL BLOCK APPLICATION TAG field in the protection information. The LSISS2520/LSISS2530 device supports 000b mode only. 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. For devices other than removable medium devices.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  AUTOLOAD MODE This field specifies the action to be taken by a removable medium device server when a medium is inserted. Table 148: AUTOLOAD MODE field Code 000b 001b 010b 011b . If the ATO bit is set to 0. The LSISS2520/LSISS2530 device does not support this bit condition set to 1.111b Definition Medium is loaded for full access. if any. then the LSISS2520/LSISS2530 device ignores the contents of the LOGICAL BLOCK APPLICATION TAG field in the protection information when received from the initiator.  VS This is a vendor-specific bit. the LSISS2520/LSISS2530 device does not support this functionality. A RLEC bit set to 0 specifies that the LSISS2520/LSISS2530 device does not report log exception conditions. The following table shows the usage of the AUTOLOAD MODE field. Medium is loaded for medium auxiliary memory access only. Medium is not loaded.

 INITIAL COMMAND PRIORITY The LSISS2520/LSISS2530 device does not support this field.  SCSI Precedence (SCSIP) The value of this bit is reported as 1. The value of this field is reported as zero.1 Mode Page 0Ah – Subpage 01h The following section describes Mode Page 0Ah – Subpage 01h. indicating that the timestamp is not changed by any method except those defined by the applicable SPC standard. Subpage 01h – Control Extension Mode Page Bit Byte 7 0 1 2:3 4 5 6:31 RESERVED RESERVED RESERVED PS (1b) 6 SPF (1b) 5 4 3 2 1 0 CAh 01h 00h 1Ch TCMOS = 0b SCSIP = 1B IALUAE = 0b 02h 00h 00h INITIAL COMMAND PRIORITY = 0h PAGE CODE (0Ah) SUBPAGE CODE (01h) PAGE LENGTH (001Ch) Default 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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 5. indicating that the timestamp changed using SET TIMESTAMP command takes precedence over the methods outside the scope of the applicable SPC standard. Table 149: Mode Page 0Ah.1.7.  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. LSI Corporation Confidential | October 2010 Page 157 .  Timestamp Changeable by Methods Outside SPC Standard (TCMOS) The value of this bit is reported as 0.

1. Table 151: Mode Page 19h . 5.8 Mode Page 18h (Protocol-Specific Logical Unit Mode Page for SAS SSP) The mode page is a read-only mode page since the LSISS2520/LSISS2530 device does not support changing the parameters of this mode page.Protocol-Specific Logical Unit Mode Page for SAS SSP Bit Byte 7 0 1 2 3:7 RESERVED PS 6 SPF(0b) 5 4 3 PAGE CODE = 18h PAGE LENGTH = 06h TRANSPORT LAYER RETRIES RESERVED PROTOCOL IDENTIFIER (6h) 2 1 0 98h 06h 06h 00h Default  PROTOCOL IDENTIFIER The PROTOCOL IDENTIFIER is set to value 6h.1.Protocol-Specific Port Mode Page for SAS SSP BIT Byte 7 0 1 2 3 4:5 (MSB) I_T NEXUS LOSS TIME (LSB) 6:7 (MSB) INITIATOR RESPONSE TIMEOUT (LSB) 8:9 (MSB) REJECT TO OPEN LIMIT (LSB) 10:15 RESERVED 00h 00h 00h RESERVED CONTINUE AWT PS 6 SPF(0b) BROADCAST ASYNCHRONOUS EVENT 5 4 3 2 1 0 99h 0Eh PROTOCOL IDENTIFIER (6h) 26h 00h 07h D0h PAGE CODE = 19h PAGE LENGTH = 0Eh READY LED MEANING RESERVED Default Page 158 LSI Corporation Confidential | October 2010 .9.1 Mode Page 19 This section describes the Mode page 19 and various subpages within the mode page 19h.9 Mode Page 19h (Protocol-Specific Port Mode Page for SAS SSP) 5. This indicates SAS as the underlying transport protocol. Table 150: Mode Page 18h .Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5.1.  TRANSPORT LAYER RETRIES The LSISS2520/LSISS2530 device does not support this field. This section describes Mode Page 19.

Time in ms The SSP target port never recognizes an I_T NEXUS loss. This indicates that it retries the connection requests forever.  PROTOCOL IDENTIFIER The field is set to value 6h. Regardless of the mode page policy. Table 152: I_T NEXUS LOSS TIME field Code 0000h 0001h to FFFEh FFFFh Description Vendor-specific amount of time. LSI Corporation Confidential | October 2010 Page 159 . the LED is usually on. but flashes on and off when commands are processed. This indicates SAS as the underlying transport protocol. The default time is 2000 ms. When the bit is 1. the LED is usually off.  A BROADCAST ASYNCHRONOUS EVENT This bit set to 1 specifies that the device server enables the origin of Broadcast (Asynchronous Event).  READY LED MEANING This bit specifies the READY LED signal behavior. but flashes on and off when commands are processed. This bit set to 0 specifies that the device server disables the origin of Broadcast (Asynchronous Event).  I_T NEXUS LOSS TIME This field contains the time that the SSP target port retries the connection requests to an SSP initiator port. and the device is in a ready state. the shared mode page policy applies to the READY LED MEANING bit. The rejected responses indicate that the SSP initiator port is no longer present before recognizing an I_T NEXUS loss. Refer SAS-2 standard.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters The Protocol-Specific Port mode page contains parameters that affect the SSP target port operation. The following table defines the I_T NEXUS LOSS TIME field values. When the bit is 0. 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). The port layer enforces I_T NEXUS LOSS TIME field values.  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).

Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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). SAS PHY MODE DESCRIPTOR for PHY 1.PHY Control And Discover Mode Page BIT Byte 7 0 1 2:3 4 5 6 7 8:55 56:103 RESERVED GENERATION CODE NUMBER OF PHYS (02h) SAS PHY MODE DESCRIPTOR for PHY 0.9. The supported values for this field range from 0 to 128.  NUMBER OF PHYS The NUMBER OF PHYS indicates the number of SAS PHYs on the LSISS2520/LSISS2530 device. or OPEN_REJECT (RESERVED CONTINUE 1). Table 153: Mode Page 19h . PS 6 SPF(1b) 5 4 3 2 1 0 D9h 01h 00h 64h 00h PROTOCOL IDENTIFIER (6h) 06h 00h 02h — — PAGE CODE (19h) SUBPAGE CODE (01h) PAGE LENGTH (0064h) RESERVED Default  PROTOCOL IDENTIFIER The PROTOCOL IDENTIFIER is set to value 6h.2 Mode Page 19 Subpage 1 This section describes Mode Page 19 . See Table 154.  INITIATOR RESPONSE TIMEOUT The LSISS2520/LSISS2530 device does not support this field. This indicates SAS as the underlying transport protocol. Page 160 LSI Corporation Confidential | October 2010 . This value can be rounded as defined in SPC-4. OPEN_REJECT (RESERVED CONTINUE 0). See Table 154. A REJECT TO OPEN LIMIT field set to 0000h indicates that the minimum time is VENDOR SPECIFIC. This field is set to 2. This minimum time is enforced by the port layer. 5.1.Subpage 1.

Table 154: SAS PHY Mode Descriptor BIT Byte 7 0 1 2:3 4 5 6 RESERVED ATTACHED DEVICE TYPE REASON RESERVED 6 5 4 3 RESERVED PHY IDENTIFIER RESERVED ATTACHED REASON NEGOTIATED LOGICAL LINK RATE ATTACHED SSP ATTACHED STP ATTACHED INITIATOR INITIATOR SMP INITIATOR PORT PORT PORT ATTACHED SSP ATTACHED STP TARGET PORT TARGET PORT SAS ADDRESS ATTACHED SAS ADDRESS ATTACHED PHY IDENTIFIER RESERVED PROGRAMMED MINIMUM PHYSICAL LINK RATE PROGRAMMED MAXIMUM PHYSICAL LINK RATE HARDWARE MINIMUM PHYSICAL LINK RATE HARDWARE MAXIMUM PHYSICAL LINK RATE RESERVED VENDOR SPECIFIC RESERVED ATTACHED SMP TARGET PORT RESERVED 2 1 0 00h — 00h — — — Default 7 RESERVED RESERVED — 8:15 16:23 24 25:31 32 33 34:41 42:43 44:47 — — — 00h 08h AAh 00h 00h 00h  ATTACHED DEVICE TYPE This field indicates the device type attached to this PHY and is defined in the following table.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  GENERATION CODE The LSISS2520/LSISS2530 device sets the GENERATION CODE to the 0 value. Code Description No device attached SAS or SATA device Expander device RESERVED 000 001 010 All Others LSI Corporation Confidential | October 2010 Page 161 .

The REASON field indicates the reason for the link reset sequence and is defined in following table. Expender Device Reduced Functionality. Table 155: REASON Codes Code 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 All Others Description Unknown Reason. MUX Received. PHY test function stopped. Loss of D-Word Synchronization.5 Gbps Ah 9h 8h Value The LSISS2520/LSISS2530 device sets the following six fields to the value obtained in the IDENTIFY address frame during the identification sequence. Table 156: Logical Link Rate Values Link Rate 6 Gbps 3 Gbps 1. Power On. Break time-out timer expired. Page 162 LSI Corporation Confidential | October 2010 . Hard Reset. SMP link Reset.        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. The value is negotiated during the link reset sequence.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  ATTACHED REASON This field indicates the value of the REASON field received in the IDENTIFY address frame during the identification sequence. RESERVED  NEGOTIATED LOGICAL LINK RATE This field indicates the logical link rate being used by the phy. I_T NEXUS time-out timer expired.

Table 157: PROGRAMMED MINIMUM\MAXIMUM PHYSICAL LINK RATE Code 0x0 0x1 to 0x7 0x8 0x9 0xA 0xB to 0xF Description Do not change current value Reserved 1.  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.  HARDWARE MAXIMUM PHYSICAL LINK RATE This field is set to 6 Gbps (Value Ah) for the LSISS2520/LSISS2530 device.  PROGRAMMED MINIMUM PHYSICAL LINK RATE This field specifies the minimum physical link rate that the PHY supports during a link reset sequence.  VENDOR SPECIFIC This field is populated by zero value in the LSISS2520/LSISS2530 device. See the following table. LSI Corporation Confidential | October 2010 Page 163 .5 Gbps (Value 8h) for the LSISS2520/LSISS2530 device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  ATTACHED SAS ADDRESS This field contains the value of the SAS ADDRESS field received in the IDENTIFY address frame during the identification sequence.5Gb/s 3Gb/s 6Gb/s Reserved for future physical link rates  HARDWARE MINIMUM PHYSICAL LINK RATE This field is set to 1.

1.1. in one millisecond increments. that a target port responds to connection requests with OPEN_REJECT (RETRY) after receiving NOTIFY (POWER LOSS EXPECTED).9. etc.). Table 159: Mode Page 19h .ENHANCED PHY CONTROL Mode Page BIT Byte 7 0 1 2:3 4 5 6 RESERVED GENERATION CODE PS 6 SPF(1b) 5 4 3 2 1 0 59h 03h 00h 2Ch 00h PROTOCOL IDENTIFIER (6h) 06h 00h PAGE CODE (19h) SUBPAGE CODE (03h) PAGE LENGTH (002Ch) RESERVED Default Page 164 LSI Corporation Confidential | October 2010 . values of 1 to 10 are set to 10 milliseconds. and values of 11 to 20 are set to 20 milliseconds.Shared Port Control Mode Page BIT Byte 7 0 1 2:3 4 5 6:7 8:15 RESERVED POWER LOSS TIMEOUT RESERVED PS 6 SPF(1b) 5 4 3 2 1 0 D9h 02h 00h 0Ch 00h PROTOCOL IDENTIFIER (6h) 06h 00h 00h PAGE CODE (19h) SUBPAGE CODE (02h) PAGE LENGTH (000Ch) RESERVED Default The page is a read-only mode page and the LSISS2520/LSISS2530 device does not support modifying parameters of this page.3 Mode Page 19 Subpage 2 This section describes Mode Page 19 .Subpage 3. (i.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5. This field is rounded up to the nearest 10 millisecond value.Subpage 2. Table 158: Mode Page 19h . the default timeout value is 2 seconds.9. This indicates SAS as the underlying transport protocol. 5.e.4 Mode Page 19 Subpage 3 This section describes Mode Page 19 .  POWER LOSS TIMEOUT The POWER LOSS TIMEOUT field contains the maximum time.  PROTOCOL IDENTIFIER The PROTOCOL IDENTIFIER is set to value 6h. If this field is set to 0x0000.

 CURRENT PHY CAPABILITIES This field indicates the outgoing SNW-3 PHY capabilities bits transmitted in the last link reset sequence. The field is set to 2.  NUMBER OF PHYS The NUMBER OF PHYS indicates Number of SAS Phys on the LSISS2520/LSISS2530 device. Table 160: ENHANCED PHY CONTROL MODE DESCRIPTOR BIT Byte 7 0 1 2:3 4:7 8:11 12:15 16:17 18 19 RESERVED 6 5 4 3 RESERVED PHY IDENTIFIER DESCRIPTOR LENGTH PROGRAMMED PHY CAPABILITIES CURRENT PHY CAPABILITIES ATTACHED PHY CAPABILITIES RESERVED NEGOTIATED SSC RESERVED NEGOTIATED PHYSICAL LINK RATE HW MUXing SUPPORT 2 1 0 00h 00h 01h 00h 10h — — — 00h — 00h Default  PROGRAMMED PHY CAPABILITIES This field indicates the SNW-3 PHY capabilities bits transmitted in the next link reset sequence containing SNW-3. the CURRENT PHY CAPABILITIES field is set to 0. See Table 160. This indicates SAS as the underlying transport protocol. See Table 160. ENHANCED PHY CONTROL MODE DESCRIPTOR for PHY 1. If the last link reset sequence did not include SNW-3 or was a SATA link reset sequence.  GENERATION CODE The LSISS2520/LSISS2530 device sets the GENERATION CODE to the zero value. Default  PROTOCOL IDENTIFIER The PROTOCOL IDENTIFIER is set to value 6h. LSI Corporation Confidential | October 2010 Page 165 .ENHANCED PHY CONTROL Mode Page (Continued) BIT Byte 7 7 8:27 28:47 6 5 4 3 2 1 0 02h — — NUMBER OF PHYS (02h) ENHANCED PHY CONTROL MODE DESCRIPTOR for PHY 0.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 159: Mode Page 19h .

 NEGOTIATED PHYSICAL LINK RATE If the PHY is a physical PHY.  A NEGOTIATED SSC This field set to 1 indicates that SSC is enabled. Page 166 LSI Corporation Confidential | October 2010 . It can be greater than the PROGRAMMED MAXIMUM PHYSICAL LINK RATE. 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. The NEGOTIATED SSC field is valid only when the NEGOTIATED PHYSICAL LINK RATE field is greater than or equal to 8h. set this field to the MAXIMUM PHYSICAL LINK RATE supported by the expander device. If the PHY is a virtual PHY. For details.  HW MUXing SUPPORT The LSISS2520/LSISS2530 device does not support this field and it is always set to 0. A NEGOTIATED SSC field set to 0 indicates that SSC is disabled.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  The ATTACHED PHY CAPABILITIES This field indicates the incoming SNW-3 PHY capabilities bits received in the last SNW-3. the ATTACHED PHY CAPABILITIES field is set to 0. refer to the SAS-2 spec. If the last link reset sequence did not include SNW-3 or was a SATA link reset sequence. this field indicates the physical link rate negotiated during the link reset sequence.

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

10.1.11 Mode Page 1Ch (Informational Exceptions Control) Table 163: Mode Page 1Ch BIT Byte 7 0 1 2 3 PERF RSVD RESERVED EBF PS 6 SPF EWASC = 0 5 4 3 2 PAGE CODE = 1Ch PAGE LENGTH = 0Ah DEXCPT = 0 TEST = 0 EBACKERR = 0 LOGERR = 1 Method of Reporting 1 0 9Ch 0Ah 81h 06h Default This section describes Mode Page 1Ch. the ATA SET FEATURES – Disable the APM feature set (subcommand 85h) command is sent.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5. the LSISS2520/LSISS2530 device ignores the value contained in the APM Value field. If the APM VALUE field contains a zero.1. depending on the value contained in the APM Value field. 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). BIT Byte 7 0 1 2 3 4 5 6 7:15 PS 6 SPF 5 4 3 2 1 0 DAh F1h 00h 0Ch 00h APMP 00h 00h 00H Page Code = 1Ah SUBPAGE CODE = F1h (MSB)PAGE LENGTH = 0 (LSB)PAGE LENGTH = 0Ch RESERVED RESERVED APM Value RESERVED Default  APMP This bit set to 1 indicates that the LSISS2520/LSISS2530 device alters the APM Mode by issuing the ATA SET FEATURES command. When this bit is set to 0.  APM Value If the APM VALUE field contains a nonzero value.1 ModePage 1Ah Subpage F1h: ATA Power Condition ModePage Table 162: ModePage 1Ah Subpage F1h This section describes ModePage 1Ah Subpage F1h. 5. Page 168 LSI Corporation Confidential | October 2010 .

The reporting of information exception conditions when the DEXCPT bit is set to 0 is determined from the Method of Reporting field. informational exception operations that are the cause of delays are acceptable. and the PERF field is set to 1 in a Mode Sense data.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 163: Mode Page 1Ch (Continued) BIT Byte 7 (MSB) 4:7 (MSB) 8:11 REPORT COUNT (LSB) 00h INTERVAL TIMER (LSB) 00h 6 5 4 3 2 1 0 Default 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. ASCQ 01h) is reported.  EWASC (Enable Warning ASC) This bit set to 0 indicates that Temperature Warning is not reported. background self-test errors. The LSISS2520/LSISS2530 device does not support this field. If this bit is set these counters are not written to disk and so is lost at the next power cycle. the device server does not cause delays while doing informational exception operations. Recovered Error (Sense Key 01h. LSI Corporation Confidential | October 2010 Page 169 . If the PERF bit is set to 1. ASC 0Bh. If the temperature reading inside of the disk enclosure exceeds the threshold (default or set by MODE SELECT Page 0).  DEXCPT (Disable Exception Control) This bit set to 0 indicates information exception operations is enabled. An EWASC bit of 1 allows Temperature Warning to be reported when DEXCPT bit is set to 0.  EBF (Enable Background Function) This bit is not used and is ignored by the LSISS2520/LSISS2530 device. 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. The LSISS2520/LSISS2530 device does not support this bit set to 1. The LSISS2520/LSISS2530 device does not support this bit set to 1.  PERF (Performance) If the performance (PERF) bit is set to 0. Informational exception conditions occur as the result of background scan errors. 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.

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

A value of zero allows the LSISS2520/LSISS2530 device to chose the interval.  FLASHING TIMER CONFIGURATION The LSISS2520/LSISS2530 device periodically flushes the logs to flash. 5. A REPORT COUNT of 0 indicates no limits on the number of times the target reports an informational exception condition. or how soon after a log message is generated the flush to the flash begins. LSI Corporation Confidential | October 2010 Page 171 .1. This value is one of the four levels. the log message is dropped.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  REPORT COUNT This field indicates the number of times the target reports an informational exception condition. LSISS25x0 does not support this field set to nonzero value.12 Mode Page 25h (Logging Configuration Parameters) Table 165: Mode Page 25h This section describes Mode Page 25h. BIT Byte 7 0 1 2:3 4 5:7 PS 6 SPF RESERVED LOGGING SYSTEM LEVEL FLASHING TIMER CONFIGURATION 5 4 3 2 1 0 A5h 06h 00h 02h 00h PAGE CODE = 25h PAGE LENGTH = 06h Default This page is used to change the behavior of logging. This timer provides the 100ms interval to control the period. The LSISS2520/LSISS2530 device does not support a nonzero value for this field. If it is less than the system level. It can change the types of messages that are saved. Table 166: Log Levels Value 00 01 10 11 Informational Message Low Priority Error/Warning Error (Default): Errors are considered to be disruptive but recoverable Severe: these are unrecoverable errors that results in a reset Description  LOGGING SYSTEM LEVEL The Logging feature is configured at the system level of logging. There are four different log levels. When an log request is made. the logging module first checks for the priority of the log.

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

If this flag is set. and then restarts.  DISABLE DPO CHECK This flag specifies whether to check the DPO field value within the READ/WRITE/VERIFY/WRITE AND VERIFY command CDB. 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. the transition to the Active_Wait power condition state is enabled. If set to 1 (and Drive Spin-up Algorithm set to SPINUP ON NOTIFY PRIMITIVE – DRIVEPOWER or SPINUP ON NOTIFY PRIMITIVE – DRIVEPHY). If this flag is not set. when the device receives a SAS Target Reset (SAS Hard Reset primitive).  ENABLE ACTIVE WAIT This flag. with the Drive Spin-up Algorithm field. LSI Corporation Confidential | October 2010 Page 173 . If this flag is set and the Device State Machine is in the SATA_DRIVE_DOWN state. If set to 1.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 167: Mode Page 32h (Continued) BIT Byte 7 39:42 43:44 45-46 6 5 4 3 2 1 0 00000005h 006Eh 00h DEVICE QUALIFICATION FLAGS DSM SPINUP TIMEOUT RESERVED Default  CLEAN REBOOT This flag specifies whether to clean reboot the LSISS2520/LSISS2530 device or not. NOTE: Mode sense for this flag always returns 0.  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. the LSISS25x0 device disables checking of the DPO field value. See Section B. the firmware sends an Aborted by Device Server status for the commands which are present in queue. the firmware does nothing.1. Device State Machine for a description of the Device State Machine. controls the transition to the Active_Wait power condition state from the Stopped/Standby power condition state.

the LSISS2520/LSISS2530 device drives 1 to turn on the ready LED. When the bit is set to 1.  DISABLENON512ANDDIF It signifies Disable the Non 512 sector block size and DIF information. the LSISS2520/LSISS2530 device attempts to configure Mode page 35h SCT time-out values to the device if they are nonzero. — If TRUE. READ CAPACITY 16 works as it is. the LSISS2520/LSISS2530 device drives 0 to turn on the ready LED. Else the LSISS2520/LSISS2530 device attempts to configure Recovery timeout -1 sec value to the device.ILLEGAL REQUEST.  READYLEDACTIVESTATE When this bit field is set to 0. and WRITE (16) commands and is translated as WRITE AND VERIFY (10). This field is added for critical event simulation. Page 174 LSI Corporation Confidential | October 2010 .  MAX ALLOWED INITIATOR PER PORT This field specifies Max Initiators per Port for the LSISS2520/LSISS2530 device. the Check Condition .  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. WRITE (12).  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 field ranges from 1 to 4.  PANIC ON SAS LINK LOSS This firmware flag specifies whether to panic on SAS LINK LOSS event.  LEGACYINITIATORDISABLE This bit flag disables the support for Legacy Initiators. This is applicable only to WRITE (10). The Flag is set by default to disable Non-512 byte mode and DIF. WRITE AND VERIFY (12). If set to 1b. — If FALSE. When this flag is set. the LSISS2520/LSISS2530 device attempts to configure Mode page 35h SCT time-out values to the device if they are nonzero.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  ALTERNATESCTTIMEOUTBEHAVIOUR This flag identifies the behavior for the LSISS2520/LSISS2530 device to program SCT time-out on the device. and the ASC set to INVALID FIELD in CDB is sent out for READ CAPACITY 10 command. The default value is set to 04h by default. the LSISS2520/LSISS2530 device panics when SAS Link goes down else it brings up the SAS Links and continues execution normally. and WRITE AND VERIFY (16) commands.

Therefore.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  QUEUE DEPTH This parameter specifies the command queue depth that the LSISS2520/LSISS2530 device supports.  DISABLE HOST PORT 1 When this bit field is set to 1. Device Name. this value is cleared to zero. the Host Port 0 is disabled.  DISABLE HOST PORT 0 When this bit field is set to 1. Port numbering is performed in bit 0 and bit 1 as determined by the OUI in the device's WWN. Type set to 1. The maximum and minimum allowable queue depth is 64 and 1 respectively. When this bit is set to 0. When this bit is set to 0. because it loads the customer-specific default values for all values. the Target Port Identifiers. In addition. TYPE This field specifies the WWN generation algorithm that is used by the LSISS2520/LSISS2530 device. both DISABLE HOST PORT 1 and DISABLE HOST PORT 0 set to 1 (11) is not valid.  RESTORE TO FRESH MANUFACTURING When this bit field is set to 1 and SP is enabled. This bit value cannot be saved. Upon reboot. No other field values are saved in this mode page. Upon reboot. 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. using the WWN field of IDENTIFY DEVICE data). LSISS25x0 does not allow port 1 to be disabled if port 0 is already disabled and vice-versa. the LSISS2520/LSISS2530 device resets itself to fresh manufacturing config data values.0 specification (that is.  WWN GEN. This bit value cannot be saved. bit 1 is set for port 1. This setting is not recommended. then the Host Port 1 is enabled. TYPE Field Values Field 0 Description As specified in SAT 2. 1 LSI Corporation Confidential | October 2010 Page 175 . the Host Port 1 is disabled. When WNN Gen. this value is cleared to zero. 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. NOTE: The LSISS2520/LSISS2530 device does not allow both the host ports together in a disabled state. then the Host Port 0 is enabled. all logs and crash dumps are purged. In this mode. LSISS25x0 sends out a CC status with INVALID_FIELD_IN_PARAMETER_LIST for such request. and Logical Unit Name are derived from the programmed WWN value. Vendor-specific method (using the node name provided in the WWN field). The LSISS2520/LSISS2530 device requires a reboot for changes in the Queue Depth to take effect. Table 168: WWN GEN.

 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. For example. a value of 4 specifies 2 ^ 4 = 16 blocks to be written at once. the LSISS2520/LSISS2530 device initializes the blocks in the device with a user-defined pattern (if provided) or with a vendor-specific pattern. When a FORMAT UNIT command is received.  REPORT FORMAT CORRUPT This field specifies whether to report a Format Corrupt condition. — For WRITE/WRITESAME/FORMAT commands. The default value is set to 8 (that is. the LSISS2520/LSISS2530 device restarts on panic. If clear. the command time-out is calculated using the following equations: — For READ commands. this field is not considered and maximum possible blocks are initialized per command. This parameter defines the number of blocks to be initialized in one stretch. Table 169: VARIABLE Command Timeout Field Descriptions Field 0 1 Description Stick to command time-out specified in Mode page 01 for all commands 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. This flag indicates whether or not the LSISS2520/LSISS2530 device recalculates the command time-out. TimeoutValue = (TransferLength / 32) + command timeout specified in mode page 01. 256 blocks). it enters into diagnostic mode where diagnostics / management commands are performed through the console interface. This operation results in more than one command to the device depending upon the size of the device.  VARIABLE COMMAND TIMEOUT Command time-out could be configured if the LSISS2520/LSISS2530 device uses Mode page 01h. TimeoutValue = (TransferLength / 64) + command timeout specified in mode page 01. 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. If set. For the TIMEOUTVALUE calculation. when the Variable command time-out is set to TRUE.  REBOOT LSISS2520/LSISS2530 When this field is set to 1. This is measured in the units of powers of 2.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  REBOOT ON PANIC This field specifies whether to reboot on a Panic condition. the LSISS2520/LSISS2530 device restarts itself. Page 176 LSI Corporation Confidential | October 2010 . This field is used in conjunction with Reboot Type. This is a vendor-specific method for re-booting the LSISS2520/LSISS2530 device.

DRIVEPOWER SPINUP IMMEDIATE SPINUP ON STARTSTOP-DRIVEPHY SPINUP ON NOTIFY PRIMITIVE – DRIVEPHY RESERVED Meaning Apply device power on Notify Spinup primitive from initiator. the LSISS2520/LSISS2530 device ignores the changeable values mask while processing a mode select command. The following table shows the possible values for the field: Table 171: REBOOT OPTIONS AFTER FW UPGRADE Field Values Field 00 Description Deferred Reboot (The initiator has to do an explicit mode select /console command to reboot the LSISS2520/LSISS2530 device after completing the firmware upgrade.) Clean reboot after firmware upgrade (Firmware sends an aborted by device server status for the commands in queue and then restarts). Spinup as soon as the device is powered. RESERVED 01 10 11 LSI Corporation Confidential | October 2010 Page 177 . Immediate reboot after the firmware upgrade (Firmware restarts on its own as soon as the firmware upgrade completes. Start OOB to device on Start stop unit command from initiator Start OOB to device on reception of Notify primitive from initiator RESERVED  IGNORECHANGABLEVALUES If this bit is set to 1. Table 170: DEVICE SPIN-UP ALGORITHM Values Value 0x0 0x1 0x2 0x3 0x4 0x5 to 0xF Acronym SPINUP ON NOTIFY PRIMITIVE -DRIVEPOWER SPINUP ON STARTSTOP . Apply device power on Start stop unit command from initiator.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  DEVICE SPIN-UP ALGORITHM This parameter controls how the SATA device spins after the LSISS2520/LSISS2530 device is powered up. The field is two bits long.  REBOOT OPTIONS AFTER FW UPGRADE This field specifies the action taken by the LSISS2520/LSISS2530 device after a firmware upgrade.) This is the default value for the field.

Reboot After firmware upgrade flag Clean reboot/Immediate reboot as per Mode Page 32 . Page 178 LSI Corporation Confidential | October 2010 .  RESTORE_DEFAULTS When this bit is set. The range for this field is 250 ms to 4 seconds.  WORLD WIDE NAME PROGRAMMED This field specifies the world wide node name.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 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 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). The default time-out is 14 sec. which the LSISS2520/LSISS2530 device uses when reporting the Node Name in Inquiry data (that is.  WATCH DOG TIMEOUT VALUE This field is specified in units of 250 milliseconds. The default value is 4 (which is 1 second).Reboot After firmware upgrade flag Behavior 1 0 1 nonzero — 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.  COMMAND TIMEOUT FOR PACKAGE UPGRADE (in sec) The command time-out values are specified in seconds for Package upgrade. The following table illustrates the LSISS25x0 devices’ s reset behavior: Table 172: LSISS25x0 Reset Behavior Options Reset Flag in Package 0 0 0 nonzero Mode Page 32 – Reboot After Firmware Upgrade Flag No reboot Deferred reboot/Clean reboot/Immediate reboot as per Mode Page 32 . VPD page 83h Device Identification Page).Reboot After firmware upgrade flag Deferred reboot/Clean reboot/Immediate reboot as per Mode Page 32 .

 WORLD WIDE NAME FROM DEVICE This is the World Wide Name supplied by the device. Each bit is meaningful for a different customer. If the device does not support those features. LSI Corporation Confidential | October 2010 Page 179 . This field is read-only. the Start bit is set and the Immediate bit is reset.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 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. The field is Don't Care when a mode select operation is performed. Otherwise the LSISS2520/LSISS2530 device uses the node name from its nonvolatile memory that has been constructed from the device's WWN. in the Start Stop Unit CDB.  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. Table 173: Supported Features Bit 0 1 2 3 4 5 Device Supports NCQ Device Supports SCT Device Supports ATA7 Device Supports ATA8 Device Supports SMART Device has a Valid WWN Feature  DSM SPINUP TIMEOUT This field specifies the Spinup time-out for LSISS2520/LSISS2530 device's drive state machine in seconds.  CUSTOMER This field is a customer specific value. The value programmed in this field is also used as the command time-out value for the Start Stop Unit command when. it enters the DRIVE_DOWN state in the device state machine and logs an error message. The field is Don't Care when a mode select operation is performed. Setting this value to a nonzero changes the behavior of the LSISS2520/LSISS2530 device for a specific customer.  DEVICE QUALIFCATION FLAGS This field determines which features a device must support in order to come ready on the LSISS2520/LSISS2530 device. Which bit has meaning for which customer is defined elsewhere.

1 Mode Page 32 – Subpage 1 The following section describes Mode Page 32 . When this value is 0. the LSISS25x0 device sends out the vendor-specific debug sense information in the sense data in the format specified in Section 3. When this flag is set.  WRITE COMMAND TIMEOUT This field indicates the command time-out value for all Write or Write as Write Verify Commands in milliseconds.Subpage 1. The default time-out is 0 ms.16. Table 174: Mode Page 32h Subpage 1 – Firmware Parameter Control Subpage 1 BIT Byte 7 0 1 2:3 4:5 6:7 8:9 10 PS 6 SPF(1b) 5 4 3 2 1 0 F2h 01h 00h 14h 0000h 0000h 00h CUSTOMER SPECIFIC BEHAVIOUR ENABLE DEBUG SENSE INFORMATION 00h PAGE CODE = 32h SUBPAGE CODE (01h) PAGE LENGTH (0014h) READ COMMAND TIMEOUT WRITE COMMAND TIMEOUT WRITE VERIFY COMMAND TIMEOUT RESERVED Default 11:12 13:14 15:16 17:23 DRIVE INITIALIZATION TIMEOUT DRIVE HARD RESET TIME DELAY DRIVE POWER DOWN RESET TIME DELAY RESERVED 00FAh 00FAh 03E8h 00h  READ COMMAND TIMEOUT This field indicates the command time-out value for all Read Commands in milliseconds.1. When this value is 0. The default time-out is 0 ms. the default Write or Write as Write Verify commands time-out value is considered as the RECOVERY TIME LIMIT value in Mode page 1h. Page 180 LSI Corporation Confidential | October 2010 . Error Reporting Codes.  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. The default time-out is 0 ms. the default 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 Read commands time-out value is considered as the RECOVERY TIME LIMIT value in Mode page 1h. When this value is 0.13.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5.

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  DRIVE INITIALIZATION TIMEOUT This field indicates the time-out in milliseconds for the Drive Initialization Sequence. The minimum supported values and maximum supported values are 1000 milliseconds and 8000 milliseconds respectively.  CUSTOMER SPECIFIC BEHAVIOUR If this field is set.  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 and maximum supported values are 250 and 8000 milliseconds respectively. 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. Table 175: Mode Page 33h BIT Byte 7 0 1 2 3 4 5 6 7 PS 6 SPF(0b) 5 4 3 2 1 0 B3h 06h SkewAlgori thm 70h 08h 00h 00h 00h 00h PAGE CODE = 33h PAGE LENGTH = o6h RESERVED Stripe Size RESERVED RESERVED RESERVED RESERVED Default LSI Corporation Confidential | October 2010 Page 181 . The mode page is accessible only if the DISABLENON512ANDDIF field within mode page 32h is set to 0. Otherwise.1. 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 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. 5. The minimum supported values and maximum supported values are 250 milliseconds and 8000 milliseconds respectively.14 Mode Page 33h (Sector Skewing Support Parameter Page) This mode page is a vendor-specific mode page for configuring the sector skewing capabilities of the LSISS2520/LSISS2530 device.

Mode Select commands with any other sector skewing combinations are terminated with a Check Condition status. 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.  Sparse Mode — 520 bytes Logical Blocks with 8/16/32/64/116 blocks stripes on 512 bytes sector sized SATA device. — 4104 bytes Logical Blocks on 4096 bytes sector sized SATA device. — 528 bytes Logical Blocks with 8/16/32/64 blocks stripes on 512 bytes sector sized SATA device.  Stripe Size – This field is applicable only in Sparse Mode. 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. Once the Format Corrupt condition is cleared. 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. — 4104 bytes Logical Blocks with 8/16/32/64/116 blocks stripes on 4096 bytes sector sized SATA device. then the following commands are terminated with the Check Condition status. theses commands are processed normally. This field specifies the count of logical blocks after which the LSISS2520/LSISS2530 device leaves the remaining bytes (in the physical sector) unused. with SENSE KEY set to ILLEGAL REQUEST and ASC set to INVALID FIELD IN PARAMETER LIST. The LSISS2520/LSISS2530 device supports the following sector skewing configurations:  Packed Mode — 520/528 bytes Logical Blocks on 512 bytes sector sized SATA device.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  Skew Algorithm – This field specifies the mode for sector skewing. Page 182 LSI Corporation Confidential | October 2010 . — Sparse Mode (1) – logical blocks (as seen by the initiator) are not placed in consecutive physical blocks in the drive.

FW does not program a value in this range. Table 177: SATA DATA FIFO THRESHOLD Field Descriptions Field 00h-13h 14h 15h 16h Description Not a valid value.  SATA MAX RETRY (On R_ERR) This field indicates the maximum number of attempts to send the same FIS to the device.  SATA DATA FIFO THRESHOLD This field specifies the Command Buffer Manager's FIFO limit. The legal values for this field range between 0 to 3. BIT Byte 7 0 1 2 3 4 5 6 7 8 PS 6 SPF(0B) 5 4 3 2 1 0 B4h 12h 00h 00h 0x02 30h 20h 20h RESET LINK RESET LINK ON ON RECEIVE TRANSMIT TIMEOUT TIMEOUT RESERVED 03h PAGE CODE = 34H PAGE LENGTH = 12H SATA LINK RETRY LIMIT RESERVED SATA MAX RETRY (ON R_ERR) SATA DATA FIFO THRESHOLD SATA LINK TRANSMIT TIMEOUT SATA LINK RECEIVE TIMEOUT RESERVED Default 9:19 00h  SATA LINK RETRY LIMIT This field specifies the maximum number of Link Retries.15 Mode Page 34h (SATA Link Configuration) Table 176: Mode Page 34h This mode page is a vendor-specific mode page for configuring the SATA Link present in the LSISS2520/LSISS2530 device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 5. The Field is non-changeable field and the value is set to 0.1. 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. Free space at 20 DWORDs Free space at 21 DWORDs Free space at 22 DWORDs LSI Corporation Confidential | October 2010 Page 183 .

Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 177: SATA DATA FIFO THRESHOLD Field Descriptions (Continued) Field ..  RESET LINK ON RECEIVE TIMEOUT This field specifies that the SATA Link be reset upon expiration of SATA LINK RECEIVE TIMEOUT. the SATA Link Reset is required and hence. the SATA link is reset after successful mode select to this page.. 3Eh 3Fh . since the SATA link might time out because of SAS congestion. Free space at 62 DWORDs Free space at 63 DWORDs Description  SATA LINK TRANSMIT TIMEOUT This field specifies the SATA Link Transmit\Receive State Machine time-out. Table 179: SATA LINK RECEIVE TIMEOUT Field Descriptions Field 0 1 0xff Disabled 32msec 8..16 sec Description  SATA LINK RECEIVE TIMEOUT This field specifies the SATA Link Receive State Machine time-out... Table 178: SATA LINK TRANSMIT TIMEOUT Field Descriptions Field 0 1 0xff Disabled 32msec 8.. The value needs to be configured in terms of 32msec steps.. Page 184 LSI Corporation Confidential | October 2010 .16 sec Description NOTE: For these parameters to take effect.  RESET LINK ON TRANSMIT TIMEOUT This field specifies that the SATA Link is reset upon expiration of SATA LINK TRANSMIT TIMEOUT. The value needs to be configured in terms of 32msec steps. Setting of this flag is not recommended.

 ALLOW STANDBY This flag allows the LSISS2520/LSISS2530 device to enter a low power state. SCT Read Error recovery timer is disabled if the value is zero.  SKIP HARD RESET This parameter instructs the LSISS2520/LSISS2530 device not to issue hard resets when doing error handling.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters 5. then it remains until the LSISS2520/LSISS2530 device is power cycled.1.  SKIP POWER CYCLE This parameter instructs the LSISS2520/LSISS2530 device not to power cycle the device when doing error handling. BIT Byte 7 0 1 2 RESERVED RESERVED ALLOW STANDBY PS 6 SPF(0B) 5 4 3 2 1 0 B5h 0Ah SKIP SOFT RESET STAY IN DEVICE DOWN STAY IN SYS DOWN 27h PAGE CODE = 35H PAGE LENGTH = 0AH SKIP POWER SKIP HARD CYCLE RESET Default 3:4 5:6 7:11 SCT READ ERROR RECOVERY TIMEOUT SCT WRITE ERROR RECOVERY TIMEOUT RESERVED 00h 00h 00h  STAY IN SYS DOWN FLAG This parameter specifies if the LSISS2520/LSISS2530 device enters a system down state. This is in the units of 100 milliseconds. 2 = 200 ms). (1 = 100 ms. stay there until chip reset or console command is received.  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. LSI Corporation Confidential | October 2010 Page 185 .16 Mode Page 35h (SATA Queuing and Error Recovery) Table 180: Mode Page 35h This mode page is a vendor-specific mode page for configuring SATA Queuing behavior and Error Recovery Timeout.  SKIP SOFT RESET This parameter instructs the LSISS2520/LSISS2530 device not to issue Soft Reset when doing error handling.  STAY IN DEVICE DOWN FLAG This flag specifies that if the device enters device down state.

2=200 misc. Table 182: PHY EVENT SOURCE SELECTION Values PHY Event Source Field 0x00 0x06 0x20 0x21 No PHY Event Source Received Error Count Received Address Frame Error Count Transmitted Abandon-Class OR Count Description Page 186 LSI Corporation Confidential | October 2010 . NOTE: In order to exercise the Read Error Recovery Timeout and Write Error Recovery Timeout. Else.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  SCT WRITE ERROR RECOVERY TIMEOUT This parameter configures the SCT WRITE ERROR RECOVERY TIMEOUT of the SATA device. This parameter is composed of 4 one-byte fields. The legal values for this field are described in the following table. 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.). LSISS2520/2530 device sends a check condition with the sense key. and is ATA8 compliant.1. the connected SATA device must support Smart Command Transfer (SCT). 5. SCT Write Error recovery timer is disabled if the value is zero. PHY EVENT SOURCE SELECTION RESERVED  SAS MAX TRANSMIT FRAME COUNT This parameter specifies the Maximum frames to transmit per connection.17 Mode Page 36h (SAS Link Configuration) Table 181: Mode Page 36h BIT Byte 7 0 1 2 3 4:5 6 7:8 9:12 13 PS 6 SPF(0b) 5 4 3 2 1 0 B6h 0Ch 00h 00h 00h 0x00h 00h 00h 00h PAGE CODE = 36h PAGE LENGTH = 0CH RESERVED SAS MAX TRANSMIT FRAME COUNT RESERVED Default This mode page is a vendor-specific mode page for configuring the SAS Links in the LSISS2520/LSISS2530 device. This is in the units of 100 milliseconds (1=100 ms. where each byte corresponds to a specific PHY Event Source. INVALID FIELD IN CDB PARAMETER LIST.

Transmitted SSP frame count.1. 5.18 Mode Page 37h (Firmware Debug Mode Page) Table 183: Mode Page 37h BIT Byte 7 0 1 2 3 4:7 (MSB) LOG CODE (LSB) 8:11 (MSB) PARAMETER 1 (LSB) 12:15 (MSB) PARAMETER 2 (LSB) 00h 00h RESERVED PS 6 SPF RESERVED PARAMETER COUNT 5 4 3 2 1 0 B7h 0Eh 00h 02h 00h PAGE CODE = 37h PAGE LENGTH = 0Eh Default This section describes Mode Page 37h. to select Transmitted Abandon-Class OR Count. PHY Event Source Selection is set to 0x21224041. LSI Corporation Confidential | October 2010 Page 187 . and Received SSP frame count.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 182: PHY EVENT SOURCE SELECTION Values (Continued) PHY Event Source Field 0x22 0x23 0x24 0x25 0x26 0x40 0x41 Description Received Abandon-Class OR Count Transmitted Retry-Class OR Count Received Retry-Class OR Count Received AIP (WAITING ON PARTIAL) count Received AIP (WAITING ON CONNECTION) count Transmitted SSP frame count Received SSP frame count For example. Received Abandon-Class OR Count.

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters The following table shows the PHY Specific Settings for SAS PHYs. refer to Section A.2.1. The receiver loss of signal input amplitude adjustment control For further reading.1 (April 2009). TX post-emphasis. For further reading.2. TX Termination Trimming Program. TX emphasis/de-emphasis selection. Force SSC. MODE TERM_SEL RESERVED 6 5 4 RESERVED TX AMPLITUDE ALL SPEEDS 3 2 1 0 0x00 0x0D 0x00 0x84 0x4C 0xA1 0x00 0x20 0x03 0x13 0x00 Default TERMT_REG Table 186: Field Descriptions for SAS PHYS Field Description Reference For further reading. Table 185: PHY Specific Settings for SAS PHYS BIT Byte 7 0 1 2 3 4 5 6 7 8 9 10:15 RX CT-DFE SEL.3 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. refer to Section A.1. Manual V1.2. refer to Section A. RX termination selection. Tx PLL Zeros Tx PLL Poles For further reading.2. TX termination selection.1 (April 2009). RX Termination Trimming Program.1 (April 2009). refer to Section A.1.2 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. Termination trimming mode selection.1.1.1 (April 2009).7 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. For further reading. TX pre-emphasis.8 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. ENABLESSC FORCESSC TXCTRLI TX POST-EMPHASIS FOR ALL SPEEDS TX PRE-EMPHASIS REF50T REF50R TERM_SEL TERMT_REG TERMR_REG TZ TP LOSADJ Enable SSC.2. For further reading.2. LSI Corporation Confidential | October 2010 Page 189 . refer to Section A.1 (April 2009).1. RESERVED ENABLESSC RESERVED FORCESSC TXCTRLI RESERVED RESERVED RESERVED TX PRE-EMPHASIS TERMR_REG RESERVED LOSADJ RESERVED RX POLE/GAIN RESERVED RX ZERO/POLE RESERVED REF50T TX POST-EMPHASIS FOR ALL SPEEDS REF50R RESERVED TZ TP RISEFALL RX CT-DFE RATE RX EQ. PD RX EQ.1 (April 2009). refer to Section A. TX AMPLITUDE ALL SPEEDS Transmit driver peak-to-peak differential voltage swing.1 of the LSISS2520 SAS-SATA Bridge Reference Manual V1.6 of sets the threshold at which the receiver detects a Receiver Loss of the LSISS2520 SAS-SATA Bridge Reference Signal status.

For further reading.5G TX POST-EMPHASIS FOR 6G SATA TX POST-EMPHASIS FOR 1. RX Linear EQ Zeros.1.2 Mode Page 39 Subpage1 The following table shows the Mode Page 39 Subpage 1 Format for SATA Phys.5 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. 5.4 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. Table 188: PHY Specific Settings for SATA PHYS BIT Byte 7 0 1 2 3 4 5 6 7 RESERVED RESERVED ENSSC TXCTRLI 6 RESERVED TX AMPLITUDE FOR 3G RESERVED TX POST-EMPHASIS FOR 3G SATA TX PRE-EMPHASIS TERMR_REG RESERVED LOSADJ RESERVED RESERVED REF50T 5 4 3 2 1 0 0x0C 0xDB 0x04 0x42 0x4C 0xA1 0x00 0x20 TX AMPLITUDE FOR 6G TX AMPLITUDE FOR 1.2.1 (April 2009). RX CT-DFE Adaptive Equalization Select. refer to Section A. RX Linear EQ Poles. PD RX CT-DFE SEL RX CT-DFE RATE RX POLE/GAIN RX ZERO/POLE RX Equalizer Mode.1.2. Reference For further reading.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 186: Field Descriptions for SAS PHYS (Continued) Field RISEFALL Description The transmitter (TX) slew rate (rise/fall times). Equalizer Adaptation Powerdown.19.1 (April 2009).5G SATA REF50R TERMT_SEL TZ TP RISEFALL TERMR_SEL Default TERMT_REG RESERVED Page 190 LSI Corporation Confidential | October 2010 . RX EQ MODE RX EQ. refer to Section A.1. RX CT-DFE Adaptive Equalization Rate. Table 187: Mode Page 39 Subpage 1 Format for SATA PHYS BIT Byte 7 0 1 2:3 4:5 6:21 PS 6 SPF(1b) 5 4 3 2 1 0 F9h 01h 00h 12h 00h PAGE CODE (39h) SUBPAGE CODE (01h) PAGE LENGTH RESERVED PHY SPECIFIC SETTINGS FOR SATA PHY Default The following table shows the PHY Specific Settings for SATA Phys.

1 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. refer to Section A.1.1 (April 2009) TX emphasis/de-emphasis selection.1.1 (April 2009) RX EQ MODE RX EQ. refer to Section A. RX Termination Trimming Program. refer to Section A.1. PD RX CT-DFE SEL RX CT-DFE RATE RX POLE/GAIN RX ZERO/POLE LOSADJ RX Equalizer Mode.8 of the LSISS2520 SAS-SATA Bridge Reference Manual V1.3 of the LSISS2520 SAS-SATA Bridge Reference Manual V1.1.1. refer to Section A. RX termination selection. PD RX EQ. TX post-emphasis for a given link speed Description Transmit driver peak-to-peak differential voltage swing for the specified Link Speed. 6 5 RESERVED RX POLE/GAIN RESERVED RX ZERO/POLE 4 3 2 1 RX CT-DFE RATE 0 RX EQ.1. Equalizer Adaptation Powerdown.1.1.1.4 of the LSISS2520 SAS-SATA Bridge Reference Manual V1.1 (April 2009) For further reading.1.1. For further reading.1 (April 2009) REF50T REF50R TERMT_SEL TERMR_SEL TERMT_REG TERMR_REG ENSSC LSI Corporation Confidential | October 2010 Page 191 .1. (April 2009) TX termination selection.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters Table 188: PHY Specific Settings for SATA PHYS BIT Byte 7 8 9 10:15 RX CT-DFE SEL. RX CT-DFE Adaptive Equalization Rate. RX Linear EQ Zeros.5G TXCTRLI TX PRE-EMPHASIS TX POST-EMPHASIS FOR 6G SATA TX POST-EMPHASIS FOR 3G SATA TX POST-EMPHASIS FOR 1. refer to Section A. TX Termination trimming mode selection. RX Linear EQ Poles. refer to Section A.6 of the adjustment control sets the threshold at which the LSISS2520 SAS-SATA Bridge Reference Manual V1. TX pre-emphasis. For further reading.1 receiver detects a Receiver Loss of Signal status.1. RX Termination trimming mode selection TX Termination Trimming Program.1 (April 2009) For further reading.1.2 of the LSISS2520 SAS-SATA Bridge Reference Manual V1.5G SATA TZ TP RISEFALL Tx PLL Zeros Tx PLL Poles The transmitter (TX) slew rate (rise/fall times). refer to Section A. RX CT-DFE Adaptive Equalization Select. Enable SSC.1.5 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. MODE 0x03 0x13 0x00 Default The following table shows the Mode Page 39 Subpage1 field descriptions Table 189: Mode Page 39 Subpage1 Field Descriptions Field TX AMPLITUDE FOR 6G TX AMPLITUDE FOR 3G TX AMPLITUDE FOR 1. Reference For further reading.1.1 (April 2009) For further reading. The receiver loss of signal input amplitude For further reading.7 of the LSISS2520 SAS-SATA Bridge Reference Manual V1. refer to Section A.1 (April 2009) For further reading.

19. Table 191: PHY Test Specific Settings BIT Byte 7 0:3 4 5 6 7 8:10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29:31 RESERVED 6 5 4 RESERVED PhyIdentifier PhyTestFunction PhyTestPattern PhyTestFuncSSC RESERVED PhyTestPatternDwordControl PhyTestPatternDword0 PhyTestPatternDword1 PhyTestPatternDword2 PhyTestPatternDword3 PhyTestPatternDword4 PhyTestPatternDword5 PhyTestPatternDword6 PhyTestPatternDword7 PhyTestPatternDword8 PhyTestPatternDword9 PhyTestPatternDword10 PhyTestPatternDword11 PhyTestPatternDword12 PhyTestPatternDword13 PhyTestPatternDword14 PhyTestPatternDword15 PhyTestControl RESERVED PhyTestFunctionRate 3 2 1 0 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h Default Page 192 LSI Corporation Confidential | October 2010 .1. Table 190: Mode Page 39 Subpage 2 Format for PHY Testing BIT Byte 7 0 1 2:3 4:35 PS 6 SPF(1b) 5 4 3 2 1 0 79h 02h 0024h — PAGE CODE (39h) SUBPAGE CODE (02h) PAGE LENGTH PHY SPECIFIC TEST PATTERN SETTINGS Default The following table shows the PHY Test Specific settings.3 Mode Page 39 Subpage 2 The following table shows the Mode Page 39 Subpage 2 format for PHY testing.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5.

with Sense Key set to ILLEGAL REQUEST. this field controls the disparity of the JTPAT pattern. — 0x00 – SAS Port 0 — 0x01 – SAS Port 1 — 0x02 – SATA Port  PhyTestFunction This field specifies the action to perform on the selected PHY.0Gb/s  PhyTestPatternDwordControl When the PhyTestPattern field is set to 0x01 (JTPAT). 0x00 . — 0x01 – Transmit Pattern. 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. This is the only currently supported value for this field is 0x00.  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.  PhyTestFunctionRate This field specifies the physical link rate at which the phy test function is performed: — 0x08 – 1. The selected PHY transmits the PHY test pattern specified by the PhyTestPattern field at the physical link rate specified by the PhyTestFunctionRate field. — 0x55 – Negative Disparity (JTPAT-) — 0xAA – Positive Disparity (JTPAT+) LSI Corporation Confidential | October 2010 Page 193 .5Gb/s — 0x09 – 3.0Gb/s — 0x0A – 6. — 0x00 – Stop. the LSISS2520/LSISS2530 device terminates the Mode Select command with Check Condition status.No SSC. The selected PHY stops performing a PHY test function and originates a chip reset. 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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters NOTE: You cannot save Mode Page 39h Subpage 2.

BIT Byte 7 0 1 2 3 4 5 6:7 DISABLE SATA LINK COM-RESET PS 6 SPF(0B) 5 4 3 2 1 0 BAh 06h 00h 01h 00h 00h 00h PAGE CODE = 3AH PAGE LENGTH = 06H RESERVED SATA MAX LINK SPEED SATA MIN LINK SPEED SATA NEGOTIATED SPEED RESERVED Default Following are the meanings of the various fields within this mode page:  DISABLE SATA LINK If set. 5. This field is not saved to the nonvolatile memory and read to this bit always returns zero.  COM-RESET If set.  PhyTestControl This field is not used for the currently implemented functionality. the SATA link is disabled otherwise enabled.20 Mode Page 3Ah (SATA Link Control) Table 192: Mode Page 3Ah This is a vendor-specific mode page to control the SATA Link present in the LSISS2520/LSISS2530 device. Page 194 LSI Corporation Confidential | October 2010 .5G 3.0G Speed The field values from 2 to 7 are reserved.  SATA MAX and MIN LINK SPEED These fields are saved to the nonvolatile memory and define the maximum and minimum SATA link speeds.Chapter 5: SCSI Parameters | Mode Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  PhyTestPatternDWord(0 to 15) These fields are not used for the currently implemented functionality. the SATA link undergoes the reset cycle.1. This field is saved to a nonvolatile memory.: Table 193: SATA MAX and MIN LINK SPEED Values Value of Field 0 1 2 1.0G 6.

Following are the meanings of the various fields within this mode page. The values are returned as per the previous table. Else the soft reset if any is processed. 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.  POWER ON/OFF This bit is set/cleared by using a MODE SELECT command to power ON or power OFF the device respectively. 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.21 Mode Page 3Bh (Device Control) Table 194: Mode Page 3Bh BIT Byte 7 0 1 2 3:7 POWER ON/OFF SOFT RESET HARD RESET RESERVED PS 6 SPF(0B) 5 4 3 2 1 0 3Bh 06h RESERVED 80h 00h PAGE CODE = 3BH PAGE LENGTH = 06H Default This is a vendor-specific mode page to control the device connected to the LSISS2520/LSISS2530 device. This is valid only for Mode Sense and ignored in case of Mode Select. The fields within this mode page are not saved to a nonvolatile memory. Else the device resets if any are processed. if set. — 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.  SOFT RESET If set.  HARD RESET If set. 5. — The hard reset takes a higher priority than the soft reset. a COMRESET to the device is initiated and read to this bit always returns zero. 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.1. device in ON and vice versa.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Mode Parameters  SATA NEGOTIATED SPEED This field indicates the negotiated SATA link speed. While doing a MODE SENSE. LSI Corporation Confidential | October 2010 Page 195 . 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. this bit indicates whether the device is ON or OFF. a soft reset to the device is initiated and read to this bit always returns zero.

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

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

 TOTAL REPEATED COMMANDS This field specifies the total commands that are repeated for processing (Rewrites). 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 WITH POSSIBLE DELAYS This field specifies the number of Errors corrected with substantial delay 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 ERRORS CORRECTED This field specifies the total number of Errors corrected for write type commands.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 196: Write Error Counter Log Page (Continued) Bit Byte 7 38 39 40:43 44:45 (MSB) PARAMETER CODE = 0005H TOTAL BYTES PROCESSED (LSB) 46 47 48:51 52:53 (MSB) PARAMETER CODE = 0006H TOTAL UNCORRECTED ERRORS (LSB) 54 55 56:59 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL UNCORRECTED ERRORS = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL BYTES PROCESSED = 0000 DU = 0 6 DS = 0 5 TSD = 0 4 ETC = 0 3 TMC = 0 2 1 LBIN = 0 0 LP = 0 PARAMETER LENGTH (04H) TOTAL TIMES CORRECTION ALGORITHM PROCESSED = 0000 Currently. Page 198 LSI Corporation Confidential | October 2010 .  ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY This field specifies the number of Errors corrected without any delay for write type commands.

5.2.3 Log Page 03h (Read Error Counter) Table 197: Read Error Counter Log Page This log page contains the counters for read errors. BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 38H (LSB) 4:5 (MSB) PARAMETER CODE = 0000H ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY (LSB) 6 7 8:11 12:13 (MSB) PARAMETER CODE = 0001H ERRORS CORRECTED WITH POSSIBLE DELAYS (LSB) 14 15 16:19 20:21 (MSB) PARAMETER CODE= 0002H TOTAL REPEATED COMMANDS (LSB) 22 23 24:27 28:29 (MSB) PARAMETER CODE = 0003H TOTAL ERRORS CORRECTED (LSB) 30 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL REPEATED COMMANDS = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) DELAYED ERROR CORRECTED COUNT = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) ERROR CORRECTED WITHOUT SUBSTANTIAL DELAY = 0000 RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 03h LSI Corporation Confidential | October 2010 Page 199 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters  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.

 ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY This field specifies the number of Errors corrected without any delay for read type commands. the LSISS2520/LSISS2530 device does not support these PARAMETER CODE fields and hence the LSISS2520/LSISS2530 device returns default values 0000h for these fields. Page 200 LSI Corporation Confidential | October 2010 .  TOTAL ERRORS CORRECTED This field specifies the total number of Errors corrected for read type commands.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 197: Read Error Counter Log Page (Continued) BIT Byte 7 31 32:35 36:37 (MSB) PARAMETER CODE = 0004H TOTAL TIMES CORRECTION ALGORITHM PROCESSED (LSB) 38 39 40:43 44:45 (MSB) PARAMETER CODE = 0005H TOTAL BYTES PROCESSED (LSB) 46 47 48:51 52:53 (MSB) PARAMETER CODE = 0006H TOTAL UNCORRECTED ERRORS (LSB) 54 55 56:59 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL UNCORRECTED ERRORs = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL BYTES PROCESSED = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL TIMES CORRECTION ALGORITHM PROCESSED = 0000 6 5 4 3 2 1 0 PARAMETER LENGTH (04H) TOTAL ERRORS CORRECTED = 0000 Currently.  ERRORS CORRECTED WITH POSSIBLE DELAYS This field specifies the number of Errors corrected with substantial delay for read type commands.  TOTAL REPEATED COMMANDS This field specifies the total commands that are repeated for processing (Rereads).

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Chapter 5: SCSI Parameters | Log Parameters

TOTAL TIMES CORRECTION ALGORITHM PROCESSED This field specifies the total number of times the correction algorithm part was processed by the firmware for read type commands.

TOTAL BYTES PROCESSED 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 Counter) Table 198: Verify Error Counter Log Page

This log page contains the counters for verify errors.

BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 38H (LSB) 4:5 (MSB) PARAMETER CODE = 0000H ERRORS CORRECTED WITHOUT SUBSTANTIAL DELAY (LSB) 6 7 8:11 12:13 (MSB) PARAMETER CODE = 0001H ERRORS CORRECTED WITH POSSIBLE DELAYS (LSB) 14 15 16:19 20:21 (MSB) PARAMETER CODE = 0002H TOTAL REPEATED COMMANDS (LSB) 22 23 24:27 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL REPEATED COMMANDS = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) DELAYED ERROR CORRECTED COUNT = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) ERROR CORRECTED WITHOUT SUBSTANTIAL DELAY = 0000 RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 05H

LSI Corporation Confidential | October 2010

Page 201

Chapter 5: SCSI Parameters | Log Parameters

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 198: Verify Error Counter Log Page (Continued) BIT Byte 7 28:29 (MSB) PARAMETER CODE = 0003H TOTAL ERRORS CORRECTED (LSB) 30 31 32:35 36:37 (MSB) PARAMETER CODE = 0004H TOTAL TIMES CORRECTION ALGORITHM PROCESSED (LSB) 38 39 40:43 44:45 (MSB) PARAMETER CODE = 0005H TOTAL BYTES PROCESSED (LSB) 46 47 48:51 52:53 (MSB) PARAMETER CODE = 0006H TOTAL UNCORRECTED ERRORS (LSB) 54 55 56:59 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL UNCORRECTED ERRORs = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL BYTES PROCESSED = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL TIMES CORRECTION ALGORITHM PROCESSED = 0000 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (04H) TOTAL ERRORS CORRECTED = 0000 6 5 4 3 2 1 0

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.

ERROR CORRECTED WITHOUT SUBSTANTIAL DELAY This field specifies the Number of Errors corrected without any delay for verify type commands.

ERRORS CORRECTED WITH POSSIBLE DELAYS This field specifies the Number of Errors corrected with substantial delay for verify type commands.

Page 202

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Chapter 5: SCSI Parameters | Log Parameters

TOTAL REPEATED COMMANDS This field specifies the total verify commands that are repeated for processing.

TOTAL ERRORS CORRECTED This field specifies the total number of Errors corrected for Verify 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 verify type commands.

TOTAL BYTES PROCESSED 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 Error Log page)

The Non-Medium Error log page provides for summing the occurrences of recoverable 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 0 1 2:3 (MSB) PAGE LENGTH = 06H (LSB) 4:5 (MSB) PARAMETER CODE = 0000H NON MEDIUM ERROR COUNT (LSB) 6 7 8:9 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH (02H) NON MEDIUM ERROR COUNT= 0000 RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 06H

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.

LSI Corporation Confidential | October 2010

Page 203

Chapter 5: SCSI Parameters | Log Parameters

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

5.2.6 Log Page 0Dh (Temperature Log page)

Page 0Dh indicates the Temperature Log Page for the device connected to the 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 0 1 2:3 (MSB) PAGE LENGTH = 0CH (LSB) 4:5 (MSB) PARAMETER CODE = 0000H (LSB) TEMPERATURE 6 7 8 9 10:11 (MSB) PARAMETER CODE = 0001H (LSB) REFERENCE TEMPERATURE 12 13 14 15 DU = 0 DS = 1 TSD = 0 ETC = 0 RESERVED REFERENCE TEMPERATURE (°C) TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH(02H) DU = 0 DS = 1 TSD = 0 ETC = 0 RESERVED TEMPERATURE (°C) TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (02H) RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE(0DH)

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.

Page 204

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Chapter 5: SCSI Parameters | Log Parameters

5.2.7 Log Page 0Eh (Start Stop Cycle Counter Log page)

This log page defines the Start Stop Cycle Counter.

Table 201: Start Stop Cycle Counter Log Page Format BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 24h (LSB) 4:5 (MSB) PARAMETER CODE = 0001H (LSB) DATE OF MANUFACTURE 6 7 8:11 (MSB) YEAR OF MANUFACTURING (4 ASCII CHARACTERS) (LSB) 12:13 (MSB) WEEK OF MANUFACTURING(2 ASCII CHARACTERS) (LSB) 14:15 (MSB) PARAMETER CODE = 0002H (LSB) PARAMETER CODE ACCOUNTING DATE 16 17 18:21 (MSB) ACCOUNTING DATE YEAR (4 ASCII CHARACTERS) (LSB) 22:23 ACCOUNTING DATE WEEK (2 ASCII CHARACTERS) 24:25 (MSB) PARAMETER CODE = 0003H (LSB) PARAMETER CODE SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME 26 27 DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH(04H) DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 1 PARAMETER LENGTH(06H) DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 0 LP = 1 PARAMETER LENGTH (06H) RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE(0Eh)

LSI Corporation Confidential | October 2010

Page 205

Chapter 5: SCSI Parameters | Log Parameters

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 201: Start Stop Cycle Counter Log Page Format (Continued) BIT Byte 7 28:31 (MSB) SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME (4-BYTE BINARY NUMBER) (LSB) 32:33 (MSB) PARAMETER CODE = 0004H (LSB) ACCUMULATED START STOP CYCLE 34 35 36:39 (MSB) ACCUMULATED START STOP CYCLE(4 BYTE BINARY NUMBER) (LSB) DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH(04H) 6 5 4 3 2 1 0

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.

Page 206

LSI Corporation Confidential | October 2010

the data is vendor specific.8 Log Page 0Fh (Application Client Log page) Table 202: Application Client Log Page The intended use for this information is to aid in describing the system configuration and system problems.2. 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. BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 4000H (LSB) APPLICATION CLIENT LOG PARAMETERS 4 : 259 16132 : 16387 FIRST APPLICATION CLIENT LOG PARAMETER : : LAST APPLICATION CLIENT LOG PARAMETER : : RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 0FH Table 203: General Usage Application Client Log Parameter Data BIT Byte 7 0:1 (MSB) PARAMETER CODE (LSB) 2 3 4:255 DU = 1 DS = 0 TSD=0 ETC=0 TMC=0 LBIN = 1 LP = 1 PARAMETER LENGTH (FCH) GENERAL USAGE PARAMETER BYTES 6 5 4 3 2 1 0 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. Also the log parameters must be sent in sequentially ascending order in the LOG SELECT data. LSI Corporation Confidential | October 2010 Page 207 . The LSISS2520/LSISS2530 device supports the PARAMETER CODEs from 0000h to 01FFh.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters 5.

Table 204: Self-Test Results Log Page BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 190H (LSB) SELF-TEST RESULTS LOG PARAMETERS 4 : 23 384 : 403 FIRST SELF-TEST RESULTS LOG PARAMETER : : LAST SELF-TEST RESULTS LOG PARAMETER : : RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 10h The following table describes the self-test results log parameter structure. the unused self-test log parameter entries is 0. The results of the twenty most recent self-tests are stored in this Log page.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5.9 Log Page 10h (Self-Test Results Log Page) This log page contains the self-test results of the underlying device present in the LSISS2520/LSISS2530 device system. Table 205: LOG Sense Page 10h Log Parameter Structure BIT Byte 7 0:1 (MSB) PARAMETER CODE (LSB) 2 3 4 5 6:7 (MSB) ACCUMULATED POWER ON HOURS (LSB) 8:15 (MSB) ADDRESS OF FIRST FAILURE (LSB) 16 RESERVED SENSE KEY SELF TEST CODE DU = 0 DS = 0 TSD = 0 ETC = 0 RESERVED EXTENDED SEGMENT NUMBER TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (10H) SELF TEST RESULTS VALUE 6 5 4 3 2 1 0 Page 208 LSI Corporation Confidential | October 2010 .2. If fewer than 20 self-tests have occurred.

The self-test completed having a test element that failed and the test element that failed is not known. The Self-Test Results Value for this field is described in the following table. RESERVED The self-test is in progress.  ACCUMULATED POWER ON HOURS This field contains the total accumulated power-on hours of the drive at the time the self-test completed.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 205: LOG Sense Page 10h Log Parameter Structure (Continued) BIT Byte 7 17 18 19 6 5 4 ASC ASC QUALIFIER RESERVED 3 2 1 0  PARAMETER CODE This field identifies the log parameter for the log page. The parameter for the next most recent is 0002h. The background self-test routine was aborted by the initiator using a SEND DIAGNOSTIC command with the Abort Background self-test function. The first segment of the self-test failed. the LSISS2520/LSISS2530 device returns zero value in this field. Currently. this field is 00h. Description  EXTENDED SEGMENT NUMBER This field identifies the number of the segment that failed during self-test. LSI Corporation Confidential | October 2010 Page 209 . The third or greater segment of the self-test failed.  SELF-TEST CODE This field contains the content of the Function Code field in the SEND DIAGNOSTIC command that initiated this self-test. Table 206: Self-Test Results Value Value 0h 1h 2h 3h 4h 5h 6h 7h 8h to Eh Fh The self-test routine completed without error. The initiator aborted the self-test routine by a Task Management function of a reset. The second segment of the self-test failed. the LSISS2520/LSISS2530 device return zero value in this field. Currently. The PARAMETER CODE field for the results of the most recent test is 0001h. If no segment failed. An unknown error occurred while the target was executing the self-test routine and the target was unable to complete the self-test routine.

 SENSE KEY. ASC and ASC QUALIFIER These fields contains the additional information relating to the error or exception conditions during self-test.2.10 Log Page 15h (Background Scan Results Log page) This log page contains the Background Scanning Status parameter and Background Medium Scan parameters for the underlying device present in the LSISS2520/LSISS2530 device system. Table 208: Background Scan Results log page PARAMETER CODEs PARAMETER CODE 0000h 0001h to 0013h Description Background Scanning Status Background Medium Scan Page 210 LSI Corporation Confidential | October 2010 . then the field is FFFF FFFF FFFF FFFFh. Table 207: Extended Segment Number Extended Segment Number 0h 1h 2h 3h 4h 5h 6h 7h 8h 9h Ah Bh — NA LSISS2520/LSISS2530 device ready check RAM Test Spin Check Write/Read/Compare ECC Test Random Seek SMART Check Low Level Format Check Physical Head Check Read Scan SMART Check — Foreground Test NA LSISS2520/LSISS2530 device ready check NA Spin Check Write/Read/Compare ECC Test Random Seek SMART Check Low Level Format Check Physical Head Check Read Scan SMART Check — Background Test 5.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. 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 210: Background Scanning Status Parameter Format BIT Byte 7 0:1 (MSB) PARAMETER CODE (LSB) = 0000H (LSB) 2 3 4:7 (MSB) ACCUMULATED POWER ON MINUTES (LSB) 8 9 10:11 (MSB) NUMBER OF BACKGROUND SCANS PERFORMED (LSB) 12:13 (MSB) BACKGROUND MEDIUM SCAN PROGRESS (LSB) 14:15 RESERVED RESERVED BACKGROUND SCANNING RESULTS DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 00 LBIN = 1 LP = 1 PARAMETER LENGTH (0CH) 6 5 4 3 2 1 0 LSI Corporation Confidential | October 2010 Page 211 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters The following table shows the Background Scan Results Log Page. Table 209: Background Scan Results Log Page BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 1D8H (LSB) BACKGROUND SCAN RESULTS LOG PARAMETER 4:19 20:43 : 452:475 BACKGROUND SCANNING STATUS PARAMETER BACKGROUND MEDIUM SCAN PARAMETER LIST BACKGROUND MEDIUM SCAN PARAMETER (FIRST) : BACKGROUND MEDIUM SCAN PARAMETER (NINETEENTH) RESERVED RESERVED 6 5 4 3 2 PAGE CODE = 15H 1 0 The following table shows the Background Scanning Status Parameter format.

The LSISS2520/LSISS2530 device returns zero value in this field.0013H (LSB) 2 3 4:7 (MSB) ACCUMULATED POWER ON HOURS (LSB) 8 9 10 REASSIGN STATUS ASC ASC QUALIFIER SENSE KEY DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (14H) 6 5 4 3 2 1 0 Page 212 LSI Corporation Confidential | October 2010 . The LSISS2520/LSISS2530 device returns zero value in this field.  BACKGROUND MEDIUM SCAN PROGRESS This field is a percent complete indication of background indication. waiting for Background Medium Interval timer expiration RESERVED Description The following table shows the Background Medium Scan Parameter format.  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.vendor-specific cause Background medium scan halted because of temperature out of allowed range Background medium scan halted. Table 211: Background Scanning Status Code 00h 01h 02h 03h 04h 05h 06h 07h 08h 09h to FFh No background scans active Background medium scan is active Background pre-scan is active Background medium scan halted because of a fatal error Background medium scan halted because of a vendor-specific pattern of errors Background medium scan halted because of medium formatted without P-list Background medium scan halted .Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  ACCUMULATED POWER ON MINUTES This field indicates the number of minutes the device connected to the LSISS2520/LSISS2530 device is powered on since manufacturing. Table 212: Background Medium Scan Parameter Format BIT Byte 7 0:1 (MSB) PARAMETER CODE = 0001H .

• REASSIGN BLOCKS command. and contains valid data (For example.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 212: Background Medium Scan Parameter Format BIT Byte 7 11:15 16:23 (MSB) LOGICAL BLOCK ADDRESS (LSB) 6 5 4 RESERVED 3 2 1 0  BACKGROUND MEDIUM SCAN PARAMETER This field describes a defect location on the medium encountered by background scanning. The logical block specified by the LOGICAL BLOCK ADDRESS field failed. The logical block specified by the LOGICAL BLOCK ADDRESS field failed and was successfully reassigned by the SCSI target device with recovered data.  LOGICAL BLOCK ADDRESS This field indicates the LBA associated with the medium error. by a REASSIGN BLOCKS command that successfully recovered the data. ASC and ASC QUALIFIER These fields contains the additional information relating to the error or exception conditions during background scans.  SENSE KEY.  REASSIGN STATUS VALUE The LSISS2520/LSISS2530 device returns zero value in this field. RESERVED 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. if auto write reallocation is allowed. The logical block specified by the LOGICAL BLOCK ADDRESS field failed and was recovered by the SCSI target device through a rewrite in-place. Table 213: Reassign Status Values Code 0h 1h No Yes Reported RESERVED 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. Description 2h 3h 4h 5h 6h No RESERVED Yes No Yes LSI Corporation Confidential | October 2010 Page 213 .  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. or by command performing a write operation). was successfully reassigned by the initiator.

LAST ATA PASS THROUGH RESULTS LOG PARAMETERS RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 16h 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 0:1 (MSB) PARAMETER CODE (LSB) PARAMETER CONTROL 2 3 4 5 RESERVED = 0 DU= 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (16H) DESCRIPTOR FORMAT SENSE DATA RESPONSE CODE SENSE KEY 6 5 4 3 2 1 0 Page 214 LSI Corporation Confidential | October 2010 . (For example. Reassign block command that did not successfully recover the data.2.11 Log Page 16h (ATA PASS-THROUGH Results Log page) Log Page 16h reports descriptor format sense data for ATA PASS-THROUGH commands 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. Reassign block command that failed) RESERVED 5. 368:393 FIRST ATA PASS THROUGH RESULTS LOG PARAMETERS .. (For example..Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 213: Reassign Status Values (Continued) Code 7h 8h 9h Fh Yes Yes RESERVED Reported Description Logical block specified by the LOGICAL BLOCK ADDRESS field was successfully reassigned by the initiator but not contain valid value.) Logical block specified by the LOGICAL BLOCK ADDRESS field was not successfully reassigned by the initiator. Table 214: ATA PASS-THROUGH Results Log page Format BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH (LSB) ATA PASS THROUGH RESULTS 4:29 .

3.2. LSI Corporation Confidential | October 2010 Page 215 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 215: ATA PASS-THROUGH Results Log Parameter Format (Continued) BIT Byte 7 6 7 8:10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 6 5 4 3 2 1 0 ADDITIONAL SENSE CODE ADDITIONAL SENSE CODE QUALIFIER RESERVED = 0 ADDITIONAL SENSE LENGTH ATA RETURN DESCRIPTOR DESCRIPTOR CODE (09h) ADDITIONAL DESCRIPTOR LENGTH (0Ch) RESERVED ERROR SECTOR_COUNT (15:8) SECTOR_COUNT (7:0) LBA_LOW (15:8) LBA_LOW (7:0) LBA_MID (15:8) LBA_MID (7:0) LBA_HIGH (15:8) LBA_HIGH (7:0) DEVICE STATUS EXTEND  PARAMETER CODE This field indicates the value of the LOG INDEX field minus one.  ATA RETURN DESCRIPTOR See Section 4. ATA PASS THROUGH Status Return – Descriptor Format Sense Data.1. The device server supports log parameter codes 0h through Eh. returned in fixed format sense of ATA Pass through results command.

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 218: SAS-2 PHY Log Descriptor BIT Byte 7 6 7 8:15 16:23 24 25:31 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 48:50 51 52:63 … 100:111 PHY EVENT DESCRIPTOR (FIFTH) (MSB) PHY RESET PROBLEM (LSB) RESERVED NUMBER OF PHY EVENT DESCRIPTORS = 5 PHY EVENT DESCRIPTOR (FIRST) 6 RESERVED RESERVED 5 4 3 2 1 0 RESERVED RESERVED ATTACHED SSP ATTACHED STP ATTACHED SMP INITIATOR PORT INITIATOR PORT INITIATOR PORT ATTACHED SSP TARGET PORT SAS ADDRESS ATTACHED SAS ADDRESS ATTACHED PHY IDENTIFIER RESERVED ATTACHED STP TARGET PORT ATTACHED SMP TARGET PORT 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 0:2 3 4:7 8:11 6 5 4 RESERVED PHY EVENT INFORMATION SOURCE PHY EVENT INFORMATION PEAK VALUE DETECTOR THRESHOLD 3 2 1 0 LSI Corporation Confidential | October 2010 Page 217 .

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.  INFORMATIONAL EXCEPTION ASC If this field contains 0. Table 220: Informational Exceptions Log Page BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 08H (LSB) 4:5 (MSB) PARAMETER CODE = 0000H (LSB) 6 7 8 9 10 11 DU= 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH = 04H INFORMATIONAL EXCEPTION ASC INFORMATIONAL EXCEPTION ASC QUALIFIER MOST RECENT TEMPERATURE READING RESERVED RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 2Fh  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. the value returned is FFh. If the LSISS2520/LSISS2530 device cannot detect a valid temperature because of a sensor failure or other condition.2.13 Log Page 2Fh (Informational Exceptions Log page) This log page contains the SMART status and the Temperature reading of the underlying device present in the LSISS2520/LSISS2530 device system. If the INFORMATIONAL EXCEPTION ASC field contains any value other than 0. no informational exception condition is pending and contents of the INFORMATIONAL EXCEPTION ASC QUALIFIER field are unspecified. Page 218 LSI Corporation Confidential | October 2010 . Temperatures equal to or less than 0 degrees Celsius is indicated by a value of 0.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5.

 DISPARITY ERROR COUNT SATA disparity error count. Table 221: SATA Link Errors Log Page BIT Byte 7 0 1 2:3 4:5 6 7 8:9 10:11 12:13 14:15 16:19 20:21 22:23 24:25 26:27 28:29 30:31 32:33 34:35 DU = 0 DS = 1 RESERVED RESERVED PAGE LENGTH = 20H PARAMETER CODE = 0000H TSD = 0 ETC = 0 RESERVED RECEIVE ERROR COUNT RESERVED TRANSMIT ERROR COUNT LINK DOWN COUNT RESERVED DISPARITY ERROR COUNT RESERVED INVALID DWORD COUNT RESERVED LOSS OF DWORD SYNC COUNT RESERVED SPEED NEGOTIATION ERROR COUNT TMC = 0 LBIN = 0 LP = 0 PARAMETER LENGTH = 1CH 6 5 4 3 PAGE CODE = 30H 2 1 0  RECEIVE ERROR COUNT SATA receive error count information.14 Errors) Log Page 30h (SATA Link This Log page is a vendor-specific log page for providing error details of underlying device present in the LSISS2520/LSISS2530 device system.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters 5. It increments when the device returns R_ERR for a FIS transmitted by the LSISS2520/LSISS2530 device.  TRANSMIT ERROR COUNT SATA transmit error count information.2.  LINK DOWN COUNT This field indicates the number of times the SATA link went down. LSI Corporation Confidential | October 2010 Page 219 . Specifies the number of running disparity errors detected in a DWORD. It counts for each error detected such that R_ERR is returned to the device for a FIS received from the device. All counters saturate at their maximum field value.

Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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. BIT BYTE 7 0 1 2:3 4:5 6 7 8:11 12:15 16:19 20:23 24:27 28:31 32:35 36:39 40:41 DU=0 DS=1 TSD=0 RESERVED RESERVED PAGE LENGTH = 3CH PARAMETER CODE = 0000H ETC=0 TMC=0 TMC=0 LBIN=0 LP=0 PARAMETER LENGTH = 38H NUMBER OF SCSI RESPONSES SENT NUMBER OF SCSI READ/WRITE REQUESTS NUMBER OF READS COMPLETED NUMBER OF WRITES COMPLETED NUMBER OF SATA I/O ERRORS NUMBER OF PHY RESETS (SATA) NUMBER OF PHY RESETS (SAS PORT A) NUMBER OF PHY RESETS (SAS PORT B) RESERVED 6 5 4 3 PAGE CODE = 32h 2 1 0 Page 220 LSI Corporation Confidential | October 2010 . Table 222: SMART Data Log Page BIT Byte 7 0 1 2:3 4:515 RESERVED RESERVED PAGE LENGTH = 200H SMART DATA 6 5 4 3 2 1 0 PAGE CODE = 31H 5.System Statistics Table 223: Log Page 32h .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.2.System Statistics This is a vendor-specific log page for providing the LSISS2520/LSISS2530 device system statistics.15 Log Page 31h .16 Log Page 32h .2.  SPEED NEGOTIATION ERROR COUNT This field specifies the number of SATA speed negotiation failures. 5.

 NUMBER OF SCSI READ/WRITE REQUESTS This counter specifies the number of SCSI I/O requests processed by the LSISS2520/LSISS2530 device. 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 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.System Statistics (Continued) BIT BYTE 7 42:43 44:47 48:51 52:55 56:59 60:63 6 5 4 3 2 1 0 NUMBER OF DISPARITY ERRORS (SATA PHY) NUMBER OF DISPARITY ERRORS (SAS PHY A) NUMBER OF DISPARITY ERRORS (SAS PHY B) NUMBER OF CRC ERRORS (SATA PHY) NUMBER OF CRC ERRORS (SAS PHY A) NUMBER OF CRC ERRORS (SAS PHY B) All counter within this log page saturate at their maximum field value. these counters are not stored in a nonvolatile memory. LSI Corporation Confidential | October 2010 Page 221 . Also.  NUMBER OF READS COMPLETED This counter specifies the number of SCSI Read commands completed by the LSISS2520/LSISS2530 device.  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 WRITES COMPLETED This counter specifies the number of SCSI Write commands completed by the LSISS2520/LSISS2530 device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 223: Log Page 32h . This is the sum of number of reads and writes received by the LSISS2520/LSISS2530 device.  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 CRC ERRORS (SAS PHY B) This field specifies the number of CRC errors detected at the SAS PHY B.17 Log Page 33h (LSISS2520/LSISS2530 Device Temperature) This log page provides die temperature information of the LSISS2520/LSISS2530 device. Table 224: LSISS2520/LSISS2530 Device Temperature Log Page BIT Byte 7 0 1 2:3 (MSB) PAGE LENGTH = 12H (LSB) 4:5 (MSB) PARAMETER CODE = 0000H TEMPERATURE (LSB) 6 7 8 9 DU = 0 DS = 1 TSD = 0 ETC = 0 RESERVED CURRENT TEMPERATURE (IN °C) TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (02H) RESERVED RESERVED 6 5 4 3 2 1 0 PAGE CODE = 33H Page 222 LSI Corporation Confidential | October 2010 .  NUMBER OF CRC ERRORS (SAS PHY A) This field specifies the number of CRC errors detected at the SAS PHY A. The following counters in this log page do not support the Read-Clear feature.  NUMBER OF DISPARITY ERRORS (SAS PHY B) This field specifies the number of Disparity errors detected at the SAS PHY B.Chapter 5: SCSI Parameters | Log Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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 A) NUMBER OF DISPARITY ERRORS (SAS PHY B) NUMBER OF CRC ERRORS (SAS PHY A) NUMBER OF CRC ERRORS (SAS PHY B) In addition.  NUMBER OF CRC ERRORS (SATA PHY) This field specifies the number of CRC errors detected at the SATA PHY. the following counters are wrapping:   NUMBER OF PHY RESETS (SAS PORT A) NUMBER OF PHY RESETS (SAS PORT B) 5.2.

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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 224: LSISS2520/LSISS2530 Device Temperature Log Page (Continued) BIT Byte 7 10:11 (MSB) PARAMETER CODE = 0001H MAXIMUM TEMPERATURE (LSB) 12 13 14 15 16:17 (MSB) PARAMETER CODE = 0002H MINIMUM TEMPERATURE (LSB) 18 19 20 21 DU = 0 DS = 0 TSD = 0 ETC = 0 RESERVED MINIMUM TEMPERATURE (IN °C) TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (02H) DU = 0 DS = 0 TSD = 0 ETC = 0 RESERVED MAXIMUM TEMPERATURE (IN °C) TMC = 0 LBIN = 1 LP = 1 PARAMETER LENGTH (02H) 6 5 4 3 2 1 0  TEMPERATURE This field specifies the current temperature of the LSISS2520/LSISS2530 device. For details.2. 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 temperature equal to or less than zero degrees Celsius is indicated by a value of zero.18 Log Page 34h (LSISS2520/LSISS2530 device Log Page) This log page is used to retrieve the LSISS2520/LSISS2530 firmware logs.  MAXIMUM TEMPERATURE This field specifies the maximum temperature and operating the device above this temperature causes physical damage to the LSISS2520/LSISS2530 device. LSI Corporation Confidential | October 2010 Page 223 .  MINIMUM TEMPERATURE This field specifies the minimum temperature and operating the device below this temperature causes physical damage to the LSISS2520/LSISS2530 device. 5. see Log Retrieval.

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters  SERIAL NUMBER (16 ASCII characters) This field specifies the LSISS2520/LSISS2530 device SERIAL NUMBER.  PACKAGE VERSION (4 Bytes) This field specifies the LSISS2520/LSISS2530 device package version.dd.  BOOT LOADER VERSION (12 ASCII characters) This field specifies the LSISS2520/LSISS2530 device Boot Loader version.  BOARD FORM FACTOR HEIGHT (1 byte): This field specifies the height of the LSISS2520/LSISS2530 device.  PORT A IDENTIFIER (8 bytes) This field specifies the LSISS2520/LSISS2530 device port A SAS address.  REVISION (12 ASCII characters) This field specifies the LSISS2520/LSISS2530 device hardware revision.yyyy) This field specifies the LSISS2520/LSISS2530 device manufacturing date.  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.  REFURBISH DATE (8 ASCII characters) (mm.  OEM NAME (16 ASCII characters) This field specifies the LSISS2520/LSISS2530 device OEM name.yyyy) This field specifies the LSISS2520/LSISS2530 device refurbish date.  CONFIGURATION DATA VERSION (8 Bytes) This field specifies the LSISS2520/LSISS2530 device configuration data version. LSI Corporation Confidential | October 2010 Page 225 .  PORT B IDENTIFIER (8 bytes) This field specifies the LSISS2520/LSISS2530 device port B SAS address.  DATE OF MANUFACTURE (8 ASCII characters) (mm.dd.  WWN (8 bytes) This field specifies the LSISS2520/LSISS2530 device World Wide Name.  FIRMWARE VERSION (12 ASCII characters) This field specifies the LSISS2520/LSISS2530 device firmware version.  LOCATION OF MANUFACTURe (8 ASCII characters) This field specifies the LSISS2520/LSISS2530 device manufacturers location.

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

 COMMAND ABORT ERROR COUNT This field specifies the number of SCSI commands aborted.  SOFTWARE RESET ISSUED COUNT This field specifies the number of times SATA SRST has been performed. LSI Corporation Confidential | October 2010 Page 227 . 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.  CHECK CONDITIONS ERROR COUNT This field specifies the number of check conditions occurred.  READ LOG EXT COUNT This field specifies the number of READ LOG EXT command issued to SATA device.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | Log Parameters Table 227: LSISS2520/LSISS2530 Device Firmware Statistics Log Page (Continued) BIT Byte 7 10:11 12:13 14:15 16:17 18:21 22:25 6 5 4 3 2 1 0 COMMAND ABORT ERROR COUNT CHECK CONDITIONS ERROR COUNT SOFTWARE RESET ISSUED COUNT READ LOG EXT COUNT READ LOG EXT-10 COUNT RESERVED  COMMAND TIMEOUTS ERROR COUNT This field specifies the number of SCSI commands timed out.

This field has the same value as in the page code field of the INQUIRY command descriptor block.1 VPD Page 00 .Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual 5. 5.3. The list is in ascending order. Page 228 LSI Corporation Confidential | October 2010 .3 VPD Parameters This section describes the VPD pages.  SUPPORTED PAGE CODE This field contains the PAGE CODEs supported by the target. 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.  PAGE LENGTH This field specifies the length of the following page data. When the Offline Drive Change feature is enabled. the inquiry command returns a CC status with ASC/ASCQ = Becoming ready.List of pages Supported Table 228: VPD Supported Page The following table lists the VPD pages that the LSISS2520/LSISS2530 device supports: BIT Byte 7 0 1 2 3 4 5 6 7 8 9 10 6 PERIPHERAL QUALIFIER PAGE CODE 00h RESERVED PAGE LENGTH 07h SUPPORTED PAGE CODE 00h SUPPORTED PAGE CODE 80h SUPPORTED PAGE CODE 83h SUPPORTED PAGE CODE 86h SUPPORTED PAGE CODE 87h SUPPORTED PAGE CODE 89h SUPPORTED PAGE CODE B1h 5 4 3 2 PERIPHERAL DEVICE TYPE 1 0  PAGE CODE This field is set to 0.

words 19:10) last retrieved from the SATA device.2 VPD Page 80 . byte 1) IDENTIFY DEVICE word 10 bits 7:0 (that is. byte 2) …………… IDENTIFY DEVICE word 19 bits 15:8 (that is.3 VPD Page 83 . BIT 5 4 3 2 1 0 PERIPHERAL QUALIFIER PAGE CODE 83h PAGE LENGTH PERIPHERAL DEVICE TYPE DESIGNATION DESCRIPTOR IDENTIFYING THE LOGICAL UNIT NAME LSI Corporation Confidential | October 2010 Page 229 .Device Identification Page.Unit Serial Number.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters 5. byte 3) IDENTIFY DEVICE word 11 bits 7:0 (that is. 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 0 1 2 3 : 18 19 IDENTIFY DEVICE word 10 bits 15:8 (that is. byte 18) Contents 5.3. byte 0) IDENTIFY DEVICE word 11 bits 15:8 (that is. byte 19) IDENTIFY DEVICE word 19 bits 7:0 (that is.3.Unit Serial Number Table 229: Unit Serial Number VPD Page Byte 7 0 1 2 3 4 :23 6 This section describes the VPD Page 80 .Device Identification Page Table 231: Device Identification VPD Page Byte 7 0 1 2:3 4 n 6 This section describes the VPD Page 83 . BIT 5 4 3 2 PERIPHERAL DEVICE TYPE PAGE CODE 80h RESERVED PAGE LENGTH 14h PRODUCT SERIAL NUMBER 1 0 PERIPHERAL QUALIFIER  PRODUCT SERIAL NUMBER This field contains a representation of the Serial number field in the SATA IDENTIFY DEVICE data (that is.

Table 233: Logical Unit Name derived from World Wide Name BIT Byte 7 0 1 2 3 4 5:6 7 8:11 NAA IEEE COMPANY_ID VENDOR SPECIFIC IDENTIFIER PIV (0b) 6 5 4 3 2 CODE SET (1h) IDENTIFIER TYPE (3h) RESERVED IDENTIFIER LENGTH (08h) IEEE COMPANY_ID 1 0 PROTOCOL IDENTIFIER (0h) RESERVED ASSOCIATION (00b) Page 230 LSI Corporation Confidential | October 2010 . Table 232: Identification Descriptor Format BIT Byte 7 0 1 2 3 4:N PIV 6 5 4 PROTOCOL IDENTIFIER RESERVED RESERVED DESIGNATOR LENGTH DESIGNATOR ASSOCIATION 3 2 1 0 CODE SET DESIGNATORTYPE  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.Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 231: Device Identification VPD Page Byte 7 n+1:n+12 n+13:n+24 n+25:n+36 6 5 4 BIT 3 2 1 0 DESIGNATION DESCRIPTOR IDENTIFYING THE TARGET PORT IDENTIFIER DESIGNATION DESCRIPTOR IDENTIFYING THE RELATIVE TARGET PORT IDENTIFIER DESIGNATION DESCRIPTOR IDENTIFYING THE TARGET DEVICE NAME The following table describes the Identification Descriptor Format. the Logical unit name is derived from the world wide name as shown in the following table.

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 234: Fields in the Logical Unit Name Field Contents Field Name NAA IEEE COMPANY_ID Specific bits Byte 4 bits 7:4 Byte 4 bits 3:0 Byte 5 Byte 6 Byte 7 bits 7:4 IDENTIFY DEVICE word 108 bits 15:12 IDENTIFY DEVICE word 108 bits 11:8 IDENTIFY DEVICE word 108 bits 7:0 IDENTIFY DEVICE word 109 bits 15:8 IDENTIFY DEVICE word 109 bits 7:4 IDENTIFY DEVICE word 109 bits 3:0 IDENTIFY DEVICE word 110 bits 15:8 IDENTIFY DEVICE word 110 bits 7:0 IDENTIFY DEVICE word 111 bits 15:8 IDENTIFY DEVICE word 111 bits 7:0 VENDOR SPECIFIC IDENTIFIER Byte 7 bits 3:0 Byte 8 Byte 9 Byte 10 Byte 11 If the SATA IDENTIFY DEVICE data returned by the SATA device word 87 bit 8 is set to 0.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters  VENDOR SPECIFIC IDENTIFIER This field is based on the SATA IDENTIFY DEVICE data World wide name field as described in the following table. Table 235: Logical Unit Name Derived from the Model Number and Serial Number BIT Byte 7 0 1 2 3 4:11 12:71 PIV (0b) 6 5 4 3 2 CODE SET (2h) IDENTIFIER TYPE (1h) RESERVED IDENTIFIER LENGTH (68) VENDOR IDENTIFICATION (ATA) VENDOR SPECIFIC IDENTIFIER 1 0 PROTOCOL IDENTIFIER (0h) RESERVED ASSOCIATION (00b) LSI Corporation Confidential | October 2010 Page 231 .

IDENTIFY DEVICE word 19 bits 7:0  TARGET PORT IDENTIFIER DESCRIPTOR This field returns the port identifier value by which the target port can be referenced.. Table 236: VENDOR SPECIFIC IDENTIFIER Field for Logical Unit Name Field Contents Field Name 0 1 2 . IDENTIFY DEVICE word 46 bits 7:0 IDENTIFY DEVICE word 10 bits 15:8 IDENTIFY DEVICE word 10 bits 7:0 IDENTIFY DEVICE word 11 bits 15:8 ... Table 237: TARGET PORT IDENTIFIER DESCRIPTOR BIT Byte 7 0 1 2 3 4 11 PIV =1 6 5 4 3 2 CODE SET = 1h DESIGNATORTYPE = 3h RESERVED DESIGNATOR LENGTH = 8h TARGET PORT IDENTIFIER DESIGNATOR 1 0 PROTOCOL IDENTIFIER = 6h RESERVED ASSOCIATION = 1 Page 232 LSI Corporation Confidential | October 2010 .... 59 Serial Number field Specific bits Model Number field IDENTIFY DEVICE word 27 bits 15:8 IDENTIFY DEVICE word 27 bits 7:0 IDENTIFY DEVICE word 28 bits 15:8 . 39 40 41 42 ...Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  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.

Extended Inquiry Data . Table 239: TARGET DEVICE NAME DESCRIPTOR Byte 7 0 1 2 3 4:11 PIV = 1 6 BIT 5 PROTOCOL IDENTIFIER = 6 RESERVED RESERVED DESIGNATOR LENGTH = 8h TARGET DEVICE NAME DESIGNATOR ASSOCIATION = 2 4 CODE SET = 1 DESIGNATORTYPE = 3h 5. Table 238: RELATIVE TARGET PORT IDENTIFIER DESCRIPTOR Byte 7 0 1 2 3 4:7 PIV = 1 6 5 4 BIT 3 2 CODE SET = 1h DESIGNATORTYPE = 4h RESERVED DESIGNATOR LENGTH = 4h RELATIVE TARGET PORT IDENTIFIER DESIGNATOR 1 0 PROTOCOL IDENTIFIER = 6h RESERVED ASSOCIATION = 1  TARGET DEVICE NAME DESCRIPTOR The target device name in NAA format is returned.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters  RELATIVE TARGET PORT IDENTIFIER DESCRIPTOR This field returns the identifier which is unique within the ports of LSISS2520/LSISS2530 device.4 VPD Page 86 .3.Extended Inquiry Data Table 240: Extended Inquiry Data VPD Page Byte 7 0 1 2 3 4 5 6 7:63 RESERVED RESERVED 6 This following table describes VPD Page 86 . BIT 5 4 3 2 PERIPHERAL DEVICE TYPE PAGE CODE 86h RESERVED PAGE LENGTH 3Ch SPT = 7 GRP_SUP = 0 PRIOR_SUP = 0 RESERVED RESERVED GRD_CHK HEADSUP = 1 COR_D_SUP = 0 APP_CHK NV_SUP = 0 REF_CHK V_SUP ORDSUP = 1 SIMPSUP = 1 1 0 PERIPHERAL QUALIFIER LSI Corporation Confidential | October 2010 Page 233 .

if any. if any. The LSISS2520/LSISS2530 device does not support task priority. The LSISS2520/LSISS2530 device does not support Grouping.  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). For the LSISS2520/LSISS2530 device. if any. It is considered a reserved case. This bit set to 0 indicates that task priority is not supported.  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.  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 field returns 0x7. This bit set to 0 indicates that the grouping function is not supported.  APP_CHK (Application tag check) This bit set to 0 indicates that the device server does not check the LOGICAL BLOCK APPLICATION TAG field in the protection information (refer SBC-3). This bit set to 0 indicates that the HEAD OF QUEUE task attribute is not supported. This bit set to 1 indicates that the device server checks the LOGICAL BLOCK GUARD field in the protection information. if any. Ignore the SPT field if the PROTECT bit in the Standard Inquiry Data is set to 0. The LSISS2520/LSISS2530 device Supports Head of queue task attribute.  SPT (Supported Protection Type) This field indicates the type of protection the logical unit supports. if any. Page 234 LSI Corporation Confidential | October 2010 . This bit set to 1 indicates that the device server checks the LOGICAL BLOCK APPLICATION TAG field in the protection information. The LSISS2520/LSISS2530 device does not support Logical Block Application Tag checking.Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  PAGE LENGTH This field specifies the length of the following VPD page data and set it to 3Ch. This bit set to 1 indicates that the device server checks the LOGICAL BLOCK REFERENCE TAG field in the protection information. if any.  REF_CHK (Reference tag check) This bit set to 0 indicates that the device server does not check the LOGICAL BLOCK REFERENCE TAG field in the protection information (refer SBC-3). which indicates support for all three protection types.  PRIOR_SUP (Priority supported) This bit set to 1 indicates that task priority (Refer SAM-4) is supported by the logical unit.

Mode Page This following table describes the VPD Page 87 .  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). The LSISS2520/LSISS2530 device always returns the NV_SUP bit set to 0. the FUA_NV bit in SBC-3). Table 241: Mode Page Policy VPD Page Byte 7 0 1 2:3 4:7 : n-3:n 6 PERIPHERAL QUALIFIER PAGE CODE 87h PAGE LENGTH (n-3)h MODE PAGE POLICY DESCRIPTOR (first) ….Mode Page Policy. The LSISS2520/LSISS2530 device supports Simple.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters  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 does not support the correction disable attribute and sets it to 0.  SIMPSUP (Simple supported) This bit set to 1 indicates that the SIMPLE task attribute (Refer SAM-4) is supported by the logical unit. This bit set to 0 indicates that the device server does or does not support a volatile cache. 5.3.  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. MODE PAGE POLICY DESCRIPTOR (last) 5 4 BIT 3 2 PERIPHERAL DEVICE TYPE 1 0 LSI Corporation Confidential | October 2010 Page 235 .  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.5 Policy VPD Page 87 . the FUA bit in SBC-3). The LSISS2520/LSISS2530 device receives the underlying device's FUA data and sends the data to the initiator. The LSISS2520/LSISS2530 device supports Ordering. 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. This bit set to 0 indicates that the device server does or does not support a non-volatile cache. The LSISS2520/LSISS2530 device support FUA.

Page 236 LSI Corporation Confidential | October 2010 .subpage 02h Vendor Specific Mode Page: SAS Link Configuration  MLUS This field is set to 1 for Policy PAGE CODE set to 02h.subpage 02h Protocol specific port mode page . 19h (all SUBPAGE CODEs) and 36h. 03h).  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 .Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual The following table describes the MODE PAGE POLICY DESCRIPTOR Format. 01h 02h. Table 243: POLICY PAGE CODE and POLICY SUBPAGE CODE Field Settings POLICY PAGE CODE POLICY SUBPAGE CODE 3Fh 02h 19h 19h 19h 19h 36h FFh 00h 00h 01h 02h 03h 00h Description Retrieve all policy pages Disconnect-Reconnect mode page Protocol specific port mode page Protocol specific port mode page . and set to Per Target Port (1h) for POLICY PAGE CODE 36h.subpage 01h Protocol specific port mode page .00h. Table 242: MODE PAGE POLICY DESCRIPTOR Format Byte 7 0 1 2 3 MLUS RESERVED RESERVED RESERVED 6 5 4 BIT 3 2 1 0 POLICY PAGE CODE POLICY SUBPAGE CODE MODE PAGE POLICY = 0  The POLICY PAGE CODE and POLICY SUBPAGE CODE fields are set according to the following table.

 SAT PRODUCT REVISION LEVEL This field contains four bytes of ASCII data. The LSISS2520/LSISS2530 device sets this field to the ASCII string LSI followed by ASCII spaces. The data is left aligned within the field.3. BIT 5 4 3 2 PERIPHERAL DEVICE TYPE PAGE CODE 89h PAGE LENGTH 238h RESERVED SAT VENDOR IDENTIFICATION SAT PRODUCT IDENTIFICATION SAT PRODUCT REVISION LEVEL SATA DEVICE SIGNATURE COMMAND CODE RESERVED SATA IDENTIFY DEVICE DATA 1 0 PERIPHERAL QUALIFIER  SAT VENDOR IDENTIFICATION This field contains an 8-byte ASCII string identifying the vendor of the LSISS2520/LSISS2530 device.6 VPD Page 89 -SATA Information VPD Page Table 244: SATA Information VPD Page Byte 7 0 1 2:3 4:7 8:15 16:31 32:35 36:55 56 57:59 60:571 6 This following table describes the VPD Page 89 -SATA Information VPD Page. LSI Corporation Confidential | October 2010 Page 237 . The vendor identification string is assigned by INCITS for use in the Standard INQUIRY data VENDOR IDENTIFICATION field.  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.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters 5.

 INTERRUPT This bit is set to 1. refer to ATA8-APT and SATA-2. Table 245: SATA DEVICE SIGNATURE Byte 7 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14:19 RESERVED INTERRUPT/ RESERVED 6 5 4 BIT 3 2 1 0 TRANSPORT IDENTIFIER RESERVED PM PORT/RESERVED STATUS (00 – 70h) any value in between (Setting of 6:4 bits is device specific) ERROR = 01 LBA LOW = 01 LBA MID = 00 LBA HIGH = 00 DEVICE LBA LOW EXP = (00) LBA MID EXP = (00) LBA HIGH EXP = (00) RESERVED SECTOR COUNT = 01 SECTOR COUNT EXP (00) 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. Page 238 LSI Corporation Confidential | October 2010 .6 specs. For the remaining field description within the SATA DEVICE SIGNATURE.Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual  COMMAND CODE This field contains the of the SATA command used to retrieve the data in the IDENTIFY DEVICE for the LSISS2520/LSISS2530 device.

 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. LSI Corporation Confidential | October 2010 Page 239 . Table 246: Block Device Characteristics VPD Page BIT Byte 7 0 1 2 3 4:5 6 7 8:63 RESERVED RESERVED 6 PERIPHERAL QUALIFIER PAGE CODE B1h RESERVED PAGE LENGTH 3Ch MEDIUM ROTATION RATE RESERVED NOMINAL FORM FACTOR 5 4 3 2 PERIPHERAL DEVICE TYPE 1 0  PAGE LENGTH This field specifies the length of the following VPD page data and is set to 3Ch.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Chapter 5: SCSI Parameters | VPD Parameters 5.7 VPD Page B1 .  MEDIUM ROTATION RATE This field is set to the value of SATA IDENTIFY DEVICE data word 217.3.Block Device Characteristics The Block Device Characteristics VPD page contains parameters indicating the characteristics of the logical unit.

Chapter 5: SCSI Parameters | VPD Parameters LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 240 LSI Corporation Confidential | October 2010 .

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

— Initialize the SATA PHY on receipt of this command.3 Device Spin-Up In the LSISS2520/LSISS2530 device. When the primitive is received. the SATA PHY is initialized.Appendix A: | Device Spin-Up LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual A. There is an option to ignore spin-up on this SCSI command if NOTIFY (ENABLE SPIN-UP) has not yet been received. — Power up device upon receipt of this command. 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. 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. Page 242 LSI Corporation Confidential | October 2010 .

1 Device State Machine The Device State Machine operations are composed of five states.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.1. B.1 Device State Machine Operations SSD1 – SATA_DRIVE_INIT Initialization Commands Failed N Times or Drive not meet minimum standards for this Vendor SSD4 – SATA_DRIVE_DOWN 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 LSI Corporation Confidential | October 2010 Page 243 . The following figures shows the Device State machine operations. B.

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

The drives ID data can be checked for Support of the following features: NCQ Mode. In the LSISS2520/LSISS2530_02: SYS_RDY state. The following figure shows the System State machine operations.2 System State Machine The System State Machine operations are composed of five states.2.3 Flags Device Qualification During SSD1 (SATA_DRIVE_INIT) state when the Identify Device Command is sent to the device.1 LSISS2520/LSISS2530_01: SYS_INIT B.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix B: | System State Machine B. and device Based World Wide Name. SCT Commands. B. Smart. If the Qualification flag is enabled and the device connected does not support the feature. LSISS2520/ LSISS2530_02_SYS_RDY LSISS2520/ LSISS2530_04_SYS_STANDBY LSISS2520/ LSISS2530_01_SYS_INT Boot Successful System Idle Command Received LSISS2520/ LSISS2530_05_SYS_DEGRADED Processor Reset There are no longer any log sectors available LSISS2520/ LSISS2530_03_SYS_DOWN Boot Successful except no Log Sectors Config or log sectors are not available 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: B. LSI Corporation Confidential | October 2010 Page 245 .2. the device is booting.1. the device is in the ready state and is being processed in the polling loop. The device is checked for minimum level of support as specified in the device Qualification flags. the device State Machine transitions to the SSD4 (SATA_DRIVE_DOWN) state and logs the error.2.2 LSISS2520/LSISS2530_02: SYS_RDY System State Machine In the LSISS2520/LSISS2530_01: SYS_INIT state. ATA8. ATA7.

This UA and CC could not be overridden by using Error lookup table.5 LSISS2520/LSISS2530_05:SYS_ DEGRADED Page 246 LSI Corporation Confidential | October 2010 .3 LSISS2520/LSISS2530_03: SYS_DOWN In the LSISS2520/LSISS2530_03: SYS_DOWN state. firmware update and a few other important commands are operational. As soon as the LSISS2520/LSISS2530 device enters this state.2. In the LSISS2520/LSISS2530_04: SYS_STANDBY state. In the LSISS2520/LSISS2530_05:SYS_DEGRADED state.2. the device has a major problem and cannot continue with the normal operations.2.Appendix B: | System State Machine LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual B. Only a crash dump retrieval. the device is idle for a while and has lowered the power consumption. 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. B. log retrieval. the device is functional but unable to retrieve logs because of the flash going bad.4 LSISS2520/LSISS2530_04: SYS_STANDBY B.

the first copy is written first and once completed. a byte compare of the first copy with the second copy is performed to ensure that the second copy is good. 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. LSI Corporation Confidential | October 2010 Page 247 . the firmware checks its version label to determine if its what it is expecting. it continues to scan until it finds one that does or it runs out of configuration and logs sectors.1 Configuration Data Two copies of the configuration data are stored in the flash with each copy protected by a checksum. During initialization. If the current firmware does not understand what the old configuration version was. C. On a configuration update. When the first copy of configuration data is retrieved successfully. the firmware loads the customer specific default data and attempts to rewrite the configuration data. the second copy is written. and LED behavior. device replacement algorithm. then the second copy is overwritten with the data from the first. If the compare fails. 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. the system enters the system down state. In the event of total failure. the device processes the data using the Firmware Upgrade code to change the configuration data to the current version. If this fails. When this operation is a result of a SCSI command. the SCSI Response is held until both writes are complete. If the first sector checked does not pass this check. it sets the data to the customer specific default data. firmware scans the configuration and log area looking for valid configuration data.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix C: | Configuration Data Appendix C Additional Information This appendix describes the configuration data. Upon retrieving a good copy of configuration data. If the version is different.

perform the following steps: 1. 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. you can delay SAS links bring up on Power-On reset until one of the following actions occurs. 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. See Section 5. Once the SATA device is capable of responding to an Identify Device command. The System State Machine enters the System Down State. If all the three features are enabled.1.Appendix C: | Delaying SAS Links Bring Up LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual C. The Drive State Machine enters the Drive Down State. the actual inquiry data is available.3 Device Replacement Algorithm The LSISS2520/LSISS2530 device supports the ability to initially connect to a device for the first time given any configuration. Mode Page 32h (Firmware Parameter Control) for descriptions of these fields. 2. Page 248 LSI Corporation Confidential | October 2010 . Set WWN GenType to 0. 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. Mode Page 32h (Firmware Parameter Control) for a description of the DEVICE SPIN-UP ALGORITHM field.1. SAS links are not brought up after a Power-On reset until IDD from the drive has been received.13. It also returns the customer specific fake inquiry data available until this point. SAS links come up irrespective of whether IDD response from the drive has been received or not (this is required for debugging). the SAS links are brought up before the LSISS2520/LSISS2530 device receives IDD from the drive. The LSISS2520/LSISS2530 device also supports the ability to change the device while the LSISS2520/LSISS2530 device has no power. the LSISS2520/LSISS2530 device seamlessly changes from one SATA device to another.    Identify Device Data (IDD) from the drive is received.    Enable WWN Override Program a WWN Enable OffLineDriveChangeEnable If you do not enable these features. Set DEVICE SPIN-UP ALGORITHM to SPINUP IMMEDIATE (0x2). If you do enable this feature. In case the LSISS2520/LSISS2530 device goes to drive-down or system-down state.2 Up Delaying SAS Links Bring With the LSISS2520/LSISS2530 device. To enable this feature.13. If you do not enable this feature. C. the LSISS2520/LSISS2530 device does not support changing the device from its initially connected SATA device. See Section 5.

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

Appendix C: | LED Behavior LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 250 LSI Corporation Confidential | October 2010 .

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

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

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 LSISS2520/LSISS2530 device. After the complete Boot Loader image successfully writes in flash. 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.3 Boot Option Image Upgrade Use the Write Buffer command. the LSISS25x0 firmware cannot reboot again and the part becomes unusable. then the Write Buffer command is check conditioned with the sense key as an illegal request. the LSISS25x0 device assumes that the complete drive firmware is sent in a single Write Buffer command.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Boot Option Image Upgrade D. an additional sense key as an invalid field in CDB.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. If the write to the Non-Volatile memory fails. perform the Boot Loader upgrade with extreme caution. To avoid this. The Write Buffer command has a Buffer Offset of zero. it is written into the Non-Volatile Memory. 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. D. The LSISS2520/LSISS2530 device can receive a single Write Buffer command to upgrade its Boot Option. the flash is locked to prevent accidental overwriting and a success status is sent to the initiator. the LSISS2520 device transmits Transfer Readys with the size of Parameter list length bytes to the initiator. the LSISS25x0 device assumes that the complete drive firmware is being sent through multiple Write Buffer commands. and an additional sense key qualifier as an invalid field in CDB. 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. If this is not the case. to perform an Inband Boot Option image upgrade. When the mode is set to 0x7 (Download Microcode with Offsets and Save). Once the data is received from 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 LSISS2520/LSISS2530 device must then be sent to the Lab to restore the Boot Loader. When the mode is set to 0x5 (Download Microcode and Save). with the mode set to Download microcode with offsets and save (mode 07h) with the Buffer ID set to 0x03. LSI Corporation Confidential | October 2010 Page 253 . The LSISSS25x0 device sends an ATA DOWNLOAD MICROCODE command to the ATA drive. with the mode set to 7 and the buffer ID set to 0x03. After receiving the Write Buffer command.

exe utility from LSI. see Section D. D. NOTE: The package must be generated using the lsi_package.2. if the buffer offset is set to a nonzero value. LSISS25x0 Boot Loader – Optional. the LSISS25x0 firmware. If the package firmware upgrade is done using the mode 0x7 buffer ID 0xA. This is the third component of the package. in order. Component headers – This is also a mandatory part of the package. the LSISS25x0 device performs automatic drive reset. For more information on the main package. The header contains the revision for all the components and the package revision. Drive image – Optional. LSISS25x0 Boot Options – Optional. the entire package must be sent through the single Write Buffer command. This is the fourth component of the package. NOTE: After successful completion of a drive firmware upgrade through Write Buffer Mode 5 buffer ID 0. Page 254 LSI Corporation Confidential | October 2010 . boot options. LSISS25x0 firmware image – Optional. on page 256. and drive firmware. For more information on the individual component headers. LSISS25x0 boot options.1.5. 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.      This order of the components in the package is fixed and cannot be changed. In this case. 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. In the package firmware upgrade. the LSISS25x0 device responds to the command with the check condition. on page 257.5 Package Firmware Upgrade The LSISS25x0 device supports the package firmware upgrade feature. Individual Component Header Description.5. see Section D. This is the second component of the package. For drive error translation see Section 3. This contains the four individual component headers for the LSISS25x0 Boot loader. If the package firmware upgrade is done using the mode 0x5 buffer ID 0xA. following are the assumptions made from the initiator perspective. boot loader. the drive reset is left to the initiator. In this case.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. Error Translations. Main Package Header Description. LSISS25x0 firmware.15. 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). With a Mode 7 buffer ID 0 drive firmware upgrade. The package sent by the host contains the following constituents:  Package Main header – This is a mandatory part of the package. This is the first component of the package. the firmware upgrade takes place through multiple Write Buffer commands with each command containing a chunk from a package as payload.

with the size of each chunk a multiple of one KB. The minimum chunk size does not apply to the last chunk from the package.  If the Package Revision is newer that the one reported in the Inquiry Data. or LSISS25x0 firmware) are written to non-volatile memory. If the Boot Loader upgrade fails. then the LSISS25x0 device returns a SCSI Check Condition status for the Write Buffer command. The package header has the starting offsets to each component. and returns a SCSI GOOD status. the LSISS25x0 device exhibits the following behavior: — The Corresponding Write Buffer command is terminated with CC (appropriate ASC/ASCQ) status. then the contents of the package (Boot Loader.  If the package revisions match. — The package data received before the error was detected (data of the package received through any previous and current Write Buffer commands) is discarded. 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. or the Force Upgrade option is set to TRUE. Hence the initiator needs to reinitiate the entire package upgrade sequence. then the LSISS25x0 device cannot boot successfully. so an implied minimum of one KB.  If the package contains LSISS25x0 firmware or Drive firmware as a component. If the upgrade of one or more components included in the package is not successful. then the LSISS25x0 device receives the package. NOTE: Use the Boot Loader upgrade rarely and cautiously. No repetitions or reordering of chunks is allowed.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Package Firmware Upgrade  The initiator splits the package into chunks. Boot Options.  The initiator sends the chunks of the firmware to the LSISS25x0 device in the correct order. The LSISS25x0 device parses the header and compares the Package Revision with the revision reported in the Inquiry Data. discards the contents of the package. LSI Corporation Confidential | October 2010 Page 255 . — 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 package identifier value is LSIP. 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 no part of the package upgrade was successful. then the package revision used during the previous package upgrade is used as the calculated package revision. If the revisions of all the components match. However. Image is for Flash of 512 KB flash _type = 1. with 64 KB sector size flash _type = 2. then the result of the package revision check is ignored.  Page 256 LSI Corporation Confidential | October 2010 . LSISS25x0 firmware is upgraded and the drive firmware upgrade is unsuccessful) the package revision is reported as 4321. Package Option: – The Package Option field provides option for a force upgrade field. then update routines are initiated. Before initiating the package update.e. provides the revision of component in the package. Image is for Flash of 2 MB. then the package revision does not change. if a mismatch is detected..   Package Signature – The Package Signature is used an identifier of package. then the FW images included in the package are used for the upgrade. 4321). and the package update is initiated. The force upgrade option in the package header indicates that you ignore the current package revision while deciding whether to update or not. then.If the package upgrade was partially successful.Appendix D: | Package Firmware Upgrade LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual D. CRC – The CRC field provides the CRC of the main header. If the force upgrade bit is set. (i. irrespective of the value of the flash type field. Flash type – This field is used to specify the flash type. flash _type = 0.exe utility that is used to generate the package. if flash type matches. the FW images included in the package are used for the upgrade. Image is for Flash of 2 MB. the LSISS25x0 device compares the package revision in package header to calculated package revision. Ignore Flash – The Ignore Flash type flag in the package header is set.1 Main Package Header Description These are the constituents of the LSISS25x0 device’s package main header. Component Count – The Component Count field provides the number of component present in the package.5. If ignore flash type is not set LSISS25x0 compares the flash type in main package header to flash type in the hardware. Package Utility Revision – The Package Utility Revision field indicates the revision of the lsi_package. Package Revision – The Package Revision field. 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. if the revision is different.e. then the calculated package revision is marked as bad (i.

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

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

and if the LSISS2520/LSISS2530 device image update is successful in the package and the drive firmware update is unsuccessful.  LSI Corporation Confidential | October 2010 Page 259 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix D: | Package Firmware Upgrade  If the currently running image has revision ABCD and the new package to be upgraded has package revision WXYZ. then the package upgrade is unsuccessful and the package revision reported after reboot is 4321. and if none of the image upgrades in the package are successful. If the currently running image has revision ABCD and the new package to be upgraded has package revision WXYZ. then the package upgrade fails and the package revision reported is ABCD.

Appendix D: | Package Firmware Upgrade LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 260 LSI Corporation Confidential | October 2010 .

logs are preserved across resets. Log entries are in a predefined format indicating the module. In the event of a crash.1. E. Strings are only used for debug images where the parallel flash is used. and any specific information that is relevant. A typical log entry is 8 to 16 bytes.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. The Boot Loader does not run a memory test in this memory location if the reset was not caused by a power-on-reset. Normal Log 32-bits Timestamp 32-bits Log Info 32-bits Parameter 1 (optional) 32-bits Parameter 2 (optional) E.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix E: | Logging Appendix E Debug This appendix describes the logging and crash dump format. The following is a diagram of both the normal and crash logs.1 Log Format Crash Log 32-bits Timestamp 32-bits Log Info 32-bits Reason Code 32-bits Crash Data 0 32-bits Crash Data 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 SubModule R Unique Code/Crash Log Size V = Valid Bit C = Crash Log Bit LT = Log Type PC = Parameter Count R = Reserved GRF000040_00 Figure 6: Normal and Crash Log Structure LSI Corporation Confidential | October 2010 Page 261 . sub-module. The Boot Loader reserves a section of memory dedicated for these logs.

Warning – These warnings do not halt the operations of the LSISS2520/LSISS2530 device. If this bit is set to 1. For a crash dump. These bits determine the priority of the debug and specify if the message is categorized as information or error. then the log entry is a normal log entry. For these values. If this bit is set to 0. 0 1 1 0 1 1 Page 262 LSI Corporation Confidential | October 2010 . Table 251: Log Type Bit Values Bits Log Type 29 0 0 28 Informational – These messages give the status of an operation or the details about the firmware state at a particular point of time. — These bits specify the module from which the log message originated. These bits specify the sub module from which the log message originated. then the log entry is a crash dump. the log entry is for a crash dump. see Table 251. Examples are queue full conditions and check conditions. Valid numbers are 0 to 2. Error – These messages signify that an error has occurred in the LSISS2520/LSISS2530 device which might affect normal operation. Critical (Fatal) – These messages are for critical errors. the Unique Code field contains the size of the dump in bytes and the parameter count field is invalid. Definition 29:28 27:26 25:24 23:21 20:17 16 15:0 Log Type Reserved Module Sub Module Reserved Unique Code/ Crash Log Size Parameter Count These bits contain the number of parameters for this log entry.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). See Table 250. — These bits uniquely identify the message that forms the format string. Table 250: Log Information Bit 31 30 Valid Crash Log Name If this bit is set to 1. Optional parameter 1. then it is a valid log message. (See Table 255). In most cases. Optional parameter 2. The following table lists the log information. Table 249: Log Entry Structure Word 0 1 2 3 Name Timestamp Log Info Param1 Param2 Definition This timestamp has a resolution of 10 milliseconds and it starts from the time the LSISS2520/LSISS2530 device was booted.

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

System maintains the current log sector in flash.5 Crash Log Format During firmware panics or other catastrophic failures for certain processor exceptions. Crash Dump BIT Byte 7 0 1 2 3 4:4099 (MSB) Page Length = 1000h (LSB) LSISS2520/LSISS2530 Crash Dump DS = 1 6 SPF = 1 5 4 3 2 1 0 Page Code = 34h Subpage Code = 01h E. For the crash log. The Log Sense page reads log data from the flash. These fields contain reason specific information. Table 253: Log Sense Page 34h Log Entry Structure BIT Byte 7 0:3 4:7 8:N 6 5 4 Time Stamp Log Info Log Specific Data 3 2 1 0 Mode Select Command with Page code 25h(vender specific) is used to get/set the logging configuration information. For details.Appendix E: | Logging LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Based on the given Log Sense command. the firmware generates a crash log. The following table lists the Log Entry structure. Table 254: Log Sense Page 34h. This log provides sufficient information to help identify the cause of the failure in firmware. The following is the format for the crash log. Subpage 01h. Page 264 LSI Corporation Confidential | October 2010 . see Mode Page 25h (Logging Configuration Parameters).1. Table 255: Crash Log Format Word 0 1 2 3:N Name Timestamp Log Info Reason Code Reason Specific Information Definition This timestamp has a resolution of 10 milliseconds and it starts from the time the LSISS2520/LSISS2530 device was booted. bits [15:0] contain the size of the log in words. The contents of the dump information depend on the type of failure that triggered the dump. appropriate log pages are returned to the user. The code that identifies the reason for the log.

SPSR…) Stack Trace . saving the ARM® registers (r0 . Table 257: Crash Dump format Section Title Header Word Index 0x0000 – 0x0003 Values Timestamp. an ARM data abort exception has occurred.Last 64 entries of the stack for the normal operating processor mode Definition E. Crash dump version. The following rows lists the crash dump format for crash dump version 106.0x0081 0x0082 – 0x00E9 0x00EA – 0x00FC 0x00FD – 0x013E 0x013F – 0x017A 0x017B – 0x01BA 0x01BB – 0x01BD 0x01BE – 0x01C4 0x01C5 – 0x01D3 0x01D4 – 0x01E1 0x01E2 – 0x0221 0x0222 – 0x0246 0x0247 – 0x02B4 0x02B5 – 0x02BF 0x02C0 – 0x02C4 0x02C5 0x02C6 – 0x02D0 0x02D1 – 0x02E5 0x02E6 0x02E7 – 0x030F LSI Corporation Confidential | October 2010 Page 265 . The exception handler creates this log.2 Crash Dump format The following table shows the crash dump format.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix E: | Crash Dump format The following is an example crash log. Length.r15 and the CPSR and SPSR) and the last 64 bytes of the stack. LSISS2520/LSISS2530 FW Version String ARM Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Hardware Registers Lynx™ Registers Firmware Structure Firmware Structure Firmware Structure Firmware Structure Firmware Structure Firmware Structure Error Counters Firmware CPU Registers SM Ports SASAM MPRM MPTM DM DBM DMA CBM Subsystem SATA Port MISC Lynx g_STHDGlobal SE Abort Details SE Lun State SE Task Set SE Background TD SE Misc SAS Port Counts 0x0004 – 0x0006 0x0007.R15. In this example. CPSR. Reason Code. Table 256: Crash Log Example Word 0 1 2 3:N N+1:M Name Timestamp Log Info Reason Code Reason Specific Information Reason Specific Information continued Current timestamp for the crash Crash Dump of size (M * 4) bytes Data Abort Processor Exception ARM Specific Processor Registers (R0 .

0x03F0 0x03F1 0x03F2 – 0x03F3 0x03F4 – 0x03FB 0x03FC – 0x03FF Initiators Task List Disk and System State Logging Info Bad Sector Map Timer Info Values Page 266 LSI Corporation Confidential | October 2010 .Appendix E: | Crash Dump format LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 257: Crash Dump format (Continued) Section Title FW Init Table Task Descriptors State Machine State Log Info NVM Defect Timer Word Index 0x0310 – 0x0327 0x0328 .

To assist in debugging problems. See Table 259 for the numeric value for the various FRU codes. 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. F. removed from the current implementation.2 Sense Information Table 258: Sense Information ErrorIdx Numeric Value Skey (Hex) ASC (Hex) ASCQ (Hex) ErrorIdx Unit Attentions UA_ERROR_CODE_SCSI_BUS_RESET UA_ERROR_CODE_ABRT_TS UA_ERROR_CODE_FLASH_WRITE_F AILURE UA_ERROR_CODE_MICROCODE_UP DATED UA_ERROR_CODE_RESERVATIONS_ CLEARED UA_ERROR_CODE_REGISTRATIONS _PREEMPTED UA_ERROR_CODE_INITIATOR_LOGI N UA_ERROR_CODE_LOG_PARAMETE RS_CHANGED Description 0 1 2 3 4 6 6 6 6 6 29 2F 3 3F 2A 2 2 0 1 4 Error code returned when unit attention condition is established because of a hard reset. removed from the current implementation.1. Error code returned when unit attention condition is established because the persistent reservation of the I_T NEXUS has been preempted. Error code returned when unit attention condition is established because persistent reservation with registrants only type or all registrants type was released. Instance ID reserved.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. Error code returned when unit attention condition is established because a task management function is in progress.1 F. Instance ID reserved. Error code returned when unit attention condition is established because the target device does not support independent states of log parameters and log parameters which could affect other I_T NEXUS are changed.1 Error Lookup Table FRU Code Values This section lists the Error Lookup table. Error code returned when unit attention condition is established because power on occurred and an initiator logged in.1. This section describes the default Sense Information table maintained with the LSISS2520/LSISS2530 device firmware. FRU codes are returned with both fixed and descriptor format sense data. 5 6 2A 5 6 7 6 6 29 2A 1 2 LSI Corporation Confidential | October 2010 Page 267 .

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

Error code reserved for future use. Error code reserved for future use. Error code returned when a command is check conditioned because the connected SATA drive is being initialized. Error code returned when a command is check conditioned because of internal target failure. and our initiator table is full. 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. Error code returned when a command is check conditioned because of prediction threshold failure.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 258: Sense Information (Continued) ErrorIdx Numeric Value 31 32 33 34 35 36 46 38 Skey (Hex) 6 6 6 6 0 0 0 7 ASC (Hex) 0 0 0 0 0 19 5D 27 ASCQ (Hex) 0 0 0 0 0 1 0 0 ErrorIdx UA_ERROR_CODE_RESERVED_8 UA_ERROR_CODE_RESERVED_9 UA_ERROR_CODE_RESERVED_10 UA_ERROR_CODE_RESERVED_11 CC_ERROR_CODE_NO_SENSE_DAT A_AVAILABLE CC_ERROR_CODE_DEFECT_LIST_N OT_FOUND CC_ERROR_CODE_FAIL_PREDICTIO N_THRESHOLD_EXCEEDED CC_ERROR_CODE_DATA_PROTECT Description Error code reserved for future use. Error code returned when a command is check conditioned because drive is in standby mode and requires an initializing command. Error code returned when a command is check conditioned because logical unit is not ready and additional sense info is not available in case of start stop unit. Error code returned when the Test Unit Ready command is check conditioned because the logical unit did not respond to selection. Error code returned when a command is check conditioned because information from medium memory is inaccessible because of absence of medium. Error code returned when a command is check conditioned because of hardware error but additional sense information is not present. Error code returned when a command is check conditioned because device is being formatted. Error code returned when a command is check conditioned because self-test is being performed in foreground mode. Other Check Conditions CC_ERROR_CODE_BACKGROUND_E RRRS CC_ERROR_CODE_SNS_NOT_RDY_I NIT_CMD_REQUIRED CC_ERROR_CODE_SNS_NOT_RDY_ NO_RESP_BY_LU CC_ERROR_CODE_SNS_NOT_RDY_ MED_ABSENT CC_ERROR_CODE_SNS_NOT_RDY_ FMT_IN_PROG CC_ERROR_CODE_SELF_TEST_IN_P ROGRESS CC_ERROR_CODE_BECOMING_REA DY CC_ERROR_CODE_INITIATOR_OVER FLOW CC_ERROR_CODE_MISCOMP_DURI NG_VERIFY CC_ERROR_CODE_HW_ERR_NO_SE NSE CC_ERROR_CODE_HW_ERR_INT_TA RGET_FAILURE CC_ERROR_CODE_HW_ERR_DIAG_ FAIL_COMP_84 CC_ERROR_CODE_HW_ERR_DIAG_ FAIL_COMP_85 CC_ERROR_CODE_HW_ERR_DIAG_ FAIL_COMP_86 39 2 4 0 40 41 42 2 2 2 4 5 3A 2 0 0 43 44 45 46 47 48 49 50 51 52 2 2 2 2 E 4 4 4 4 4 4 4 4 55 1D 0 44 40 40 40 4 9 1 3 0 0 0 84 85 86 LSI Corporation Confidential | October 2010 Page 269 . Error code returned when a command is check conditioned but no sense data is available. Error code returned when a command is check conditioned because CRC check failed during write and verify operation. Error code returned when a command is check conditioned because the underlying ATA drive resulted in self test execution status 6. Error code returned when a command is check conditioned because the underlying ATA drive resulted in self test execution status 4 Error code returned when a command is check conditioned because the underlying ATA drive resulted in self test execution status. Error code returned when a command is check conditioned in case of Read Defect Data command because it is not supported. 5. Error code returned when we receive a command from a new initiator. Error code reserved for future use.

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

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

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Appendix F:

| Error Lookup Table

Table 258: Sense Information (Continued) ErrorIdx Numeric Value 115 116 117 118 119 120 121 Skey (Hex) 5 0 0 0 0 0 0 ASC (Hex) 39 0 0 0 0 0 0 ASCQ (Hex) 0 0 0 0 0 0 0

ErrorIdx CC_ERROR_CODE_SAVING_PARAM S_NOT_SUPPORTED CC_ERROR_CODE_RESERVED_0 CC_ERROR_CODE_RESERVED_1 CC_ERROR_CODE_RESERVED_2 CC_ERROR_CODE_RESERVED_3 CC_ERROR_CODE_RESERVED_4 CC_ERROR_CODE_RESERVED_5

Description Error code returned for mode sense command when requested mode page does not support saved values. Error code reserved for future use. Error code reserved for future use. Error code reserved for future use. Error code reserved for future use. Error code reserved for future use. Error code reserved for future use.

F.1.3 List of InstIds Occurrences and ErrorIdx Class of Errors Table 259: InstIds Numeric Value for InstId

This LSISS2520/LSISS2530 device firmware has the following default association of InstIds occurrences and ErrorIdx class of errors.

InstId

Default ErrorIdx

Numeric Value for default ErrorIdx

Explanation

INST_UA_SCSI_BUS_RESET=0 0 INST_UA_ABRT_TS 1

UA_ERROR_CODE_SCSI_BUS_ 0 RESET UA_ERROR_CODE_ABRT_TS 1

The UA Instance when unit attention condition is established because of a hard reset. The UA Instance when unit attention condition is established because a task management function is in progress. The UA Instance when unit attention condition is established because new device firmware could not be written to flash. The UA Instance when unit attention condition is established because new microcode - netlist has been updated as a result of Write Buffer command. The UA Instance when unit attention condition is established because new microcode - configdata has been updated as a result of Write Buffer command. The UA Instance when unit attention condition is established because new microcode - configdata has been updated as a result of Write Buffer command. The UA Instance when unit attention condition is established with affected registrants because persistent reservation with registrants only type or all registrants type was released. The UA Instance when unit attention condition is established with affected registrants because persistent reservation are preempted.

INST_UA_FLASH_WRITE_FAIL URE

2

UA_ERROR_CODE_FLASH_W 2 RITE_FAILURE UA_ERROR_CODE_MICROCO 3 DE_UPDATED UA_ERROR_CODE_MICROCO 3 DE_UPDATED UA_ERROR_CODE_MICROCO 3 DE_UPDATED UA_ERROR_CODE_RESERVATI 4 ONS_CLEARED

INST_NETLIST_UPGRADE_UA_ 3 MICROCODE_UPDATED INST_CONFDATA_UPGRADE_ UA_MICROCODE_UPDATED 4

INST_DRIVE_FW_UPGRADE_U 5 A_MICROCODE_UPDATED INST_UA_RESERVATIONS_CLE 6 ARED

INST_PREEMPT_UA_REGISTRA 7 TIONS_PREEMPTED

UA_ERROR_CODE_REGISTRAT 5 IONS_PREEMPTED

LSI Corporation Confidential | October 2010

Page 273

Appendix F:

| Error Lookup Table

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_CLEAR_UA_REGISTRATIO 8 NS_PREEMPTED INST_UA_INITIATOR_LOGIN 9

UA_ERROR_CODE_REGISTRAT 5 IONS_PREEMPTED UA_ERROR_CODE_INITIATOR 6 _LOGIN UA_ERROR_CODE_LOG_PARA 7 METERS_CHANGED

The UA Instance when unit attention condition is established with affected registrants because persistent reservation are cleared. The UA Instance when unit attention condition is established because power on occurred and an initiator logged in. The UA Instance when unit attention condition is 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. The UA Instance when unit attention condition is 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. The UA Instance when unit attention condition is established because mode parameters which affect the I_T NEXUS are changed on another I_T NEXUS. The UA Instance when unit attention condition is established because self test running in the background mode failed. The UA Instance when unit attention condition is established because SAS link went down. The UA Instance when unit attention condition is established because logical unit reset or clear task set occurred. The UA Instance when unit attention condition is established because the LSISS2520/LSISS2530 device entered drive-down state. The UA Instance when unit attention condition is established because the LSISS2520/LSISS2530 device entered system-down state. Instance ID reserved, removed from the current implementation. The UA Instance when unit attention condition is established because reboot due to panic occurred in the LSISS2520/LSISS2530 device firmware. The UA Instance when unit attention condition is established because the LSISS2520/LSISS2530 device was unable to program the set link speed configured using the mode page interface The UA Instance when unit attention condition is established to inform the initiator that the Inquiry data has been changed. The UA Instance when unit attention condition is established to inform the initiator that the underlying hardware is A0

INST_DEFLTVAL_UA_LOG_PAR 10 AMETERS_CHANGED

INST_CLEAR_UA_LOG_PARAM 11 ETERS_CHANGED

UA_ERROR_CODE_LOG_PARA 7 METERS_CHANGED

INST_UA_MODE_PARAMETER 12 S_CHANGED INST_UA_BACKGROUND_SELF 13 _TEST_FAILED INST_UA_LINK_DOWN INST_UA_CTS_LUN_RESET 14 15

UA_ERROR_CODE_MODE_PA 8 RAMETERS_CHANGED UA_ERROR_CODE_BACKGRO 9 UND_SELF_TEST_FAILED UA_ERROR_CODE_DRIVE_NO 10 N_POWERON_RESET UA_ERROR_CODE_DRIVE_NO 10 N_POWERON_RESET UA_ERROR_CODE_DRIVE_DO 14 WN UA_ERROR_CODE_SYSTEM_D 15 OWN NA NA

INST_UA_DRIVE_DOWN

16

INST_UA_SYSTEM_DOWN

17

INST_ID_SEQERR_FORMAT_RE 18 SPONSE INST_UA_CRASH_RESET 19

UA_ERROR_CODE_CRASH_RE 13 SET_OCCURED UA_ERROR_CODE_SATA_LINK 15 SPEED_SET_ERR

INST_UA_SATA_LINK_SPEED_S 20 ET_ERROR

INST_UA_INQ_DATA_CHANGE 21 D INST_UA_ERROR_CODE_A0_H 22 ARDWARE

UA_ERROR_CODE_INQ_DATA 16 _CHANGED UA_ERROR_CODE_A0_HARD 17 WARE

Page 274

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Appendix F:

| Error Lookup Table

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_ID_CC_BACKGROUND_E 23 RRORS INST_ATAPASSTHRU_1_CC_N O_SNS_DATA INST_ATAPASSTHRU_2_CC_N O_SNS_DATA INST_ATAPASSTHRU_3_CC_N O_SNS_DATA 24 25 26

CC_ERROR_CODE_BACKGRO 39 UND_ERRRS NA NA NA NA NA NA

The CC-sense not ready instance for Start Stop Unit command when the operation fails but no additional information is available. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. The CC-no sense data instance when the LSISS2520/LSISS2530 device firmware upgrade fails because of failure to write data to flash, but no additional information available. The CC-no sense data instance when Bootloader upgrade fails because of failure to write data to flash, but no additional information available. Instance ID reserved, removed from the current implementation. The CC-no sense data instance when Boot Option upgrade fails because of failure to write data to flash, but no additional information available. The CC- Hardware error instance for Log Select command to NV Scratch page when the log select command fails because of memory access failure. The CC-Hardware error instance for Log Sense command to NV Scratch page when the log sense command fails because of memory access failure. The CC-aborted command, Log Sense to Log Page 34h fails because of memory allocation failure. Instance ID reserved, for future planned feature. The CC-becoming ready instance for Start Stop Unit command when drive is in the process of becoming ready. The CC-becoming ready instance for Log Select command, Application Client Logpage when the drive is in the process of becoming ready. The CC-becoming ready instance for Log Sense command, when a page which requires the drive to be in ready state is requested but the drive is in process of becoming ready. The CC-becoming ready instance when a command checks LU state and the result is that drive is becoming ready. The CC-becoming ready instance when a command checks LU state and the result is that microcode is getting upgraded.

INST_WRBUF_FLASHFAIL_1_C 27 C_HW_ERR

CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED

INST_WRBUF_FLASHFAIL_2_C 28 C_HW_ERR INST_WRBUF_FLASHFAIL_3_C 29 C_HW_ERR INST_WRBUF_FLASHFAIL_4_C 30 C_HW_ERR INST_NV_SCRATCH_PAGE_WR 31 _FLASHFAIL_1_CC_HW_ERR INST_NV_SCRATCH_PAGE_RD 32 _FLASHFAIL_1_CC_HW_ERR INST_DA_LOGS_CC_ABRTED_I 33 NSF_RES INST_CC_DEFECT_LIST_NOT_ 34 FOUND INST_SRT_STP_UNT_CC_BECO 35 MING_RDY INST_LGSLT_CC_BECOMING_R 36 DY INST_LGSNS_CC_BECOMING_ 37 RDY

CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 35 LASH_ACCESS_FAILED CC_ERROR_CODE_ABORTED_ 35 INSUFFICIENT_RES CC_ERROR_CODE_DEFECT_LI 36 ST_NOT_FOUND CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY 45 45

45

INST_CHK_LUST_DRIVEDOWN 38 _CC_BECOMING_RDY INST_CHK_LUST_MICROCODE 39 _UPGRD_CC_BECOMING_RDY

CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY

45 45

LSI Corporation Confidential | October 2010

Page 275

Appendix F:

| Error Lookup Table

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx 45

InstId

Default ErrorIdx

Explanation

INST_CHK_LUST_STARTUP_CC 40 _BECOMING_RDY INST_MDSNS_CC_BECOMING 41 _RDY INST_RVMDSEL_CC_BECOMIN 42 G_RDY INST_WRITEBUF_UNT_CC_BEC 43 OMING_RDY INST_SND_RECV_DIAG_CC_BE 44 COMING_RDY INST_SRT_STP_UNT_CC_SELF 45 _TEST_IN_PROG INST_CHK_LUST_CC_SELF_TE 46 ST_IN_PROG INST_SND_RECV_DIAG_BG_TS 47 T_CC_SELF_TEST_IN_PROG INST_SND_RECV_DIAG_FG_TS 48 T_CC_SELF_TEST_IN_PROG INST_CC_SNS_NT_RDY_FMT_I 49 N_PROG INST_CHK_LUST_CC_INIT_CM 50 D_REQD INST_TST_UNT_RDY_CC_SNS_ 51 NT_RDY_LU_NORESPOND

CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY CC_ERROR_CODE_BECOMIN G_READY

The CC-becoming ready instance when a command checks LU state and the result is that startup operation is in progress. The CC-becoming ready instance fro Mode Sense command when Control Mode page is requested and drive is in the process of becoming ready. The CC-becoming ready instance for Mode Select command when drive is in the process of becoming ready. The CC-becoming ready instance for Write Buffer command when the mode requires drive to be in ready state and drive is in the process of becoming ready. Instance ID reserved, for a feature planned for future. The CC-self test in progress instance for Start Stop Unit command when foreground self test is in progress. The CC-self test in progress instance when a command checks LU state and the result is that a self test is in progress. Instance ID reserved, for a feature planned for future. Instance ID reserved, for a feature planned for future. The CC-format in progress instance when a command checks LU state and the result is that format operation is in progress. The CC-initializing command required a command checks LU state and the result is that the drive is in standby mode and requires an initializing command. The CC-not ready, LU did not respond to selection instance when the Test Unit Ready command is check conditioned because the logical unit did not respond to selection. The CC-miscompare during verify instance returned when CRC check failed during write and verify operation. The CC-defect list not found instance for Read Defect Data command when he requested defect list format and returned defect list format are not same. The CC-ATA pass through info available instance for the LSISS2520/LSISS2530 device Pass Through command with CK_COND bit set when the command completes successfully. Instance ID reserved, removed from the current implementation. The CC-hardware error, no sense instance for Mode Select command when the command fails, but no additional information is available.

45

45 45

45

CC_ERROR_CODE_SELF_TEST 44 _IN_PROGRESS CC_ERROR_CODE_SELF_TEST 44 _IN_PROGRESS CC_ERROR_CODE_SELF_TEST 44 _IN_PROGRESS CC_ERROR_CODE_SELF_TEST 44 _IN_PROGRESS CC_ERROR_CODE_SNS_NOT_ 43 RDY_FMT_IN_PROG CC_ERROR_CODE_SNS_NOT_ 40 RDY_INIT_CMD_REQUIRED CC_ERROR_CODE_SNS_NOT_ 41 RDY_NO_RESP_BY_LU

INST_WVFY_CC_MISCOMP_D 52 URING_VFY INST_RD_DFECT_DATA_CC_RE 53 C_ERR_LST_NOT_FOUND INST_CC_REC_ERR_ATAPASST 54 HRU_INFO_AVAILABLE

CC_ERROR_CODE_MISCOMP 47 _DURING_VERIFY CC_ERROR_CODE_REC_ERR_ 75 DEFECT_LIST_NT_FOUND CC_ERROR_CODE_REC_ERR_ 76 ATAPASSTHRU_INFO_AVAILA BLE NA NA

INST_CC_BGND_TST_FAILED

55

INST_MDSEL_RV_CC_HWERR_ 56 NOSNS

CC_ERROR_CODE_HW_ERR_ 48 NO_SENSE

Page 276

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Appendix F:

| Error Lookup Table

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_SNDRCV_DIAG_1_CC_H 57 WERR_SLFTST_FAIL INST_SNDRCV_DIAG_2_CC_H 58 WERR_SLFTST_FAIL INST_SNDRCV_DIAG_3_CC_H 59 WERR_SLFTST_FAIL INST_CHK_LUST_DRIVEDOWN 60 _CC_DRIVE_DOWN INST_SET_VER_LGPG_CC_HW 61 _ERR INST_START_STOP_CNT_LGPG 62 _CC_HW_ERR INST_MDSEL_RV_CC_MEDIUM 63 _ERROR_NOSNS INST_MDSEL_DRV_CMD_FAIL 64 _CC_HW_ERROR_NOSNS INST_SMART_ERRCODE_CC_A 65 BRTD_PARAM_NOT_SUP INST_RWV_LGPG_CC_HW_ER 66 R INST_GET_STRT_STP_CNT_LG 67 PG_CC_HW_ERR INST_NON_MED_ERR_LGPG_C 68 C_HW_ERR INST_GET_VER_LGPG_CC_HW 69 _ERR INST_DA_LGPG_FLASHFAIL_C 70 C_HW_ERR_1 INST_DA_LGPG_FLASHFAIL_C 71 C_HW_ERR_2 INST_SET_DA_TEMP_LGPG_C 72 C_HW_ERR INST_GET_DA_TEMP_LGPG_C 73 C_HW_ERR

CC_ERROR_CODE_HW_ERR_L 54 U_SELF_TEST_FAILED CC_ERROR_CODE_HW_ERR_L 54 U_SELF_TEST_FAILED CC_ERROR_CODE_HW_ERR_L 54 U_SELF_TEST_FAILED CC_ERROR_CODE_DRIVE_IS_ 55 DOWN CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_MEDIUM_ ERROR_NO_SENSE NA

Instance ID reserved, for a feature planned for future. Instance ID reserved, for a feature planned for future. Instance ID reserved, for a feature planned for future. The CC-drive is down instance when a command checks LU state and the result is that the underlying SATA drive is in a down state. The CC-Hw error, instance for Log Select command to Version Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Select command to Start Stop Cycle Counter Logpage when write to nonvolatile memory fails. Instance ID reserved, removed from the current implementation. The CC-Hw error, no sense instance for Mode Select command when the LSISS2520/LSISS2530 device cannot post commands to the underlying SATA drive. The CC-aborted command, the SCT command returns the unexpected status. The CC-Hw error, instance for Log Sense command to Read/Write/Verify Error Counter Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Start Stop Cycle Counter Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Non Medium Error Counter Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Versions Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Drive Attachment Logs Logpage when access to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Drive Attachment Logs Logpage when access to nonvolatile memory fails (clearing the logs/crash dump). The CC-Hw error, instance for Log Select command to Drive Attachment Temperature Logpage when write to nonvolatile memory fails. The CC-Hw error, instance for Log Sense command to Drive Attachment Temperature Logpage when write to nonvolatile memory fails.

CC_ERROR_CODE_HW_ERR_ 48 NO_SENSE CC_ERROR_CODE_ABORTED_ 106 PARAM_NOT_SUPPORTED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED CC_ERROR_CODE_HW_ERR_F 104 LASH_ACCESS_FAILED

LSI Corporation Confidential | October 2010

Page 277

Appendix F:

| Error Lookup Table

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_CHK_LUST_CC_MEDIUM 74 _ERROR_FMT_CORRUPTED INST_WRBUF1_CC_MEDIUM_E 75 RROR_DEV_WT_FAULT INST_WRBUF2_CC_MEDIUM_E 76 RROR_DEV_WT_FAULT INST_REASS_BLK1_CC_MEDIU 77 M_ERR_AUTOREALLOC_FAIL INST_REASS_BLK2_CC_MEDIU 78 M_ERR_AUTOREALLOC_FAIL INST_VFY_CC_MEDIUM_ERRO 79 R_AUTO_RELOC_FAILED INST_WT_VFY_CC_MEDIUM_E 80 RROR_AUTO_RELOC_FAILED INST_SEEK_CC_MEDIUM_ERR 81 OR_AUTO_RELOC_FAILED INST_HDL_RSP_ABT_CMD_CC 82 _ABRTD_LU_TIMEOUT INST_DRV_RST_TIMEOUT_CC_ 83 ABRTD_LU_TIMEOUT INST_HDL_ABRTD_RSP_CC_A 84 BRTD_LU_TIMEOUT

CC_ERROR_CODE_MEDIUM_ 57 FORMAT_CORRUPTED CC_ERROR_CODE_PERIPHER AL_DEVICE_WRITE_FAULT CC_ERROR_CODE_PERIPHER AL_DEVICE_WRITE_FAULT 61

The CC-fmedium format corrupted instance when a command checks LU state and the result is that medium format is corrupted. The CC-peripheral device write fault instance for Write Buffer command when firmware image invalidation to upgrade new image fails. The CC-peripheral device write fault instance for Write Buffer command when new firmware image validation fails. The CC-auto reallocate failed instance for Reassign Blocks command. The CC-auto reallocate failed instance for Reassign Blocks command when the ATA write command sent to the underlying SATA drive results in failure. Instance ID reserved, removed from the current implementation. The CC-auto reallocate failed instance for Write Verify command. The CC-auto reallocate failed instance for Seek command. The CC-aborted command, LU time-out instance when a command that was not active on the drive was aborted because of time-out of logical unit. The CC-aborted command, LU time-out instance when command time-out occurs because of reset of the underlying ATA drive. The CC-aborted command, LU time-out instance when a 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. Instance ID reserved, for a feature planned for future. The CC-aborted command, command cleared by another initiator instance when a command was aborted because of TMF from another initiator. The CC-aborted command, command cleared by another initiator instance when a command that was active on drive got aborted since the drive was reset because of TMF from another initiator. The CC-aborted command, command cleared by device server instance when the hardware layer returns the reason of command being aborted as side effect of TMF processing for other initiator.

61

CC_ERROR_CODE_AUTO_REA 62 LLOCATE_FAILED CC_ERROR_CODE_AUTO_REA 62 LLOCATE_FAILED NA NA

CC_ERROR_CODE_AUTO_REA 62 LLOCATE_FAILED CC_ERROR_CODE_AUTO_REA 62 LLOCATE_FAILED CC_ERROR_CODE_ABORTED_ 91 LU_TIMEOUT CC_ERROR_CODE_ABORTED_ 91 LU_TIMEOUT CC_ERROR_CODE_ABORTED_ 91 LU_TIMEOUT

INST_SRCV_DIAG_CC_ABRTD_ 85 ATA_FT_NT_ENB INST_HDL_RSP_ABT_CMD_CC 86 _ABRTD_CMDS_CLRD_BY_OT HER_INIT INST_HDL_ABRTD_RSP_CC_A 87 BRTD_CMDS_CLRD_BY_OTHE R_INIT INST_HDL_ABRTD_RSP_CC_A 88 BRTD_CMDS_CLRD_BY_DEV_ SERVER

CC_ERROR_CODE_ABORTED_ 86 ATA_FEATURE_NT_EN CC_ERROR_CODE_ABORTED_ 93 CMDS_CLRD_BY_OTHER_INIT CC_ERROR_CODE_ABORTED_ 93 CMDS_CLRD_BY_OTHER_INIT

CC_ERROR_CODE_ABORTED_ 98 CMDS_CLRD_BY_DEVSRV

Page 278

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Appendix F:

| Error Lookup Table

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_HDL_ABRTD_RSP_CC_A 89 BRTD_ACK_NAK_TIMEOUT

CC_ERROR_CODE_ABORTED_ 94 ACK_NAK_TIMEOUT

The CC-aborted command, ack-nak time-out instance (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. The CC-aborted command, ack-nak time-out instance (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. The CC-aborted command, nak received instance (case 1) 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. The CC-aborted command, nak received instance (case 2) 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. The CC-aborted command, data offset error instance 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. The CC-aborted command, too much write data error 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. The CC-aborted command, too much write data error instance (case 2) 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. The CC-aborted command, info unit too short error instance (case 1) when the transport protocol layer indicates that the reason of aborted command was that data frame of zero bytes was received from the target. It is recommended that case1 and case 2 for this ErrorIdx must be customized together. The CC-aborted command, info unit too short error instance (case 2) when the transport protocol layer indicates that the reason of aborted command was that data frame of zero bytes was received from the target. It is recommended that case1 and case 2 for this ErrorIdx must be customized together.

INST_TPLERR_CC_ABRTD_ACK 90 _NAK_TIMEOUT

CC_ERROR_CODE_ABORTED_ 94 ACK_NAK_TIMEOUT

INST_HDL_ABRTD_RSP_CC_A 91 BRTD_NAK_RCVD

CC_ERROR_CODE_ABORTED_ 92 NAK_RECEIVED

INST_TPLERR_CC_ABRTD_NA 92 K_RCVD

CC_ERROR_CODE_ABORTED_ 92 NAK_RECEIVED

INST_HDL_ABRTD_RSP_CC_A 93 BRTD_DATA_OFFSET_ERR

CC_ERROR_CODE_ABORTED_ 97 DATA_OFFSET_ERROR

INST_HDL_ABRTD_RSP_CC_A 94 BRTD_TOO_MUCH_WDATA

CC_ERROR_CODE_ABORTED_ 96 TOO_MUCH_WRITE_DATA

INST_TPLERR_CC_ABRTD_TO O_MUCH_WDATA

95

CC_ERROR_CODE_ABORTED_ 96 TOO_MUCH_WRITE_DATA

INST_HDL_ABRTD_RSP_CC_A 96 BRTD_INFO_UNT_TOO_SHOR T

CC_ERROR_CODE_ABORTED_ 95 INFO_UNT_TOO_SHORT

INST_TPLERR_CC_ABRTD_INF 97 O_UNT_TOO_SHORT

CC_ERROR_CODE_ABORTED_ 95 INFO_UNT_TOO_SHORT

LSI Corporation Confidential | October 2010

Page 279

Appendix F:

| Error Lookup Table

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx

InstId

Default ErrorIdx

Explanation

INST_HDL_ABRTD_RSP_CC_A 98 BRTD_DATA_CRC_ERR

CC_ERROR_CODE_ABORTED_ 90 DATA_PHASE_CRC_ERROR

The CC-aborted command, data phase error instance (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 recommended that case1 and case 2 for this ErrorIdx must be customized together. The CC-aborted command, data phase error instance (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 recommended that case1 and case 2 for this ErrorIdx must be customized together. Instance ID reserved, for a feature planned for future. Instance ID reserved, for a feature planned for future. Instance ID reserved, for a feature planned for future. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation.

INST_TPLERR_CC_ABRTD_DAT 99 A_CRC_ERR

CC_ERROR_CODE_ABORTED_ 90 DATA_PHASE_CRC_ERROR

INST_NTFY_DIFERR_CC_ABRT 100 D_LBLK_GRD_CHK_FAILED INST_NTFY_DIFERR_CC_ABRT 101 D_APPTAG_CHK_FAILED INST_NTFY_DIFERR_CC_ABRT 102 D_REFTAG_CHK_FAILED INST_ID_CC_START_STOP_UNI 103 T INST_ID_CC_SAT_SMARTFEAT 104 URES INST_ID_CC_APPCLT_LGPG_L 105 GSLT INST_ID_CC_WRITEBUF INST_ID_CC_READBUFF INST_ID_CC_INQUIRY 106 107 108

CC_ERROR_CODE_ABORTED_ 79 LBLK_GUARD_CHK_FAILED CC_ERROR_CODE_ABORTED_ 81 LBLK_APP_TAG_FAILED CC_ERROR_CODE_ABORTED_ 80 LBLK_REF_TAG_FAILED NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA

INST_ID_CC_REQUEST_SENSE 109 INST_ID_CC_RD_MDFY_RT INST_ID_CC_WRITESAME INST_ID_CC_WRITE INST_ID_CC_READ INST_ID_CC_SYNC_CACHE INST_ID_CC_WRITE_VERITY 110 111 112 113 114 115

Page 280

LSI Corporation Confidential | October 2010

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual

Appendix F:

| Error Lookup Table

Table 259: InstIds (Continued) Numeric Value for InstId NA NA NA NA NA NA NA Numeric Value for default ErrorIdx NA NA NA NA NA NA NA

InstId

Default ErrorIdx

Explanation

INST_ID_CC_APPCLT_LGPG_L 116 GSNS INST_ID_CC_SELFTEST_RESUL 117 T_LGPG INST_ID_BG_SCAN_RES_LGPG 118 INST_ID_CC_WLONG 119

Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. Instance ID reserved, removed from the current implementation. The CC-Invalid field in CDB instance In start stop unit command when control bit in the CDB is set or invalid combination of start bit and LOEJ bit in the CDB occurs The CC-Invalid field in CDB instance In format unit command when control bit in the CDB is set or LongList or CmpList bits in the CDB are set. Instance ID reserved, for a feature planned for future.

INST_ID_CC_SMARTDATA_LGP 120 G INST_ID_CC_INFO_EXCP_LGP 121 G INST_ID_CC_RLONG 122

INST_SND_STP_UNT_CC_INV_ 123 FIELD_IN_CDB INST_FMT_UNT_GET_DATA_C 124 C_INV_FIELD_IN_CDB INST_FMT_UNT_PROCESS_RC 125 V_DATA_CC_INV_FIELD_IN_C DB INST_FMT_UNT_CC_INV_BLK_ 126 LEN_IN_CDB INST_ATAPASSTHRU_CHK_BYT 127 E_XFER_CC_INV_FIELD_IN_CD B INST_ATAPASSTHRU_ERROR_P 128 ATH_RETURN_CC_INV_FIELD_I N_CDB INST_LGSLT_VALIDATE_CDB_C 129 C_INV_FIELD_IN_CDB

CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB

Instance ID reserved, for a feature planned for future. The CC-Invalid field in CDB instance In ATA pass through command when byte transfer is requested. The CC-Invalid field in CDB instance in ATA pass through command when invalid combination of PROTOCOL and T_DIR or T_LENGTH field in the CDB. The CC-Invalid field in CDB instance in Log Select command when control bit in the CDB is set or an invalid combination of PC, PCR and transfer length field in the CDb occurs. The CC-Invalid field in CDB instance in Log Select command when transfer length is higher than maximum and not equal to the size of NV ScratchPage The CC-invalid field in CDB instance in Log Select command for NV Scratch Page when DS or SPF bit is set or if pagelength is incorrect. The CC-invalid field in CDB instance in Log Select command when Read Clear is requested but not supported by the log page.

INST_LGSLT_CHK_XFER_LEN_ 130 CC_INV_FIELD_IN_CDB INST_LGSLT_VALIDATE_NV_SC 131 RATCH_PAGE_HEADER_CC_IN V_FIELD_IN_CDB INST_LGSNS_CHK_RD_CLEAR 132 _SUPPORTED_CC_INV_FIELD_ IN_CDB

CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB

LSI Corporation Confidential | October 2010

Page 281

The CC-invalid field in CDB instance in Write Buffer command if the mode is Download and save Offset and either the field Buffer ID or Buffer offset field in the CDB is set to a nonzero value. when task descriptor is in wait ordered state. The CC-invalid field in CDB instance in Mode Sense command when smart support is turned off and modepage Exceptions control is requested.Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_LGSNS_VALIDATE_CDB_ 133 CC_INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Log Sense command when control or PPC bit in the CDB is set or invalid combination of PC. The CC-invalid field in CDB instance in Mode Select command when the control field in the CDB is set to a nonzero value. removed from the current implementation. The CC-invalid field in CDB instance in Log Sense command when Drive attachment Logpage is requested and the allocation length is not equal to standard size of the LSISS2520/LSISS2530 device Logpage. The CC-invalid field in CDB instance in Mode Select command when the block length field in the block descriptor is not equal to SATA block size. The CC-invalid field in CDB instance in Log Sense command when the page code requested for is not supported. The CC-invalid field in CDB instance in Write Buffer command when in Data mode and the fields Buffer ID 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. The CC-invalid field in CDB instance in Mode Sense command when the page code requested is not supported. INST_LGSNS_CHK_ALLOCATIO 134 N_LEN_CC_INV_FIELD_IN_CD B INST_LGSNS_INVAILD_PGCOD 135 E_CASE_CC_INV_FIELD_IN_CD B INST_GET_MDPG_INFO_EXCP 136 _CC_INV_FIELD_IN_CDB INST_MDSNS_CHK_NONZERO 137 _CONTROL_CC_INV_FIELD_IN _CDB INST_MDSNS_CHK_MEMORY_ 138 REQD_CC_INV_FIELD_IN_CDB INST_MDSNS_CHK_MODE_PG 139 _DATA_FILL_1_CC_INV_FIELD _IN_CDB INST_MDSNS_CHK_MODE_PG 140 _DATA_FILL_2_CC_INV_FIELD _IN_CDB INST_MDSEL_CC_INV_FIELD_I 141 N_CDB INST_MDSEL_CC_INV_BLK_LE 142 N_IN_CDB INST_WRBUF_MODE_SUPPOR 143 TING_NONZER0_BUFID_CC_IN V_FIELD_IN_CDB INST_WRBUF_MODE2_PARAM 144 _LEN_NON512_CC_INV_FIELD _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_WRBUF_MODE2_BUFID_ 145 NONZERO_CC_INV_FIELD_IN_ CDB NA NA Page 282 LSI Corporation Confidential | October 2010 . The CC-invalid field in CDB instance in Mode Sense command when the control field is set to a nonzero value. Page Code and Param Pointer occurs. The CC-invalid field in CDB instance in Mode Sense command when the drive cannot return data. Instance ID reserved. when task descriptor is in wait for drive response state. The CC-invalid field in CDB instance in Mode Sense command when the drive cannot return data.

Instance ID reserved. The CC-invalid field in CDB instance in Read Capacity 16 command when one of the LBA. The CC-invalid field in CDB instance in Read Defect Data 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. for a feature deprecated. The CC-invalid field in CDB instance in Reassign Blocks 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. The CC-invalid field in CDB instance in Read Capacity 10 command when one of the LBA. Instance ID reserved. for a feature deprecated. The CC-invalid field in CDB instance in Write Buffer command when the Identify Device Byte 234 is nonzero and Parameter length is lesser than the same.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_WRBUF_MODE7_DRV_F 146 W_BUFFOFFSET_CC_INV_FIEL D_IN_CDB INST_WRBUF_PARAMLEN_GRE 147 ATER_ID_DATA_BYTE235_CC_I NV_FIELD_IN_CDB INST_WRBUF_PARAMLEN_LES 148 S_ID_DATA_BYTE234_CC_INV _FIELD_IN_CDB INST_WRBUF_MODE7_BUF_ID 149 1_FIRST_WB_BUFFOFFSET_N ONZERO_CC_INV_FIELD_IN_C DB INST_RDBUF_ILLEGAL_CMD_ 150 CC_INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Write Buffer command if the mode is Download and save Offset. The CC-invalid field in CDB instance when the first Write Buffer command for the LSISS2520/LSISS2530 device firmware upgrade has buffer offset field in the CDB set to a nonzero value. Instance ID reserved. PMI or Control field in the CDB is set to a nonzero value. The CC-invalid field in CDB instance in Read Buffer 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. The CC-invalid field in CDB instance in read Buffer command when in Descriptor mode and the allocation length field in the CDB is set to a value less than the minimum allowed for SATA Read Descriptor. The CC-invalid field in CDB instance in Read Capacity 16 command when the service action field in the CDB is set to an unsupported value. for a feature deprecated. buffer ID is zero and the lower 8 bits of Buffer offset fields in the CDB are nonzero. CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_RDBUF_CHK_ALLOCATI 151 ON_LEN_CC_INV_FIELD_IN_C DB INST_REASS_BLK_CC_INV_FIE 152 LD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_RD_DEFECT_DATA_CC_I 153 NV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_RD_CAPACITY10_CDB_C 154 HK_CC_INV_FIELD_IN_CDB INST_RD_CAPACITY16_CDB_C 155 HK_CC_INV_FIELD_IN_CDB INST_RD_CAPACITY_UNSUPP 156 ORTED_SRV_ACTION_CC_INV _FIELD_IN_CDB INST_REZERRO_UNIT_CC_INV 157 _FIELD_IN_CDB INST_RESERVE_REL10_CC_INV 158 _FIELD_IN_CDB INST_RESERVE_REL6_CC_INV_ 159 FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB LSI Corporation Confidential | October 2010 Page 283 . The CC-invalid field in CDB instance in Write Buffer command when the Identify Device Byte 235 is nonzero and Parameter length is greater than the same. PMI or Control field in the CDB is set to a nonzero value.

Exclusive. Prempt.Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_PER_RESERVE_OUT_CC_ 160 INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Persistent Reserve Out command when the service action code is one of Reserve. Write Exclusive Registrants Only and Exclusive Registrants Only. The CC-invalid field in CDB instance in Persistent Reserve In command when the service action code is Read Reservation and the allocation length provided is insufficient to transfer the required data. The CC-invalid field in CDB instance in Persistent Reserve In command when the service action code is Read Full Status and the allocation length provided is insufficient to transfer the required data. INST_PER_RESERVE_IN_CC_IN 161 V_FIELD_IN_CDB INST_PRI_RD_KEYS_CC_INV_F 162 IELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_PRI_RD_RESERVATION_C 163 C_INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_PRI_REPORT_CAPABILITI 164 ES_CC_INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_PRI_RD_FULL_STATUS_C 165 C_INV_FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_REPORT_LUNS_CC_INV_ 166 FIELD_IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_REQUEST_SENSE_CC_IN 167 V_FIELD_IN_CDB INST_TST_UNT_RDY_CC_INV_ 168 FIELD_IN_CDB INST_VALIDATE_RW6_CDB_CC 169 _INV_FIELD_IN_CDB INST_VALIDATE_RW10_CDB_V 170 ALIDATION_CC_INV_FIELD_IN _CDB INST_VALIDATE_RW10_CDB_I 171 NVAILD_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_RW12_CDB_V 172 ALIDATION_CC_INV_FIELD_IN _CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Read/Write 12 command when control. The CC-invalid field in CDB instance in Read/Write 10 command when control. Release. The CC-invalid field in CDB instance in Request Sense command when the control bit or DESC bit in the CDB is set to a nonzero value. The CC-invalid field in CDB instance in Read/Write 6 command when control field in the CDB is set to a nonzero value. The CC-invalid field in CDB instance in Persistent Reserve In command when the control field in CDB is set or the service action code is set to an unsupported value. The CC-invalid field in CDB instance in Report LUNS 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. The CC-invalid field in CDB instance in Persistent Reserve In command when the service action code is Report Capabilities and the allocation length provided is insufficient to transfer the required data. FUA_NV or DPO field in CDB is set to nonzero value. Instance ID reserved. The CC-invalid field in CDB instance in Persistent Reserve In command when the service action code is Read Keys and the allocation length provided is insufficient to transfer the required data. FUA_NV or DPO field in CDB is set to nonzero value. Prempt and Abort and Register and Move. Page 284 LSI Corporation Confidential | October 2010 . The CC-invalid field in CDB instance in Test Unit Ready command when the control bit in the CDB is set to a nonzero value. for a feature planned for future. and the type is not of one Write Exclusive.

FUA_NV or DPO field in CDB is set to nonzero value.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_VALIDATE_RW12_CDB_I 173 NVAILD_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_RW16_CDB_V 174 AILADTION_CC_INV_FIELD_IN _CDB INST_VALIDATE_RW16_CDB_I 175 NVAILD_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_RW32_CDB_V 176 AILADTION_CC_INV_FIELD_IN _CDB INST_VALIDATE_PROTECTION 177 _DIF_CHK_CC_INV_FIELD_IN_ CDB INST_VALIDATE_PROTECTION 178 _MODEL_CHK_CC_INV_FIELD _IN_CDB INST_VALIDATE_WR_PROTECT 179 ION_CHK_CC_INV_FIELD_IN_ CDB INST_VALIDATE_RD_PROTECTI 180 ON_CHK_CC_INV_FIELD_IN_C DB INST_VALIDATE_WS10_CDB_V 181 ALIDATION_CC_INV_FIELD_IN _CDB INST_VALIDATE_WS10_CDB_L 182 B_PB_DATA_SUPPORT_CC_IN V_FIELD_IN_CDB INST_VALIDATE_WS10_CDB_I 183 NVALID_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_WS16_CDB_V 184 ALIDATION_CC_INV_FIELD_IN _CDB INST_VALIDATE_WS16_CDB_L 185 B_PD_DATA_SUPPORT_CC_IN V_FIELD_IN_CDB INST_VALIDATE_WS16_CDB_I 186 NVALID_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_WS32_CDB_V 187 ALIDATION_CC_INV_FIELD_IN _CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB Instance ID reserved. FUA_NV or DPO field in CDB is set to nonzero value. The CC-invalid field in CDB instance in Read/Write 16 command when control. for a feature planned for future. The CC-invalid field in CDB instance in Read/Write 32 command when control. for a feature planned for future. for a feature planned for future. The CC-invalid field in CDB instance in Write Same 16 command when LBDATA and PBDATA fields in the CDB are both set to 1. for a feature planned for future. The CC-invalid field in CDB instance in Write Same 10 command when LBDATA and PBDATA fields in the CDB are both set to 1. for a feature planned for future. Instance ID reserved. Instance ID reserved. Instance ID reserved. The CC-invalid field in CDB instance in Write Same 32 command when the control field in the CDB is set to a nonzero value. Instance ID reserved. for a feature planned for future. The CC-invalid field in CDB instance in Write Same 16 command when the control field in the CDB is set to a nonzero value. Instance ID reserved. Instance ID reserved. for a feature planned for future. LSI Corporation Confidential | October 2010 Page 285 . for a feature planned for future. The CC-invalid field in CDB instance in Write Same 10 command when the control field in the CDB is set to a nonzero value. Instance ID reserved.

for a feature planned for future. for a feature planned for future.Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_VALIDATE_WS32_CDB_L 188 B_PD_DATA_SUPPORT_CC_IN V_FIELD_IN_CDB INST_VALIDATE_WS32_CDB_I 189 NVALID_PROTECTION_CC_INV _FIELD_IN_CDB INST_VALIDATE_VERIFY10_CD 190 B_VALIDATION_CC_INV_FIELD _IN_CDB INST_VALIDATE_VERIFY10_CD 191 B_INVALID_PROTECTION_CC_I NV_FIELD_IN_CDB INST_VALIDATE_VERIFY12_CD 192 B_VALIDATION_CC_INV_FIELD _IN_CDB INST_VALIDATE_VERIFY12_CD 193 B_INVALID_PROTECTION_CC_I NV_FIELD_IN_CDB INST_VALIDATE_VERIFY16_CD 194 B_VALIDATION_CC_INV_FIELD _IN_CDB INST_VALIDATE_VERIFY16_CD 195 B_INVALID_PROTECTION_CC_I NV_FIELD_IN_CDB INST_VALIDATE_VERIFY32_CD 196 B_VALIDATION_CC_INV_FIELD _IN_CDB INST_VALIDATE_VERIFY32_CD 197 B_INVALID_PROTECTION_CC_I NV_FIELD_IN_CDB INST_SYNC_CACHE_CC_INV_F 198 IELD_IN_CDB INST_SND_RECV_DIAG_VALID 199 ATE_CDB_CC_INV_FIELD_IN_C DB INST_SND_RECV_DIAG_LED_C 200 NTRL_PG_CC_INV_FIELD_IN_ CDB INST_SND_RECV_DIAG_ALTA_ 201 SELF_TEST_PG_CC_INV_FIELD _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Write Same 16 command when LBDATA and PBDATA fields in the CDB are both set to 1. CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Synchronize Cache command when control or sync_nv field in the CDb is set to a nonzero value. The CC-invalid field in CDB instance in Write and Verify 10/Verify 10 commands if control or DPO bit is set or in Verify 10 command if BYTECHK field is set to a nonzero value. CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Write and Verify 10/Verify 32 commands if control or DPO bit is set or in Verify 10 command if BYTECHK field is set to a nonzero value. CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Write and Verify 10/Verify 16 commands if control or DPO bit is set or in Verify 10 command if BYTECHK field is set to a nonzero value. Page 286 LSI Corporation Confidential | October 2010 . Instance ID reserved. for a feature planned for future. Instance ID reserved. Instance ID reserved. Instance ID reserved. CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB The CC-invalid field in CDB instance in Write and Verify 10/Verify 12 commands if control or DPO bit is set or in Verify 10 command if BYTECHK field is set to a nonzero value. for a feature planned for future. Instance ID reserved. for a feature planned for future. Instance ID reserved. Instance ID reserved. Instance ID reserved. for a feature planned for future. for a feature planned for future. for a feature planned for future.

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

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

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

The CC-invalid parameter list length instance for Persistent Reserve Out command when the initiator sends insufficient data. The CC-invalid parameter list length instance for the LSISS2520/LSISS2530 device firmware upgrade when the length of image provided by initiator is greater than the maximum LSISS2520/LSISS2530 device firmware image size allowed. Instance ID reserved. The CC-invalid parameter list length instance for Reassign Blocks command when length of LBA header list is equal to zero. Instance ID reserved. Instance ID reserved. The CC-invalid parameter list length instance for Log 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. Instance ID reserved. for a feature planned for future. INST_REASS_BLK_1_CC_PARA 252 M_LIST_LEN_ERR INST_REASS_BLK_2_CC_PARA 253 M_LIST_LEN_ERR INST_REASS_BLK_3_CC_PARA 254 M_LIST_LEN_ERR INST_REASS_BLK_4_CC_PARA 255 M_LIST_LEN_ERR INST_RES_REL_CC_PARAM_LI 256 ST_LEN_ERR INST_PER_RES_OUT_1_CC_PA 257 RAM_LIST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_INV_FIELD 71 _IN_PARAM_LIST CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR INST_PER_RES_OUT_2_CC_PA 258 RAM_LIST_LEN_ERR INST_WR_SAME_CC_PARAM_ 259 LIST_LEN_ERR INST_SND_DIAG_CC_PARAM_ 260 LIST_LEN_ERR INST_NV_SCRTACH_PAGE_CC 261 _PARAM_LIST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR INST_WRBUF_1_CC_INV_FIEL 262 D_IN_CDB CC_ERROR_CODE_INV_FIELD 66 _IN_CDB Page 290 LSI Corporation Confidential | October 2010 . for a feature deprecated. for a feature planned for future. The CC-invalid parameter list length instance for 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. The CC-invalid parameter list length instance for Write Buffer command when the initiator sends insufficient data. removed from the current implementation. The CC-invalid parameter list length instance for Write Same command when the initiator sends insufficient data. The CC-invalid parameter list length instance for Mode Select command when the initiator sends insufficient data.Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_DA_TEMP_LGPG_CC_PA 247 RAM_LIST_LEN_ERR INST_MDSEL_CC_PARAM_LIST 248 _LEN_ERR INST_WRBUF_1_CC_PARAM_L 249 IST_LEN_ERR INST_WRBUF_2_CC_PARAM_L 250 IST_LEN_ERR INST_WRBUF_INVALID_ALTA_I 251 MAGE_LEN_CC_PARAM_LIST_ LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR The CC-invalid parameter list length instance for Log Select command for Drive Attachment Temp Logpage when the initiator sends insufficient data. The CC-invalid operation code instance for command Write Buffer when the value of the mode field in CDB indicates an unsupported mode. The CC-invalid parameter list length instance for Reassign Blocks command when the number of LBAs transferred gets calculated as zero. The CC-invalid parameter list length instance for Reassign Blocks command when the longlba bit in the CDB is set and length of LBA header list is not a multiple of 8.

for a feature planned for future. Instance ID reserved. Instance ID reserved. for a feature planned for future. for a feature planned for future. The CC-invalid operation code instance for command Log Sense when Application Clients Log Page is requested but smart feature is not enabled or smart self test is not supported by the drive. Instance ID reserved. INST_BACKGRND_SCAN_LGPG 274 _CC_INV_OPCODE CC_ERROR_CODE_INV_OPCO 66 DE INST_PROCESS_USING_SAT_C 275 C_INV_OPCODE INST_VALIDATE_RW32_CDB_I 276 NVAILD_PROTECTION_CC_INV _OPCODE INST_SMART_DATA_LGPG_CC 277 _INV_OPCODE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE The CC-invalid operation code instance for command Log Sense when SATA Firmware Statistics Page is requested but smart feature is not enabled or smart self test is not supported by the drive. Instance ID reserved. for a feature planned for future. for a feature planned for future. for a feature planned for future. for a feature planned for future. The CC-invalid operation code instance for command Log 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. Instance ID reserved. The CC-invalid operation code instance for command Read Buffer when the word 82 of Identify device data indicates that the drive does not support the command.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_WRBUF_2_CC_INV_OPC 263 ODE INST_RDBUF_CC_INV_OPCOD 264 E INST_TYPE1_PROTECT_CC_IN 265 V_OPCODE INST_TYPE2_PROTECT_CC_IN 266 V_OPCODE INST_TYPE3_PROTECT_CC_IN 267 V_OPCODE INST_VALID_RW6CDB_CC_INV 268 _OPCODE INST_VALID_PROTECT_CHK_C 269 C_INV_OPCODE INST_SMART_WR_SAME_CC_I 270 NV_OPCODE INST_WR_LONG_CC_INV_OPC 271 ODE INST_RD_LONG_CC_INV_OPC 272 ODE INST_SELF_TEST_LGPG_CC_IN 273 V_OPCODE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE CC_ERROR_CODE_INV_OPCO 66 DE The CC-invalid operation code instance for command Write Buffer because of an invalid combination of mode and buffer ID fields in the CDB. for a feature planned for future. INST_APP_CLNT_LGPG_CC_IN 278 V_OPCODE CC_ERROR_CODE_INV_OPCO 66 DE LSI Corporation Confidential | October 2010 Page 291 . Instance ID reserved. The CC-invalid operation code instance for command Log 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. Instance ID reserved. Instance ID reserved. Instance ID reserved. The CC-invalid operation code instance returned when a command with invalid operation code is sent to the drive. for a feature planned for future.

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

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

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

NA NA The CC error code depends upon the error code returned by drive .Refer to Table 260.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 259: InstIds (Continued) Numeric Value for InstId NA Numeric Value for default ErrorIdx NA InstId Default ErrorIdx Explanation INST_RMW_RSP_DRV_ERR_BA 436 SE = INST_DRA_MDPG_DRV_ERR_B ASE + DRV_ERR_MAX INST_WT_DRV_ERR_BASE = 451 INST_RMW_RSP_DRV_ERR_BA SE + DRV_ERR_MAX INST_RD_DRV_ERR_BASE = INST_WT_DRV_ERR_BASE + DRV_ERR_MAX 466 The CC error code depends upon the error code returned by drive .Refer to Table 260. NA NA INST_WT_BUFF_DRV_ERR_BA 481 SE = INST_RD_DRV_ERR_BASE + DRV_ERR_MAX INST_RD_BUFF_DRV_ERR_BAS 496 E= INST_WT_BUFF_DRV_ERR_BA SE + DRV_ERR_MAX INST_REQ_SNS_DRV_ERR_BAS 511 E= INST_RD_BUFF_DRV_ERR_BAS E + DRV_ERR_MAX INST_WSAME_DRV_ERR_BASE 526 = INST_REQ_SNS_DRV_ERR_BAS E + DRV_ERR_MAX INST_SYNC_CACHE_DRV_ERR 541 _BASE = INST_WSAME_DRV_ERR_BASE + DRV_ERR_MAX INST_VFY_DRV_ERR_BASE 556 = INST_SYNC_CACHE_DRV_ERR _BASE + DRV_ERR_MAX INST_WT_VFY_DRV_ERR_BAS 571 E = INST_VFY_DRV_ERR_BASE + DRV_ERR_MAX INST_WLONG_DRV_ERR_BASE 586 = INST_WT_VFY_DRV_ERR_BAS E + DRV_ERR_MAX INST_RLONG_DRV_ERR_BASE 601 = INST_WLONG_DRV_ERR_BASE + DRV_ERR_MAX INST_APPCLT_LGSNS_DRV_ER 616 R_BASE = INST_RLONG_DRV_ERR_BASE + DRV_ERR_MAX NA NA NA NA NA NA The CC error code depends upon the error code returned by drive .Refer to Table 260. NA NA The CC error code depends upon the error code returned by drive .Refer to Table 260 NA NA NA NA The CC error code depends upon the error code returned by drive . The CC error code depends upon the error code returned by drive .Refer to Table 260.Refer to Table 260. NA NA The CC error code depends upon the error code returned by drive . The CC error code depends upon the error code returned by drive .Refer to Table 260.Refer to Table 260.Refer to Table 260.Refer to Table 260. NA NA The CC error code depends upon the error code returned by drive .Refer to Table 260. The CC error code depends upon the error code returned by drive .Refer to Table 260. NA NA The CC error code depends upon the error code returned by drive . The CC error code depends upon the error code returned by drive . NA NA The CC error code depends upon the error code returned by drive .Refer to Table 260. LSI Corporation Confidential | October 2010 Page 295 .

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

commands with Protect field set to a nonzero value. The CC error code depends upon the error code returned by drive . The CC-Invalid field in CDB instance for WriteBuffer when Invalid parameter list length/buffer offset is received for mode 7 buffer Id 0 drive firmware upgrade. The CC-invalid field in CDB instance for MDIO access command. The CC-Invalid field in CDB instance for WriteBuffer when Invalid BuffId is received for mode 0x7.LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 259: InstIds (Continued) Numeric Value for InstId Numeric Value for default ErrorIdx InstId Default ErrorIdx Explanation INST_UNREGISTER_UA_RESER 701 VATIONS_CLEARED UA_ERROR_CODE_RESERVATI 4 ONS_CLEARED UA-Reservations cleared Instance. The CC-invalid field in CDB instance for READ. WRITE. The CC-Invalid field in CDB instance for Write Buffer command where multiple Write Buffer package upgrade is going on and parameter list length is less than 1k or not multiple of 1k. etc. The CC-Invalid field in CDB instance for Write Buffer command Boot option upgrade using Mode 7 buffer ID 3 and buffer offset is nonzero. The CC-invalid field in CDB instance for MDIO access command. This is returned for the 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_INV_FIELD_IN_CDB INST_MDIO_ACCESS_INV_DAT 703 A_OR_ADDR INST_MDIO_ACCESS_INV_DEV 704 _TYPE INST_WRBUF_MULTIPLE_PKG_ 705 UPG_INVALID_BUFFOFFSET CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_WRBUF_MULTIPLE_PKG_ 706 UPG_INVALID_PLL CC_ERROR_CODE_INV_FIELD 64 _IN_CDB INST_WRBUF_CC_DRV_NT_SU 707 PPRT_MULTI_DNLD_OR_WRO NG_LENGTH CC_ERROR_CODE_INV_FIELD 65 _IN_PARAM_LIST INST_WRBUF_CC_INV_FLD_C 708 DB_BOOT_OPT_UPGRADE_N ONZERO_BUFOFFSET INST_SECURITY_IN_OUT_CC_I 709 NV_OPCODE INST_SECURITY_IN_OUT_CHK 710 _ALLOC_LEN_CC_INV_FIELD_I N_CDB INST_TRUSTED_CMD_DRV_ER 711 R_BASE INST_WRBUF_CC_ALTA_IMAG 726 E_SMALL_SIZE = INST_TRUSTED_CMD_DRV_ER R_BASE + DRV_ERR_MAX INST_UA_WB_DFW_UPGRADE 727 _MICROCODE_CHANGED INST_WRBUF_MD7_INV_BUFI 728 D_CC_INV_FLD_IN_CDB INST_WRBUF_CC_MODE7_BU 729 FID0_CDB_VALIDATION CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB NA NA CC_ERROR_CODE_PARAM_LI 71 ST_LEN_ERR UA_ERROR_CODE_MICROCO 3 DE_UPDATED CC_ERROR_CODE_INV_FIELD 64 _IN_CDB CC_ERROR_CODE_INV_FIELD 64 _IN_CDB LSI Corporation Confidential | October 2010 Page 297 .Refer to Table 260. The CC-Parameter List Length error when the LSISS2520/LSISS2530 device firmware size is beyond flash capacity. The CC-Invalid field in CDB instance for Security IN OUT Protocol for invalid allocation length. The CC-Invalid field in Parameter list length instance for Write Buffer command where multiple Write Buffer package upgrade is going on and drive does not support multiple download microcode firmware download or non-512 chunk is detected. if Dev Type is not set to the Dev Type when FW Control was enabled. if MDIO Register is not 4-byte aligned or the data field is not zero for a read type command. The UA-Microcode updated instance for mode 0x5 bufferId 0x0 drive firmware upgrade in Write Buffer. The CC-Invalid field in CDB instance for Security IN OUT Protocol for trusted command not supported. The CC-Invalid field in CDB instance for Write Buffer command where multiple Write Buffer package upgrade is going on and out of sequence Write Buffer command is received.

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

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

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

LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix F: | Error Lookup Table Table 260: DRIVE ERROR LOOKUP DATA ERROR OFFSET DRV_ERR_DF DRV_ERR_NM DRV_ERR_UNC DRV_ERR_DP DRV_ERR_IDNF DRV_ERR_MC DRV_ERR_MCR DRV_ERR_ICRC DRV_ERR_ABRT DRV_ERR_UNHANDELED DRV_ERR_RSVD1 DRV_ERR_RSVD2 DRV_ERR_RSVD3 DRV_ERR_RSVD4 DRV_ERR_RSVD5 DRV_ERR_MAX OFFSET 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 DF bit NM bit UNC bit DP bit IDNF bit MC bit MCR bit ICRC bit ABRT bit Reserved for future use Reserved for future use Reserved for future use Reserved for future use Reserved for future use Reserved for future use Drive Errors Numeric Value of Default ErrorIdx 49 42 59 38 72 11 12 85 78 NA NA NA NA NA NA ErrorIdx CC_ERROR_CODE_HW_ERR_INT_TARGET_FAILURE CC_ERROR_CODE_SNS_NOT_RDY_MED_ABSENT CC_ERROR_CODE_MED_ERR_UNRECOVERED_READ CC_ERROR_CODE_DATA_PROTECT CC_ERROR_CODE_LBA_OUT_OF_RANGE UA_ERROR_CODE_MEDIUM_CHANGED UA_ERROR_CODE_MEDIUM_REMOVAL_REQUEST CC_ERROR_CODE_ABORTED_INF_UINT_CRC_ERROR CC_ERROR_CODE_ABORTED_NO_SENSE CC_ERROR_CODE_ILLEGAL_REQ_NO_SENSE NA NA NA NA NA NA UNHANDLED Drive error 63 LSI Corporation Confidential | October 2010 Page 301 .

Appendix F: | Error Lookup Table LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 302 LSI Corporation Confidential | October 2010 .

G. The LSISS25x0 device supports 520. and 4160 bytes sector size SATA drives. 4104. lengths of Log Parameter Data and Smart Data within log page 0Fh and log page 31h. 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.2 ATA PASS THROUGH Commands with Long Logical Sector SATA Drive The following ATA commands transfer 512 bytes per block:          ADD LBA(S) TO NV CACHE PINNED SET DEVICE CONFIGURATION IDENTIFY DEVICE CONFIGURATION SET DOWNLOAD MICROCODE IDENTIFY DEVICE IDENTIFY PACKET DEVICE QUERY NV CACHE MISSES QUERY NV CACHE PINNED SET READ BUFFER LSI Corporation Confidential | October 2010 Page 303 . G.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. do not change with the Long Logical Sector SATA drive.1 SCSI Commands with Long Logical Sector SATA Drive The following SCSI commands transfer Long Logical Sector size data per block:       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. respectively. 528. 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. 4096. 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.

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) Page 304 LSI Corporation Confidential | October 2010 .

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 LSI Corporation Confidential | October 2010 Page 305 .

Appendix G: | ATA PASS THROUGH Commands with Long Logical Sector SATA Drive LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 306 LSI Corporation Confidential | October 2010 .

where each block is not 512 bytes in length (see the previous figure). Run a single sector read command to the SATA device for SATA LBA m if FSO is a nonzero value.1 Packed Mode Non-512 Byte Mapping The following figure shows the Packed Mode non-512 byte mapping. The LSO is defined from the ending of SCSI LBA n + k to end of SATA LBA m + j.  LSI Corporation Confidential | October 2010 Page 307 . the firmware must perform the following calculations:    Calculate m.1 Read Case Packed Mode Non-512 Byte Mapping For a SCSI read request for k blocks starting from SCSI LBA n. The calculations performed in these modes to support SCSI command requests are described in the following sections.1. Calculate the Last Sector Offset (LSO). Calculate the First Sector Offset (FSO). Figure 7: H. the firmware must perform the following calculations:  Calculate m.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. and j. the number of 512 byte sectors needed to cover the entire SCSI read request. the equivalent starting LBA on the SATA device. H. and j the number of 512 byte sectors needed to cover entire SCSI write request.1. 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. The FSO is defined from the beginning of SATA LBA m to the start of SCSI LBA n. H. FSO and LSO as described in the previous read case.2 Write Case For a SCSI write request for k blocks starting from LBA n. The LSISS25x0 device supports Packed and Sparse Mode Sector Skewing configurations. the equivalent starting LBA on the SATA device. where each block is not 512 bytes in length (see the previous figure).

this space is unavailable to the initiators. are not used. Run a write command with the FSO and LSO fields as shown in Figure 7 and described in Section 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. The LSISS25x0 device’s hardware handles the merging of the data received from the initiator with the data read from the SATA device.1.2 Sparse Mode Non-512 Byte Mapping The Sparse Mode is similar to Packed Mode except that the bytes remaining on the SATA device sector after the end of the stripe. H.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. The same gets recalculated if the SATA device is changed. These commands are check conditioned with a sense key set to ILLEGAL REQUEST and ASC set to INVALID COMMAND OPERATION CODE. 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.  Page 308 LSI Corporation Confidential | October 2010 . Therefore. H. if any. The LSISS25x0 device calculates maximum supported SCSI LBA for the configured sector skewing mode. The LSISS25x0 device skips this space in case of multistripe accesses. when issued in sector skewing configurations.1.

2 Unsupported T10 DIF Features The LSISS25x0 device does NOT support the following T10 DIF features:    User Data Sizes other than 512 or 520 bytes. 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. LSI Corporation Confidential | October 2010 Page 309 . I. 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. I. SATA drives with non-512 byte sector sizes. PROT_EN and P_TYPE fields are updated after a FORMAT for DIF completes. and REF_CHK = 1  READ CAPACITY(16) Command Support.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.1 Supported T10 DIF Features The LSISS25x0 device supports the following T10 DIF 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. 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.

Appendix I: | Unsupported T10 DIF Features LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Page 310 LSI Corporation Confidential | October 2010 .

 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. the SECURITY PROTOCOL SPECIFIC field is set to 0.1 SECURITY PROTOCOL IN Command The following table defines the parameter data sent in response to a SECURITY PROTOCOL IN command with the SECURITY PROTOCOL field set to EFh.1 SECURITY PROTOCOL IN Parameter Data J.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.1 ATA Device Server Password Security Protocol The LSISS2520/LSISS2530 device supports the ATA Device Server Password Security Protocol when the SECURITY PROTOCOL field is set to EFh in the SECURITY PROTOCOL IN/OUT command. All other values of the SECURITY PROTOCOL SPECIFIC field are reserved. The INC_512 bit is set to 0. The SECURITY PROTOCOL IN command is used by the application client to cause the LSISS2520/LSISS2530 device to return ATA Security feature set data extracted from the ATA IDENTIFY DEVICE data from the ATA device. If a SECURITY PROTOCOL IN command is received with the INC_512 bit set to 1.1. J.  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. If the SECURITY PROTOCOL field is set to EFh in a SECURITY PROTOCOL IN command.1. 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. and the additional sense code set to INVALID FIELD IN CDB.1. LSI Corporation Confidential | October 2010 Page 311 . sense key set to ILLEGAL REQUEST. the SECURITY PROTOCOL IN command is terminated with CHECK CONDITION status. J. 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.

 FROZEN This is the frozen state bit. If the ATA IDENTIFY DEVICE data word 128 bit 2 is set to 1. If the ATA IDENTIFY DEVICE data word 128 bit 5 is set to 1. If the ATA IDENTIFY DEVICE data word 128 bit 3 is set to 0.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. the LSISS2520/LSISS2530 device sets this bit to 0. If the ATA IDENTIFY DEVICE data word 128 bit 8 is set to 0.  LOCKED This is the locked state bit. the LSISS2520/LSISS2530 device sets this bit to 1. If the ATA IDENTIFY DEVICE data word 128 bit 8 is set to 1. If the ATA IDENTIFY DEVICE data word 128 bit 3 is set to 1. the LSISS2520/LSISS2530 device sets this bit to 1. the LSISS2520/LSISS2530 device sets this bit to 0. the LSISS2520/LSISS2530 device sets this bit to 1. If the ATA IDENTIFY DEVICE data word 128 bit 2 is set to 0. If the ATA IDENTIFY DEVICE data word 128 bit 4 is set to 0. If the ATA IDENTIFY DEVICE data word 128 bit 4 is set to 1. the LSISS2520/LSISS2530 device sets this bit to 1. the LSISS2520/LSISS2530 device sets this bit to 0. Page 312 LSI Corporation Confidential | October 2010 .  EN_ER_SUP This is the enhanced erase mode supported bit. If the ATA IDENTIFY DEVICE data word 128 bit 5 is set to 0. the LSISS2520/LSISS2530 device sets this bit to 0. the LSISS2520/LSISS2530 device sets this bit to 0. Table 261: SECURITY PROTOCOL IN Parameter Data BIT Byte 7 0 1 (MSB) 2:3 (MSB) 4:5 (MSB) 6:7 8 9 10:15 RESERVED EN_ER_SUP MASTER PASSWORD IDENTIFIER (LSB) RESERVED PWCNTEX FROZEN LOCKED S_ENABLD S_SUPRT ENHANCED SECURITY ERASE TIME (LSB) SECURITY ERASE TIME (LSB) 6 5 4 RESERVED PARAMETER LIST LENGTH (0Dh) 3 2 1 0  PWCNTEX This is the password attempt counter exceeded bit. the LSISS2520/LSISS2530 device sets this bit to 1.

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

2. Table 263: Set Password Parameter List BIT Byte 7 0 1 (MSB) 2:33 (MSB) 34:35 MASTER PASSWORD IDENTIFIER (LSB) PASSWORD (LSB) 6 5 4 RESERVED RESERVED 3 2 1 0 MAXLVL MSTRPW  MAXLVL The LSISS2520/LSISS2530 device copies the contents of the MAXLVL bit to word 0.2.2 Unlock Parameter List If the SECURITY PROTOCOL SPECIFIC field is set to 0002h in the SECURITY PROTOCOL OUT CDB. J. the TRANSFER LENGTH field in the CDB is set to 24h.  PASSWORD The LSISS2520/LSISS2530 device copies the contents of the PASSWORD field to words (16:1) of the ATA SECURITY SET PASSWORD data.1. Table 264: Unlock Parameter List BIT Byte 7 0 1 6 5 4 RESERVED RESERVED MSTRPW 3 2 1 0 Page 314 LSI Corporation Confidential | October 2010 .1. the TRANSFER LENGTH field in the CDB is set to 24h.Appendix J: | ATA Device Server Password Security Protocol LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual J. If the MSTRPW field is set to 1.  MSTRPW The LSISS2520/LSISS2530 device copies the contents of the MSTRPW bit to word 0. The following table defines the parameter list for the SECURITY PROTOCOL OUT command when the SECURITY PROTOCOL SPECIFIC field is set to 0002h (unlock). bit 8 of the ATA SECURITY SET PASSWORD data. 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). the LSISS2520/LSISS2530 device copies the contents of the MASTER PASSWORD IDENTIFIER field to the ATA SECURITY SET PASSWORD data. bit 0 of the ATA SECURITY SET PASSWORD data.1 List Set Password Parameter If the SECURITY PROTOCOL SPECIFIC field is set to 0001h in the SECURITY PROTOCOL OUT CDB.

J. LSI Corporation Confidential | October 2010 Page 315 .LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Appendix J: | ATA Device Server Password Security Protocol Table 264: Unlock Parameter List (Continued) BIT Byte 7 (MSB) 2:33 34:35 PASSWORD (LSB) RESERVED 6 5 4 3 2 1 0  MSTRPW The LSISS2520/LSISS2530 device copies the MSTRPW bit to word 0.1. Table 265: Erase Unit Parameter List BIT Byte 7 0 1 (MSB) 2:33 34:35 PASSWORD (LSB) RESERVED 6 5 4 RESERVED RESERVED 3 2 1 EN_ER MSTRPW 0  EN_ER The LSISS2520/LSISS2530 device copies the EN_ER bit to word 0. bit 1 of the ATA SECURITY ERASE UNIT data. bit 0 of the ATA SECURITY UNLOCK data.2.  PASSWORD The LSISS2520/LSISS2530 device copies the PASSWORD field to words 16:1 of the ATA SECURITY UNLOCK data. the TRANSFER LENGTH field in the CDB is set to 24h.  PASSWORD The LSISS2520/LSISS2530 device copies the password field to words 16:1 of the ATA SECURITY ERASE UNIT data. bit 0 of the ATA SECURITY ERASE UNIT data.3 Erase Unit Parameter List If the SECURITY PROTOCOL SPECIFIC field is set to 0004h in the SECURITY PROTOCOL OUT CDB. The following table defines the parameter list for the SECURITY PROTOCOL OUT command when the SECURITY PROTOCOL SPECIFIC field is set to 0004h (erase unit).  MSTRPW The LSISS2520/LSISS2530 device copies the MSTRPW bit to word 0.

1. bit 0 of the ATA SECURITY DISABLE PASSWORD data.1. After command completion. the command executes and the device remains in Frozen mode.  PASSWORD The LSISS2520/LSISS2530 device copies the PASSWORD field to words 16:1 of the ATA SECURITY DISABLE PASSWORD data. Frozen mode is disabled by power-off or hardware reset. the TRANSFER LENGTH field in the CDB is set to 24h.6 Freeze Lock Page 316 LSI Corporation Confidential | October 2010 . J.4 Disable Password Parameter List If the SECURITY PROTOCOL SPECIFIC field is set to 0006h in the SECURITY PROTOCOL OUT CDB.5 Erase Prepare For Erase Prepare. The following table defines the parameter list for the SECURITY PROTOCOL OUT command when the SECURITY PROTOCOL SPECIFIC field is set to 0006h (disable password). The FREEZE LOCK command sets the device to Frozen mode when the SECURITY PROTOCOL SPECIFIC field is set to 0005h. the SECURITY PROTOCOL SPECIFIC field is set to 0003h in the SECURITY PROTOCOL OUT CDB.2. Erase Prepare is issued immediately before the Erase Unit command. J. any other commands that update the device Lock mode are command aborted.2.1. Table 266: Disable Password Parameter List BIT Byte 7 0 1 (MSB) 2:33 34:35 PASSWORD (LSB) RESERVED 6 5 4 RESERVED RESERVED MSTRPW 3 2 1 0  MSTRPW The LSISS2520/LSISS2530 device copies the MSTRPW bit to word 0.2. If FREEZE LOCK is issued when the device is in Frozen mode.Appendix J: | ATA Device Server Password Security Protocol LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual J.

T10 DIF Features.13.37.1. REQUEST SENSE. Added Appendix I.2.1.46.16. on page 237.3.6. on page 273. on page 35. July 2010 Description of Changes Updated Section 2. on page 109 • Section 4. SAT-Specific Security Protocol Parameters. Mode Page 32 – Subpage 1. Mode Page 19 . Features.4. on page 124 • Section 4. Error Lookup Table. WRITE (32). Task Management Functions.2.1. Sense Information. READ (32). SECURITY IN PROTOCOL. on page 267 • Table 259. Sense Data. Added Section F. Log Page 16h (ATA PASS-THROUGH Results Log page).3. SEND DIAGNOSTIC.9. VPD Page 89 -SATA Information VPD Page.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. Updated Table 259.2.1 Previous Versions Revision History The revision history table on the second page of this document lists only the changes made to the current version of the document. InstIds. InstIds. Added Appendix J. on page 87 • Section 4. FRU Code Values.11. on page 13.55. Drive Firmware Upgrade. on page 47 • Section 4.1. on page 33 • Section 4.29. April 2010 Version/Date LSI Corporation Confidential | October 2010 Page 317 . Error Reporting Codes. WRITE SAME (32). ATA PASS THROUGH Status Return.1. on page 214 Updated the following tables: • Table 258.7. on page 106 • Section 4. Updated Section 5.1. Added Table 108 on page 115 and Table 109 on page 116. on page 101 • Section 4.Subpage 2. on page 22 • Section 3. on page 180 • Section D. on page 164.34. Description of Changes Version 2.32. Added the following sections: • Section 3. K. on page 253 Updated the following sections: • Section 4. Updated Section 3. on page 136 • Section 5.3. SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16).1. Table 267: Revision Information Version/Date Version 2. on page 117 • Section 5. on page 267. on page 273 Updated Appendix F. Updated Section 5.18.18.

on page 20 • Table 5. on page 172.0. MDIO ACCESS RESPONSE.14. Updated following tables: • Table 4.7. • Section 5.33.3 October 2009 Version 1. Mode Page 32h (Firmware Parameter Control). PERSISTENT RESERVE OUT Service Actions Allowed in the Presence of Various Reservations. SYNCHRONIZE CACHE(10) and SYNCHRONIZE CACHE(16). SECURITY OUT PROTOCOL. REPORT LUNS.3. Log Page 35h (Versions Page). on page 108 • Section 5. WRITE BUFFER. on page 248 • Section 5.29. Long Logical Sector SATA Drive Support Added Appendix H. on page 98 • Section 4.50. Updated Appendix D. Command Processing During Persistent Reservation. on page 224.1. • Section 4. Made several technical changes throughout the document.Appendix K: Revision Information | Previous Versions Revision History LSISS2520/LSISS2530 SAS-SATA Bridge System Application Reference Manual Table 267: Revision Information (Continued) Version/Date Version 2.32. Initial release of the preliminary document.2.19. MDIO ACCESS COMMAND. on page 89. on page 63 • Section 4. Mode Page 33h (Sector Skewing Support Parameter Page). on page 192 • Section C. on page 101. on page 106 • Section 4. July 2009 Version 1. on page 61 • Section 4.1. on page 105 • Section 4.13.1.2. Sense Information. Mode Page 39 Subpage 2. REQUEST SENSE. December 2008 Page 318 LSI Corporation Confidential | October 2010 . InstIds. Version 1.37.0.1. SECURITY IN PROTOCOL. on page 267 • Table 259.19. Technical changes throughout the document. Delaying SAS Links Bring Up.27.6. • Section 5. RELEASE (10). on page 117 • Section 4. Firmware Upgrade. on page 273 Fixed minor bugs in the document.19. August 2009 Version 1. on page 97 • Section 4. on page 129. Sector Skewing Support Added following sections: • Section 4.26.31. on page 21 • Table 258. READ BUFFER. February 2010 Description of Changes Added Appendix G. • Section 4. RESERVE (10). on page 181 Updated following sections: • Section 4.2.