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.
I want to use VCD file from QuestaSim 6.0 in RTL compiler to obtain power report. The netlist file I am using in QuestaSim for simulation and VCD file generation is also generated by RTL compiler byt when I run following commands I got no asserted signals in the power result. Does RTL compiler supports other VCD files besides from NCVHDL?
read_netlist synthesized_RISC_32.vdefine_clock -name clk_main -period 5000 [find / -port clk_main]read_vcd -module RISC_32 -static RISC_32.vcd
VCD is VCD and it does not matter what tool generates it as long as VCD it is legal. You will have to do some additional debug and figure why it is not annotating. Most common reason is testbench generating VCD scoped at the testbench level which the design obviously does not have. Other reasons are naming conventions on elaborated flops, etc.
As I said, a quick peek at why your annotation is failing will shed ample light on your issue
In reply to grasshopper:
Yes I have checked the contents of VCD file and it only contains signals from the component I am testing. However when I convert this VCD file into saif format using vcd2saif tool from Synopsys it reads correctly in RTL compiler.
In reply to dkhan:
It is great that you got it to work with vcd2saif.
However, that should not be necessary. I suspect you need to use the -vcd_scope (or -vcd_module in older releases) option to read_vcd in order to select the "scope" in the VCD that you want to apply to the top design in RC.
It is very common for a VCD to only contain signals from the design you are interested in, but also contain the full hierarchy from the testbench. For example, your VCD may look like this:
$scope module tb $end$scope module dut $end$scope module my_top_design $end$var wire 1 Tc4# clk $end$var wire 1 Eb4# reset_n $end....
In this above case, you need to specify "read_vcd -vcd_scope tb/dut/my_top_design ..." or just "read_vcd -vcd_scope my_top_design ...".