• 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
  • chaitu1488
    chaitu1488 over 15 years ago

     

     I have many doubts and am encountering many situations in the cadence encounter,

    first of all i am getting the following error in the clock tree synthesis:

     

    **ERROR: (SOCCK-114): No valid clock tree root specified.

    actually i am using a clock for my module. What may i have done  wrong that i got this error?

     

    I have another doubt. as i dont know where to post, i am posting it here in this message itself.

    I have a module wherin i am using a ROM from the faraday's memory maker.The memory maker is giving an lef file for the rom we want.

    what order should we include the lef files for a 6 metal layer libraries?

     meaning should i include rom.lef  first in the list or last? i hope it is last because the import was done perfectly. I want to know what is the significance of the order of the lef files.

     

    also i encountered another problem because of the rom.lef file.

    i dont know the error log number, but it happens during the special route 

    it says something like this:

                                 Reading LEF technology information...

                                         *ERROR*  "../rom1/rom1.lef", line 44: SITE core not defined at or near "core"

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

     

     I have many doubts and am encountering many situations in the cadence encounter,

    first of all i am getting the following error in the clock tree synthesis:

     

    **ERROR: (SOCCK-114): No valid clock tree root specified.

    actually i am using a clock for my module. What may i have done  wrong that i got this error?

     

    I have another doubt. as i dont know where to post, i am posting it here in this message itself.

    I have a module wherin i am using a ROM from the faraday's memory maker.The memory maker is giving an lef file for the rom we want.

    what order should we include the lef files for a 6 metal layer libraries?

     meaning should i include rom.lef  first in the list or last? i hope it is last because the import was done perfectly. I want to know what is the significance of the order of the lef files.

     

    also i encountered another problem because of the rom.lef file.

    i dont know the error log number, but it happens during the special route 

    it says something like this:

                                 Reading LEF technology information...

                                         *ERROR*  "../rom1/rom1.lef", line 44: SITE core not defined at or near "core"

    • 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