Forum Discussion
generated clocks or derived clocks "... without an associated clock assignment"
- 5 years ago
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
We do not receive any response from you to the previous reply that we have provided. Please post a response in the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you with your follow-up questions.
- JanSch5 years ago
New Contributor
Hello Kenny, I had already marked my problem as solved (-> there was a button)? The solution for a warning (332060) is ( contrary to the recommendation of "sstrell") to insert a "create_generated_clock" command into the SDC file. The correct syntax can be generated with the "Timing Analyzer". I took your post of February 10 as an additional, final comment. Should I better have added a comment like: "Yes, I also copy-pasted the command from the command generator", in response to your comment? If I have unknowingly broken etiquette here, I apologize! I find a platform like this very useful and do not want to appear impolite at all. I think we can close this thread. Jan