Forum Discussion
Altera_Forum
Honored Contributor
13 years agoTimeQuest tries to analyze everything, and with the tightest relationships it can find. This is the safest approach since it doesn't know how the design actually works. If you design something that can be asynchronous, then you add a set_false_path to tell TimeQuest that. If you design something that can occur over several clock cycles, then a set_multicycle_path is applied to tell TimeQuest that. These are called exceptions, and are the way to tell TQ how your design works, at least from a timing analysis perspective. So it is acceptable, and not really a work-around but the recommended flow.