• 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.

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 94
  • Views 26745
  • 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.

gops
gops over 16 years ago
How should i manage CTS efficiently. I need to know what all things should be taken care in the clock tree sppecification file for an optimized clock tree. I usually create the .ctsch file from the tool itself. I just used to give the clock buffer and clock inverter foot prints for the purpose. Will this much information create the clock tree in an efficient way? if not please give me some tips to improve my clock tree. thanks gops.
  • Cancel
Parents
  • archive
    archive over 16 years ago

     Hello Kari,

     I' m using a similar clock specification file:

    ClkGroup
          + reset_n
          + clk


    # Sample Route Type Command
    RouteTypeName        CK1
    PreferredExtraSpace    1
    TopPreferredLayer        5
    BottomPreferredLayer     4
    Shielding   VDD VSS
    End

    # Sample Gated CTS Command
     AutoCTSRootPin  clk
     Period            1ns
     MaxDelay      10ps
     MinDelay      0ps
     SinkMaxTran   5ps
     BufMaxTran    5ps
     RootInputTran 5ps    
     MaxSkew           1ps
     LevelBalanced         YES
     NoGating     rising
     MaxDepth      10
     RouteType     CK1
     DetailReport  NO
     RouteClkNet   YES
     PostOpt     YES
     OptAddBuffer  NO
     LeafPin
     + I2/CP rising
     + I0/CP rising
     + I1/CP rising

     AddDriverCell CKBXD8
     End

     

    However, when Im trying to synthesize the tree I'm getting the following error:

     **ERROR: (SOCCK-657):   No cell is specified for clock clk in the clock tree specification file.
    **ERROR: (SOCCK-427):   The clock tree specification file contains an error at line 47: End

     

    My design is a simple shift register with 3 FFs, with the clock input named 'clk'. Do you have any idea what the problem might be??

     

    Thanks,

    Alex

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 16 years ago

     Hello Kari,

     I' m using a similar clock specification file:

    ClkGroup
          + reset_n
          + clk


    # Sample Route Type Command
    RouteTypeName        CK1
    PreferredExtraSpace    1
    TopPreferredLayer        5
    BottomPreferredLayer     4
    Shielding   VDD VSS
    End

    # Sample Gated CTS Command
     AutoCTSRootPin  clk
     Period            1ns
     MaxDelay      10ps
     MinDelay      0ps
     SinkMaxTran   5ps
     BufMaxTran    5ps
     RootInputTran 5ps    
     MaxSkew           1ps
     LevelBalanced         YES
     NoGating     rising
     MaxDepth      10
     RouteType     CK1
     DetailReport  NO
     RouteClkNet   YES
     PostOpt     YES
     OptAddBuffer  NO
     LeafPin
     + I2/CP rising
     + I0/CP rising
     + I1/CP rising

     AddDriverCell CKBXD8
     End

     

    However, when Im trying to synthesize the tree I'm getting the following error:

     **ERROR: (SOCCK-657):   No cell is specified for clock clk in the clock tree specification file.
    **ERROR: (SOCCK-427):   The clock tree specification file contains an error at line 47: End

     

    My design is a simple shift register with 3 FFs, with the clock input named 'clk'. Do you have any idea what the problem might be??

     

    Thanks,

    Alex

     

     

     

    • 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