Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16611 Discussions

Timequest difference between 11.1sp1 and 13.1

Altera_Forum
Honored Contributor II
1,020 Views

Have an SDC file with this constraint for some data output signals: 

 

set Clock100p0MHz PLL:inst28|……..auto_generated|wire_pll1_clk[3] 

set_output_delay -add_delay -max 1.0 -clock $Clock100p0MHz [get_ports SomeSignals*] 

 

With 11p1sp1, Timequest sees the set_output_delay as a valid command, but in 13.1 and 15.1, TimeQuest throws an error saying that there is no such clock “Clock100p0MHz” 

 

is there a different way now to constrain IO pins?
0 Kudos
1 Reply
Altera_Forum
Honored Contributor II
257 Views

 

--- Quote Start ---  

Have an SDC file with this constraint for some data output signals: 

 

set Clock100p0MHz PLL:inst28|……..auto_generated|wire_pll1_clk[3] 

set_output_delay -add_delay -max 1.0 -clock $Clock100p0MHz [get_ports SomeSignals*] 

 

With 11p1sp1, Timequest sees the set_output_delay as a valid command, but in 13.1 and 15.1, TimeQuest throws an error saying that there is no such clock “Clock100p0MHz” 

 

is there a different way now to constrain IO pins? 

--- Quote End ---  

 

 

 

Maybe recompilation changed "auto_generated|wire_pll1_clk[3]" signal name?
0 Kudos
Reply