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 am new to cadence and I tried to sweep a mosfet w/L ratio under a dc sweep. ( for every w/l , a gate bias dc analysis is run from 0 to Vdd).
However I tried to define my variable as "param" to indicate the number of fingers so that I could change the total width but couldt get the result.
Can anyone help me with this ?
I am using vurtuoso schematic to design and vurtuoso analog design environment to simumlate.
This may depend on your design kit. Some design kits over-use CDF callbacks, which prevent you being able to parameterize certain parameters. See The Dangers of CDF Callbacks (written by me) on sourcelink.
In reply to Andrew Beckett:
thanks for your reply.
However I couldn't view your documents as I don't have access to sourcelink. ( couldn't register)
Can you send me a copy of that ?
for my design, I just put parameter in the number of fingers box when editting the instance property. Not sure if it's allowed.
And I am using ibm 130nm CMSF8SF. I don't know how to use the callback you mentioned. Can you kindly tell me ?
In reply to whlinfei:
To be honest, the solution is not going to help you very much anyway, because it's more about describing how to create a PDK which doesn't use callbacks, or uses them in such a way to not have this problem.
I don't have access to the PDK you're using, so I can't offer that much advice. When you enter a parameter name in the parameter field, do you get any errors in the CIW? CDF callbacks are defined in the CDF for each field for the component in question (you should be able to see them in Tools->CDF->Edit CDF and pick the component you're using), and are often used to derive one parameter from another. So for example, if you enter width and or fingers, and it auto-calculates total width, then that is done by a CDF callback. The question is often which parameters actually get netlisted - this is controlled by the simulation information section.
The PDK User Guide (assuming there is one) may describe what is and isn't supported, so it's worth reading that. Essentially you can probably figure it out by entering parameters in various fields, checking for errors in the CIW, and seeing what gets netlisted.
Are you sweeping number of fingers (i.e. Width of single finger) for a fixed W (i.e. Width of all fingers)? I don't think you can do that in IBM8RF unless you edit the CDF parameters as Andrew mentioned. There are many parameters in the model defined by "Width of all fingers" and "Length" in the instance properties. If you're with MOSIS ask them if theres a way to do this. email@example.com or http://tech.groups.yahoo.com/group/MOSIS_Users_Group/. Also in the CDSLIB users guide there is a section on CDF parameters, you might want to take a look at that.