Honored ContributorAm I the only one that get lots of compilation warning froms SignalTap II modules? I think it started since I upgraded from Quartus 7.1 to 7.2. Among the warnings are critical ones, one for each monitored signal, that power-up levels are ignored. They all seem to be harmless, but it is quite annoying.
Honored ContributorThe critical warnings are mostly harmless, unless you're using the Power-up trigger feature. The issue is fixed in Quartus II v.7.2SP1 and later.
Honored ContributorThanks. Yes, they seem to be harmless. Are you sure this is fixed in 7.2 SP1? I can't find any mention about the issue on the release notes.
Btw, even power-up triggers seem to work fine (but I didn't test them too much). The only feature that doesn't work for me is chaining two instances using trigger-in/trigger-out link (no idea if this is related to the warnings, probably not).Honored ContributorI'm fairly sure about this one. I saw the same errors in 7.2. The errors were gone with 7.2 SP1. Power up trigger is probably not reliable if the critical warnings appear.
What kind of problems are you having with the trigger-in trigger out?Honored ContributorThanks. I'll install the latest SP shortly.
Regarding trigger-in/trigger-out. I'm chaining two Singal Tap instances. And it simply doesn't work at all. The master instance (the one using trigger out) triggers, but the "slave" instance (the one using trigger in) never triggers. Just in case I tried all possible trigger level combinations. I also tried using additional trigger conditions, and also with trigger-in alone. No matter what I do, the "slave" instance never triggers (unless I disable trigger-in, in which case it works without problems).Honored ContributorI'm seeing the same thing with 7.2. I am, though, having success chaining the instances using 7.2 SP1. It's maybe helpful to upgrade at this point just for the fixes.
Hope this helps, FQHonored ContributorInstalled SP2 and the warnings went away :) I will try chaining instances later.
Thanks once again.Honored Contributorcool. I'm glad it worked out for you.
A slight clarification to what I meant earlier when I said "The critical warnings are mostly harmless". I just want to make sure I don't downplay Critical Warnings, as its easy to get burned when you don't read them carefully. I meant the statement to specifically apply to the power-up trigger warnings that you were seeing. If you see other critical warnings, please pay attention to them. In particular, for SignalTap II, if you have a failed connection between your design and and signalTap II, the compiler will not generate a compile error; the compiler will report it as a critical warning. I've seen a few people miss the critical warning and run SignalTap with confusing results. Cheers, FQHonored ContributorI know you were talking specifically about those warnings. Yeah, critical warnings should not be ignored. That's precisely why this Signal Tap bug was so nasty.
Once you get used to see and "ignore" (spurious) critical warnings, as I had to here, then you could easily miss real ones.
