• 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. setup violation

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13292
  • 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

setup violation

PhilBzh
PhilBzh over 15 years ago

 Hi,

 I can't solve a problem with a lot of setup violation. Even if I run optDesign I still have the same huge number of setup violation.

In my, .sdc, I only create the clock and define its period and waveform. Is it enouth ?

I already worked on my .ctsch and it seems to be good.

Has anyone some ideas to solve this problem ? 

 

Phil 

  • Cancel
Parents
  • Kari
    Kari over 15 years ago

     Having just a clock definition in the sdc file should work, but for realistic timing analysis, you really should have more than that. At the least, I would think you'd need input/output delays and drive cell assertions. Check out the following blog series for a great tutorial on creating timing constraints:

    http://www.cadence.com/Community/blogs/di/archive/2009/02/09/constraint-construction-what-s-it-s-function-part-1-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/02/18/constraint-construction-what-s-it-s-function-part-2-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/03/06/constraint-construction-what-s-its-function-part-3-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/04/09/constraint-construction-what-s-its-function-part-4-of-4.aspx

    If you post the timing report for your worst path, I might be able to tell a few things.

    - Kari

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

     Having just a clock definition in the sdc file should work, but for realistic timing analysis, you really should have more than that. At the least, I would think you'd need input/output delays and drive cell assertions. Check out the following blog series for a great tutorial on creating timing constraints:

    http://www.cadence.com/Community/blogs/di/archive/2009/02/09/constraint-construction-what-s-it-s-function-part-1-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/02/18/constraint-construction-what-s-it-s-function-part-2-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/03/06/constraint-construction-what-s-its-function-part-3-of-4.aspx

    http://www.cadence.com/Community/blogs/di/archive/2009/04/09/constraint-construction-what-s-its-function-part-4-of-4.aspx

    If you post the timing report for your worst path, I might be able to tell a few things.

    - Kari

    • 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