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'm currently trying to draw the layout of a device not present in the library of my technology. So, I think to create a symbol to put in the schematic of my circuit and after to draw the complete layout.
When I will finish the layout, what can I do to execute the LVS?
I think the LVS will not recognize the new device. Someone suggested me to add a lot of labels in my circuit near to the non-standard devices.
Is it a good idea?
Are there other more efficient method to execute the LVS of circuit with non-standard devices?
A bit of a vague and open-ended question, unfortunately. It depends what you mean by "non-standard". It may well be that the device extraction in your LVS rules can extract your device, despite the fact that it didn't come from a standard pcell, say. That's because LVS rules would typically extract interacting geometries and recognize the device that way - it doesn't matter what your cell is called, because it looks at the interaction of poly and diffusion (for example, if it's a MOSFET) geometries.
If an existing device recognition does not work, you can either modify the LVS rules to add device extraction statements for your particular device structure, or maybe you can use a "black box" approach to recognize it. Exactly how you do that will depend on which LVS tool you're using (you didn't say).
In reply to Andrew Beckett:
Sorry, you are right!
I used for my simulation a model of a diode, obtained through TCAD simulations. So, the device doesn't exist in the technology library, but it has been used to design a rectifier!
Now, I have to draw the layout of the circuit, but I think that if I simply draw the layout of the diode and associate a symbol view, the LVS will not work? A solution that someone suggested to me was to insert a lot of labels in the schematic and in the layout, in order to check that the connectivity is correct! Of corse, the LVS will have the errors due to the unknown devices, but at least the connectivity could be checked.
I hope I was more clear...
In reply to Ueue:
If the device does not get recognized by the LVS rules, then I think your best bet (if you don't want to code the recognition into the rule deck - which would be worth it if you're using them a lot) would be to use a black box approach.
Relying on labelling nets around the device is risky - for a start, it's hard to guarantee that the mismatch of this device would only cause a localized problem - it could cause a bigger mismatch (this is very dependent on the LVS tool you're using). Also, it makes it much hard to distinguish between real errors and intentional errors such as this.
So I refer you back to the suggestions I made in my previous reply.