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.
Here is my problem:
I would like to create the hspiceD (or spectre, doesn't really matter) netlist for a circuit, let us call it depth0. This circuit has a subblock, i0, which is an instance of cell depth1. Inside depth1, there is a resistor and a capacitor. In addition, depth1 has a parameter called myParam (defaults to 1) that I would like to pass to the netlist. In other words, I would like to create a netlist like this:
.subckt depth1 in out* INPUT: in * OUTPUT: out * ----------------------------*.PININFO in:I *.PININFO out:O * ----------------------------r0 in out 1e3c0 out 0 1e-12.ends depth1.subckt depth0 in0 out0* INPUT: in0 * OUTPUT: out0 * ----------------------------*.PININFO in0:I *.PININFO out0:O * ----------------------------xi0 in0 out0 depth1 myParam=1
To achieve this, I have edited the CDF parameters of depth1 (Scope:Cell, Layer:Base). I added a parameter called myParam, type:String, Default Value:1, Parse as CEL:yes, Parse as Number:yes, Store Default:yes. When I build the dept0 schematic and add the depth1 symbol, I can see the myParam parameter in the symbol view. In the Simulation Information of the CDF parameters window, in hspiceD simulator, I added myParam in instParameters section.
When I netlist, I do get the netlist above without the myParam value. In other words, the bold line above in the actual netlist is this:
xi0 in0 out0 depth1
If in the stop view list, I put schematic, then I do get the bold line as I want, (i.e. xi0 in0 out0 depth1 myParam=1), but then the netlister does not descend into i0, and the netlist file does not include the depth1 subckt at all.
Is there a way to keep both the parameter value and the subckt information in the netlist?
You need something in the schematic to actually use the parameter - e.g. set the resistor value to 1e3*pPar("myParam") - and then it should get netlisted.
In reply to Andrew Beckett:
I am having the same issue with spectre. If I use the parameter inside the lower level schematic, parameter shows up in the netlist. However, I want this netlist to include the defined parameter even if I don't use itin the lower level schematic. Is there a workaround? Is there a dummy block I can add to include these in the netlist?
In reply to gintel:
As I said, the workaround is to use the parameter. You can always set something like: