• 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. Low power design - Power estimations Genus - Toggle rates...

Stats

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

Low power design - Power estimations Genus - Toggle rates and static probability

yenass
yenass over 6 years ago

Hello,

I have a problem when I used the lp_computed toggle rates and static probability, when I built an 8 bit register like 8 DFF flip flops with an asserted clock frequency of 100MHZ (toggle rates=0.2 and static probability=0.5), and the problem that I did not understand when the data inputs are with inputs asserted_toggle_rates that exceed 0.1 (more than f/2), and I got at the output of the flip flops toggle rates as the inputs, for example if 0.15 asserted toggle rates, I got 0.15 for the output, classically the flip flop should suppress the effect of glitch (cases where toggle_rates > 0.1 in our case).

Noting that, by definition: toggle rates of a clock signal is = 2*(1/T) , where T is the period in ns and 2 means 2 toggles within T (source: cadence RTL-Compiler reference guide), for a data signal at the input of a flip flop, a signal with activity factor of 1 like a clock signal toggles 2 times within 2*T so the toggle rates maximum without glitch is equal to 2/2*T=0.1 for this purpose any value of 0.1 toggle rates represent a data signal that toggles each T, so for this purpose numbers greater than 0.1 and less than 0.2 should be suppressed by a flip flop by theory, but is not the case with the tools and simulations. Note that also, putting values greater than 0.2 at the input of a flip flops gave a maximum of 0.2 at the outputs.

Thanks to help to understand why the tools gave this results.

Regards,

Yenass.

  • 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