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'm trying to use verilog generic on my vhdl instance via the defparam option of ncelab and I get the following message:
"Attempted propagation of defparam results to a non-Verilog instance"
The generic in my dut instance are not set and use the default value. Is that not supported?
module tb_top; parameter G_DATA_WIDTH = 8;
wire [G_DATA_WIDTH-1:0] data_in;
wire [G_DATA_WIDTH-1:0] data_out;
/* DUT */ top #(.G_DATA_WIDTH (G_DATA_WIDTH)) my_dut ( .clk (clk), .data_in (data_in), .data_out (data_out), );endmodule
Thank you for the help
NC as a tool does not allow you to propagate the new value across the language boundary. The default initial value of the parameter is taken as its value. The defparam statement tries to re-propagate the value of G_DATA_WIDTH in the VHDL instance and this warning suggests that the tool is not able to do so and retains the value of G_DATA_WIDTH to be 8 only.A VHDL generic is an elaboration time constant and we do not have a way to re-evaluate it based on a new defparam statement. To work around this, you can use the "-gpg" flag or a combination of “-defparam/-generic” options . % irun -mess ...... -generic "tb_top.my_dut.G_DATA_WIDTH => 16"Or% irun -mess ...... -gpg "tb_top.my_dut:G_DATA_WIDTH => 16"
In reply to muffi:
Thank you Muffi, it helps!
But, that sounds like a missing feature for me, is there plans to support that later? Synopsys VCS and modelsim support that for instance. If one wants to migrate from one of these tools to cadence, this would give quite a lot of work to get the elaboration up and running.
In reply to fbochud:
Defparam is going to be a deprecated feature from the new Verilog LRM perspective. See section C.4.1 - Defparam statements.From a re-usability of code perspective, defparams are not the ideal solution and should be avoided.
So using the "-gpg" or a combination of "-defparam/-generic" options should be a clean solution to avoid this warning