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.
Hello, I have a question regarding the differences between a PDK/CDK (Process/Cadence Design Kit) and a standard cell library. Sometime people use them interchangeably, but I think there are some inherent differences between these two things. Can anyone clarify this? The reason I asked this question is because recently I began searching for a MOSIS compatible 130nm or 90nm process for Cadence to do custom IC layout. I personally used GPDK and NCSU before; they have layout/schematic/symbol views for nmos, pmos, metal1-9, vias, nwell, psub... basically components that let users to build a circuit. However, GPDK is not MOSIS compatible and NCSU does not have 130nm or 90nm processes. I recently obtained IBM cms9flp process ARM Standard Cell Library, however, I don't know how to install it with Cadence. For GPDK or NCSU, there is a "lib" folder that contains all the components and their views (for example, lib/nmos/Layout, lib/nmos/Schematic...). However, there is no such thing for the ARM Standard Cell Library I obtained. Is this one of the differences between PDk and Standard Cell Library. Can anyone explain? I am wondering if I should be looking for cms9flp IBM PDK instead of the Standard Library. Thank you all in advanced!
A PDK includes the technology data, the base devices, DRC and LVS decks, model files, etc. The CDK (complete design kit) usually is a PDK with digital standard cell libraries. The stdCellLibraries include .lib file (timing) Verilog, .LEF ( Library Echange Format ), GDS - physical layout and some other files are used for place and route. The LEF is input (LEFin) to create the abstracts, the symbols (VerilogIn) and the layout (GDS). Once these are input, you will have your stdCell library.