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 assuming you the layout is flat data or shapes, not instances or pcells
This might get you some info to start.
load the script
Select your shapes then excute the script.
procedure(printPts()let( (type (cnt 0) (objList geGetSelSet()))foreach(obj objList ++cnt type = obj~>objType case(type ("inst" printf("%s %L at %L\n" type obj~>xy)) ("rect" printf("%s on layer %L at %L\n" type obj~>lpp obj~>bBox)) ("polygon" printf("%s on layer %L at %L\n" type obj~>lpp obj~>points)) ("path" printf("%s on layer %L at %L\n" type obj~>lpp obj~>points)) ("pathSeg" printf("%s on layer %L at %L\n" type obj~>lpp list(obj~>beginPt obj~>endPt))) ("label" printf("%s on layer %L at %L\n" type obj~>lpp obj~>xy)) (t printf("%s not defined\n" type)) ))printf("%n objects selected\n" cnt)); end of let); end of printPts
You can find more about the objects from selecting an object/s then executing in the ciw the command geGetSelSet()~>? this will output the variables to the object or geGetSelSet()~>?? will output the variables and values.
In reply to psill:
I want to get the code for finding the coordinates of a Layer which is inside a Pcell ?
And it is not flattened .
In reply to Binoy CK:
If you have the instance id of the instance, you can access all the shapes by doing:
or on each layer purpose pair by doing:
M1=car(exists(lpp instId~>master~>lpps lpp~>layerName=="Metal1" && lpp~>purpose=="drawing"))M1~>shapes
of course, having got the shapes, you can find out the ~>bBox of each or whatever you want. The "coordinates of a layer" is a bit vague, so it's not obvious what you want to do with them.
You might need to use dbTransformPoint or dbTransformBBox of points or bounding box with instId~>transform as the second argument if you want the coordinates referred to the cellView the pcell is instantiated in, otherwise they are relative to the origin of the pcell.