A feature that allows you to capture data at a recurring event after the trigger in the selected instance of the SignalTapII Logic Analyzer.
Acquired data is placed in a segmented buffer, with the newest samples replacing the oldest. You must select the segmented buffer size, which is the size of each segment, or the amount of data captured around each trigger condition.
A segmented buffer partitions the entire acquisition space into evenly sized segments. Each segment acts as a separate circular buffer. The difference between segmented buffering in a sequential triggering flow and in a state-based triggering flow is:
- In a sequential triggering flow, the trigger condition for the first buffer is a consecutive evaluation of all the trigger conditions. Each subsequent segment trigger is based on only the last trigger condition of the sequential flow.
- In a state-based trigger flow, the trigger condition for each segment is defined by the command <segment_trigger>, in which you define the trigger flow.
The default trigger position for each segment is defined in the Setup tab. You can customize trigger positions with the state-based trigger flow, with post-fill count arguments.