Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
In RTL compiler, I have successfully used the following flow
- Read Verilog Netlist
- Read VCD Annotation Data between times t0 and t1 (Chip "Active")
- Report Power for "Active"
- Reset Design
- Read VCD Annaotation Data between times t2 and t3 (Chip "Standby")
- Report Power for "Standby"
This has worked succesfully and reported "Active" and "Standby" power is as excpected
I am now trying to improve the flow by reading the CPF file, which defines the power modes. So, now I attempting to report power for each power mode, whilst also including the VCD annotation data.
Unfortunately, this does not seem to work. As far as I can tell, the VCD annotation data is not being used in the power calculation such that the power is the same in both "Active" and "Standby".
Has anyone used this flow? Should it work?
The solution to your problem would be one of the following.
Solution #1: Annotate switching activities for each power mode in your cpf file. Check update_power_mode -activity_file command .
Solution #2: Your flow should look something like this:
//diagnostics, reports etc here
Notice that we read tcf (or vcd or saif) AFTER read_cpf . If you try to read it before, you won't get accurate results
Hope I helped,
In reply to Fotios Nt:
Thanks for the reply - I am trying your solution #2 - the only difference is that I am using a GL nelitst.
Therefore, my flow is
1) read_cpf (libraries)
3) read_vcd -start_time $start -end_time $end
4) report power # This gives expected result
5) report pwer -mode myode # Result same as if no annotation
6) report power # The VCD annotation data has been lost -> incorrect annotation data
Note that when I perform command 5, it looks like a reset_design is performed and VCD data is lost. This is confirmed by repeating the report power (without mode) where I see incorrect results.
In reply to moogydmaxim:
This is somewhat strange, could you please file a case in support.cadence.com ?
Thanks for the feedback - it's good to have confirmation that what I am trying to work should work :-)
When time permits, I will try with a later version of RC, and then I will pass the issue to our central EDA group, who will check further.