TimeQuest timing relationship for unrelated clocks

Dave,

Thank you for the suggestion. I have given it a try using the manual approach. It looks like this would work if I was using false path constraints that specified clocks instead of registers as the from & to arguments of the command. However, when I run the "Report Clock Transfers," there is a footnote at the bottom that says:

"Entries labeled "false path" only account for clock-to-clock false paths and not path-based false paths. As a result, actual path counts may be lower than reported."

In other words, it ignores my register-to-register false paths.

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.

Thanks everybody for the help.

Martin