1

Protocol Insight® Test Executive™

Universal Flash Storage (UFS)

UFS Compliance Test - Methods of Implementation

UFSA Compliance Test Matrix v1.0

The Protocol Insight Test Executive provides complete protocol debug and analysis of UFS

devices, including compliance testing, margin and stress testing, and custom test creation and

execution.

In this MOI, UFS Test Executive is used to execute the JESD224 Test Standard to verify

compliance with the UFSA Compliance Test Matrix v1.0. Test Executive uses the Keysight

Technologies U4431A packet generator to execute a range of CTS test cases, and analyzes the

captured results.

Test Executive:

Automatically sets up the analyzer, generator and DUT for each test

Allows auto-configuration and reconfiguration of speeds, link widths and LUNs during the testing process

Allows users to select and run individual or multiple CTS tests

Allows creation of custom test cases to test the thresholds at which marginal or critical warnings appear

Provides detailed information for each test that has been run

Creates a printable PDF report and CSV export file of the tests that have been run

2

Contents Required Test Instrumentation ..................................................................................................................... 3

System Setup and Operation ........................................................................................................................ 3

Step 1A: Configure instrument hardware ................................................................................................. 3

Step 1B: Connect probes ........................................................................................................................... 4

Step 1C: Connect reset signal ................................................................................................................... 4

Step 2: Configure and Connect to DUT ..................................................................................................... 4

Step 3: Configure and Run Tests in the Test Matrix ................................................................................. 5

Step 4: Configure Stress Testing in Test Matrix (optional) ....................................................................... 5

Step 5: Configure Run Control in Test Matrix (optional) .......................................................................... 6

Interpreting Packet Inspection Results ......................................................................................................... 7

Generating a UFSA Compliance Report ........................................................................................................ 8

Supplemental Analysis ................................................................................................................................ 10

Group and Summarize test results ......................................................................................................... 10

Sort and Filter test results ....................................................................................................................... 11

Packet Decode pane ............................................................................................................................... 11

Analysis Reports ...................................................................................................................................... 11

Appendix A: Theory of Operation ............................................................................................................... 13

Appendix B: Configuring the Keysight Technologies U4431A GUI .............................................................. 14

Appendix C: How to Find Device Configuration Values .............................................................................. 15

3

Required Test Instrumentation 1. Keysight Technologies U4431A MIPI M-PHY Protocol Analyzer, minimum system:

Note: not all PC have BIOSs can handle the enumeration of the Keysight AXIe chassis. If an off-the-shelf PC is used, Keysight has a list of laptops and PCs that are known to be compatible with the AXIe chassis at http://literature.cdn.keysight.com/litweb/pdf/5990-7632EN.pdf?id=2023354

2. Required Software and Firmware

Windows 7 64 bit operating system with minimum 12GB RAM

Protocol Insight UFS20COMP UFS Test Executive version 1.0 or later

Keysight technologies U4431A application software version 6.1 or later

Keysight Technologies U4431A option 613 Command Line Packet Generator (CLPG). Go to http://www.protocolinsight.com/sw-compatibility/ for information on compatible SW/FW versions. Contact your local Keysight FE or AE to obtain the latest compatible SW and FW.

For information on how to install and configure Keysight AXIe based Logic Analysis and

Protocol Test contact your local FE or AE, or refer to this installation guide:

http://literature.cdn.keysight.com/litweb/pdf/U4000-97000.pdf?id =2169537

System Setup and Operation See REQUIRED TEST INSTRUMENTATION for information on the

equipment configuration.

Step 1A: Configure instrument hardware 1. Connect the U4432A SMA probe to Pod 1 of the

Keysight U4431A (see Figure 2: POD1 and POD2

connections below).

2. Install the loopback board in Pod 2 of the U4431A (see

Module

U4431A Protocol test module, MIPI M-PHY, Gear 1, one lane, 1 GB memory

U4431A-412 Increase to 2-lane MIPI M-PHY (FW only)

U4431A-514 Increase data rate to Gear 3 (FW only)

U4431A-613 Command Line Packet Generator and loopback board

U4431A-712 MIPI M-PHY Universal Flash Storage (UFS) plus UniPro

U4432A SMA cable, MIPI M-PHY, 21 leads/6 Gbps

System

M9502A Two Slot AXIe Chassis With PCIe Connection for Host PC, Cascading Capabilities, External Trigger In/Out, External Clock In/Out

M9536A AXIe Embedded Controller PC Quad Core, 2.13 GHz , 160+ GB SSD Hyper Threading Technology

Optional - pick one PC

NA Off-the-shelf laptop PC with ExpressCard slot Optional - pick one PC

M9045A ExpressCard (Laptop) Adaptor Required if laptop is chosen

Y1200A PCIe x1 to x8 Cable (2m length) for laptop Required if laptop is chosen

NA Off-the-shelf desktop PC Optional - pick one PC

M9048A PCIe Desktop Adaptor, Gen2, x8 Required if desktop is chosen

Y1202A PCIe Cable x8 (2m length) for desktop Required if desktop is chosen

Figure 1: Typical Setup

4

Figure 2: POD1 and POD2 connections below).

3. Launch the Keysight Analyzer Software and configure it. See APPENDIX B: CONFIGURING THE

KEYSIGHT TECHNOLOGIES U4431A GUI.

Figure 2: POD1 and POD2 connections

Step 1B: Connect probes The labels on the Keysight U4432A SMA probe are from the packet generator perspective.

1. Connect RX0p on the SMA probe (black) to TX0p on the DUT

2. Connect RX0n on the SMA probe (black with white) to TX0n on the DUT

3. Connect TX0p on the SMA probe (white) to RX0p on the DUT

4. Connect TX0n on the SMA probe (white with white) to RX0n on the DUT

5. The CLK on the SMA probe is packet generator input only, it does NOT provide a clock. Leave

disconnected as the data generator and analyzer do not need a reference clock.

6. If your DUT requires a reference clock you will need to provide that from an external source.

Step 1C: Connect reset signal Note: Reset signal is only applicable for JESD220B and JESD220C embedded UFS

1. Connect the DUT reset cable from the trigger out port of the U4431A to your DUT

2. The output voltage of the reset signal coming from the Keysight packet generator is 3.3V. This is

larger than the MIPI specification value of 1.8V. If your device cannot tolerate the 3.3V reset

signal create a reset cable that has a voltage divider circuit:

a. The output driver of the reset line is 50 ohms and the output is 3.3V so for 1.2V you

need to add a resistor to divide the output voltage down.

b. Assuming the input resistance of the reset pin

on your device is very large you can you the

formula on this wiki page:

https://en.wikipedia.org/wiki/Voltage_divider.

c. Solder the resistor between the pin and ground.

Step 2: Configure and Connect to DUT 1. Launch Test Executive and open the Device tab.

2. If required, load the UFS device-specific UniPro boot

sequence TCl script by browsing the “Custom UniPro

Script” field. Otherwise the default will be used.

U4432A SMA probe in POD1 Loopback board in POD2

5

3. Configure Device and LUN parameters by entering in all the parameters for your device and save

the configuration. See APPENDIX C: HOW TO FIND DEVICE CONFIGURATION VALUES for tips on how

to poll your device for this information if it is not already known.

4. Press the “Online” button to boot the device thru UniPro and UFS.

Step 3: Configure and Run Tests in the Test Matrix 1. Open Test Matrix tab (see FIGURE 3: TEST MATRIX).

2. Select which LUNs, Speeds, and Link Widths to test

3. Under Miscellaneous in Device Configuration in the Device tab make the following selections:

bConfigDescrLock=0 = selected

bOutOfOrderDataEn has been written = not selected

bRefClkFreq has been written = not selected

bConfigDescrLock has been written = not selected

Enable Write Once Attribute Test Cases = selected

4. Select and Run the following test cases in any order

7.8.4 (requires fPermanentWPEn = 0x00, will write to 1)

8.4.14 (requires bConfigDescr = 0)

8.6.25 (requires bOutOfOrderDataEn = 0)

8.6.36 ((requires bRefClkFreq = 0) (only PWM)

8.6.38 (requires bConfigDescr = 0)

5. Generate a Report and save results – See GENERATING A UFSA

COMPLIANCE REPORT.

6. Select and Run the following test cases in any order, these will write

the above parameters

8.6.24 (writes bOutOfOrderDataEn)

8.6.35 (writes bRefClkFreq = 2) (only PWM)(Not a valid value for cards)

8.6.37 (writes bConfigDescr)

7. Generate a Report and save results – See GENERATING A UFSA COMPLIANCE REPORT.

8. Under Miscellaneous in Device Configuration in the Device tab make the following selections:

bConfigDescrLock=0 = not selected

bOutOfOrderDataEn has been written = selected

bRefClkFreq has been written = selected

bConfigDescrLock has been written = selected

Enable Write Once Attribute Test Cases = not selected

9. Select and Run all test cases defined in the CTM

(deselect the 8 tests listed above so they won’t be run a second time)

10. Generate a Report and save results – See GENERATING A UFSA

COMPLIANCE REPORT.

Step 4: Configure Stress Testing in Test Matrix (optional) 1. Test Run Order controls the order in which tests are executed.

a. Loop Order: loop order specifies the nested order of test

execution. Tests will be run from the bottom up, with all tests in

each loop executed before the next higher loop is begun. So if

Figure 3: Test Matrix

6

the Loop Order is Speeds, Link Widths, LUNs, Tests then all Tests will be completed for a

LUN before being executed for the next LUN, etc. The loop order can be adjusted by

dragging categories up or down in the Loop Order box.

b. Ascending, Descending, Random Seed: this specifies which order the tests are executed

within the Loop. If Random Seed is selected a value can be entered to generate a

random but reproducible test order based on the seed value.

2. To test all permutations of all tests, from the main menu select TestSelect All Tests to run all

valid test configurations.

Step 5: Configure Run Control in Test Matrix (optional) Test Run Control specifies the number of iterations of the Test Matrix to run, dictated by Test Run

Order. Test execution will stop after the specified Number of Loops (outer loops on Test Run Control),

Failures or Warnings have occurred. Note that the Failure and Warning counters count test case

warnings and failures, not packet inspection rule warnings or failures.

The user can specify the number of Test Matrix loops to run OR

the number of Failures OR Warnings to allow before terminating

the test run. When Number of Failures and Number of Warnings

fields are blank or 0, tests are run for the given number of loops.

If values are provided for all three conditions, then tests are run

until any ONE of the three conditions is met.

All test results are stored in application memory, with a limit of

1,000,000 unique test case configurations allowed for each test

run. A test case configuration is a defined as 1 Test Case x 1 Speed x 1 LUN x 1 Link Width, so 1 Test x 2

Speeds x 1 LUN x 1 Link Width counts as two test case configurations for the purposes of calculating the

maximum number of loops. Thus, if a total of 2 test case configurations are selected in the Test Matrix,

then the maximum number of loops allowed are (1,000,000/2) or 500,000 loops. And if 2000 test case

configurations are selected, then the maximum number of loops allowed are (1,000,000/2000) or 500

loops.

The number of loops that can be run is calculated, based on the Test Matrix selections, and shown in the

tool tip for the Number of Loops variable input field. This value is automatically adjusted when any of

the LUNS, Link Widths, Speed or Tests are Selected/Deselected.

Figure 4: Test Run Control

7

Interpreting Packet Inspection Results The Rule Checker engine performs deep packet inspection with

four possible status results for each rule check:

Failure

Any response packet that does not meet a rule specified in

JESD224

Warning

Any response packet that does not conform to a “shall”

specified in JESD220

Pass

Any response packet that conforms to both JESD220 and

JESD224

Info

For those packets not inspected, the reason no evaluation

was done

The results of the deep packet inspection are listed in the Test Results pane and can be grouped,

summed, sorted and filtered by various test parameters or packet characteristics. See GROUP AND

SUMMARIZE test results and SORT AND FILTER test results for more information.

8

Generating a UFSA Compliance Report To create a UFSA Compliance Report the Test Results pane is modified to reflect the required

information and then a PDF report is created from that view.

To create the UFSA Compliance Report view in the Test Results pane:

1. If necessary, drag columns to order them by Category, Test, LUN, Link Width and Speed

2. Right click in the column header and select only Category, Test, LUN, Link Width and Speed as

below:

3. Group the results by Test by clicking on the Test column header and dragging it into the Test

Results field. See GROUP AND SUMMARIZE test results for more information.

4. Sort results in ascending order by the Test column. See SORT AND FILTER test results for more

information.

5. From the Results menu select ResultsExpand All to display all test results.

6. Double click on the column dividers to expand column widths to show all description

information.

To generate the UFSA Compliance PDF report:

1. From the Reports menu select ReportsTest ResultsPrint Preview…

2. Select a PDF printer.

3. Set Page Orientation to Landscape.

4. Print the results to a file.

9

The resulting UFSA Compliance report should look like this before printing:

10

Supplemental Analysis The Test Results pane allows extensive quantitative analysis of results data. Results can be grouped and

summarized, sorted, and filtered by any header column:

By test parameters

1. Status

2. Category

3. Test#

4. Loop#

5. Test Order

6. Packet Inspection Rule

By packet characteristics

1. Failure Value

2. Packet

3. Byte position

4. Configured LUN

5. Link Speed

6. Link width

Group and Summarize test results To group and summarize, click on any column header and drag into the Test Results field. This will

summarize the results with an item count of occurrences. Multiple column headers can be dragged into

the Test Results field (1) to create tiered groupings for analysis:

Grouping and Summarizing

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

Item count: represents the number of items in the grouping below, so in this example (2) Category 7.4

MODE SELECT 10 counted 17 items, representing 17 different mode select tests. This item count

summing function can be manipulated with a high degree of flexibility by reordering the groupings to

count many different items in addition to tests, such as number of Failures (Status) or packet inspection

Rules.

Summary Status flag: for any grouping of results the summary status flag represents the worst case

result of the grouping (3). In this example, 17 tests were executed for MODE SELECT 10, and the worst

result was a Failure so MODE SELECT 10 is marked as Failure.

Sort and Filter test results Any column header can be clicked to filter out results or to sort results by that column:

Figure 5: Sorting and Filtering

Packet Decode pane To view the Command and Response packets of a

test, click on the result in the Test Results pane.

1. Open the Packet Decode tab.

2. All packets in the test of interest are listed in

the top section.

3. By selecting a packet in the top section the

bit structure is displayed in the lower section

with Failures and Warnings flagged

4. Selecting 8, 16, or 32 defines the bit width of

the display.

Analysis Reports ReportsTest Results

Summary reports can be created by configuring the

Test Results pane and then printing it. See

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

SUPPLEMENTAL Analysis for more information.

ReportsPacket DecodeExport to PDF…

The Packet Decode report generates a PDF of the test case packets in transaction sequence, similar to

the Packet Decode pane. For the Response packets, the Failure and Warning errors are highlighted by

color in each packet and listed in a summary table below the packet. The reports generated can include

just the selected packet, all packets in the selected test, or all test results, depending on test selection.

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

Appendix A: Theory of Operation The Test Executive controls the Keysight U4431A MIPI Protocol Analyzer Command Line Packet

generator (CLPG) to talk to the Device Under Test (DUT) and capture and analyze the response packets.

This flow charts shows the operation of the Test Executive. Blue indicates Protocol Insight Test Executive

functions and red indicates Keysight Technologies U4431A functions:

Figure 6: Method of Operation

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

Appendix B: Configuring the Keysight Technologies U4431A GUI 1. In U4431A software select the “Data Gen + Analyzer” link mode on the Connection Setup tab. 2. Choose “Both Sublinks” on the Connection Setup tab so both the TX and RX data is captured. 3. Choose the correct Sublink Width for your Device.

4. On the Analyzer Setup tab choose the correct rate series for your Device.

5. Press ok.

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

Appendix C: How to Find Device Configuration Values

Device Configuration pane: “Device Descriptor Values”

o All values for this can be found by looking at the response of test case ReadDescriptor_01

Device Configuration pane: “Geometry Descriptor Values”

o All values for this can be found by looking at the response of test case ReadDescriptor_09

LUN Configuration pane: “Read-Write recovery mode page”

o All values for this can be found by looking at the response of test case ModeSense_06

LUN Configuration pane: o Some values for this can be found by looking at the response of test case

ReadDescriptor_03 o Select all configured LUNs in the Test Matrix

Set the correct values for the following: bProvisioning set to 0x2 or 0x3 MaxContextID=0 can be found from wContextCapabilities, bits [3:0] is

MaxContextID Run test case ReadCapacity_10 and set the MAX addressable LBA, qLogicalBlockCount and

bLogicalBlockSize in the LUN Configuration pane Min Page code should be fine at 0x02 (Vendor Specific) IMMD (Vendor Specific) “Mode Page PS Values” and “Mode Saveable”

o All values for this can be found by looking at the response of test case ModeSense_02,06,10

Read-Write Recovery Mode Page are vendor specific, default to unselected

Specifications and descriptions in this document

are subject to change without notice.

© Protocol Insight, LLC 2016

Revision 1.32, July 25, 2016

© Protocol Insight, 2016