TimeQuest command precedence for clock group

Question

Hi Forum.

In my system I got several clock domains and it is quite handy to set clock groups instead of false commands on thousands of paths. However it is not clear what happens to those ip fifo automatically generated sdc commands for crossing clock domains such as max delay or max skew. If they are then ignored then set clock groups is misleading and useless in my system.

Any thoughts especially from Timequest gurus. Thanks in advance.

altera_forum · Answer

If possible try to avoid clock group constraint applied to the clock that used by any IP, you wouldn't know it may cut those crucial paths without any explicit warning, like dcfifo in your example. It's better to verify each of path and false-path it through wildcard *

altera_forum · Answer

Yeah, you can't use set_clock_groups if some of the cross-domain paths require analysis while others don't.

Forum Discussion

TimeQuest command precedence for clock group

2 Replies

Recent Discussions

Timing analysis - long combinational path

QuartusPro 25.3 Crashed after using the Signal Tap Logic Analyzer

Duplicate_hierarchy_depth / duplicate_register

Automatically added negative node for TDS output doesn't work with Agilex 5

Quartus 20.1std compilation fails for Quartus map - Device 10AS057K2F40I1SG