• 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. Max tran violations

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 19792
  • 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

Max tran violations

diablo
diablo over 16 years ago

Pls suggest on improving max tran violations in SocEncounterafter after routing. After postCTS, there are no violations on setup, hold, max_tran, max_fanout. However, after post route, I can see around 100 of max_tran violations but there is still no setup and hold violations. After iteratively running  optDesign -postRoute -drv, i still get those violations. I was wondering why the tool is not using buffers to fix it. 

  • Cancel
Parents
  • frankz
    frankz over 16 years ago

     Pay attention to the mark behind the transition violations in the report.

    The one marked as dont_touch_net and clock_net will be ignored by the opt enginee.

     You need to double check with your logical design engineer .

    Some non clock tree instance will be marked as clock tree so that the transition violation wont be fixed.

    I usually manually fix this kind of transition violation. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • frankz
    frankz over 16 years ago

     Pay attention to the mark behind the transition violations in the report.

    The one marked as dont_touch_net and clock_net will be ignored by the opt enginee.

     You need to double check with your logical design engineer .

    Some non clock tree instance will be marked as clock tree so that the transition violation wont be fixed.

    I usually manually fix this kind of transition violation. 

    • 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