Signal Tap Logic Analyzer II Trigger Condition

What do you have the trigger position in the .stp file set to? If you want to see more captured data from before the trigger occurs (to the right of the trigger in the waveform view), set it to the post-trigger position.

However, none of the 3 trigger position options would only show a single value unless either your signals are not toggling around the time of the trigger or you've set the size of the buffer incorrectly (only 1 sample perhaps?).

Also, of course, your sampling clock has to toggle so data gets captured at each rising edge.

Hi,

Check this https://www.intel.com/content/www/us/en/docs/programmable/683819/22-4/continuous-mode-and-a-storage-qualifier.html

Make sure you're using non-segmented buffer in continuous mode instead of non-segmented buffer using a storage qualifier and segmented buffer. In the continuous data capture, Trig1 occurs several times in the data buffer before the Signal Tap logic analyzer trigger activates. The buffer must be full before the logic analyzer evaluates any trigger condition.

Thanks,

Best Regards,

Sheng

So what are you expecting to see?

You have stop~0 set as a trigger in (like trigger condition 0). You don't show what you have set up for your main trigger condition from the Signal Tap node list.

CLOCK_50 should not be in the node list. You already have that as the capture clock. I think perhaps you mean to put the 1Hz clock as the capture clock and have CLOCK_50 in the node list, but then the capture clock would be way too slow to capture CLOCK_50. So simply have the 1Hz clock as the capture clock and remove CLOCK_50 from the node list. With CLOCK_50 as the sampling clock, you're filling up the buffer long before there's even one cycle of the counter.

You also don't need the trigger in. Disable that.

You already have stop in the node list as your trigger. Trigger in is only used to get a trigger from another instance of the logic analyzer or from some other external signal that you're not tapping in the node list. You don't need to use it here.

OK, then keep it.

ok as you said that as i have stop signal in my node list so i dont have to used it as trigger in. What if remove it from node list and only use it as trigger in so will that stop the acquisition as soon as stop value gets to 1?

so than how does these trigger logic work?

As i have tried three different positions of sampling data and i can see that it log data before trigger and after trigger as well based on my buffer value.

So what's the problem? Left-click to zoom in.

I mean i am just trying to understand that how it is working as i cant always make sure that the program i am running will be complete in 64 samples or it will take more than that so isnt there any way to set up such a configuration which works as per my design requirements