• 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. Logic Design
  3. Does clock power included in Power Report ?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 62
  • Views 15139
  • 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

Does clock power included in Power Report ?

dkhan
dkhan over 12 years ago

Hi All,

I am conserned whether my power reports include clock power or I have to calculate it separately. Currently I am defining clock period using "define_clock" command before loading my Netlist and then using "report power" command, however when RC loads the VCD file it shows 0.0% activity for clock while asserted signals are at 100%.   

  • Cancel
  • grasshopper
    grasshopper over 12 years ago

     Hi dkhan,

    unfortunately the answer is "It depends" If you are using a netlist and also annotating all parasitics, you will effectively have the clock tree accounted for but if you do not annotate parasitics or working at RTL level, the answer is mostly not. The reason I say mostly is that the CGICs are still traced downstream and on the enable side hence it is hard to really say that there is none of the clock tree accounted for but the key parts or at least some significant parts are not. RC provides the option '-clock_tree' to the command 'report power' for the purpose of estimating a clock tree that has not been inserted yet. It will look something like this

     

    rc:/> set_attr lp_clock_tree_buffers CLKINVX8 /designs/* 
      Setting attribute of design 'emac_plus': 'lp_clock_tree_buffers' = /libraries/slow/libcells/CLKINVX8
    rc:/> set_attr lp_clock_tree_leaf_max_fanout 10 /designs/*
      Setting attribute of design 'emac_plus': 'lp_clock_tree_leaf_max_fanout' = 10
    rc:/> report power -clock_tree -width 200 -heigh 300     
    . . .
    Clock Power Estimation Summary for clock 'clk'
    ==============================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max              13.428    9299298.048    9299311.476

    Leaf Clock Buffers                    70
    Total Clock Buffers                   92

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um
    Clock Power Estimation Summary for clock 'rx_clk'
    =================================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max              13.516    3666707.676    3666721.192

    Leaf Clock Buffers                    64
    Total Clock Buffers                   92

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um

    Clock Power Estimation Summary for clock 'tx_clk'
    =================================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max               7.946    2882486.746    2882494.692

    Leaf Clock Buffers                    32
    Total Clock Buffers                   54

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um

    Info    : Time taken to report power. [RPT-7]
            : 5.00 cpu seconds
     

     hope this helps,

    gh-

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

     

    grasshopper said:

     Hi dkhan,

    unfortunately the answer is "It depends" If you are using a netlist and also annotating all parasitics, you will effectively have the clock tree accounted for but if you do not annotate parasitics or working at RTL level, the answer is mostly not. The reason I say mostly is that the CGICs are still traced downstream and on the enable side hence it is hard to really say that there is none of the clock tree accounted for but the key parts or at least some significant parts are not. RC provides the option '-clock_tree' to the command 'report power' for the purpose of estimating a clock tree that has not been inserted yet. It will look something like this

     

    rc:/> set_attr lp_clock_tree_buffers CLKINVX8 /designs/* 
      Setting attribute of design 'emac_plus': 'lp_clock_tree_buffers' = /libraries/slow/libcells/CLKINVX8
    rc:/> set_attr lp_clock_tree_leaf_max_fanout 10 /designs/*
      Setting attribute of design 'emac_plus': 'lp_clock_tree_leaf_max_fanout' = 10
    rc:/> report power -clock_tree -width 200 -heigh 300     
    . . .
    Clock Power Estimation Summary for clock 'clk'
    ==============================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max              13.428    9299298.048    9299311.476

    Leaf Clock Buffers                    70
    Total Clock Buffers                   92

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um
    Clock Power Estimation Summary for clock 'rx_clk'
    =================================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max              13.516    3666707.676    3666721.192

    Leaf Clock Buffers                    64
    Total Clock Buffers                   92

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um

    Clock Power Estimation Summary for clock 'tx_clk'
    =================================================

    ------------------------------------------------------
    Estimate   Leakage (nW)   Dynamic (nW)   Total (nW)  
    ------------------------------------------------------
    Max               7.946    2882486.746    2882494.692

    Leaf Clock Buffers                    32
    Total Clock Buffers                   54

    Estimation Parameters
    =====================

    Clock Buffers Used: CLKINVX8

    Max flops driven by one leaf buffer: 10
    Die width: 200.0 um
    Die height: 300.0 um

    Info    : Time taken to report power. [RPT-7]
            : 5.00 cpu seconds
     

     hope this helps,

    gh-

     


    Thanks gh,

    I am using Netlist and define_clock command, when I run "report power", rc shows following info which says there is no activity in clock nets eventhough the simulation runs fine and I have included all nets when generation VCD/SAIF files in Modelsim.  You said clock_tree command is used to estimate clock nets that are not inserted yet, so are they not included in synthesized netlist? What do you mean by parasitics?, other constraints besides clock period?

     

    Nets/ports asserted in SAIF file : 2881
    Total Nets/ports in SAIF file    : 163806
    -------------------------------------------------------
    Asserted Primary inputs in design              : 1930 (100.00%)
    Total connected primary inputs in design       : 1930 (100.00%)
    -------------------------------------------------------
    Asserted sequential outputs                    : 0 (0.00%)
    Total connected sequential outputs             : 5000 (100.00%)
    -------------------------------------------------------
    Total nets in design                 : 62449 (100.00%)
    Nets asserted                        : 10584 (16.95%)
    Clock nets                           : 0 (0.00%)
    Constant nets                        : 47 (0.08%)
    Nets with no assertions              : 51865 (83.05%)
    -------------------------------------------------------

     

    • 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