Protocol Insight™ UFS Test Executive™ UFS20COMP Test Executive provides complete protocol debug and analysis of UFS devices, including deep packet inspection, stress testing, custom test case execution, and CTS and UFSA interoperability verification. It is available as a 12 month license with an annual renewal option, and operates in conjunction with the Keysight Technologies U4431A MIPI M-PHY protocol analyzer.

Key Features and Benefits Deep packet inspection performed with a unique protocol-aware Rule Checker engine with full protocol decode and rule checking against the JEDEC JESD220B UFS 2.0 spec and JESD224 UFS CTS. For example, Test Executive evaluates over 30 major packet characteristics against the UFS 2.0 standard along with the four checks required by the CTS for Test Case 7.1.1 compliance, providing a much richer picture of packet characteristics and device behavior.

Perform extensive stress testing executing hundreds of thousands of tests with multiple packet inspection rules per test. Execute any test or set of tests against any selection of LUNs, speeds and link widths. Run the tests in ascending, descending or random order, looped in nest order with flexibility to specify the nesting order by LUN, speed, link width or test case. Stop after any number of loops, Warnings or Failures. All failures and warnings are tagged, allowing the user to find, view and analyze the full test sequence in the Keysight analyzer.

Design custom test cases to test corner cases or introduce errors for margin, stress, or error recovery testing. Test Case Builder™ allows complex test case creation, with virtually unlimited transactions, device control, and command and response packet construction, Data Buffer and Payload support, and Loop and Compare functions. Local and global variables and run conditions are used to create test case conditions. Syntax checker verifies custom test case validity.

Perform compliance testing to the JEDEC JESD224 Universal Flash Storage (UFS) Protocol CTS, to verify compliance with JESD220B UFS Standard version 1.1A.

Performance

JESD220B UFS 2.0 conformance o Rule Checker engine evaluates all “shall” statements and logical requirements

JESD224 compliance covers 29 test categories:

o Inquiry o Request Sense o Mode Sense o Mode Select (10) o Unmap o Start Stop Unit o Read Capacity

(10) o Format Unit o Test Unit Ready o Write (6) o Write (10)

o Read (6) o Read (10) o Verify (10) o Send Diagnostic o Report LUNs o Synchronize

Cache (10) o Pre Fetch (10) o Context

Management o UFS Task

Management

o UFS Boot o UFS Descriptor o UFS Flag o UFS Attribute o UFS Power Mode o UFS UPIU o UFS Unit

Attention Cond o UFS RPMB o UFS UPIU Flags

o 230 test cases, covering all LUN, Speed and Link Widths supported by Keysight analyzer o Executes the SCSI and UFS Command test cases specified in the JEDEC Compliance Test

Spec JESD224

Custom Test Case Builder o Local and Global Variables and Run

Conditions control Transactions o Script execution for device control o Command/Response packet construction

with pre-defined field and rule sets 23 UPIU fields/rules 16 UFS fields/rules 32 SCSI fields/rules 2 other fields/rules

o Write payload insertion and Read payload analysis and comparison

Stress Testing

o Execute any loop order by Speed, Link widths, LUNs, or individual test cases o Each category can be run ascending, descending, or random seed order o Stop after up to 1,000,000 test case configuration loops (~30 hours of operation) or a

specified number of test case Warnings or Failures

Deep Packet Inspection and Analysis Failure and Warning status flags

A Warning is any response packet that does not conform to a “shall” specified in JESD220B UFS 2.0.

A Failure is a response packet that does not meet a rule specified in JESD224 protocol CTS

Pass and Info status flags

Any response packet that conforms to both JESD220B and JESD224 is marked as Pass

Any packets not inspected due to run conditions are highlighted and explained with the Info flag

Group, filter and summarize test results

By test parameters – status, test category, individual tests, or test rules

By packet characteristics – packet number, byte, LUN, speed, link

Full packet decode in 8, 16 or 32 bit mode

Offline analysis of previously acquired packets

Summary reports and full file exports

Applications Device compliance and Host-Device interoperability verification of silicon and end-products

Initial device turn-on debug System integration debug Interop workshop preparation UFSA device compliance certification

Specifications Test Executive operates in conjunction with the Keysight Technologies U4431A MIPI M-PHY protocol analyzer, and supports UFS lane widths and speeds within the capabilities of the U4431A hardware.

Inspection of the entire packet offers a much richer picture of packet protocol characteristics and device behavior. Below is an example of the additional detail provided in the Basic UPIU Header Check, Data In Check and Response UPIU Check:

Basic UPIU Header Checks - All Messages are checked for proper UIPI headers:

The message structure is >= 32 Bytes and ends on a 4 byte boundary 1.1. TRANSACTION TYPE Both the DD and HD bits are set to 0 That it is a valid and defined

Transaction Type 1.2. FLAGS This field is 0 unless the Transaction

Type is Command or Response No reserved flag bits are set in any

Transaction Type IF Transaction Type is command:

o R & W flag are not both set o Flag Attribute Type is not ACA

IF Transaction Type is Response o U & O flags are not both set

1.3. LUN No Checks 1.4. TASK TAG No checks as all values are valid 1.5. COMMAND SET TYPE Bits [7:4] are reserved and that these

bits are 0 The value of bits[3:0] is 0 or h8 to hf.

o A value of 1 is UFS Specific command which is not currently supported

o A value of 2-7 is reserved 1.6. QUERY FUNCTION / TASK MANAG. FUNCTION This field is 0 unless the Transaction

Type is Task Management Request, Query Request or Query Response

IF Transaction Type is Task Management Request

o The value is one of the following valid values h1, h2, h4, h8, h80, h81

IF Transaction Type is Query Request or Query

o The value is one of the following valid values h1, h40 to h7F, h81, hC0 to hFF

1.7. RESPONSE This field is 0 unless the Transaction

Type is Task Management Response, Response, reject or Query Response

IF Transaction Type is Task Management Response, response, reject or Query Response

o The value is not a reserved value, h80 to hFF

1.8. STATUS This field is 0 unless the Transaction

Type is Response IF Transaction Type is Response

o The value is a one of the following valid values h0, h2, h4, h8, h18, h28, h30, h40

1.9. TOTAL EHS LENGTH This value shall be 0 has Extra Header

Segments are not supported 1.10. DEVICE INFORMATION This field is 0 unless the Transaction

Type is Response or Query Response IF the Transaction Type is Response or

Query Response o The value is a one of the

following valid values h0 or h1 1.11. DATA SEGMENT LENGTH That the number of bytes in the Data

Segment are equal to or greater than the Data Segment Length field

IF greater not greater than 3 bytes All padding byte are 0

Response UPIU Check

The Status and Response fields match the expected values

The flags match the expected flags IF an overflow or underflow flag is set

o The Residual Transfer count is non zero and equal to the expected value

2.1 SENSE DATA CHECKS IF the Data Segment Length is non zero the Sense Data is checked:

The Data Segment Length shall equal 20 The Sense Data Length shall equal the

Data Segment Length - 2 (18) The following fields of the Sense Data

Format are static: o Response Code = 0x70 o Obsolete = 0x00

o FILEMARK, EOM, ILI, Reserved = 0x0

o Additional Sense Length = 0x0A o Command Specific Information

(4Bytes) = 0x00 0x00 0x00 0x00 o Field Replaceable Unit Code =

0x00 o Sense Key Specific Information

(3 Bytes) = 0x00 0x00 0x00 The following fields are compared to an

expected value (NOTE each check can be ignored by setting the value to “X”)

o Sense Information Valid o Sense Key o Sense Information o Additional Sense Code (can be a

list of codes to compare to) o Additional Sense Code Qualifier

(can be a list of codes to compare to)

Data In Checks

This checks the Transaction Specific Fields of the Data In UPIU The Data Buffer Offset value shall equal the specified value The Data Transfer Count shall match the Data Segment Length The Reserved fields shall be 0

Program Outputs Test Executive issues UFS Command packets to a device and captures and analyses the Response packets. For example, for UFS_Inquiry_01 the following are checked in the Response packet:

2. UFS_Inquiry 2.1. UFS_Inquiry_01 Basic UPIU Header Check on the Response and Data In message Data In Check on the Data In message Response UPIU Check on the Response message. If Sense data is present the default value checks are performed but the

expected value checks are ignored o Status should be GOOD o Response should Target Success

The following is checked on the Data In message: o The correct number of bytes are returned (36) with a maximum of 36 Bytes o The Data Buffer Offset is equal to 0 o The Data Transfer Count matches the Data Segment Length o The first 8 bytes of the match the definition in the UFS specification

Reports the Vendor Identification, Product Identification, Product Revision Level

Product specifications and descriptions in this document are subject to change without notice.

© Protocol Insight, LLC 2015 Revision 4.00, April 14, 2015

Some of the checks are required for compliance testing, but many of the checks are not. These additional checks provide deeper protocol insight by looking for packet errors as defined in the UFS specification.

General Characteristics System requirements:

Windows 7 32 or 64 bit OS are supported. Minimum 12Gb RAM recommended for stress testing with multilevel grouping.

The Keysight U4431A MIPI M-PHY protocol analyzer is required for operation. Test Executive is compatible with Keysight U4431A application software v6.1 or later and firmware v91.27.1032 or later.

Ordering Information Product Description Pricing UFS20COMP UFS Test Executive – 12 month license Contact Protocol Insight UFS20COMPMAS 12 month license extension, with maintenance and support Contact Protocol Insight

Contact Information For additional information, to request a demonstration or quote, or place an order, please contact: sales@protocolinsight.com

Support materials and examples files are available at www.protocolinsight.com/support

For technical support please contact: support@protocolinsight.com