The Error Summary details all errors analyzed throughout the recording. After the report appears, click USB 2.0 Errors or USB 3.2 Errors to view the respective errors.
-
Select Error Summary under Report in the Menu Bar.
OR
-
Click
USB 2.0 Errors
The figure below shows the USB 2.0 errors.
The following table lists each USB 2.0 error and its description.
|
Error Type |
Error Description |
|
Bad PID |
The Packet ID is malformed. Either it is not a USB 2.0 Specifica- tion defined value, or the upper nibble is not equal to the inverted bit value of the lower nibble. |
|
Bad CRC5 |
The CRC5 field has an incorrect value. The packet is corrupt (either the data or the CRC itself). |
|
Bad CRC16 |
The CRC16 field has an incorrect value. The packet is corrupt (either the data or the CRC itself). |
|
Bad Packet Length |
The packet is shorter or longer than expected. |
|
Bad Stuff Bits |
The NRZI encoding has a problem. |
|
Bad EOP |
The End of Packet signaling does not conform to the USB 2.0 Specification. |
|
Babble Start |
The packet started too late in the Frame or Microframe. |
|
Babble End (LOA) |
The packet ended to late in the Frame or Microframe. |
|
Bad Frame Length |
The Frame or Microframe time was out of spec. (expected ~1 ms or ~125 Sec) |
|
Bad Turnaround/Timeout |
The device or host took too long to respond to a packet within a transaction. |
|
Bad Data Toggle |
Unexpected Data Toggle value; incorrect according to the USB 2.0 Specification. |
|
Bad Frame/uFrame Number |
Frame number not sequential, or not exactly 8 repetitions of a frame number in a High Speed frame sequence. |
|
Analyzer Internal Error |
Teledyne LeCroy hardware capture problem (not a USB error). |
|
Last Byte Incomplete |
The packet length in bytes was not modulo 8. |
|
Bad OTG Signal Value |
The OTG signal was not within USB 2.0 OTG Specification. |
|
TP Non-Zero Reserved Field |
A reserved value within a Transaction Packet has a non-zero value. |
|
PTP Tra No Command |
No command seen in this PTP Transfer. |
|
PTP Tra No Response |
No response seen in this PTP Transfer. |
|
PTP Tra Id Misordered |
The Transfer ID's appear to be in the wrong order. |
|
PTP Tra No Operation code |
The operation code is missing in this PTP transfer. |
|
SCSI Op No Command |
The Command is missing from this SCSI Operation. |
|
SCSI Op No Data |
The Data is missing from this SCSI Operation. |
|
SCSI Op status |
Invalid Status is found for this SCSI Operation. |
|
SCSI Op Invalid OpCode |
The SCSI OpCode is not supported by the current standards. |
USB 3.2 Errors
The following table lists each USB 3.2 error and its description.
|
Error Type |
Error Description |
|
Bad CRC5 |
The CRC5 field has an incorrect value. The packet is corrupt (either the data or the CRC itself). |
|
Bad CRC16 |
The CRC16 field has an incorrect value. The packet is corrupt (either the data or the CRC itself). |
|
Bad CRC32 |
The CRC32 field has an incorrect value. The Packet is corrupt (either the data or the CRC itself). |
|
Running Disparity (RD) Error |
The symbol captured has an incorrect number of “1” bits than expected by following the 10-bit symbol encoding rules. |
|
10-bit Symbol Error (Inv Sym) |
An illegal/undefined 10-bit symbol pattern was detected. Not all combinations of 10-bits are legal in this 8B/10B scheme. |
|
Unknown Packet |
The type of the packet declared in the header is not supported in the USB 3.2 Specification. |
|
Framing Symbol Error |
The sequence of framing symbols found is not supported by the USB 3.2 Specification. |
|
Link Command Data Symbol Error |
A data field in the link command has an incorrect symbol value. |
|
Bad Header Packet Length |
Header Packet has a length other than 16 bytes. |
|
Bad Data Length Field |
The Data Packet Header has a wrong value in the Data Length field. |
|
TP non-zero Reserved Field |
A reserved value within a Transaction Packet has a non-zero value. |
|
SKP Symbol error |
An error was detected in the Skip Sequence. |
|
Ctrl Endp Dir Error |
The bit indicating the direction of this control stage is inconsis- tent with the USB 3.2 Specification. |
|
Missed DPH Error |
The expected Data Packet Header was not captured as expected. |
|
Missed DPP Error |
The Data Packet Payload was not seen after the Data Header Packet as required by the USB 3.2 Specification. |
|
Setup DP Error |
The format of the Setup DPH is incorrect (Seq # !=0, Datalength != 8, etc.). |
|
Sequence Number Error |
The DP or TP Sequence Number is not in the order expected according to the USB 3.2 Specification. |
|
PTP Tra No Command |
No command seen in this PTP Transfer. |
|
PTP Tra No Response |
No response seen in this PTP Transfer. |
|
PTP Tra Id Misordered |
The Transfer IDs appear to be in the wrong order. |
|
PTP Tra No Operation code |
The operation code is missing in this PTP transfer. |
|
SCSI Op No Command |
The Command is missing from this SCSI Operation. |
|
SCSI Op No Data |
The Data is missing from this SCSI Operation. |
|
SCSI Op status |
Invalid Status is found for this SCSI Operation. |
|
SCSI Op Invalid OpCode |
The SCSI OpCode is not supported by the current standards. |
USB4 Sideband Errors
The figure below shows USB4 Sideband errors traffic.
The following table lists each USB4 Sideband error type and its description.
|
Error Type |
Error Description |
|
Incomplete packet |
Packet appears to have terminated before reaching its prescribed length |
|
Invalid CLSE |
In SBU LT packet: CLSE is not a complement of LSE field |
|
CRC error |
CRC Calculated does not match the one captured |
|
Reserved field not zeroed |
Non-zero value found in a Reserved field |
|
Unexpected DLE symbol |
In SBU LT packet: LT packet is started, but mistakenly interrupted by DLE symbol |
|
Invalid Command len |
Command length is not a valid value |
|
DLE symbol not duplicated |
DLE symbol inside SBU AT or RT packet's payload is not duplicated |
|
EXT symbol missing |
ETX (End Of Transaction) symbol is missing in SBU AT/RT packet |
|
LEN field error |
Actual length of SBU AT/RT packet doesn't match LEN field |
|
Incorrect data size |
In SBU AT/RT packets: Cmd Data Len is bigger than maximum; Cmd Data Len of Write packet is not 1; Cmd Data Len of Request packet is not 0 |
|
Undefined data size |
In SBU AT/RT packets: actual Cmd Data Len doesn't match expected one |
|
Invalid LSESymbol |
In SBU LT packets: unspecified value of LSE field |
USB4 Rx/Tx Errors
The figure below shows USB4 Rx/Tx errors traffic.
The following table lists and describes the USB4 Rx/Tx errors.
|
Error Type |
Error Description |
|
Incomplete packet |
Packet is incomplete (interrupted, didn't come in complete form) |
|
Unknown packet content |
Packet type cannot be detected |
|
Error packet content |
OS packet type is detected, but content has errors |
|
TS lane number error |
In TS1 and TS2: LaneNumber field is not 0 or 1 |
|
LBT (Lane bonding target) field value does not match LBT2 |
In TS1 and TS2: LaneBondingTarget2 doesn't match LaneBond- ingTarget |
|
HEC Error |
HEC Calculated does not match the one captured. |
|
CRC Error |
CRC Calculated does not match the one captured. |
|
ECC Error |
ECC Calculated does not match the one captured. |
|
Data size is invalid |
Invalid Length in TLP Header for specific Control packet types |
|
Adapter Num is invalid |
Adapter number is not within the allowable range |
|
Notification Event code Warning |
Invalid EventCode in Notification Control Packet |
|
Notification PG Warning |
Invalid value of PG field of Notification Control Packet |
|
Interdomain CM is invalid |
CM is not 0 in InterDomain Packets |
|
Invalid gap between HS packets |
More than one TLP Header within Gen2/Gen3 symbol |
|
Length and size values don’t match |
Lengths in TLP Header and Control Packets Data don't match |
|
Payload length is invalid |
Actual TLP Packet length doesn't match what’s expected (from TLP Header) |