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 have used the pPar("my_parameter") approach to define parameters in subcircuits I wanted to instantiate on a higher level.
One simple example would be a parallel RLC whose element values are calculated by using Q factor, resonance freq, impedance level.
I have done this type of things with elements from the analogLib several times, so I guess that the procedure is correct.
I have tried lately to parametrize a cell with transistors from the PDK we use for our chips, and I am encountering a very fuzzy behavior. I start from scratch and add first one passive element - a MOM capacitor - and define all parameters to be inherited as pPar(..), like metal spacing, width, number of vertical fingers etc...
After editing the CDF, I can simulate, no problem.
Then, I add an NMOS, various parameters, edit CDF, simulate. Again, no problem.
A PMOS, same story, simulate, perfect.
Then, I add some more transistors, and use the same labels for those whose sizes must match. That is, if I define the finger width to be pPar("fw_n") for the NMOS and I have two transistors which should have equal widths, in the second transistor the finger width will again be defined as pPar("fw_n"). Well...at this point, things go wrong. The generated netlist is flawed. I get errors like:
ERROR (SFE-874): "input.scs" 46: Unexpected real number "00.0". Expected close parenthesis.
ERROR (SFE-709): "input.scs" 46: No master specified for instance `exp'
I can get any sort of this errors...expected this, expected that.
The crazy thing is that if I now delete the transistors that 'caused' the netlist to fail...The new netlist fails nevertheless!! Once this effect happens, there is no turning back. Unless I take ALL transistors out of my cell. If I dare to put back one - the same configuration I had and which worked - the netlist fails.
To my non-expert eye it looks like the transistor parameters like drain area and such, which are functions of other transistor sizes which I parametrized, are maybe written in a way that causes problems...But I cannot dig deeper than that.