• 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. Static power analysis with SOC

Stats

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

Static power analysis with SOC

DavidBD
DavidBD over 16 years ago

 Hello,

I would like to generate power report using the following corner :

- RC = CWORST

- PVT =  BC

The inputs are :

- Netlist

- DEF

- SDC

 I would like to generate static report ( no activity file) ( using SOC 8.1 )

 

 

  • Cancel
  • DavidBD
    DavidBD over 16 years ago

    ...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     Hi David,

    I assume you mean a power consumption report (command reportPower). If you are using MMMC, then you should have a view set up with BC .libs and rc_corner of CWORST. Then you can just set that as the active view and run reportPower with the options of your choosing. If you're not using MMMC, then the design should be loaded with the BC .libs and you should have run an RC extraction with a CWORST QRC tech file or FE captable. I'm not sure if this completely answers your question.

     - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidBD
    DavidBD over 16 years ago

     Hi Kari,

    Thanks for the reply.

    Which Cadence tools is the most appropritated to generate this report ?

    David.

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidBD
    DavidBD over 16 years ago

    Hi Kari,

    Please take a look at this Encounter power report script :

     

    =============================================

    loadConfig design.conf
    defIn design.def

    # use Min lib + BCCOM OPC for power corner
    setTimingLibrary -max Min -min Min

    # use CWORST RC corner
    defineRCCorner -late {worst} 125 -early {worst} 125
    setExtractRCMode -engine detail

    extractRC

    reportPower -outfile power.rep -sort { total }

    ======================================

     

    config file :

    ======================================

    global rda_Input
    set rda_Input(ui_netlist) "design.v"
    set rda_Input(ui_topcell) { top }

    # LEF Files
    set rda_Input(ui_leffile) "tcbn45gsbwp_7lm4X2ZRDL.lef"

    # WORST LIB
    set rda_Input(ui_timelib,max) "tcbn45gsbwpwc.lib"

    set rda_Input(ui_timelib,min) "tcbn45gsbwpbc.lib"

    set rda_Input(ui_timingcon_file) "design.sdc"

    set rda_Input(ui_captbl_file) " \
    -typical cln45gs_1p07m+alrdl_typical_top2.captable \
    -best cln45gs_1p07m+alrdl_cbest_top2.captable \
    -worst cln45gs_1p07m+alrdl_cworst_top2.captable"

    ======================================

    Can you please review this code and let me know if it is OK.

    David.

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     David,

    The command reportPower is used inside SoC-Encounter. You could also run the tool powermeter. In fact, reportPower runs powermeter "under the hood". Running powermeter standalone involves more setup on your part, but also more flexibility if you have a complicated design. 

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     I think your script looks ok - you are missing the pwr/gnd info from the .conf file though. You may want to add some lines like the following:

    set rda_Input(ui_pwrnet) {VDD}
    set rda_Input(ui_gndnet) {SS}
    set rda_Input(PIN:VDD:) {VDD}
    set rda_Input(PIN:VSS:) {VSS}
    set rda_Input(TIEHI::) {VDD}
    set rda_Input(TIELO::) {VSS}
     

    • 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