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

Teledyne LeCroy PCI Express Script Automation Test Tool User Manual
48
3.2.2.3 Test 2-4. TXN_BFT_ErrorSignaling
ASSERTIONS COVERED: TXN.2.15#2, TXN.2.15#3, TXN.2.15#4
The intent of this test is to verify basic error signaling functionality of a Root or Switch port related to Uncorrectable
(Non-Fatal or Fatal) errors.
Trainer Stimulus: trans_2-4_TXN_BFT_ErrorSignaling.peg
Recording Options: link_layer.rec
Verification Scripts: trans_2-4_TXN_BFT_ErrorSignaling.pevs
Test Algorithm:
1. Issue command to the Driver to read and reflect to the link the value of the Uncorrectable Error Severity
register for the Root or Switch port to which the Device Emulator is attached. The Verification script uses
this value to determine how each of the errors created during the test should be reported.
2. Issue command to the Driver to clear all error status bits for the Root or Switch port to which the Device
Emulator is attached.
3. Send Memory Write TLP with Length = 1, but no Payload, thus creating a Malformed TLP error.
4. Issue command to the Driver to reflect the current values of the Error Reporting Registers for the port to
which the Device Emulator is attached (using Configuration Writes).
5. Issue four commands to the Driver to read and reflect to the link the value of the four DWORDS of the
Header Log register for the Root or Switch port to which the Device Emulator is attached. (If Advanced
Error Reporting capability is not implemented, the values are ignored).
6. Issue command to the Driver to clear all error status bits for the Root or Switch port to which the Device
Emulator is attached.
7. Send Memory Read Completion that is not expected, thus creating an Unexpected Completion error.
8. Issue command to the Driver to reflect the current values of the Error Reporting Registers for the port to
which the Device Emulator is attached (using Configuration Writes).
9. Issue four commands to the Driver to read and reflect to the link the value of the four DWORDS of the
Header Log register for the Root or Switch port to which the Device Emulator is attached.
10. Send Memory Write TLP with EP = 1, thus creating a Poisoned TLP error.
11. Issue command to the Driver to reflect the current values of the Error Reporting Registers for the port to
which the Device Emulator is attached (using Configuration Writes).
12. Issue four commands to the Driver to read and reflect to the link the value of the four DWORDS of the
Header Log register for the Root or Switch port to which the Device Emulator is attached.
Pass/Fail Criteria:
Test should successfully progress though all test stages.
All test stages should be executed without protocol violations.
Verify that:
a) After each of the three error types, the DUT set the corresponding Non-Fatal or Fatal bit in the Device Status
register for the Root/Switch port.
b) The DUT did not set any error bits in the Advanced Correctable Error Status register (if implemented), for all
three types of errors.
c) The DUT set the corresponding error bits in the Advanced Uncorrectable Error Status register (if implemented),
for each of the three types of errors.
d) The DUT logged the four DWORDS of the header for each of the three erroneous TLPs the Device Emulator
generated in the Header Log register (if implemented).
e) The DUT set the corresponding bits in the Root Error Status register (if implemented), for each of the three types
of errors.
If the DUT meets all these criteria, the DUT passes the test.