Teledyne ST User Manual

PROTOCOL SOLUTIONS GROUP
3385

SCOTT BLVD

SANTA CLARA, CA 95054

Automated Test Suite

User Manual

ST

Manual Version 1.10

Software Version 1.10

November 2012

Document Disclaim er

The information contained in this document has been carefully checked and is believed to be
reliable. However, no responsibility can be assumed for inaccuracies that may not have been
detected. Teledyne LeCroy reserves the right to revise the information presented in this document
without notice or penalty.

Trademarks and Servicemarks

Teledyne LeCroy and ST Automated Test Suite are trademarks o f Teledyne LeCroy.
Microsoft and Windows are registered trademarks of Mi cr os o ft Inc.
All other trademarks are property of their respective companies.

Copyright

Teledyne LeCroy© 2012. All rights reserved.
This document may be printed and reproduced without additional permission, but all copies should

contain this copyright notice.

2

Contents

1. Introduction ...................................................................................................................... 4

1.1 Test Case Overview .................................................................................................. 4

1.2 Folder Structure ......................................................................................................... 4

2. Automated Test Suite Appl i cati o n S hell ........................................................................... 5

2.1 Main Toolbar .............................................................................................................. 6

2.2 Workspace Area ........................................................................................................ 8

2.3 Test Monitoring Console ............................................................................................ 9

2.4 Output Window ........................................................................................................ 10

2.5 Menus ...................................................................................................................... 10

3. Operation of the Automated Test Suite Software ........................................................... 11

4. Writing ATS VB Scripts .................................................................................................. 12

4.1 Creating the Main Objects ....................................................................................... 12

4.2 Specifying Port Configuration .................................................................................. 14

4.3 Running the Analyzer and Capturing a Trace File ................................................... 15

4.4 Running Host Emulator ............................................................................................ 16

4.5 Running Trainer ....................................................................................................... 17

4.6 Running InFusion ..................................................................................................... 19

4.7 Activating Device Emulator ...................................................................................... 20

4.8 Running Mixed Configurations/Functionalities ......................................................... 21

4.9 VSE Verification ....................................................................................................... 23

4.10 Loading Pre Emphasis Signal Settings............................................................... 32

How to Contact Teledyne LeCroy ............................................................................................ 33

3

1. Introduction

The ST Automated Test Suite is a turnkey verification system that allows developers to pre-test
devices for SAS/SATA specification conformance. The system generates specific traffic conditions to
the Host or Device under Test (DUT). The Analyzer simultaneously records and analyz es responses.
The ST Automated Test Suite includes a software console that manages the entire compliance
verification proc ess by allowing users to run individual test cases or run the full suite in batch mode
operation.

The ST Automated Test Suite operates on Sierra M6-4, Sierra M6-2 and Sierra M6-1 platforms.

1.1 Test Case Overview

Each individual test case is controlled by a VB script that automates operation of the hardware and
software. The ST Automat ed Tes t Suite has Available VB Scripts:

o General, such as PreemphasisLoad and VSE
o Analyzer, such as Multi-Open-Close, Run Analyzer project (Make recording), and Run Analyzer

project (Start-stop recording)

o Target Emulator, such as Activate-Deactivate and Analyzer-Target
o Host Emulator, such as AnalyzerExerciser and HostOnly
o Infusion, such as Analyzer-Infusion and Infusion
o Trainer, such as Analyzer-Trainer, Analyzer-Trainer - 1 Port, Analyzer-Trainer - 2 Ports, Trainer

Only, and Trainer WithEx i tC ode

o Mixture Configurations, such as AnalyzerDeviceInfusion, AnalyzerHostDevice, HostInfusion,

TargetInfusion, Trai n er In fusi o n

See Chapter 4, Writing ATS VB Scripts.

1.2 Folder Structure

The ST Automated Test Suite application has its own folder structure. These folder s are a t the top
level:

o Examples/Scripts: Contains VB scripts.
o Reports: Contains the generated reports.
o Output: Def ault fol der f or sav ing trace files. You can change the default folder in the

Settings dialog.

4

2. Automated Test Suite Application Shell

The ST Automated Test Suite installs an application that initiates the test process and manages the
test output (Figure 2-1).

Figure 2-1

The software contains the following main parts:

o Main Toolbar
o Workspace Area
o Monitoring Console
o Output Window
o Menus

5

2.1 Main Toolbar

Settings Button

The Settings button, at the left, opens the Settings dialog (Figure 2-2), which provides access to
user-configurable options.

Figure 2-2

VB Scripts root directory: Specifies the folder in which to save VB scripts.
Generated reports path: Specifies the folder in which to save reports.
Trace files path: Specifies the folder in which to save trace file output during test execution.
VB Script Editor: Specifies the application with which to open VB scripts.

Automatically Save Log: To automatically save log files, select the checkbox and enter the

File Path and the Max(imum) Size in kilobytes.

Project files path: Specifies the folder in which to save the project.
Automatically Save Log: To automatically save log files, select the checkbox and enter the

File Path and the Max(imum) Size in kilobytes.
ATS working protocol: Specifies SAS or SATA protocol.

6

Configuration Button
The Configuration button opens the Configuration dialog (Figure 2-3), in which you can enter the

DUT Name and then set the SAS Address and Speed (1.5 Gbps, 3.0 Gb ps, 6. 0 Gbps, or

AutoSpeed) for each Port number.

Figure 2-3
Click the Find Device button to locate devices.

Help Button

The Help button displays information about the application.

7

2.2 Workspace Area

The Workspace Area provides a nested tree structure that allows you to select individual tests to run
(Figure 2-4).

Figure 2-4
This window lists all available tests. Checkboxes allow selection of the entire suite or individual test

cases.

Buttons

After tests are selected, the Add button adds test(s) to the execution pipe.
After tests are selected, the Show VBS button, or double-clicking the test case name, opens the VB

script file in the Scripts Editor, such as the Notepad application.
The Refresh Test list button refreshes the list of tests, if tests have been added or modified within

the Scripts folder.

8

2.3 Test Monitoring Console

The Test Monitoring Console (Figure 2-5) lists the tests that have been selected for execution, their
results, and their descriptions.

Figure 2-5
After adding a test (using the Add button in the Workspace Area), the test appears in the

Test Monitoring Console.
The Result column displays the test status upon completi on . The Result field may display Passed,

Failed, or Done.

• When the test passes, Pass is shown in the Result field on a green background.

• When the test fails, Fail is shown in the Result field on a red background.

• When the test executes and the verification process is unable to confirm the expected behavior,

Done is shown in the Result fiel d on a gray background (rarely occurs).

• When the test is unable to capture a valid trace file, the software displays a message:
“Error during recording; No trace file created”.

If the test fails, the verification software shows an error code in the Description field.

Buttons

The green Run all button, at the left, starts execution in sequential order of all tests in the monitoring
window.

The black Stop button, second from left, allows you to stop execution of the current test run.
The Run Failed Test Case(s) button, third from left, runs the failed test cases again.
The Run Selected Test Case(s) button, fourth from left, runs the selected test cases. You can select

multiple rows using CTRL+Right-Click.
The Remove Selected Test Case(s) button, fifth form left, deletes the selected tests from the list of

potential running tests. You can select multiple rows using CTRL+Right-Click.

9

The Remove All Test Case(s) button, sixth from left, removes all tests from the running queue.
Upon completion of a test run, the View HTML report of latest run button, seventh form left, opens

a summary report. The HTML report summarizes the test results including the result, suspected error
code, and test execution details. If individual test cases generate a fail result, hyperlinks are added to
navigate directly to the error point in the trace file.(Figure 2-7):

Upon completion of a test run, the View XML report of latest run button, ei ghth from left, opens an
XML version of the summary report.

The Load Project button, second from right, loads saved Projects from a folder. A Project is a
collection of scripts. The scripts are listed in the right pane.

The Save Project button, at the right, saves the current Project to a folder.

2.4 Output Window

The Output Window (Figure 2-6) provides a real time test log in text format. The software generates
a text-based report during execution of the test run and appends the report to the Output Window as
each test completes. The log summarizes the status of the each test and alerts you to possible test
operation problems as they are detected.

Figure 2-6

Buttons

The Save Log button, second from left, saves the Log to a text file.
The Print Log button, second from right, prints the Log.
The Clear button, at the right, clears the window.

2.5 Menus

The Menus are:

o File: Configuration, Settings, Exit
o Run: Run, Stop
o Commands: Add, Remove, Add All, Remove All
o View: Toolbar, Status Bar, Workspace, Output
o Reports: HTML, XML
o Help: Help Topics, About LeCroy STATS

10