Table of Contents
Advertisement
6
Setting Up Triggers
Possible Reasons for an Errored Packet not Appearing in the Protocol Viewer After the Trigger on Error Occurred
In case of an Idle Symbol error or a Block Header error, the trigger occurs on encountering the error
but you may not be able to see the errored data because of the reasons listed in the table below.
Reasons
The errored packet occurred during Logical Idle and you have not enabled Logical Idles storage in the Trigger
setup.
Even after enabling the Logical Idle storage, the errored packet may not get captured/displayed because:
•
•
•
70
The U4301 Analyzer can store upto 10000 logical idle bytes. The errored packet may have occurred after
the Analyzer reached this limit resulting in this packet not getting stored.
The error event may have occurred within one of the packets that is already being shown. If the error event
occurred outside a packet, then you can view the error data in the Lane view of the Protocol Viewer.
The error event occurred between two packets and therefore cannot be shown.
Keysight U4301 PCIe Gen3 Analyzer User's Guide
Advertisement
Table of Contents
