Teledyne LeCroy Protocol PCI Express Script Automation Test Tool - Manual (Page 12)

Teledyne LeCroy PCI Express Script Automation Test Tool User Manual
8
You can add tests to the package to expand test coverage. To add a test, copy a similar existing test script file into
any text editor. Replace the TestName and other information. Replace the Generation Options path, Recording
Options path, Trainer Script path, and Verification Script path. Save as a new test script file in the Endpoint or
RootComplex subfolder, depending on the DUT type, of the AutomatedTests folder. Ensure that the Generation
Options file, Recording Options file, Trainer Script file, and Verification Script file are in the appropriate folders.
Please refer to PETracer/Trainer documentation for information on how to create Recording and Generation
Options and Trainer and Verification Scripts. You can use the Trainer and Verification Scripts included with the
PCI Express Script Automation Test Tool to build your own tests.
Please refer to the 2.3
Folder Structure section for specific file locations.
Special
TestGroup
Besides the "Link Layer" and "Transaction Layer" TestGroup, there is a TestGroup called Special. This TestGroup
includes all tests that are executed before running the actual test. These tests do not appear in the test selection list
but are always executed first each time you press the Run Tests button. The Special tests read the configuration
space of the DUT and create a definitions file for the test that defines the required register addresses. The definitions
file is required to customize the Trainer and Verification Scripts for the DUT. The
AutomatedTests\Endpoint\special_test.cts and AutomatedTests\RootComplex\special_test.cts files have
examples of the Special tests.
RootBoot
TestGroup
Besides the "Special," "Link Layer," and "Transaction Layer" TestGroup, there is a TestGroup called RootBoot.
This TestGroup includes a test that is executed for a Root Complex DUT when you press the Boot RC button.
Sections 2.4 and 2.5 have details on running Root Complex tests.
Custom Initialization for Endpoint Device Testing
Some Endpoint devices require special initialization before a test can be performed. Custom initialization may
require a Configuration Write, Memory Write, and/or IO Write transaction. For example, IO Write special
initialization is required to enable error reporting.
To initialize an Endpoint device, modify the file TrainerScripts\Templates\device_specific_init.peg to include
Configuration Write, Memory Write, and/or IO Write transactions.
The TrainerScripts\Templates\device_specific_init.peg file includes commented sample code to illustrate special
initialization. Use that sample code to modify the file for special Endpoint Device testing. At the end of the file, set
the VAR_CURRENT_SEQUENCE_NUMBER parameter to an appropriate value.
The PCI Express Script Automation Test Tool runs the TrainerScripts\Templates\device_specific_init.peg script
after each Link Up before starting the actual test.