• 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. power estimation by RTL-Compiler

Stats

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

power estimation by RTL-Compiler

naderi
naderi over 16 years ago

Hello all,

In RTL-Compiler, I used "report power" command after synthesis, and got following report. Could someone please tell me what activity factor and clock frequency are considered by RC to generate that report?

my target clock period was 500ps and timing analysis shows a negetive slack time of -450ps.

Thanks,

Ali 

 ============================================================
  Generated by:           Encounter(r) RTL Compiler v06.20-s027_1
  Generated on:           Nov 21 2008  01:45:55 PM
  Module:                 decoder648
  Technology libraries:   IO90GPHVT_2V5_3V3_50A_7M2T
                          IO90GPHVT_2V5_50A_7M2T
                          IO90GPHVT_3V3_50A_7M2T
                          IO90GPHVT_ANA_50A_7M2T
                          IO90GPHVT_BASIC_50A_7M2T
                          IO90GPHVT_FILLERCUT_50A_7M2T
                          IO90GPHVT_REF_COMPENSATION_2V5_50A
                          IO90GPHVT_REF_COMPENSATION_3V3_50A
                          PR90M7
                          CORE90GPSVT
                          CORX90GPSVT
                          CLOCK90GPSVT
  Operating conditions:   wc_0.90V_125C (balanced_tree)
  Wireload mode:          top
============================================================

                             Leakage       Internal         Net         Switching   
     Instance       Cells   Power(nW)      Power(nW)     Power(nW)      Power(nW)   
------------------------------------------------------------------------------------
decoder648         480027 567216066.450 1140456537.747 407240261.752 1547696799.500

 

  • Cancel
Parents
  • naderi
    naderi over 16 years ago

     Thanks,

    if the default toggle rate is 0.02 (1/ns), then is it changed by only setting clock period? or toggle rate should be set by setting its attribute?

    I have a clock period of 500ps and default probability is 0.5 and I didn't tuch toggle rate attribute. In this case can I say that the power is reported for toggle rate of 1/250 ps == 4G, although timing shows a neg. slack time of -450?

    Thanks,

    Ali 

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

     Thanks,

    if the default toggle rate is 0.02 (1/ns), then is it changed by only setting clock period? or toggle rate should be set by setting its attribute?

    I have a clock period of 500ps and default probability is 0.5 and I didn't tuch toggle rate attribute. In this case can I say that the power is reported for toggle rate of 1/250 ps == 4G, although timing shows a neg. slack time of -450?

    Thanks,

    Ali 

    • 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