Chapter 5: Reference

Error Messages

Event lists with up to 4 unique pattern events can be combined in any combination of ANDs and ORs by a single combiner resource if all of the pattern labels are non-split and contained on the same pod pair.

Combining more than 4 labels on the same pod pair will require another combiner resource.

Non-split label pattern events from different pod pairs that are ORed together require an additional combiner resource for each additional pod pair included in the event list. (ANDing on non-split patterns from different pod pairs does not increase the required number of combiner resources).

An inequality compare (<,<=,>,>=) with a split label pattern event requires 2 combiner resources.

A range on a split label pattern event requires 4 combiner resources.

The event list in the custom store qualification dialog also allocates combiner resources from the same pool of 16 resources. If the store qualification event list equation is the same as one of the branch event list equations in the trigger sequence, the combiner resource will be shared. A unique store qualification event list requires the allocation of 1 (or more) of the combiner resources.

400/800/1250/1500 Mb/s state modes requires many more combiner resources to implement the same trigger sequence as compared to 200 Mb/ s state modes and all timing modes. Refer the discussion of complexity in the “Branch expression is too complex” on page 212 help topic.

Waiting for Trigger

This message indicates that the specified trigger pattern has not occurred. This may be expected, as when you are waiting to trigger on an unusual event.

Possible Causes

Misaligned boundaries for addresses

When the device under test is a microprocessor that fetches only from long-word aligned addresses, if the trigger is set to look for an opcode

225

Page 225
Image 225
Agilent Technologies 16760A manual Waiting for Trigger, Misaligned boundaries for addresses, 225