• 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. hoho, Bob, 1 question again for CTS

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 91
  • Views 14038
  • 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

hoho, Bob, 1 question again for CTS

archive
archive over 17 years ago

1. How can I get all the clock nets in SOC-E. I am using the command 'dbIsNetClock', but it doesn't work. Then I try to specify clock tech file, then change all the clock nets to DEF USE CLOCK, then output DEF, reload the DEF, but 'dbIsNetClock' does not work either. I can write a DB tcl to trace the clock tree, but it is time consuming. How can I do this using FE inherent commands. My SOC-E version is 52USR3.

Thanks in advance!


Originally posted in cdnusers.org by eminemshow
  • Cancel
  • archive
    archive over 17 years ago

    Hi,

    'dbIsNetClock', uses the timing information to tell is a net is clock or not.
    You should load the SDC and update the timing before using this command.


    Originally posted in cdnusers.org by sudhir.jain
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi,

    As you read a DEF, the informations are saved on an other property. If you read you SDC and update your timing you may have problem with multimode. So teh better is to make two tests:

    Here is my script:

    proc userCreateClockList { clockFile {option w} } {
    set f [open $clockFile $option]
    dbForEachCellNet [dbgTopCell] n {
    set netname [dbNetName $n]
    if {[dbIsNetClock $n] || [dbIsNetDefInClock $n]} {
    puts $f "$netname"
    }
    }
    close $f
    }
    And so you can use:

    userCreateClockList $STM_clockNetsReport "w"

    Regards ... Luc ...


    Originally posted in cdnusers.org by Black Lutin
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thank you all! This is really the solution I need.


    Originally posted in cdnusers.org by eminemshow
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Lutin:

    I really dont not know why comands like 'dbIsNetClock' and 'dbIsNetDefInClock' doesn't work.
    I have to 1st specify clock tree, then saveClockNet, then remark the clock net as 'dbSetIsNetclock'.

    BRs


    Originally posted in cdnusers.org by eminemshow
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi,

    To access to dbIsNetDefInClock, you need to have run the clcokTreeSynthesis.
    To access to dbIsNetClock, you need to have read SDC timing constrain file, and to have run a timing command (to propagate the clock information). So you need at least "report_timing".

    Try and let me know ....

    Regards .....


    Originally posted in cdnusers.org by Black Lutin
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kiranbk
    kiranbk over 14 years ago

    HI ,

    I am looking to find out if all the flops are getting clocks in design . i wish to do this early at the floorplan stage itself  just as a design check . Is there a way to do this ?  i tried to use dbIsNEtDefInClock in a snmall script but i think it only works on a cts database.

    Kindly point me to any command if available to check clock attribute on net before cts.

    Thanks, 

    Kiran 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BobD
    BobD over 14 years ago

    Have a look at this solution, "How to list flops not getting covered by CTS":

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNu
    mber=11720306;searchHash=00e3628bafd2e513d4427dce395562ec
    • 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