Protocol errors, Protocol errors detected while capturing data – Teledyne LeCroy Conquest User Manual - Users Manual User Manual
Page 114

Protocol Analysis
104
Protocol Errors
Conquest monitors and captures a variety of real time protocol errors every
time that a data capture is made. The Conquest Protocol Suite software also
detects post-process protocol errors.
Protocol Errors Detected While Capturing Data
Err0
Bit Stuff (packet corrupted, stuff bit not present)
Err1
PID Err (packet identifier check failure)
Err2
PID Unknown (packet with undefined PID)
Err3
Sync Error
Err4
CRC5 Error (IN, OUT, SETUP packet error)
Err5
CRC16 Error (DATA0, DATA1, DATA2, MDATA payload error)
Err6
Frame Len (the space between SOF is not per USB specification)
Err7
Babble (Bus not idle at end of frame error)
Err8
Data Toggle (detected incorrect data packet toggle bit)
Err9
EOP Error (incorrect width of EOP signal or incorrect EOP occurrence)
Err10 Loss Activity (packet transfer interrupted by constant state on bus)
Err11 Time Out (distance between token or data packet and corresponding
response greater than USB specified)
Err12 Bus Error indicating that both D+ and D- signals were set to one (SE1).
This error can be detected only in Full or Low speed mode.
Err13 Short Inter Pkt Delay
Err14 Truncated Transaction. This error occurs if an expected packet is not
received at all. When capturing isochronous transactions, disable this
protocol error.