Teledyne LeCroy Conquest User Manual - Users Manual User Manual

Page 221

Appendix A

211

Notes on Protocol Extraction Section

•

If the stages have a clearly defined limitations in sizes, it is preferred to mention
these sizes using the MCS, MDS, MSS keywords. This assists the decoder in
detecting these stages correctly.

•

It is valid to assign the same EndpointId to more than one stage. For example, both
Data and Status stage.

•

If the protocol does not obey the USB “Short Packet” or “Zero Length” packet
mechanisms to identify the end of a transfer block, the protocol transfer may not be
detected correctly. Please refer to sections 5.5.3, 5.7.3, and 5.8.3 of the
USB Specification for more details about these mechanisms.

•

If Data or Status stages are independent from Command stages, they must be
separate protocols. For example, Hub Class (carries hub class requests) and
Hub Class Notification (indicates change on any of hub ports) are separate

pre-defined protocols. This rule often applies to any device with an Interface that
includes an Interrupt endpoint. You must make this distinction when creating a
protocol decode.