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.
Hi, I am university student currently learning Cadence tools. I use DIVA for DRC, Extract and LVS. Process : TSMC18RF (0.18um) I am currently doing layout of an 10 phase oscillator circuit. When I run DRC on my completed layout I get no errors. When I run Extract with the "Join nets with same name" switch ON and Parasitic RC Switch SET. I get the following errors: Figure Causing Multiple Stamped Connections Figure Having Multiple Stamped Connections if i set the Parasitic RC switch OFF - that is if dont set any switches ( no parasitic extract ) I DONT get these errors or ANY errors. My Design also passes the LVS succesfully my design has following layout structure: VDD Rail ==================== BUFFER Amplifiers ==================== GND Rail ==================== Differential Amplifiers ==================== VDD Rail ==================== Buffer Amplifiers ==================== GND Rail ==================== I googled these error messages and I found some explanations but I dont seem to violate any that is mentioned in these expalnations. Like I have connected the GND and VDD properly. the divaEXT doesnt like me putting 2 separate ground Contacts. my Ground contacts are M1_SUB. if put them at separate places i get this error. How do I go about resolving this issue? please help.
Typically the problem is that you cannot check for substrate connection when doing parasitic resistance extraction. You can not do this because the metal1 layer gets broken up into resistors (parasitic) so every metal1/ptie and metal1/ntie contact is on different net. Basically what you have are two well contacts that have different nodal information. Try changing the rule (geomStamp) in your divaEXT.rul file so it does not use the "error" keyword when parasitic resistance is in use.
Another place to look is the p2lvs file. In this file you define (in the first line) which are your substrates and how are they "stamped" together. Personaly, I had many problems understanding all the options there till the end, but playing around with it might help.Ezra