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 a little bit confused. I want to simulate some schematics using
Spectre. The Cells i used have different Views. Until now i always used
the symbol-view. But now i wondering: What are the other views used for?
There are these views:
Should i use the spectre-view if i want to simulate using Spectre?
Thank you for all answers!
You should always use the symbol view for building your schematics. The spectre view is used as a so-called stop view. Interestingly, the best explanation of the function of a stop view seems to be on Agilent's website at http://cp.literature.agilent.com/litweb/pdf/ads2008/dynlnkug/ads2008/Using_Switch_Views,_Stop_Views_and_the_Hierarchy_Editor.html
In reply to Frank Wiedmann:
Actually, this is documented in the Virtuoso Analog Design Environment L User Guide (in cdnshelp, or look at <ICinstDir>/doc/anasimhelp/anasimhelp.pdf ). There's a section called "How the Netlister Expands Hierarchy" which explains this. In fact Agilent's site seems to have lifted exactly the same flowchart from the ADE documentation ;-)
It also refers to the hierarchy editor user guide (from the same document), which gives more control.
The idea is that having determined how the netlister expands the hierarchy, once it reaches a stopping view, it will then use the information in the Simulation Information section of the CDF for that component to determine how the instance formatted in the netlister.
Typically the stop view is usually just a copy of the symbol, and is just a marker to tell it where to stop - it doesn't really need much information from the view itself - except the terminals. The terminals may potentially have additional (inherited) terminals for adding bulk terminals to 3 terminal transistors (for example), but in most cases the stopping view looks identical to the symbol view.
In reply to Andrew Beckett:
Andrew Beckett Actually, this is documented in the Virtuoso Analog Design Environment L User Guide (in cdnshelp, or look at <ICinstDir>/doc/anasimhelp/anasimhelp.pdf ). There's a section called "How the Netlister Expands Hierarchy" which explains this. In fact Agilent's site seems to have lifted exactly the same flowchart from the ADE documentation ;-)
Thanks for letting me know, Andrew. For some reason, this document does not show up when I search support.cadence.com for "stop view".
I will read the User Guide an monday and write again if further questions occur.
Thank you Frank and Andrew!