• 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. Controlling logic names of CTS inserted buffers.

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 90
  • Views 15752
  • 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

Controlling logic names of CTS inserted buffers.

archive
archive over 18 years ago

Hello,
I was wondering if there is a way to tailor the instance names of buffers inserted by CTS?  Specifically, what I am trying to do is control where in the logic hierarchy the clock buffers are placed.  I would like any buffers inserted by Encounter to be logically placed inside a specific module in the hierarchy.  This allows for easier import back into the Cadence DFII world after Encounter place and route step.

Anyone had any sucess with this?


Originally posted in cdnusers.org by nph
  • Cancel
Parents
  • archive
    archive over 18 years ago

    The error message you're seeing ("Cannot create a partition without any constraint") is trying to tell us that in order to define a hierarchical module as a partition, you must first define a *placement* constraint for the module within the design. A placement constraint is a guide, region, or fence- in the case of a partition it should be a fence. You can use "createFence" to do this, or via the GUI by dragging the pink module guide from the left of the design into the core area and then calling "definePartition" (or Partition->Specify Partition... via the GUI).

    One other thing comes to mind based on your additional problem description (thanks for that- it's very helpful) is that you might want to try defining your AutoCTSRootPin on the output of an instance within the digital block instead of on the output of a top-level IO. If there is not an instance within the digital block that makes this approach possible, you could add a new buffer for this purpose (using Encounter ECO commands). If you do this, it's possible that the buffers would reside within the partition without any additional effort on your part.

    Feel free to post back for more clarification if you'd like.

    Thanks,
    Bob



    Originally posted in cdnusers.org by BobD
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    The error message you're seeing ("Cannot create a partition without any constraint") is trying to tell us that in order to define a hierarchical module as a partition, you must first define a *placement* constraint for the module within the design. A placement constraint is a guide, region, or fence- in the case of a partition it should be a fence. You can use "createFence" to do this, or via the GUI by dragging the pink module guide from the left of the design into the core area and then calling "definePartition" (or Partition->Specify Partition... via the GUI).

    One other thing comes to mind based on your additional problem description (thanks for that- it's very helpful) is that you might want to try defining your AutoCTSRootPin on the output of an instance within the digital block instead of on the output of a top-level IO. If there is not an instance within the digital block that makes this approach possible, you could add a new buffer for this purpose (using Encounter ECO commands). If you do this, it's possible that the buffers would reside within the partition without any additional effort on your part.

    Feel free to post back for more clarification if you'd like.

    Thanks,
    Bob



    Originally posted in cdnusers.org by BobD
    • 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