• 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. "optDesign -preCTS" doesn't seem to be optimizing

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 2210
  • 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

"optDesign -preCTS" doesn't seem to be optimizing

Brannon
Brannon over 14 years ago

I'm trying to get velocity to optimize flop placement at the preCTS stage. The worst path is failing by -504ps, but if I check report_timing on the cycle before and the cycle after the failing path then I see both of these have considerable slack. When I run to later stages it does seem to move those flops around and largely fix the path--but I can't get it to fix those paths at preCTS stage.

I've tried 'optDesign -preCTS -incr', am I on the wrong track here?

  • Cancel
  • BobD
    BobD over 14 years ago

    I usually try "optDesign -preCTS -incr" when it appears placement didn't do a good job sizing/buffering the gates along the worst path. The checking of the cycle before/after the failing path made me think you might be considering useful skew. If you haven't tried that yet you can enable it with "setOptMode -usefulSkew true" prior to optDesign -preCTS. It will attempt to schedule the arrival times of the launch/capture flops to enable timing closure. This information is then conveyed to CTS in a scheduling file.

    If that approach doesn't work well -or- you'd like to improve the placement of this launch/capture flop pair, you might want to try placeDesign -incremental after optDesign -preCTS. I think it would be more likely to move the flops closer together.

    Let us know how it goes!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Brannon
    Brannon over 14 years ago

     Thanks for the suggestion--I am indeed just trying to get it to place the flops more optimally (I haven't yet gotten to cycle stealing but that may be my next stop).

    I did an iteration of placeDesign -incremental and that helped but I looked and it still appeared it could do a better job. I did a couple more iterations and the worst path got better each time--but when I look at the worst path it still seemed that it could do much better by simply moving the flop further in one direction (I should mention that this is a wire dominated long route with multiple pipeline stages). I think this is the right track but I need to do more investigation.

    Thanks for pointing me in the right direction.

    • 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