• 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. Clock Tree Synthesis Through Narrow Corridors

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 13130
  • 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

Clock Tree Synthesis Through Narrow Corridors

dfick
dfick over 12 years ago

 Hi,

 I'm running clock tree synthesis on a large memory-like array structure where there are narrow corridors between some of the rows/columns. EDI CTS is having a hard time and is creating many buffers in the middle of the design, with huge congestion. Is there anything in particular that I should be looking at for this scenario?

 Thanks

  • Cancel
  • dfick
    dfick over 12 years ago

     The working solution is to insert explicit buffers in the clock tree in the netlist. When CTS is called, it creates a subtree for each buffer that is in the tree already. By inserting a buffer for each corridor (that drives the cells in the corridor), CTS was able to run quickly with a good result.

     Full disclosure: I had a sub-module for each corridor already, and a fence for that submodule which kept its cells in that corridor. I added the clock buffer to the input of the sub-modules.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • fitz
    fitz over 12 years ago

    Obstruction's are another  <DESIGN>.ctstch  option worth trying..............

    AutoCTSRootPin ................
    Obstruction    YES
    CellObstruction
    + ST_SPHS_SLRH_16384x39m16B4_bTR0P Entire
    + ST_SPREG_LRH_4096x36m8B2_bTR Entire
    + ST_DPHS_SLRH_4096x32m8B2_T0P Entire
    + ST_ROM_R_16384x32m32B4_Tol Entire
    + ARM_hard_core Entire
    END


     Shawn

    • 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