Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
Verification 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.
The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.
Participate in CDNLive
A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.
Come & Meet Us @ Events
A huge knowledge exchange platform for academia. We are looking for academic speakers to talk about their research to industry attendees.
Americas University Software Program
Join the 250+ qualified Americas member universities who have already incorporated Cadence EDA software into their classrooms and academic research projects.
EMEA University Software Program
In EMEA, Cadence works with EUROPRACTICE to ensure cost-effective availability of our extensive electronic design automation (EDA) tools for non-commercial activities.
Apply Now For Jobs
If you are a recent college graduate or a student looking for internship. Visit our exclusive job search page for interns and recent college graduate jobs.
Cadence is a Great Place to do great work
Learn more about our internship program and visit our careers page to do meaningful work and make a great impact.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
Overview All Courses Asia Pacific EMEANorth America
Instructor-led training [ILT] are live classes that are offered in our state-of-the-art classrooms at our worldwide training centers, at your site, or as a Virtual classroom.
Online Training is delivered over the web to let you proceed at your own pace, anytime and anywhere.
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 do not have left and right objects. (leftdiff, rightdiff). I have one diffusion object. Thus, I cannot use this standart:
"procedure(tranAbutFunction(instA instB pinA pinB pinAside conn event @optional group)
let(( result pinAcontP pinAstrP pinBcontP pinBstrP pinAw pinBw pinAcontV
pinAstrV pinBcontV pinBstrV drop_moving debugging eqW )"
And how I may use abutment in my case ?
I'm not entirely sure what you mean, because it would be meaningless to abut one object with itself.
I'm guessing that what you're saying is that you have a single piece of diffusion under the transistor, and so when you abut one transistor to another, you don't know how to handle that?
Well, the key thing is that the abutting objects are pins. When the abutment of two pins is detected, it can then figure out the connectivity information, and know whether there are other connections, and consequently your abut function can choose to do the abutment, either leaving the metal connection present or not. Normally the abutment is triggered by diffusion source and drain pins, because you need to have pins which will be there after the abutment has occurred; if you've removed the metal pins from either or both abutting transistors as a result of your abut function, there's nothing left to manage the abutment...
So usually you would create a diffusion pin on the source region and drain region - you can keep the single piece of diffusion underneath the transistor - I'm assuming that doesn't have any pin on it right now, because otherwise your transistor would be shorted...
The other main important feature of abutment is that the abutting pins must have the same pin name before and after abutment. Often pin names are not that important in Virtuoso; it's usually the terminal name which matters. However in this case, the pin name (which is somewhat arbitrary) is how the abutment system knows which pin is which before and after the abut function is called - this is necessary because the pcell code will have rebuilt the pcell submaster, and so it needs some way of identifying which pin was which (the db object ids will have changed).
In reply to Andrew Beckett:
Thanks, but... I will explain:
Аssume there is such transistor (I will try to represent top view):
b - substrateg - gates - sourced - drain
I want that abutment worked like this:
bgss ssgb bgsssgbbgds + sdgb = bgdsdgbbgss ssgb bgsssgb
And I write:
when(diff~>dbId != nil objId = diff~>dbId when(objId~>pin != nil objId~>pin~>name = "source") dbReplaceProp(objId "vxlInstSpacingDir" "list" list("right")) dbReplaceProp(objId "vxlInstSpacingRule" "float" msdd) dbReplaceProp(objId "abutAccessDir" "list" list("right")) dbReplaceProp(objId "abutFunction" "string" "tranAbutFunction") dbReplaceProp(objId "w" "float" W) ;dbReplaceProp(objId "contactParam" "string" "leftcnt") )
>>> spcMosAbutFunctioninstA~>name = "|MA1"instB~>name = "|MA4"pinA~>pin~>name = "source"pinB~>pin~>name = "source"pinAside = 8conn = 1event = 2group = db:239227436*Error* get/getq: second arg must be a symbol or a string – nil
>>> spcMosAbutFunctioninstA~>name = "|MA1"instB~>name = "|MA4"pinA~>pin~>name = nilpinB~>pin~>name = nilpinAside = 0conn = 0event = 3group = db:239227436Calculating un-abutmentReturning result t
But in standart example it is written:
when(leftdiff~>dbId != nil objId = leftdiff~>dbId when(objId~>pin != nil objId~>pin~>name = "source") dbReplaceProp(objId "vxlInstSpacingDir" "list" list("left")) dbReplaceProp(objId "vxlInstSpacingRule" "float" msdd) dbReplaceProp(objId "abutAccessDir" "list" list("left")) ;dbReplaceProp(objId "abutClass" "string" cellViewId~>cellName) dbReplaceProp(objId "abutFunction" "string" "tranAbutFunction") dbReplaceProp(objId "w" "float" W) dbReplaceProp(objId "contactParam" "string" "leftcnt") )
when(rightdiff~>dbId != nil objId = rightdiff~>dbId when(objId~>pin != nil objId~>pin~>name = "drain") dbReplaceProp(objId "vxlInstSpacingDir" "list" list("right")) dbReplaceProp(objId "vxlInstSpacingRule" "float" msdd) dbReplaceProp(objId "abutAccessDir" "list" list("right")) ;dbReplaceProp(objId "abutClass" "string" cellViewId~>cellName) dbReplaceProp(objId "abutFunction" "string" "tranAbutFunction") dbReplaceProp(objId "w" "float" W) dbReplaceProp(objId "contactParam" "string" "rightcnt") )
and abutment work in this case:
sgd sgd sg*gdsgd + sgd = sg*gd
and in this:
sgd dgs sgdgssgd + dgs = sgdgs
Why does not work my variant ?
In reply to Zelli:
I've read through your post three times, and I cannot fathom out what you're telling me. Some of your descriptions are rather cryptic, to say the least, and just the snippets of code are not enough for me to work out what is happening, what is not happening, or even what you're expecting to happen!
Probably the best thing would be to contact customer support with a testcase illustrating your problem. Then there's some chance of being able to work out what your problem is and how to solve it.