- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I've got an internally generated page signal which changes state every few thousand clocks and the timing isn't particularly important. Am I best to treat this as a false path or use some form of multicycle constrain in TimeQuest. If it's the latter please could you state which multi-cycle exception I should use as it is really confusing - I will read up in the mean time. Thanks, D.Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the timing doesn't matter at all, use a set_false_path exception.
If it's an asynchronous signal and your synchronizing logic assumes a maximum propagation delay, use set_max_delay. In my opinion, set_multicycle_path exceptions should be used only for synchronous signals for which the setup and/or hold relationship needs to be changed by a certain number of clock cycles.- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks.
set_false_path is what I need.
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