• 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. help ! about CTS insertion delay

Stats

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

help ! about CTS insertion delay

icmaple
icmaple over 15 years ago

in my case, there is a clkgen module, which has many divider-clock generator. i specify AutoCTSRootPin at chip port, and when i do cts, encounter total insert about 10 ns delay upto Sinks , but Only in clkgen module ,there is 7ns delay .( 70% occupied)  

what reason can cause the issue?  thanks 

  • Cancel
Parents
  • BobD
    BobD over 15 years ago

    That could indeed limit CTS's ability to size instances that pre-exist in the clock network efficiently in order to reduce insertion delay.

    You might want to try a run where you relieve all of the dont_touch markings in instances in the design (or at least under that module) even if that goes beyond what you're actually allowed to do in terms of manipulating the clock network.  Additionally, you might want to check to make sure that the library cells that these pre-instantiated gates reference don't have dont_use/dont_touch markings.  They often do (to stop data path optimization for inadvertently swapping into these cells) so it's an additional item that can impact CTS.  If you do these 2 experiments you could get a feel for whether they are what's causing your insertion delay to be so large.

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

    That could indeed limit CTS's ability to size instances that pre-exist in the clock network efficiently in order to reduce insertion delay.

    You might want to try a run where you relieve all of the dont_touch markings in instances in the design (or at least under that module) even if that goes beyond what you're actually allowed to do in terms of manipulating the clock network.  Additionally, you might want to check to make sure that the library cells that these pre-instantiated gates reference don't have dont_use/dont_touch markings.  They often do (to stop data path optimization for inadvertently swapping into these cells) so it's an additional item that can impact CTS.  If you do these 2 experiments you could get a feel for whether they are what's causing your insertion delay to be so large.

    • 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