Honored ContributorSignalTap really, really, really doesn't like it when you have no trigger conditions - even when you use trigger-in from another instance. Does it ignore the trigger conditions and just use the trigger-in? Does it handle asynchronous interfaces across the trigger?
Honored ContributorTrigger in is basically trigger condition 0. It evaluates it and then proceeds to the trigger condition columns. You need to have at least one trigger condition column, but you can turn off the checkbox at the top of the trigger condition column to skip that condition. Thus, trigger in would be your only trigger condition.
SteveHonored ContributorThanks Steve,
I have had problems when I disable all triggers on the main page (w/o regard to trigger-in). That may be have been on release 13 though. Can't recall in release 16.Honored ContributorHmm. Strange. You can of course just set all the signals in a trigger condition column to don't care or turn off all the checkboxes for using your signals to define the trigger condition.
Honored ContributorThat's what I ended up doing (don't-cares) and I complies with your understanding because it doesn't trigger until the trigger-in.
