Forum Discussion
New Contributorgenerated clocks or derived clocks "... without an associated clock assignment"
Thanks for the quick reply!
The .sdc file was of course already in the Project. Otherwise, I would not have seen the critical warning(332049) for my malformed “create_generated_clock“ command, right?
But I found the solution! Your mention of the "Timing Analyzer" made me re-read its manual, especially about the “create_generated_clock“ command! The command must be correctly stated for my example above:
create_generated_clock -name any_name -source [get_ports {CLOCK_50}] -divide_by 128 [get_pins {I2CCLK[6]|q}]With this, the warning (332060) disappears and also the results of the "Timing Analyzer" become more plausible!
Best regards,
Jan
Super ContributorCheck to make sure you've added your .sdc file to your project in the Timing Analyzer settings. Very common mistake of people not adding the .sdc to their project. If you have and you are still getting the warning, start the Timing Analyzer and generate the unconstrained paths report and the ignored constraints report. Your create_clock constraint looks correct (don't do the generated clock constraint you mention), so these diagnostic reports might clue you in to what's wrong.
New ContributorThanks for the quick reply!
The .sdc file was of course already in the Project. Otherwise, I would not have seen the critical warning(332049) for my malformed “create_generated_clock“ command, right?
But I found the solution! Your mention of the "Timing Analyzer" made me re-read its manual, especially about the “create_generated_clock“ command! The command must be correctly stated for my example above:
create_generated_clock -name any_name -source [get_ports {CLOCK_50}] -divide_by 128 [get_pins {I2CCLK[6]|q}]
With this, the warning (332060) disappears and also the results of the "Timing Analyzer" become more plausible!
Best regards,
Jan
