Forum Discussion
Altera_Forum
Honored Contributor
13 years agoconstraining push button input using TimeQuest
Dear All, have a push-button input to one of the pins in the FPGA. This passes through 2 flip-flops to get into FPGA clock domain. How can I specify this correctly in the TimeQuest? I do not wa...
Altera_Forum
Honored Contributor
13 years agoYes. I would do:
set_clock_groups -asynchronous -group { clk_A clk_B clk_C} -group { clk_D clk_E} -group { clk_F clk_G} This assignment can have as many groups as you want and as many clocks in each group, but basically cuts timing between the clocks in one group from all the clocks in another group. So in the simple case of two clocks it's just: set_clock_groups -asynchronous -group {clk_A} -group {clk_B} The syntax I have above, using \ to spread across multiple lines, makes the syntax more readable with many clocks and long clock names. Note that the simple one is the same as: set_false_path -from [get_clocks {clk_A}] -to [get_clocks {clk_B}] set_false_path -from [get_clocks {clk_B}] -to [get_clocks {clk_A}] But it's done in one line instead of two. But as the number of clocks increases, set_clock_groups becomes significantly more compact and readable than a ton of set_false_paths. I talk about this in the TimeQuest User Guide on alterawiki.com.