• 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. Digital Implementation
  3. clkgate setup timing violation is not treated by optDes...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13477
  • 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

clkgate setup timing violation is not treated by optDesign

greenblat
greenblat over 14 years ago
Perhaps someone can help here: encounter place and route problem. when i run optDesign in setup mode and -postRoute, i get 0.6ns violation on clkgating check. optDesign doesnt fix it. it looks like during optdesign run, this violation is overlooked (because i see the WNS in the middle of the log file slightly misses the timing at -0.1ns, which i know and not related to clkgating). However in final part of the log file, when optDesign wraps things up, the big violation appears again. what can i do? is there an option to force optDesign to treat clkgating violations? i looked over setOptMode and there is only option for pre-ClockTree consideration. setting it in -postRoute mode has no effect. thanks, Ilia
  • Cancel
Parents
  • Tongju
    Tongju over 14 years ago

    Also, it was possible that there are even larger violated paths (larger than 0.6ns) in the same design and the tool tried to put more attention to them and have to sacrifice this one (let it to have -0.6ns) for big gains in other paths. If this is the case, try "setOptMode -criticalRange 0.99" to change the way the tool to handle the small violations, you may be able to see different result.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Tongju
    Tongju over 14 years ago

    Also, it was possible that there are even larger violated paths (larger than 0.6ns) in the same design and the tool tried to put more attention to them and have to sacrifice this one (let it to have -0.6ns) for big gains in other paths. If this is the case, try "setOptMode -criticalRange 0.99" to change the way the tool to handle the small violations, you may be able to see different result.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

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

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