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 noticed IC6.1's new feature to allow you to "ASSIGN libname DISPLAY colorname". It works, but you have to hand-hack the cds.lib.
But I'm coding some library utilities which utilize the ccp functions, and I want to retain the colors whenever I copy/rename a library. All the ASSIGN statements get orphaned whenever I move libraries around via ccp. How do I keep the ASSIGN statements in lockstep with my ccp operations? Do I actually have to open the cds.lib file as an ASCII and sed/grep everything with a series of system calls from Skill??
Surely someone has hit this before? When your ASSIGN statements all get orphaned, that's pretty bad.
There's no SKILL API to manipulate the ASSIGN statements in cds.lib - you have to update the cds.lib (using SKILL I/O functions) yourself. If you would like a SKILL API to do this kind of manipulation, you'll need to file an enhancement request with customer support.
In reply to Andrew Beckett:
No kidding. I filed a bug (not an enhancement) and it got binned. An API should not be necessary--if you delete a library, the ASSIGNs should go with it. If you copy or rename a library, the ASSIGNs should go with it. The Skill I/O functions work, but as far as I'm concerned that is a bug that it is not default Virtuoso behavior. Cadence should not be orphaning ASSIGNs in a way that is clearly wrong.
In reply to GoRangers:
OK, I checked. Your request has not been "binned". There has been some healthy debate about the request in the CCR, and it's agreed that there should be user control over which attributes get transferred to any new library. Some people might want some (or all) of the attributes copied, some might not. For example, if you've got an attribute indicating a reference library as readonly, and you take a (writable) copy of it, having it marked as readonly might not be appropriate any more.
Also, it's perfectly reasonable to have attributes for a non-existent library in the cds.lib, so that when the library gets created, it gets those attributes.
I'm not saying that these are necessarily what most people would want, just to illustrate that it's more complicated than it might seem from a first glance. It would also require changes to various APIs (not SKILL APIs, but the APIs used at a lower level in the tools) to allow better (selective) propagation of such attributes. So this needs careful architecting.
Since it's impractical to plan any bug or enhancement request that comes in straightaway (unless it's a production-halting bug) - after all, we've already planned out the work for the next release - the normal process is for it to be backlogged (marked "Inactive") until the next planning phase - at which point it can be considered alongside all the other requests, and prioritized. If it doesn't make it for that planning phase, it can be considered at the next planning phase, and so on.
So the CCR is awaiting consideration for implementation when we next do a planning session.