• 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. CTS and dontTouch Nets/instances

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 3881
  • 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

CTS and dontTouch Nets/instances

Rajesh Vembu
Rajesh Vembu over 15 years ago

 I have a couple of questions on how CTS handles dontTouch nets/instances.

1. Assume there are pre-inserted buffers/inverters in the clock path without a FIXED attribute. However the nets belonging to them have a dontTouch attribute set.

"deleteClockTree -all"  deletes the existing buffers/inverters in the clock path if there's no FIXED attribute on them, thereby overriding the dontTouch on the nets. Is this the right behavior? 

a. Does deleteClockTree honor only the dontTouch attribute on the instance and not the nets ?

b. is there a way to instruct the deleteClockTree command to honor dontTouchNets?

2.  Will Clock Tree be synthesized if there are "DontTouch Nets" in the clock path?

If not, how to fix transition/delay violations on those nets?

 

 

  • Cancel
Parents
  • Kari
    Kari over 15 years ago

     If you want pre-existing buffers/inverters to not be deleted by deleteClockTree, then they must be marked FIXED.

    I had accidentally put a set_dont_touch on my clock net and CTS would not build a tree, so you probably need to remove the set_dont_touch on your clock nets.

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

     If you want pre-existing buffers/inverters to not be deleted by deleteClockTree, then they must be marked FIXED.

    I had accidentally put a set_dont_touch on my clock net and CTS would not build a tree, so you probably need to remove the set_dont_touch on your clock nets.

    • 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