Call to set_clock_groups fails for Stratix 10 Build

Question

When my SDC file is read while compiling for a Stratix 10 device, the set_clock_groups command is failing.  The failure occurs because at the point in time that the SDC file is read, the tool does not know about derived clocks.  My SDC file has the derive_pll_clocks included, but I get a statement "The derive_pll_clocks command is not supported in this family".  So apparently I should not have to call this command.  But the clocks that are referenced in my set_clock_groups command are not valid at the time the SDC file is read.  However, they are valid later.  For instance, if I go into TimeQuest I get the same failure initially with the set_clock_groups.  If I run report_clocks the clock names that I used are valid.  If I re-read the SDC file within TimeQuest the set_clock_groups command does not fail.  So it appears that set_clock_groups has to occur after some later step in the SDC read process.

altera_forum · Answer

--- Quote Start ---

When my SDC file is read while compiling for a Stratix 10 device, the set_clock_groups command is failing. The failure occurs because at the point in time that the SDC file is read, the tool does not know about derived clocks. My SDC file has the derive_pll_clocks included, but I get a statement "The derive_pll_clocks command is not supported in this family". So apparently I should not have to call this command. But the clocks that are referenced in my set_clock_groups command are not valid at the time the SDC file is read. However, they are valid later. For instance, if I go into TimeQuest I get the same failure initially with the set_clock_groups. If I run report_clocks the clock names that I used are valid. If I re-read the SDC file within TimeQuest the set_clock_groups command does not fail. So it appears that set_clock_groups has to occur after some later step in the SDC read process.

--- Quote End ---

what stops you from directly setting clk group to the pll outputs (without using derive pll clocks). You can find the path name from node finder in timequest.

altera_forum · Answer

S10 clocks are constrained with the IP, so when you create a PLL or transceiver IP, it usually has an accompanying .sdc with it that constrains the clocks.  You just want to make sure your .sdc is read in after this.  If you go to Assignments -&gt; Settings -&gt; TimeQuest, push your .sdc to the bottom(or do it in Assignments -&gt; Settings -&gt; Files).  After doing this, close TQ and re-open it(so it sees the changes) and see if that fixes it, before running a full compile.

altera_forum · Answer

--- Quote Start ---

what stops you from directly setting clk group to the pll outputs (without using derive pll clocks). You can find the path name from node finder in timequest.

--- Quote End ---

Nothing. But I would prefer to use the derived names. But If all else fails, that is what I'll do.

altera_forum · Answer

As I mentioned the IP should be constraining the clocks and I recommend getting that to work rather than trying to do it on your own.

altera_forum · Answer

--- Quote Start ---

As I mentioned the IP should be constraining the clocks and I recommend getting that to work rather than trying to do it on your own.

--- Quote End ---

I was responding to the other post. I had to re-run because I regenerated one of my IP. I re-arranged the files, so I'm trying what you suggested. I should know shortly if changing the order helped with this issue.

Thanks,

Forum Discussion

Call to set_clock_groups fails for Stratix 10 Build

7 Replies

Recent Discussions

Fitter stalls on "Advanced Physical Optimization" on Windows 10

NIOS V Sysnthesis Fails with Quartus 25.1 Lite

Known issues in Quartus Standard 18.0

Minimum pulse width violation on EMIF-HPS

CDC violations from DCFIFO