• 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. Fixing max transition violation

Stats

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

Fixing max transition violation

mwhite
mwhite over 14 years ago

 Hello,

 We get  max transition violations after RC extraction analysis.  They don't show up during P&R optimizations.  All of the violation nets are high buffer nets but not clocks.  One is a reset and the others are not clock or reset.  The violating nets don't necessarily have the highest fanout.

I read in the Forum that it may not be the best to insert high buffer trees on these nets.  What will be the best way to fix this?

Thanks!

  • Cancel
Parents
  • Kari
    Kari over 14 years ago

     For high-fanout nets like resets, etc. I would definitely recommend building a buffer tree. You can use bufferTreeSynthesis, or add them in to your .ctstch file and have it done along with the clocks. For non-high-fanout transition violations that only show up after extraction (you didn't say if this was signoff extraction vs native), it could be a scale factor issue. Or, you could have some congested areas in the design. During opt, when added buffers are not yet legally placed, the timing is fine - but after a refinePlace, the cell has to be moved far away, resulting in a transition violation. Visually check the net and see if you can tell what's happening.

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

     For high-fanout nets like resets, etc. I would definitely recommend building a buffer tree. You can use bufferTreeSynthesis, or add them in to your .ctstch file and have it done along with the clocks. For non-high-fanout transition violations that only show up after extraction (you didn't say if this was signoff extraction vs native), it could be a scale factor issue. Or, you could have some congested areas in the design. During opt, when added buffers are not yet legally placed, the timing is fine - but after a refinePlace, the cell has to be moved far away, resulting in a transition violation. Visually check the net and see if you can tell what's happening.

    • 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