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.
when lpp=list("prBoundary" "boundary") ?
I mean, what's the cellView~>prBoundary supposed to do?
The prBoundary is the place & route boundary that instances and shapes should be placed within. The automated Place & Route tools will operate within the confines of this boundary. In IC51x and earlier the prBoundary was a shape on a specific layer-purpose pair (e.g. "prBoundary" "boundary" or "prBoundary" "drawing").
cellView~>shapes~>lpp is something else entirely: in a cellview a shape exists on a specific layer-purpose pair, querying all the shapes of the cellview (cellView~>shapes) will obtain a list of all of the shape database objects, and further querying for the 'lpp' attribute will apply that query to each of the shapes (as long as you use the "~>" operator, not the "->" operator), so the compound query returns a list of the lpps, one for each shape. If you just want to see the lpps used in the cellview, do cellView~>lpps to obtain a list of the LP (layer-purpose) objects. The lpp query is not equivalent to the lpps query; the lpp attribute of a shape is a list of the layer and purpose, the lpps attribute of the cellview is a list of the LP db objects.
Hopefully this answers your questions?
In reply to skillUser:
Thank you, Lawrence. Your explanation about ~> is very useful because I've never used it.Still, I would like to know something about cellView~>prBoundary. Do you mean that a kind of Encounter can use the prBoundary instead of ("prBoundary" "boundary")?
In reply to Zelli:
If you are using the IC61x release of virtuoso, the underlying database OpenAccess (OA) - this uses a prBoundary object to represent the place and router boundary, rather than a shape on a specific layer. The recent versions of Encounter operate on the OA database so they should understand the prBoundary object. I don't work with Encounter tools, so I'm not able to provide much more assistance on that topic, sorry.
Please state the versions that you are using and perhaps we can give better answers.
I don't know the release of Virtuoso because it's a holiday and I'm at home. But I know it's a newer version than the one I've used before.Then how they create that prBounary? Somehow through menus? What about LEF? Are the shapes still in use or not?
As Lawrence pointed out, prBoundary is now a specific object in OpenAccess, and tools that need a boundary (such as various parts of the Virtuoso Layout Suite, such as VLS-XL and the space based router, placers, etc, and also Encounter) will create such an object.
For example VLS-XL creates one when you do a generate all from source. Also you can create them manually with the Create->P&R Objects menu.
No Cadence tool is using shapes on the prBoundary/boundary layer purpose pair any more.
LEF will also use the prBoundary object.
In reply to Andrew Beckett:
Thank you very much, Andrew.The question is now answered :)
I get that prBoundary is now an object but is there an object equivalent to cellView~>shapes~>lpp?
Thanks so much,
In reply to johnmck8:
I don't understand the question. The lpp attribute of a shape (so what you get when doing cellView~>shapes~>lpp) is a list of layerName and purpose - that is the same in OA as in CDB. Why would it be an object now?
The change with OA was to implement specific objects for things where previously shapes on particular layer purpose pairs had special meaning.