• 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. Hold violation fixing

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 16354
  • 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

Hold violation fixing

Ankit20
Ankit20 over 10 years ago

Hi,

   Can you tell me why we fix hold violations post CTS and setup violations pre CTS? In Encounter, even the option for hold violation fix in pre-CTS optimization is disabled.

  • Cancel
  • Jason Tryon
    Jason Tryon over 10 years ago
    i got some problem like this, any have ideas? thanks
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • biju4u90
    biju4u90 over 10 years ago
    I got the answer from another forum. You will get a true status of hold results only after CTS. So it is better we complete CTS and then look at hold results. Assume u have setup violations in your design. You have to resolve it by reducing Tcomb. So 2 options available to u are pipelining and say retiming. Pipelining involves logic changes where you add registers to your RTL (logic changes)
    Asume Tskew is 0 for simplicity.. If you have hold violations it means you have to push your data further ahead. You can do that by increasing TComb. The easiest way to do that is to add buffers in the data path. With this you can get incremental and precise control over the delay. If you want to do logic changes to solve this problem, what logic will you add in the data path? Any logic changes proposed will only complicate your problems. On the other hand, to fix set up violations, you have to make your data path faster. You can either upsize your cells or change your logic for this.
    • Cancel
    • Vote Up 0 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.

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

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