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,Hope this is not silly.I want to grep the list of devices from two libraries of two different technologies. Do we have any inbuilt commands for this.For example after invoking icfb for tsmc13 I will execute ddGetObjChildren(ddGetObj("tsmc13_pcells"))~>nameNow if I want device list of tsmc09 then what is the command that should be executed now.ddGetObjChildren(ddGetObj("/user/tsmc09/tsmc09_pcells"))~>name!! does not work. Is it must that the library should be present in the current directory.Thanks,
The library doesn't have to be in the current directory but the library name must be referenced in the cds.lib file (or lib.defs under OpenAccess).You can always add it by doing:ddCreateLib("tsmc09_pcells" "/user/tsmc09/tsmc09_pcells")Note you can find the cell names by doingddGetObj("libName")~>cells~>nameRegards,Andrew.
Two different pcell libraries(two different techlibs) in same cds.lib?!! does it pose any problem??How to delete this library that I have added. ddDeleteObj is giving "Read only file system". I manually removed the DEFINE statement from cds.lib and "close Data", it dumped core and exited.
It doesn't necessarily cause problems - although if both have custom SKILL functions or variables which use the same names, you might end up with a clash.I don't think there's a built-in function to remove an entry from the cds.lib. ddDeleteObj will do it, but that will try to delete the contents as well as the entry in cds.lib. Note that you should really close the data and then remove the entry - but it shouldn't really crash. You should report this to customer support (provided you're using a reasonably recent subversion of the tools - if you're using something old, it may well have been fixed)Regards,Andrew.
Ok its exiting. Is there any other way for this. If not I will just write a routine skill code of grepping devices from the library path by identifying any key files etc..,Thanks ,
What subversion are you using? (what does Help->About say as the subversion, or the SKILL function getVersion(t) ).Another way to delete it would be:cdslib=outfile("cds.lib" "a")fprintf(cdslib "UNDEFINE yourLibName\n")close(cdslib)ddUpdateLibList()Regards,Andrew.