• 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. power differences after post-syn using VCD

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 62
  • Views 14498
  • 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 differences after post-syn using VCD

leez2006
leez2006 over 12 years ago

Hi,

I want to get a quick look at the power consumption of one block.

--use RTL Compiler generate netlist(after syn) and sdf

--run gate sim with or without sdf annotated, get VCD

--use netlist and VCD in ETS, get power consumption

I found the power consumption get form VCD without sdf annotated is much greater than with sdf annotated.

This makes me confuse. I think the power with sdf annotated should be bigger. Can anyone help to explain this?

I found there is only one difference with the log (the value changes got from vcd).

without sdf annotated:

With this vcd command,  12005021 value changes and 1e-06 second
simulation time were counted for power consumption calculation.

  Filename (activity)                    :
../in/ad9651_datapath_top_gate.vcd
  Names in file that matched to design   : 234754/352833
  Annotation coverage for this file      : 54305/54305 = 100%

Activity annotation summary:
        Primary Inputs : 89/89 = 100%
          Flop outputs : 8172/8172 = 100%
  Memory/Macro outputs : 0/0 = 0%
      Tristate outputs : 0/0 = 0%
            Total Nets : 54305/54305 = 100%

with sdf annotated:

With this vcd command,  6867391 value changes and 1e-06 second
simulation time were counted for power consumption calculation.

  Filename (activity)                    :
../in/ad9651_datapath_top_gate.vcd
  Names in file that matched to design   : 234754/352833
  Annotation coverage for this file      : 54305/54305 = 100%


Activity annotation summary:
        Primary Inputs : 89/89 = 100%
          Flop outputs : 8172/8172 = 100%
  Memory/Macro outputs : 0/0 = 0%
      Tristate outputs : 0/0 = 0%
            Total Nets : 54305/54305 = 100%

  • Cancel
Parents
  • leez2006
    leez2006 over 12 years ago

    Hey, gh

     Thanks for your reply.

    What I want to compare is

    netlist(after syn) + gate_VCD(without sdf annotation) VS netlist(after syn) + gate_VCD(with sdf annotation).

    The power analysis tool is ETS for both. The sdf is generated after syn. The netlist is the same.

    In your reply you said you noticed the annotation is different yet I used the same netlist, do you mean "12005021 value changes" and "6867391 value changes "? That's what confused me. I don't know how the ETS get value changes from VCD, but I think the VCD with sdf annotation shoud have more transitions(the combitional cells would toggle more for it's inputs have different delay).

    leez

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • leez2006
    leez2006 over 12 years ago

    Hey, gh

     Thanks for your reply.

    What I want to compare is

    netlist(after syn) + gate_VCD(without sdf annotation) VS netlist(after syn) + gate_VCD(with sdf annotation).

    The power analysis tool is ETS for both. The sdf is generated after syn. The netlist is the same.

    In your reply you said you noticed the annotation is different yet I used the same netlist, do you mean "12005021 value changes" and "6867391 value changes "? That's what confused me. I don't know how the ETS get value changes from VCD, but I think the VCD with sdf annotation shoud have more transitions(the combitional cells would toggle more for it's inputs have different delay).

    leez

    • 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