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.
My current pmos pcell came with a fix NW around it, but due to our design need, we need to have an extra large NW from OD outward.
Therefore, I've use leLayerSize as following and hope that it will work.
leLayerSize(cv list("OD" "drawing") 1.5 list("NW" "drawing"))
But, as the result, leLayerSize command didn't recoganize pmos and return me a nil.
As I tried to change the "display level" to 2 and wonder if leLayerSizer will work. Still, it didn't work.
But, as I tried to cover the pmos device with OD over to whatever it came with it then set the leLayerSize command again.
This time it works and I saw the extra NW layer over it as I want to.
From this, I realized that leLayerSize didn't work on pcell. Is there any way around it?
By the way, I'm using 5.10.41 version.
You cannot use le prefix functions in a PCell (or sch, ge etc. for that matter - check the documentation for a full list of what you can use). However, you have at least a couple of ways to achieve this functionality: use the dbLayerSize() function, or use the ?size and ?fromObj arguments to a command such as rodCreateRect().
[ x_numVertices ]
If using the rod approach and the original shape was not created as a rod object, then you can use the rodNameShape() command to make a db object into a rod object. Again, check the documentation for more details, but I believe that the above should answer your questions.
In reply to skillUser:
I've tried dbLayerSize command as suggested, but I guess I didn't understand how to get m1Rect as listed example.
m3out = dbLayerSize(cv "metal3" m1Rect 0.5)
But, I tried dbCreateRect command as mentioned for another way around it.
dbCreateRect(cv list("OD" "drawing") list(9.08:2.28 9.75:3.28))
dbCreateRect created an OD layer over a line of pmos'.
Then I used leLayerSize(cv list("OD" "drawing") 1.5 list("NW" "drawing")) command. Yes, it created an extra large NW layer outward base on OD layer as I wanted.
Here come another question:
How am I going to find out (which command) the lower and upper coord of OD layer in a pcell?
I've zoomed in and find out the far left lower corner coord of OD and far right upper corner coord of the OD in order to make dbCreateRect command work for me.
In reply to kpai:
If you want to size shapes within the pcell instance, then neither dbLayerSize nor leLayerSize are going to help. They both only work on "level 0" shapes - i.e. shapes in the cellView you're editing, rather than shapes one level down (inside the pcell).
If using IC613/4 and with access to VLS GXL, you could rteGeomSize() to do this, but otherwise you'd need to do something like:
; assume that cv is the cellView you're editing, and inst is the id of the pcell instancemaster=inst~>master; find the LPP object within the pcell instanceOD=car(exists(lpp master~>lpps lpp~>layerName=="OD" && lpp~>purpose=="drawing"))ODshapes=foreach(mapcar shape OD~>shapes dbCopyFig(shape cv inst~>transform))dbLayerSize(cv "NW" ODshapes 1.5); remove the temporary copy of OD shapes into the cellViewforeach(shape ODshapes dbDeleteObject(shape))
Note this is completely untested and off the top of my head. So there may be errors in the code. Caveat Emptor.
In reply to Andrew Beckett:
Please correct me if I'm wrong here. I've test it out, but all I got are (db:xxxxx), no NW layer has been add.
Here is what I have:
OD=car(exists(lpp cv->lpps lpp->layerName=="OD" && lpp->purpose=="drawing"))
ODshapes=foreach(mapcar shape OD->shapes dbCopyFig(shape cv inst->transform))
dbLayerSize(cv "NW" ODshapes 1.5)
foreach(shape ODshapes dbDeleteObject(shape))
In this particular cellview, I've two pmos pcell instant in there.
I think it would be wise to go on a SKILL course - you've managed to significantly change my suggestion so that it wouldn't work...
Various things you've done wrong:
If you want to process all the instances, you could do:
cv=geGetEditCellView()foreach(inst cv~>instances master=inst~>master ; find the LPP object
within the pcell instance OD=car(exists(lpp master~>lpps
lpp~>layerName=="OD" && lpp~>purpose=="drawing")) ODshapes=foreach(mapcar
shape OD~>shapes dbCopyFig(shape cv inst~>transform) ) dbLayerSize(cv
"NW" ODshapes 1.5) ; remove the temporary copy of OD shapes into the
cellView foreach(shape ODshapes dbDeleteObject(shape))) ; foreach inst
Again, thank you very much Andrew.
It works perfectly this time.
I didn't intent to change the script; it's just at first time when I tried master=inst->master and it came back nil. I was just trying to figure out how to get the master to work out.
Anyway, it works for me.