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

Timequest: -clock is not an object ID

Altera_Forum
Honored Contributor II
3,878 Views

In my sdc file I have a set_input delay command as  

 

set_input_delay -add_delay -clock { dctu_i|a_uniphy_i|a_uniphy_inst|pll0|pll_afi_clk } -min -0.01 [get_ports { my_signal}] 

 

I keep getting the following warning from this line 

 

ignored set_input_delay at myfile.sdc(116): argument -clock is not an object id 

 

If I do a report clocks, I can see the clock name 

 

dctu_i|a_uniphy_i|a_uniphy_inst|pll0|pll_afi_clk 

 

Anyone got any ideas why I am getting this warning? 

 

Your help is very much appreciated 

 

C
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
2,756 Views

Run report_clocks and see if it shows up there. I usually copy from that report to make sure I get the name correct. The other possibility is that the set_input_delay is created before that clock gets generated, so the name is correct but the order isn't.

0 Kudos
Altera_Forum
Honored Contributor II
2,756 Views

Rysc, 

 

Thanks for your reply. It is the latter that is the problem. My .sdc script order had magically changed around in the quartus settings. As I use the read sdc macro command from the left hand side of the timequest quest GUI, I think it uses the order in the Quartus settings. Problem solved now. Thanks Rysc 

 

C
0 Kudos
Reply