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 now starting to read and going through the process of digital flow.
What is the best way to export the final routed and placed design in encounter to Cadence Virtuoso environment for the subsequent DRC and LVS?
As far as I saw already from several manuals, one way is to save the GDS, then go through the process of importing GDS inside Virtuoso in a new library, a process with which I am familiar with. Then of course one can perform DRC there with Assura. And then if I am correct, that library can be used in any of a custom designed analog block in another library within Virtuoso environment.
But question is, what if the digital design was fully done using the HDL (vhdl or verilog), how does one perform LVS then once the GDS was imported in the Cadence Virtuoso environment?
When I design analog circuits, LVS compares my custom layout against the CDL-type netlist which is generated from the schematics I manually build.
But if I imported the GDS layout of automatically placed and routed digital design by encounter, how do I set up the process for LVS to compare it with HDL description? Or in what other proper way this has to be done?
In reply to FrancescMoll:
What is the best way to convert the result of saveNetlist -phys to CDL?
Because the way I did it:
1) Import physical verilog to CIW as schematics
2) There from schematics create CDL netlist, then CDL netlist for LVS using preprocessor supplied by kit (the way I always produce netlist for LVS on all my hand made analog circuits, and that way works of course)
But there is a problem, first of all, even though schematics is created and looks big and have all those standard cells, when I tried to look inside those standard cells out of which my big schematics imported from physical Verilog composed I noticed there are NO TRANSISTORS, just ports... is this normal? This looks suspicious to me.
Anyway, I still tried from now on to do the LVS as I always do on all my cusotm circuits, but the LVS spits out errors something like: nfet(MOS) on Layout is unbound to any Schematic device..
So, the bottom line is, after Encounter import, the layout was corrected for residual DRC errors and was looking sexy, the physical Verilog produced by Encounter was imported, schematics of my big digital unit created on a gate level, but each gate had empty schematic inside, and LVS gave that error above.
Why would that happen? And the big question is, how do I import the physical verilog so that the CDL schematics with transistors is created, so that I can do the LVS, because the layout from transistors of course requires schematics with transistors at the bottom level for successfull LVS.
In reply to Kabal: