User's Manual

224
Chapter 5: Reference
Error Messages
The analyzer has a maximum limit of 16 event list combiner resources.
Each unique event list expression requires the use of at least one of
these combiner resources. A complex event list may require more than
one combiner resource.
The message does not mean that any single event list expression was
too complex to combine (see “Branch expression is too complex” on
page 212), but that the overall number of unique branch expressions
specified has exceeded the limit of 16.
In order to compile and run, the total number of unique event list
expressions must be reduced to 16, and the complexity of some of the
expressions may have to also be reduced.
Branch expressions that are identical (and simple enough to be
combined by a single combiner resource) share the same combiner
resource. Reusing identical event list equations where possible will
optimize the use of combiner resources (see page 224).
You may find more information in the “Branch expression is too
complex” on page 212 error message help for the 800 and 1250/1500
Mb/s modes.
Combiner resource allocation guidelines:
• Labels that span multiple pod pairs (split labels) increases the number of
required combiner resources as compared with labels that are entirely
contained within a single pod pair.
Whenever possible try to arrange the probing such that labels do not span
pod pairs. This is the single most effective way to reduce the number of
required combiner resources.
NOTE: For labels that do span pod pairs, the complexity can be reduced to the same
as that of the non-split label case if all bits in the label on all but one pod pair
can be set to Xs in the event list expression for the measurement.
For example, if label ADDR has its 16 most significant bits on pod A3 and
16 least significant bits on pod A2 (spanning pod pairs A4/A3 and A2/A1),
the complexity of the compiled expression will be reduced if all 16 most
significant bits or all 16 least significant bits are set to Xs in the pattern
event.