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.
Hey all, my librarian and I are trying to come up with an elegant solution to some library managment issues.
In our company, we have corporate part libraries that are grouped by what I will call component type. For example, all of the resistors live in a library called RE, all of the caps live in a library called CA and so forth. Part of the designation comes from the way the parts are managed in our Oracle database. As our library grows, some of the individual libraries are getting pretty unweildly and I would like your opinion on how to clean them up.
What we try to do is keep the total number of cells in a library to a minimum and then use part table files to make final part selection. For example, in our RE library, we have a single cell called r_res. When you click on this cell the part table file loads up where the designer can then sort by value, pack_type, etc. Works great.
Where we are having a problem is with cells that have some "oddball" parts. Take for example our QD library. In that library, we store all of our transistors, diodes, etc. What would be ideal would be to have a single cell for all of our mosfets for example. On the top level, a fet is a 3 terminal device. It has a gate, a source, and a drain.Unfortunately, some manufacturers make a fet in a 8 pin package where the drain goes out to 4 pins, the gate to 1 pin and the source to the rest. Is there a way to still use a single cell/schematic symbol for the fet, but have it linked up to multiple package types of different pin count?
Below is the component browser view of a fet that has a 3 pin symbol and a 3 pin physical package (first library view, then selected part view). Following those two pix are view of a fet that has a physical package that has 2 drain pins. What we had to do was create a fet symbol that had 2 drain pins. What we would like to do is use the same 3 pin fet symbol and have it be able to map to the other packages. Anyone know how to do this???
I don't know if this solves your problem. But we haver used it on some of our connectors in our library.
The way we solved it on, where to use sizable pin instead of static pins and different pack types. You will get an error, as I remember, but it worked then.
In your case, instead of D1 and D2, use D<SIZE 1..0>. Then expand it on those part that need it.
Have you looked at the PACK_SHORT property. I think this would give you the capability to short D1 and D2 together at the part. You could build this into the primitive for that particular package.
Have you looked at the PACK_SHORT property? I think this would give you the capability to short D1 and D2 together within that primitive defining that particular package.