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 creating a custom pcell, through the graphical layout method. The custom pcell layout contains an instance of a pdk pcell. I have inherited a parameter 'width' among others from the pdk pcell to my custom pcell. In my custom pcell, I need to repeat contacts based on the value of width. But, it is not possible to use parameter 'width' in repetition expressions. The software gets confused, and assigns 'width' as a new parameter.
Do you know how to reference the inherited 'width' parameter in my custom pcell, without confusing the software? Any responses are appreciated.
Well, it works for me - so I assume you must be doing something wrong. Have you set up the instance of the pdk pcell to have an inherited parameter using Pcell->Inherited Parameters? I just did that, and assigned my instance to inherit from a parameter called "width" and then also used width in my repetition expression - and also used Parameters->Edit to set the default value of width.
From what you describe you're expecting the parent pcell to inherit from the child instance, which doesn't make sense - how would the child pcell know what values to use?
If this doesn't help, I think you're going to have to post some pictures and a more detailed explanation, or contact customer support.
In reply to Andrew Beckett:
I posted the screenshots of the PCell creation on Flickr. You can see them here:
As for your question:
"From what you describe you're expecting the parent pcell to inherit from
the child instance, which doesn't make sense - how would the child
pcell know what values to use?"
It seems the Cadence software passes the value assigned to width to the inherited PCell. I was able to verify that when using this hierarchical PCell, the width changes to the avlue assigned to each instance. It's when using the parameter width for repetition that the PCell breaks down.
In reply to msharma:
From looking at your pictures, it's failing because when the instantiation of the child pcell is happening, it is expecting a string, not a float - although the error message appears to say that it's expecting 2e-12 (not sure why that is). I see that the length is being passed as a string - so I'd have expected the width to be the same type.
So my guess (without seeing the actual data) is that you should change the type of width to be a string, and then make your stepping distance in the repetitions equal to cdfParseFloatString(width)/2 .
If this doesn't help - I'd suggest going via customer support - this kind of thing is much easier if we can see the actual data. As a colleague of mine used to say - "a picture is worth a thousand words, but a database is worth a million"