ChipScope Pro analyzer - When I use the trigger sequencer with a counter I see unexpected results

Description

When I have a trigger condition sequenced like M0 -> M1 with a counter set on M1, then I do not see the correct number of events on M1. I see less events than my counter setting. Why is this?

Solution

There is a rolling counter on the second trigger event, M1. This counter does not wait for the first trigger event, M0, to complete. Hence, when the first trigger event completes the counter may not necessarily start at zero. Some events may have already accumulated. This is the expected behavior of the core.