UniPro Test Executive User Guide

Transcription

1 UniPro Test Executive User Guide The Protocol Insight UNI16COMP Test Executive provides complete protocol debug and analysis of UniPro devices, including Trace Validation mode, CTS mode, Stimulus mode, stress testing, and custom test creation and execution. Contents UniPro Test Executive Feature Overview... 3 Trace Validation (TV) mode... 3 Conformance Test Suite (CTS) mode... 3 Stimulus mode for Corner Case and Margin testing... 3 Stress testing... 3 Custom test case creation and execution... 3 Theory of Operation... 4 CTS mode... 4 Trace Validation mode... 5 Intelligent Trace Validation engine... 5 Interpreting Trace Validation Results... 6 Navigating the User Interface... 6 Tool Bar... 6 Menus... 7 Windows... 7 Stimulus Configuration Window... 8 Trace Validation Configuration window... 9 CTS Configuration window Power Configuration window Packet List window Packet Decode window Stimulus Results window Trace Validation Results window Traffic Overview window Trace Validation Statistics window Menu Functions File Menu Results Menu Reports Menu View Menu Analyzer Control Menu Tools Menu Setup and Operation Configuration for CTS and Stimulus modes Step 1A: Configure instrument hardware Step 1B: Connect probes Step 1C: Connect reset signal Step 2: Connect Test Executive to the instrument SW Step 3: Connect to DUT Step 4: Configure Tests... 19

2 Step 5: Configure Stress Testing Step 6: Configure Run Control Step 7: Run the configured tests Configuration for Trace Validation mode (alternate HW configuration) Step 1: Configure hardware Step 2: Connect to analyzer Step 3: Configure and run tests Analysis The Results windows The Trace Validation Statistics window Group and Summarize test results Sort and Filter test results Packet List window Packet Decode window Analysis Reports Appendix A: Resetting Your SQL Database Appendix B: Reconfiguring Your SQL Database Appendix C: Manually Installing Microsoft SQL Server Appendix D: Configuring Keysight Technologies U4431A for CTS and Stimulus modes Appendix E: Configuring Keysight Technologies U4431A (optional for Trace Validation mode) Appendix F: Required software and firmware Appendix G: Keysight Technologies Minimum Hardware Configuration for CTS/Stimulus modes Appendix H: Keysight Technologies Minimum Hardware Configuration for Trace Validation mode Appendix I: Known Limitations... 34

3 UniPro Test Executive Feature Overview Trace Validation (TV) mode Intelligent Trace Validation analyzes bi-directional UniPro links, performing protocol sequence and packet inspection rule checking based on the nature of the traffic. Using link traffic captured by the Keysight U4431A analyzer, Intelligent Trace Validation implements a unique protocol-aware rule checker engine to validate the trace against the MIPI UniPro v1.6 and v1.61 specifications. Conformance Test Suite (CTS) mode CTS mode uses the Keysight U4431A packet generator to execute a range of CTS test cases, analyzing results using the intelligent Trace Validation engine and generating summary reports. Conformance of MIPI UniPro is verified to the UniPro Conformance Test Suite (CTS) v1.0 and MIPI Alliance approved MOI. Stimulus mode for Corner Case and Margin testing Stimulus allows Test Executive to control the Keysight U4431A packet generator to create specific traffic on the link, and also has the ability to do error insertion. Stress testing In CTS and Stimulus modes execute hundreds of thousands of tests against any configurations such as speed or link width. Run the tests in ascending, descending or random order, looped in nest order by speed, link width or test case. Stop after any number of loops or No Result Test Cases. All failures and warnings are tagged, allowing the user to find, view and analyze the full test sequence in the Keysight analyzer. Custom test case creation and execution Design custom tests to test corner cases or introduce errors for margin, stress, or error recovery testing. Builders support Trace Validation and Stimulus modes, allowing complex test creation, error injection, device control, and protocol sequence and packet state machine construction.

4 Theory of Operation CTS mode In CTS mode Test Executive controls the Keysight U4431A Command Line Packet Generator to initiate conformance test cases, then uses the Trace Validation engine to verify that the resulting protocol sequences and packets conform to the UniPro v1.0 CTS. This flowchart shows the operation of the Test Executive, where blue indicates Protocol Insight Test Executive functions and red indicates Keysight Technologies U4431A Analyzer/Generator functions: Figure 1: CTS mode Operation To locate the beginning of each test case in the trace, testing is initiated with a PACP_SET_req marker packet, followed by the packet(s) necessary to commence the test. The marker packet contains a value that uniquely identifies the test case: The PACP_SET_req MIBattribute value identifies the author of the test case. The predefined ranges are listed below. 0xFFFF Test case authored by Protocol Insight 0xFF00-0xFFFE This range reserved 0xF000-0xFEFF Range available range for customer defined test cases. The MIBvalue identifies the specific test being executed: Domain (8 bits) Used to define a category of test case for the given owner. Existing Protocol Insight domains are: 01 - CTS specific test cases 02 - Power mode tests

5 Case ID (24 bits) Identifies a specific test case within a given domain. Protocol Insight test cases follow a major, minor, revision style using 8 bits for each. For example, the CTS test case Invalid Configuration Request written by Protocol Insight would have a complete ID of 0x Trace Validation mode Test Executive uses the Keysight U4431A to capture the link traffic, then analyzes the traffic and performs packet inspection and rule checking based on the nature of the traffic on the link. This flow charts shows the operation of the Test Executive. Blue indicates Protocol Insight Test Executive functions and red indicates Keysight Technologies U4431A Analyzer functions: Figure 2: Trace Validation mode Operation Intelligent Trace Validation engine The Trace Validation engine is the underlying protocol sequence and packet rule checker for UniPro Test Executive. Trace Validation rule checking is used in both the CTS and Trace Validation Results windows. Trace Validation is a complex state machine system that processes analyzer traces and applies state machine logic to packet sequences to verify conformance or compliance to the specifications. Figure 3: Example UniPro Power Mode Change Trace Validation State Machine

6 Interpreting Trace Validation Results The Trace Validation engine performs protocol sequence and packet inspection with five possible status results for each rule check displayed in the Trace Validation Results window: Failure Any protocol sequence or packet that does not meet a rule specified in MIPI UniPro v1.0 CTS or as defined in a custom test case Warning Any protocol sequence or packet that does not conform to a shall specified in MIPI UniPro v1.61 spec or as defined in a custom test case Pass Any protocol sequence or packet that conforms to both UniPro 1.61 and UniPro CTS 1.0 Info Info messages communicate the progress during the test or information about the packets, and are typically followed by a status result such as Pass or Failure. See example to the right, where there are several Info messages followed by a Success message and Pass status. Debug (TV mode only) Provides information on state machine execution of an inspection rule in Trace Validation mode: Indicates an Action was executed. This could be a Log Message Action, Counter Action, or a Set or Modify Variable Action run by either a State or an Event. Indicates that an Event fired and triggered a transition to a new State. Events fire when all their Validators are true. Indicates that the Trace Validation engine transitioned into a new State. Indicates that a Validator was tested and the result was true. Indicates that a Validator was tested and the result was false. The results 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. Navigating the User Interface Tool Bar New with UniPro Test Executive is a tool bar that allows selection of analysis view modes and run control for Test Executive and the Keysight U4431A analyzer:

7 Modes (1) allow the user to select a set of pre-defined windows based on the type of analysis being conducted (see WINDOWS below). Test Executive run/stop (2) initiates the selected tests. Analyzer status/control (3) manages the connection to the Keysight U4431A analyzer, allows the user to run or stop the analyzer, and displays the status of the analyzer. Green = connected to the analyzer application and module, Yellow = connected to the analyzer application but not the module, and Red = not connected. Menus The File, Results, Reports, View, Tools and Help functions are only accessible from the Menu, whereas the Test Executive Run/Stop and Analyzer Controls is also accessible from the Tool Bar. The Menu functions are explained in more detail in MENU FUNCTIONS below. Windows The Test Executive includes four Configuration windows (Stimulus, Trace Validation, CTS and Power), two protocol windows (Packet Listing and Packet decode) and three Results windows (Stimulus Results, Trace Validation Results and Trace Validation Statistics). The display Modes (1 above) position a set of predefined windows based on the type of analysis being conducted: Stimulus mode will activate the Stimulus Configuration and Stimulus Results windows. Trace Validation mode positions the Trace Validation Configuration, Trace Validation Results, Trace Validation Statistics, Packet List and Packet Decode windows. CTS mode activates the CTS Configuration, Trace Validation Results, Trace Validation Statistics, Packet List and Packet Decode windows. Power mode displays the Power Configuration window and all other windows, some docked and some tabbed. The Power Configuration window provides access to all configuration settings and the permits the running all tests, including differing Stimulus and Trace Validation tests, in one single test run. This can result in the creation of one test result trace file with many types of link traffic.

8 Figure 4: Power mode window layout All windows are dock-able inside or outside of the application framework, using standard docking paradigms. Windows can be restored to the default mode configurations by selecting View->Restore Default Layout from the main menu. Stimulus Configuration Window Device Control and Status Status: displays the current configuration of the DUT. Control - Online/Offline buttons: Clicking Online connects to the analyzer application and module, and initiates a UniPro Link Startup Sequence to boot the DUT. Control - Reboot Device: Initiates a UniPro Link Startup Sequence then sends the UniPro script selected in the Custom UniPro Script field to the device under test. Control - Initiate Reboot Device Up Every Run: If this box is checked, the reset line (see CONFIGURATION FOR CTS AND STIMULUS MODES) is asserted and a UniPro Link Startup Sequence is executed every time the Start button is pressed. Custom UniPro Settings - UniPro Script File Path: load a user supplied UniPro boot script from this location.

9 Custom UniPro Settings - Use Custom UniPro Capabilities: If this box is checked, the user can modify the values in the Link Startup Sequence capabilities packets sent by the Command Line Packet Generator. Custom UniPro Settings - Modify Device Configuration: This allows the user to set variables that are specific to their device. These variables are used in certain CTS test cases and can be used in stimulus test as well. Analyzer - Module#: is used to specify the slot number in the Keysight chassis that the analyzer/generator blade is installed in. Test Run Order Control the order in which tests are executed. Run order is specified by Loop Order in Ascending, Descending, or Random Seed order. See STEP 5: CONFIGURE STRESS TESTING for more information. Test Run Control Specify the number of test cycles of the test configuration to run. Test execution will stop after the specified number of full test loops (outer loops on Test Run Control) or No Result Test Cases have occurred. See STEP 6: CONFIGURE RUN CONTROL for more information. Transmission Mode Enables Auto or NonAuto power modes during Test Run operation. Scrambling Enable or disable data scrambling. Traffic Class Configure the Traffic Classes to be tested. Currently limited to TC0 as defined by the capabilities of the U4431A. Speed Configure the speeds to be tested. All UniPro speeds up to HS-G3 are supported within the capabilities of the U4431A. Link Width Configure the link widths to be tested. All UniPro widths up to x4 are supported. Tests Select the stimulus tests to be administered. Stimulus mode supports pre-defined CTS and other protocol sequence tests, and well as custom tests. Trace Validation Configuration window Validation Settings Debug Enabled: turns on debug trace in Trace Validation mode. Hello, World! trace messages are embedded in the trace capture to track progress in the Trace Validation analysis. See Debug under INTERPRETING TRACE VALIDATION RESULTS for more information.

10 Do not show ALA File Properties Dialog: if this box is checked, the user will not be prompted to define the trace lanes and labels or trace size when opening an analyzer trace in Trace Validation mode. Instead, the previously entered values will be used. This can be checked in either window. Tests Select the test cases to be administered. Trace Validation mode supports pre-defined CTS and other protocol sequence tests, and well as custom test cases. CTS Configuration window Device Control and Status Status: displays the current configuration of the DUT. Control - Online/Offline buttons: Clicking Online connects to the analyzer application and module, and initiates a UniPro Link Startup Sequence to boot the DUT. Control - Reboot Device: Initiates a UniPro Link Startup Sequence then sends the UniPro script selected in the Custom UniPro Script field to the device under test. Control - Initiate Reboot Device Up Every Run: If this box is checked, the reset line (see CONFIGURATION FOR CTS AND STIMULUS MODES) is asserted and a UniPro Link Startup Sequence is executed every time the Start button is pressed. Control - Test Link Startup on Reboot or Online: If this box is checked, after the Analyzer Stop button is pressed the analyzer trace will be loaded into Test Executive automatically and Link Startup Sequence Trace Validation analysis results will be displayed in the Trace Validation Results window. Check this box for quick debugging during initial DUT configuration and LSS analysis. Custom UniPro Settings - UniPro Script File Path: load a user supplied UniPro boot script from this location. Custom UniPro Settings - Use Custom UniPro Capabilities: If this box is checked, the user can modify the values in the Link Startup Sequence capabilities packets sent by the Command Line Packet Generator. Custom UniPro Settings - Modify Device Configuration: This allows the user to set variables that are specific to their device. These variables are used in certain CTS test cases and can be used in stimulus test as well. Analyzer - Module#: is used to specify the slot number in the Keysight chassis that the analyzer/generator blade is installed in.

11 Test Run Order Control the order in which tests are executed. Run order is specified by Loop Order in Ascending, Descending, or Random Seed order. See STEP 5: CONFIGURE STRESS TESTING for more information. Test Run Control Specify the number of test cycles of the test configuration to run. Test execution will stop after the specified number of full test loops (outer loops on Test Run Control) or No Result Test Cases have occurred. See STEP 6: CONFIGURE RUN CONTROL for more information. Transmission Mode Enables Auto or NonAuto power modes during Test Run operation. Scrambling Enable or disable data scrambling. Traffic Class Configure the Traffic Classes to be tested. Currently limited to TC0 as defined by the capabilities of the U4431A. Speed Configure the speeds to be tested. All UniPro speeds up to HS-G3 are supported within the capabilities of the U4431A. Link Width Configure the link widths to be tested. All UniPro widths up to x4 are supported. Tests Select the CTS test cases to be executed. Power Configuration window The Power Configuration window replicates all of the functionality of the other Configuration windows, with the following enhancements: Tests Selecting All will display all tests in the list, including Stim, TV and CTS tests. The type of test is identified by an icon as either a Stim or Trace Validation test or containing both. This permits the running of all tests, including differing Stimulus and Trace Validation tests, in one single test run, resulting in the creation of one trace result file with many types of link traffic and analysis. Selecting TV will display only Trace Validation tests.

12 Selecting Stim displays only Stimulus tests. Filter Linked Tests: Checking the Filter Linked Tests box when All is selected will filter the list and only display those tests that include both a Stim and associated TV test. Tooltips identify the Stim test used for each TV test listed. Test Categories Depending on which Configuration window is active, the following categories may be available for execution in the Tests section: CTS Test Cases: The Test Cases in this category test the DUT for compliance to the UniPro CTS. Execution of the linked Stimulus with a Trace Validation result of Pass indicates the DUT meets the CTS Test Case criteria. NAC conditions: These tests are a collection of various packet errors. They should create issues with the packets on the line causing the DUT to issue a NAC and the tester will resend a correctly formed packet. Power Mode Change: There are 40 Power Modes changes to specific modes. The DUT will start in the Power Mode defined by Test Executive and then change to the Power Mode specified by the test. Traffic Overview: These test cases provide general information about the trace file contents. For example, how many of each packet are present in the trace. UniPro: This category contains additional general test cases to check UniPro behavior. For example, to verify that the Link Startup Sequence ran correctly. Custom Tests: Custom test directories are displayed in italics at the bottom of the list; if no custom test cases exist these directories will not be displayed. Depending on the display mode selected, Stimulus and/or Trace Validation custom tests will be shown. The tests listed can be refreshed from the File menu as new custom test case are created.

13 Packet List window The Packet List window displays all packets in a trace, or a filtered set of packets located around the Trace Validation packet of interest. Clicking on a result in the Trace Validation Results window will position the cursor in the Packet List window on the packet of interest in the test sequence. Filtering the Packet List allows the user to narrow the packets displayed in the Packet List window: If All is selected, the Packet List window will display all packets in the trace, with the packet of interest centered in the display. If Test is selected, the Packet List window will display all packets in the trace that are a part of the packet sequence of interest. For example, if a packet is selected in the Results window for a Link Startup Sequence, then Test will display all packets Trace Validation has determined to be part of that specific LSS event. If Test Plus is selected, the Packet List window will display all packets in the trace that are a part of the packet sequence of interest, plus the number of additional packets on either side of the sequence of interest as specified in the user-entered value field. For example, if a packet is selected in the Results window for a Link Startup Sequence, then Test +5 will display all packets Trace Validation has determined to be part of that specific LSS event plus 5 additional packets on either side of the sequence. The In Test icon highlights the packets in the trace that are included in the test results. Color Coded packets: Common packet types in the list window are color-coded the same, for example, all End_of_Burst, PACP_SET_cnf or PACP_GET_cnf packets are of the same color. Error packets are highlighted in red.

14 Bookmarks can be added to any packet in the Packet List window by rightclicking and selecting Add Bookmark. By right-clicking and selecting Edit Bookmark an existing bookmark can be renamed or given a different color. Hovering over a bookmark will display a tooltip indicating timestamp and delta time to other bookmarks. Navigating the Packet List window can be accomplished in several ways: Search can be used to find any packet in the trace by selecting that packet type in the Search dropdown box and clicking the up and down buttons to jump to that packet. The Search function is linked to the Traffic Overview results window; if the trace is less than 100,000 packets Traffic Overview will automatically calculate the trace data when the file is loaded by the user or by Test Executive. If the trace is larger, the Calculate button must be clicked to generate the packet list in the dropdown box. Goto Packet Index is accessed by right-clicking anywhere in the Packet List window, and allows direct navigation to a specific packet. Go To is accessed by right-clicking anywhere in the Packet List window, and permits navigation to Start of Trace, End of Trace or existing bookmarks. Packet Decode window To display the protocol decode of a packet of interest, click on the packet in the appropriate Results window or in the Packet List window. Hovering over a bit displays additional decode information. Selecting 8, 16, or 32 defines the bit width of the display. Stimulus Results window The Stimulus Results window provides success/fail information on the Stimulus test cases executed. This window does not display analysis results but only whether or not the stimulus test ran successfully. Trace Validation Results window Since CTS test cases use the Trace Validation engine for protocol sequence and packet inspection, the Trace Validation Results window is used in both CTS and Trace Validation modes to display the results. The Results window allows extensive quantitative analysis of results data. Results can be grouped and summarized, sorted, and filtered by any header column: Status, TestID, Test Name or Rule. 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. Clicking on a packet will center that packet in the Packet List and Packet Decode windows for further analysis. Traffic Overview window Traffic Overview offers a summary of all packets found in the trace. If the trace is less than 100,000 packets Traffic Overview will automatically calculate the trace data when the file is loaded by the user or by Test Executive. If the trace is larger, the Calculate button must be clicked to generate the results in the Window. Any packet can then be found by selecting that packet type in the Traffic Overview window, clicking on either Host, Device or Total, and clicking the up or down buttons, or < and > to go to the beginning or end of the trace.

15 Trace Validation Statistics window Statistics window provides an overview of trace characteristics in Trace Validation mode, enabling sum, filter and sort by Test, Variable, Attribute, or Value. Example variables include TRG_UPR, Start-of-burst and End-of-burst, NAC, and PACP_CAP. These variables and attributes are defined by the user when developing a custom Trace Validation test case. Menu Functions Many menu functions are duplicated on the easy to access TOOL BAR. This section provides additional detail for the more complex menu-only functions. File Menu File Open Analyzer Capture This function is used for Trace Validation analysis to load trace files captured by a protocol analyzer. Captured traces should be stored in <User>\Documents\Protocol Insight\UniPro\AnalyzerTraceFiles to be easily accessed from this menu. This function is only active in Trace Validation or Power modes, and is greyed out for all other modes. Once a trace file has been selected, a dialog box will allow the user to assign names to the upstream and downstream channels in the trace and associate a module and sub-analyzer for each direction. The user can also specify the number of packets to read and process from the trace. Currently up to 999,999 packets are supported. Open Configuration This function is used to open a previously saved *.pit file to restore the Configuration Window and all test settings. File Open Configuration/Analyzer Capture This function is used to open a previously saved *.pit file including Configuration Window, test settings and the associated analyzer trace capture. File Save Configuration This function is used to save all settings from the Configuration Window. File Save Configuration/Analyzer Capture This function is used to save all settings from the Configuration Window, the test settings and the associated analyzer trace capture. This is a convenient approach to save a complete test environment to share with another Test Executive user. The file extension of.pit (Protocol Insight Test) is used for these files; changing the file extension to.zip allows the files to be managed separately outside of Test Executive.

16 File Refresh Stimulus Builder Tests File Refresh Trace Validation Builder Tests These functions updates the list of custom test categories and custom test cases in the Configuration windows from the categories and test cases in <User>\Documents\Protocol Insight\UniPro\CustomTests. Directories in <User>\Documents\Protocol Insight\CustomTests are displayed as categories in the test lists, appended to the bottom. For example, the directory <User>\Documents\Protocol Insight\UniPro\CustomTests\ProjectX would appear in the test lists as the category ProjectX. Custom tests must be saved in categories (directories). New categories can be created by adding new sub-directories in <User>\Documents\Protocol Insight\UniPro\CustomTests with File Explorer, or by creating a new category in the Category field of the Save Test Case dialog box in Stimulus Builder. See the separate Builder User Guides in the Test Executive or Builder Help menus for more information. Results Menu File Results Selecting these file options will clear the respective Results window or windows of all test results. Reports Menu Reports Trace Validation Results Reports Trace Validation Statistics Reports Stimulus Results Summary reports can be created by configuring the Results/Statistics window (grouping, summarizing, sorting, filtering and expanding levels) and then printing it from this menu. This menu will reproduce exactly what is reflected in the Results/Statistics window either to a PDF file or a printer or to a CSV or XML file. Reports Packet List A Packet List report can be generated from the Packet List window. Selecting All, Test or Test Plus prior to running the report will define which packets in the Packet List to include in the report. If All is selected, the Packet List report will include all packets in the trace. If Test is selected, the Packet List report will include all packets in the trace that are a part of the packet sequence of interest. If Test Plus is selected, the Packet List report will include all packets in the trace that are a part of the packet sequence of interest, plus the number of additional packets on either side of the sequence of interest as specified in the user-entered value field. This menu will reproduce exactly what is reflected in the Packet List window either to a PDF or printer or to a CSV or XML file. View Menu View

17 Any windows that have been closed will be restored by selecting these options. Restore Default Layout will only restore the default layout for the currently active display mode. Analyzer Control Menu Analyzer Control Connect This menu item provides the same functionality as the Analyzer status/control tool bar. Clicking Connect will cause Test Executive to establish a connection with the analyzer application and with the analyzer module if it is online. The status indicator in the tool bar will display green if connection to both the application and module is successful, yellow if connected to the analyzer application but not the module, and red if not connected. Tools Menu Tools Stimulus Builder This menu item will launch Stimulus Builder in a separate window. Tools Trace Validation Builder This menu item will launch Trace Validation Builder in a separate window. Tools Database Settings Test Executive can now perform extended automated stress test runs, capturing millions of results utilizing an SQL database with a total capacity of 10GB. Microsoft SQL Server and Test Executive specific database settings are configured automatically with the initial software installation. However, in some instances it may be necessary to reset your database settings, reconfigure your database or install it manually from scratch. The Database Configuration dialog is used to update and save settings to repair the database. See APPENDIX A: RESETTING YOUR SQL DATABASE thru APPENDIX C: MANUALLY INSTALLING MICROSOFT SQL SERVER for more information. Setup and Operation UniPro Test Executive has several analysis modes. You can use TRACE VALIDATION (TV) MODE to verify UniPro conformance of traces captured from a bi-directional UniPro link using the Keysight U4431A analyzer with options 712 (MIPI M-PHY Universal Flash Storage plus UniPro) and 612 (Bi-directional analysis) and two standard U4433A ZIF probes. However, if you want to use CONFORMANCE TEST SUITE (CTS) MODE or STIMULUS MODE the Keysight U4431A analyzer will also need Keysight U4431A option 613, Command Line Packet Generator, and one Keysight U4432A SMA probe. See APPENDIX G: KEYSIGHT TECHNOLOGIES MINIMUM HARDWARE CONFIGURATION FOR CTS/STIMULUS MODES and APPENDIX H: KEYSIGHT TECHNOLOGIES MINIMUM HARDWARE CONFIGURATION FOR TRACE VALIDATION MODE for more information on the required analyzer configurations.

18 Configuration for CTS and Stimulus modes Step 1A: Configure instrument hardware 1. Connect the U4432A SMA probe to Pod 1 of the Keysight U4431A (see Figure 6: POD1 and POD2 connections below). 2. Install the loopback board in Pod 2 of the U4431A (see FIGURE 6: POD1 AND POD2 CONNECTIONS below). 3. Connect the DUT reset cable to the trigger out port of the U4431A (not the ESM). 4. Set up the Keysight Analyzer Software. See APPENDIX D: CONFIGURING KEYSIGHT TECHNOLOGIES U4431A FOR CTS AND STIMULUS MODES. Figure 5: Typical Setup U4432A SMA probe in POD1 Loopback board in POD2 Figure 6: POD1 and POD2 connections Step 1B: Connect probes The labels on the Keysight U4432A SMA probe are from the packet generator perspective. 5. Connect RX0p on the SMA probe (black) to TX0p on the DUT 6. Connect RX0n on the SMA probe (black with white) to TX0n on the DUT 7. Connect TX0p on the SMA probe (white) to RX0p on the DUT 8. Connect TX0n on the SMA probe (white with white) to RX0n on the DUT 9. 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. 10. If your DUT requires a reference clock you will need to provide that from an external source. Step 1C: Connect reset signal 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: c. Solder the resistor between the pin and ground.

19 Step 2: Connect Test Executive to the instrument SW 1. In Test Executive click the Connect button on the tool bar. Test Executive will attempt to connect to the Keysight analyzer software. 2. If the connection is successful the status will indicate yellow, and if the analyzer is online and connected to a protocol analyzer module in the chassis the status will display green. If Test Executive is not successful connecting to the analyzer software the status will be red. Step 3: Connect to DUT For CTS and Stimulus modes connection to the DUT is required by initiating the UniPro Link Startup Sequence: 1. In the CTS or Stimulus Configuration window load the device-specific UniPro TCl script by browsing the Custom UniPro Script field. 2. Configure device parameters for your device. 3. If desired, check the Test Link Startup on Reboot or Online box to automatically load the analyzer trace into Test Executive and perform Link Startup Sequence Trace Validation analysis when the Online or Analyzer Stop button is pressed. 4. Press the Online button in the CTS or Stimulus Configuration window to boot the device to UniPro. Note: Pressing the Online button will not run the Custom UniPro Script it will only initiate the LSS. Each time the Run button is pressed a Reboot Device is performed which will initiate a LSS followed by executing the Custom UniPro Script. If the Initiate Reboot Device Every Run box is unchecked the Reboot Device will not be executed every run, in this case it is recommended the user issues a Reboot Device command once before testing starts. Step 4: Configure Tests 1. Select which Speeds and Link Widths to test 2. Select which test Categories and Tests to run Step 5: Configure Stress Testing 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 the Loop Order is Speeds, Link Widths, Tests then all Tests will be completed for a Link Width before being executed for the next Link Width, 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. Step 6: Configure Run Control Test Run Control specifies the number of iterations of the test configuration to run, dictated by Test Run Order. Test execution will stop after the specified Number of Loops (outer loops on Test Run Control) or No Result Test Cases have occurred.

20 The user can specify the number of test configuration loops to run OR the number of No Result Test Cases to allow before terminating the test run. When Number of No Result Test Cases field is blank or 0, tests are run for the given number of loops. If values are provided for both conditions, then tests are run until any ONE of the conditions is met. Step 7: Run the configured tests Select the appropriate Run mode and press the Run button to run the configured tests, and watch the Results window fill with Pass, Fail, Warning, or Info results. Configuration for Trace Validation mode (alternate HW configuration) Step 1: Configure hardware 1. Connect the Tx and Rx signals from customer DUT to two Keysight U4433A ZIF Flying Lead Probes 2. Connect the U4433A ZIF probes to Pod 1 and Pod 2 of the Keysight U4431A 3. Set up the Keysight Analyzer Software. See APPENDIX E: CONFIGURING KEYSIGHT TECHNOLOGIES U4431A (OPTIONAL FOR TRACE VALIDATION MODE) Step 2: Connect to analyzer 1. In Test Executive click the Connect button on the tool bar. Test Executive will attempt to connect to the Keysight analyzer software. 2. If the connection is successful the status will indicate yellow. If the analyzer is online and connected to a protocol analyzer module in the chassis the status will display green. If Test executive is not successful connecting to the analyzer software the status will be red. 3. Capture the trace on the protocol analyzer and save it to <User>\Documents\Protocol Insight\UniPro\AnalyzerTraceFiles. Step 3: Configure and run tests 1. Select the Trace Validation mode in Test Executive. 2. Open the saved trace file from <User>\Documents\Protocol Insight\UniPro\AnalyzerTraceFiles. 3. Select which Tests to run. 4. Press the Run button to run the selected tests, and watch the Results window fill with Pass, Fail, Warning, Info or Debug results.

21 Analysis The Results windows The Trace Validation window is used in both CTS and Trace Validation modes, and allows extensive quantitative analysis of results data. Results can be grouped and summarized, sorted, and filtered by any header columns Status, TestID, Test Name, or Rule. The Trace Validation Statistics window The results in the Statistics window represent a traffic summary view of the number of instances of occurrence of events in the trace. The Statistics window is used in both CTS and Trace Validation modes, offering similar grouping and summarizing, sorting, and filtering capabilities by Test, Variable, Attribute or Value. 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: Figure 7: Grouping and Summarizing The item count represents the number of items in the grouping below, so in this example (2) Test Name: UniPro: Power Mode Change counted 4 items, representing 4 different test results. This item count

22 summing function can be manipulated with a high degree of flexibility by reordering the groupings to count different items in addition to tests, such as number of Failures (Status) or 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, 4 results were determined for Test Name: UniPro: Power Mode Change, and the worst result was a Failure so Test Name: UniPro: Power Mode Change 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 8: Sorting and Filtering Packet List window The Packet List window displays all or a filtered set of packets located around the packet of interest. See PACKET LIST WINDOW for more details. Packet Decode window To display the protocol decode of a packet of interest, click on the packet in the appropriate Results window or in the Packet List window. Hovering over a bit displays additional decode information Selecting 8, 16, or 32 defines the bit width of the display. See PACKET DECODE WINDOW for more details. Analysis Reports Results Summary, Packet List and Statistics reports can be created by configuring the appropriate window and then printing it. See REPORTS MENU for more information.

23 Appendix A: Resetting Your SQL Database Follow these steps to reset your SQL database: 1. Launch Protocol Insight UniPro Test Executive 2. Select Tools Database Settings 3. Enter the following a. Server Name: "localhost\protocolinsight" b. Database Name: "ProtocolInsight" c. Authentication Type: "Windows Authentication" 4. Click Repair Database. 5. Click Yes on the warning message box 6. You should get a dialog box saying "Database was restored successfully" 7. You can now use Test Executive normally

24 Appendix B: Reconfiguring Your SQL Database Follow these steps to reset your SQL database: 1. Launch Protocol Insight UniPro Test Executive 2. Select Tools Database Settings 3. Enter the following Server name: Enter the SQL Server instance to connect to. By default this should be localhost\protocolinsight. Database Name: The name of the database on the server. By default this is Protocolinsight. Authentication Type: Two authentication modes are available when connecting to an instance of the Database Engine: Windows Authentication - Microsoft Windows Authentication mode allows a user to connect through a Windows user account. SQL Server Authentication - When a user connects with a specified login name and password from a non-trusted connection, SQL Server performs the authentication itself by checking to see if a SQL Server login account has been set up and if the specified password matches the one previously recorded. User Name: The SQL Server login id to connect to SQL Server with. Only if Authentication Type is SQL Server Authentication. Password: The Password to connect to SQL Server with. Only if Authentication Type is SQL Server Authentication. Use Default Password: This will override the password with the default password for the sa account. User Name must be sa and the SQL Server install must be the default from installing Test Executive. When you have entered all the data, click Test Connection to make sure the server, database, and security are valid.

25 Appendix C: Manually Installing Microsoft SQL Server Test Executive can now perform extended automated stress test runs, capturing millions of results utilizing an SQL database with a total capacity of 10GB. Microsoft SQL Server and Test Executive specific database settings are configured automatically at initial installation. However, in some instances it may be necessary to install Microsoft SQL Server and configure it manually. Follow these steps to manually install and configure your SQL database: NOTE: If you are manually installing during Test Executive setup, start with Step Obtain the SQL Server 2014 Express edition installation media from Microsoft a. b. Select English and click Download c. Choose ExpressAndTools 64BIT\SQLEXPRWT_x64_ENU.exe d. Click Next 2. Run SQLEXPRWT_x64_ENU.exe to extract the install files. Setup will automatically start after the extraction completes. 3. SQL Server Installation Center - Click Installation on the list of options in the left pane 4. Click " New SQL Server stand-alone installation or add features to an existing installation"

26 5. Installation Type Choose Perform a new installation of SQL Server 2014 and click Next 6. License Terms Check I accept the license terms and click Next 7. Features Selection Click the Select All button and click Next (You can optionally change the installation drive if you need to install to a drive other than C:\) 8. Instance Configuration Chose Named Instance and Enter "ProtocolInsight" as the instance name. The Instance ID should automatically update to "PROTOCOLINSIGHT"

27 9. Server Configuration Leave the default options, click Next 10. Database Engine Configuration Click the Add Current User button if the current windows user is not listed in the Specify SQL Server administrators box. Click Next. 11. Wait for the installation to complete and click Finish. Appendix D: Configuring Keysight Technologies U4431A for CTS and Stimulus modes 1. In U4431A software configure Data Gen + Analyzer on the Connection Setup tab. 2. Choose Both Sublinks on the Connection Setup tab so both the TX and RX data is captured.

28 3. Choose the correct Sublink Width for your Device. 4. On the Analyzer Setup tab choose the correct rate series for your Device. 5. In the Protocol Viewer remember to show All Channels, Direction A and B

29

30 Appendix E: Configuring Keysight Technologies U4431A (optional for Trace Validation mode) 1. In U4431A software configure Analyzer 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. In the Protocol Viewer remember to show All Channels, Direction A and B

31 Appendix F: Required software and firmware 1. Windows 7 64 bit operating system with minimum 12GB RAM 2. Protocol Insight UNI16COMP UniPro Test Executive version 1.0 or later 3. Keysight technologies U4431A application software version 6.1 or later 4. Keysight Technologies U4431A option 613 Command Line Packet Generator (CLPG). Go to for information on compatible SW/FW versions. Contact your local Keysight FE or AE to obtain the latest compatible SW and FW. 5. 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:

32 Appendix G: Keysight Technologies Minimum Hardware Configuration for CTS/Stimulus modes 1. Keysight Technologies U4431A MIPI M-PHY Protocol Analyzer, minimum system: Module U4431A U4431A-412 Protocol test module, MIPI M-PHY, Gear 1, one lane, 1 GB memory Increase to 2-lane MIPI M-PHY (note: four lanes recommended) U4431A-514 Increase data rate to Gear 3 U4431A-613 Bi-directional support and Command Line Packet Generator, with U /U 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 M9536A Two Slot AXIe Chassis With PCIe Connection for Host PC, Cascading Capabilities, External Trigger In/Out, External Clock In/Out 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 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

33 Appendix H: Keysight Technologies Minimum Hardware Configuration for Trace Validation mode 2. Keysight Technologies U4431A MIPI M-PHY Protocol Analyzer, minimum system: Module U4431A U4431A-412 Protocol test module, MIPI M-PHY, Gear 1, one lane, 1 GB memory Increase to 2-lane MIPI M-PHY (note: four lanes recommended) U4431A-514 Increase data rate to Gear 3 U4431A-612 U4431A-712 U4433A Bi-directional support MIPI M-PHY Universal Flash Storage (UFS) plus UniPro ZIF Analyzer Flying Lead probe (quantity 2 required) System M9502A M9536A Two Slot AXIe Chassis With PCIe Connection for Host PC, Cascading Capabilities, External Trigger In/Out, External Clock In/Out 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 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

34 Appendix I: Known Limitations 1. Trace Validation Builder requires Microsoft Visual Studio 2013 Shell (Isolated) to operate, which must be downloaded from the Microsoft website 2. While multiple different versions of Test Executive (UFS, UniPro, etc.) can run concurrently, only one of each instance may execute tests at a time, and only one may control the Keysight Technologies U4431A CLPG at a time 3. The Keysight U4431A MIPI M-PHY protocol analyzer command line packet generator (CLPG) is required for CTS and Stimulus mode operation. Verify compatibility with Test Executive here:

35 Protocol Insight 2015, 2016 Specifications and descriptions in this document are subject to change without notice. Protocol Insight, LLC 2015, 2016 Revision 1.4, November 22, 2016