- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the Classic Timing Analyzer,these is a constrain named "Maximum Clock Arrival Skew",but it is not supported in the Quartus II TimeQuest Timing Analyzer,how to i do to constrain the clock skew in the Timequest?
THX!Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SDC command for clock skew is
set_clock_uncertainty <your_uncertainty> <clock>
I might have the syntax wrong, but that's the name of the command. You can add this to the sdc file that timequest generates, then next time you open timequest and it reads the file it will load the setting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- The SDC command for clock skew is
set_clock_uncertainty <your_uncertainty> <clock>
I might have the syntax wrong, but that's the name of the command. You can add this to the sdc file that timequest generates, then next time you open timequest and it reads the file it will load the setting. --- Quote End --- i will try it,thank a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
While some causes of clock skew can add to clock uncertainty, set_clock_uncertainty is not a command to constrain clock skew. The on-line help page for the command does mention skew, but what the command actually does is tell TimeQuest how far the clock edge can move away from the ideal position (for example, a clock edge moving around because of jitter).

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page