Filter
Top Products
175
Chapter 3: Reference
Error Messages
Specific Guidelines - 800 Mb/s State Mode
• Labels that span pods (split labels) require more combiner resources than
labels with bits that all belong to a single pod. Whenever possible, define
labels that do not span pods. In some cases, the compiler will be able to
combine 2 non-split labels that are ANDed together even though it fails to
compile a pattern on a single label that spans pods.
• Cannot specify more than 4 patterns or 2 ranges per pod.
Non-split patterns may use operations: =, !=, <, <=,>, >=, In range, Not
in range.
Split patterns may only use operations: =, !=.
Patterns on labels with re-ordered bits may only use operations: =, !=
(same as Timing and 200 and 400 Mb/s modes).
• Restrictions on the way event resources can be used and combined vary
with the type of trigger function selected.
The "Find Pattern" and "Find n Patterns in Immediate Sequence"
trigger functions can use all of the available pattern events in any
sequence level. However, some combinations (ANDing and ORing) of
pattern events, while not exceeding the maximum number of pattern
resources, can use too many combiner resources. Any combination of 3
of the flag events and "Wait for arm in from IMB" event can also be
combined with the pattern events in each sequence level.
When using the "Find n Patterns in Eventual Sequence" trigger
functions, only non-split labels may be used and only one pattern event
per sequence level may be used. The interface allows insertion of other
events in each sequence level to allow ANDing or ORing of the pattern
event with other event types (flags or arm in) or replacement of the
pattern event with another event type. However, if more than one
pattern event is specified the trigger compiler will be unable to compile
it.
• Pattern events used in the Default Storing Control count against the
number of available resources.
Specific Guidelines - 1250 Mb/s State Mode
• Labels that span pods (split labels) require more combiner resources than
labels with bits that all belong to a single pod. Whenever possible, define
labels that do not span pods. In some cases, the compiler will be able to