Forum Discussion
adrianf0
New Contributor
7 years agoI tried the following state-based trigger:
state ST1:
if (start_acq)
goto ST2;
state ST2:
begin
if( stop_acq && store )
begin
start_store;
stop_store;
trigger 0;
end
else if (stop_acq)
begin
trigger 0;
end
else if (store)
begin
start_store;
stop_store;
end
endHowever, it doesn't work as expected:
- although I expected only a single acquisition window, SignalTap returns many (segments). One could still filter out only a single acquisition window, however, when waveform is dumped to a .csv files (for further analysis) the information about segments is lost
- even with post-fill-count argument of the trigger call set to 0, SignalTap waits for at least one valid sample. It means that if the sample doesn't occur, SignalTap will wait forever
EDIT: If I use `trigger 1`, it actually seems to work as intended. The only inconvenience is it needs to wait for an extra sample from the next acquisition window.