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 developed a skill based pcell for a particluar device. One of the parameters for the pcell is a string which is the name of a cell in the library I am working. It works fine, but when I try copy these pcells into a diferent library I do not see these cells copied since cadence thinks they are just properties. The limitation I have with the code is I need to pass the names of the cells as parameters . When I do this I exprerience these problems. I would really appreciate if someone could tell me if there is a way around.
I don't entirely understand your problem. My guess is that when you're doing a hierarchical copy, it's not copying the child instances instantiated within the cellView. Is that it? If so, I don't think there's anything you can do except copy them manually yourself. The problem is that they are not referenced in the superMaster cellView for the pcell, and hence the copy engine won't see them (I expect; I didn't try this).
In reply to Andrew Beckett:
Yes, thats correct. I was actually copying them manually. But how do I make sure that they are referenced in the superMaster cellview? Does it happen by default?
In reply to fun4skilled:
The only way this could conceivably work (and I haven't tested this) is if the default parameters for the pcell mentioned the names of the components included underneath. That way the superMaster would reference the components because your pcell code would have evaluated to create them.
But that's unlikely to be useful, because presumably each instance could reference different components underneath.
For efficiency reasons the hierarchical copy (and various other hierarchical operations) use the parent-child data in each cellView to determine the children to copy. The alternative would be to do a full load of the cellView and elaboration of each pcell instance, to collect the children that way. That's not done (as it would be much more expensive), but the down side is that it will miss cases where you have instances of cells in pcells where the cellName of the instantiated device is controlled via a pcell parameter.
If you really want that, you'd have to contact customer support for an enhancement request to provide this (as an option). However, I'd say it's a pretty unusual case and a fairly major change to the way the copy is done, so there's not an enormous chance of it being implemented (unless there have been other customers asking for the same thing; I didn't check).