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 a master layout and with various levels of heirarchy. My aim is to find and draw boxes around shapes belonging to a particular layer.
The problem comes in when I come across an instance which is a pcell while I am traversing through the hierarchy.
If I try to openthe instance using dbOpenCellViewByType(), it obviously opens with the default parameters and the purpose is lost.
I intend to do some processing on pcell layout with the instantiated parameters "without flatenning" the layout.
If you have the instance id while traversing the hierarchy, then you can access the pcell submaster using:
Any shapes you find in this master will need to be transformed to the current level of hierarchy. If shpId is the id of a shape in the master, you can do this:
ll = dbTransformPoint(car(shpId~>bBox) inst~>transform)ur = dbTransformPoint(cadr(shpId~>bBox) inst~>transform)newBox = list(ll ur)ornewBox = mapcar('(lambda (x) dbTransformPoint(x inst~>transform)) shpId~>bBox)
You can not open the pcell, add the new shape and then to save it.
You have to create a new inst eventaually withthe parameters changed.
E.g. the code bellow will create a new pcell of tipe libname/cellname/layout on the x:y coordinates, no rotation withparamaters W and L
masterId = dbOpenCellViewByType("libname" "cellName" "layout"); isntId = dbCreateParamInst( cv() masterId "my_inst_name" list(x y) "R0" list( list("W" "float" 0.5) list("L" "float" 0.6)))
Have a look on dbCreateParamInst()
Eventually you can try dbCreateParamInstByMasterName("libname" "cellName" "layout" ...)
Do you intend that the new shape be put at the top level of the hierarchy?
Pcell instances create a virtual memory master that reflects the results of the execution of the pcell code based on the parameter values. For each set of parameter values, there is one instance master (instHeader). An instHeader may point to multiple masters.
You should not modify the VM instance master of the pcell. It can corrupt the VM master as well as the cached master.
Like Derek said, you would have to find the shape in the master and then draw a shape at the top level for each instance using that instance's transform. (I would use dbTransformBBox but I'm lazy)
For shapes nested in deeper levels of hierarchy, you would need to find the instance path and concat the transforms. See dbGetTrueOverlaps and dbConcatTransform for more information on this.
In reply to theopaone:
Thanks for all the repliesinst~>master is what i was looking for....obviously some transformations has to be done before puting a rect around BBox of a shape
Will figure it out using your replies earlier.
Thanks for all the pointers