• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. What's the advantage for declaration different clock domain...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 63
  • Views 6992
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What's the advantage for declaration different clock domain in Genus

NickK
NickK over 5 years ago

Hello,

Recently I find that in Genus is supporting function of declaration different clocking domains. Instead using clock groups and than add them as asynchronous, domains seems to ignore all cross-domain relations as well as skipping timing analysis path between them.

So what's the pure advantage of declaration of clock domains? I can set falsepath between clocking groups as well. And any kind of Cadences OTPG we don't use so all features are unable for us.

Also it's pretty strange to find using any kind clock domain settings most in Legacy IU (which I believe become too old for using).

  • Cancel
  • Dimo M
    Dimo M over 4 years ago

    Hi Nick,
    the command "create_clock -domain" is Genus' way of disabling the timing paths using the tool's native command, whereas "set_clock_groups -asynchronous" is an SDC construct.
    There is no advantage, both of the methods are working in Genus to disable the timing paths.

    The existence of both methods has historical reasons, but the current recommendation is to use the SDC format


    Related articles:
    Comparing Genus command “create_clock -domain” and SDC command “set_clock_groups -asynchronous”
    Why does input SDC constraints differ from write_sdc output ?

    Dimo

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information