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 trying to simulate my extracted views but am currently having some difficulty creating the actual netlists.
I have a testbench, which instances the device under test. The testbench is a schematic view, whilst the device under test has both schematic and extracted views.
I have added the extracted view onto the switch list using 'envSetVal'. Then I have the following calls in my script:
- design( myLib myCell extracted)
However, this fails as the netlister says the testbench does not have an extracted view. I was under the impression that if there was not an extracted view available as with the testbench, then the next view on the switch list would be used for netlisting (in this case the schematic view). Therefore, this should be ok??
Is this the correct method to create extracted netlists, or am I missing something obvious? Do I have to define exactly what cells use what view?
(I should also point out that all my schematic netlisting sims etc work fine. It is just creating the extracted netlists that I am having difficulty with)
Thank you very much in advance. Any help would be greatly appreciated!
Are to trying to netlist the testbench schematic or the DUT schematic? From your description it is the DUT schematic that contains the extracted view.
If you want to create a netlist for the DUT schematic ensure that myLib/myCell in design( myLib myCell extracted) matches the DUT libName/cellName. In this case it is not necessary to set the switch list:
design( myDUTLib myDUTCell "extracted" )
If you want to create a netlist for testbench schematic which will include the extracted view for the DUT, then the design() call should be as follows:
design( myTESTBENCHLib myTESTBENCHCell "schematic" )
In reply to Jim McMahon:
Thanks kindly for your reply.
I managed to fix the problem and it was a rather silly mistake that I had made. My method was correct, however, in my haste to edit the switch list within my .cdsenv, I had actually editted the hspice switch list rather than the spectre switch list. Therefore, when running spectre, the extracted views were never included in the simulations.
Thanks again and I hope I can be of assitance in the future.
In reply to coco009:
Sounds like you haven't looked into the 'Hierarchical Configuration' approach to managing which representations are in use at netlist/simulation time. It'll make life a lot easier as you add more variants to the mix, e.g. 'sch_20090223' instead of 'schematic', 'av_RC_70C' instead of 'av_extracted', etc.
See the Cadence Hierarchy Editor User Guide for the details and/or chat with your Cadence Field contacts for quick ramp-up.
In reply to aplumb:
Anything that saves time is definately worth a look. I'll investigate this further when I get a chance.