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.
The only documentation on this I have found is from Cadence Design Framework II SKILL Functions Reference (skdref.pdf) on page 698:
Attribute Set? Type Description
valueType no string The type of the value of this property: “boolean” Boolean “fileName” file name string “float” Floating-point integer “hierProp” Property list “ILExpr” IL expression string “ILList” IL list “int” Integer “NLPExpr” NLP expression string “string” String “time” Time-valued string
I want to be able to force the display name or prompt of pcell parameters by editing the pcell's base cdf:
cdfCreateParam(cdfCreateBaseCellCDF(ddGetObj(libName cellName)) ?name "myParam" ?prompt "My Param's Prompt" ?defValue car(layerList) ?type "ILList" ?storeDefault "yes")
However I keep getting this error when loading the pcell:
*Error* icGetCurrentWindow: invalid cdf parameter type - "ILList"
I've tried ilList and ILList as the parameter type. Why isn't this working?
BTW, what does CDF stand for? Cadence Design Framework, Cell Database Function, etc?
Edit: Found out what CDF stands for... Component Description Format.
Also, I am trying to change the value of parameters on the instance of a pcell... anyone know how to do that?I would need to know the object of the parent which instances the pcell.
I think CDF stands for "Component Description Format".
You have a legitimate question that we have been asking Cadence for years. The short answer is that CDFs do not support "lists" even though Skill is a "list-based" language. You will have to convert your value to a string and complain to Cadence to finally fix this painful limitation on CDFs.
Derek is correct on multiple counts - CDF is an acronym for Component Description Format.
Unfortunately PCells do not support the use of a list CDF parameter type.
See my solution on supported CDF parameter typesfor PCells on Sourcelink: SourceLink Solution 11130422
I found a CCR (well, a PCR) request for this dating back to 1996!
The solution is, as Derek mentioned, to convert the list to a string and back again inside the PCell.
I'm presuming that you wish to know the parent from within the PCell code? In the past when I wanted to know the cell that instantiated a PCell I used a parameter on the PCell that stored the parent cellview's name. It's ugly, but a cell does not normally know where it is instantiated, and things are more complex for PCells, so I gave up searching for a more elegant solution (if one even exists).
In reply to skillUser:
Since the virtual memory database only stores a single copy of the variant master during an editing session and that master is determined by the value of the parameters on the instance, passing the master dbId as a parameter value is the only way to guarantee the correct information going into the pcell. You can pick up the current cellView in the editor using SKILL but the first time the pcell is instantiated, that value for the cellView is fixed and does not change even if you instantiate the pcell with the same parameter values in another cell. This may create bad data for anything dependent on the top level cell. Also, processing outside the editor (such as generating Stream format) may cause such a pcell to fail. So, if you need the master of your pcell instance, you need to pass that value in as a parameter.