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.
Is it possible to construct a global library with layout view which able to use in all processes? If yes, do you mind providing the proper way to do that. Thanks
BTW, Noticed that each process has their own techFile and layer mapping as well, if we create the layout in particular process, the layout will not able to work on other process due to imcompatible data.
Your advice/suggestion is very appreciated.
I think i found the solution for this. To create a library which able to use globally, we can use incremental techFile method. We can create a new library and techFile.tf that contains layers that use in the layout and load it, then save it as tech.db. The layer names and numbers in the techFile.tf cannot be the same as other techfiles. Otherwise it will lead to errors during techfile compilaton.
Then, in the main tech file, add global library to refTechLibs eg: refTechLibs("cs1234" "globLibrary")
For all other processes, you can now simply add "globLib" in refTechLibs and the library "glodLib" in cds.lib to ensure that users can make use of the rdt cells. This is basically the concept of incremental techfiles.
In reply to kbhow:
You are creating an independent library which does not collide with the existing techLib definitions. You may have to map the additional layers in the ITDB library to the layers in your process techLib using a layerMap file for GDS and equivalent layers for the tools. This leaves open many potential areas of error.
If the devices are not complex, you could represent them as pcells with the layers and possibly the rules defined from the existing techLib. Each placement would be custom for the design. Use dbWriteSkill to get the initial SKILL which you would have ot parameterize with layer names, etc.
You can also use the mapper capability to take an original library and map it to a specific technology. Copy the original library, set up the mapping table (once per technology) and it will change the layers to the ones in the techLib. You will now have a copy of the original library in the new technology. This is probably the safest methodology.
In reply to Austin CAD Guy:
Thanks for the info. I use to create an original library and map it to a specific technology, where this techFile is created with layer defination only. Can this work too?