TimeQuest timing relationship for unrelated clocks

Hi Martin,

--- Quote Start ---

It seems that I am trying to do something uncommon and that it is standard practice to just cut all paths across clock domains where signals are not expected to cross. Perhaps I should do the same.

--- Quote End ---

Its not unusual to find that you are doing something uncommon ... it happens to me all the time :)

In this case, I would typically define clock groups with the asynchronous clocks in different groups, so that TimeQuest cuts all the paths.

If a design is nicely implemented, with synchronous logic in their own blocks, and blocks connected via bridges/synchronizing logic, then I feel safe using this TimeQuest feature.

If however you're trying to constrain a design written in the "spaghetti style" of coding, with numerous clocks, then I suspect you'll have other issues than just TimeQuest constraints, and a thorough review of that design would be advised before trying to setup timing constraints.

Cheers,

Dave