Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
Verification 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.
The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.
Participate in CDNLive
A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.
Come & Meet Us @ Events
A huge knowledge exchange platform for academia. We are looking for academic speakers to talk about their research to industry attendees.
Americas University Software Program
Join the 250+ qualified Americas member universities who have already incorporated Cadence EDA software into their classrooms and academic research projects.
EMEA University Software Program
In EMEA, Cadence works with EUROPRACTICE to ensure cost-effective availability of our extensive electronic design automation (EDA) tools for non-commercial activities.
Apply Now For Jobs
If you are a recent college graduate or a student looking for internship. Visit our exclusive job search page for interns and recent college graduate jobs.
Cadence is a Great Place to do great work
Learn more about our internship program and visit our careers page to do meaningful work and make a great impact.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
Overview All Courses Asia Pacific EMEANorth America
Instructor-led training [ILT] are live classes that are offered in our state-of-the-art classrooms at our worldwide training centers, at your site, or as a Virtual classroom.
Online Training is delivered over the web to let you proceed at your own pace, anytime and anywhere.
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 would like to ask about a warning in CIW. When I try to create a library which "Attach to an existting techfile" option, the CIW displays warning:
*WARNING* (TECH-230035): User-defined rule "minExtensionDistance" in constraint
group "foundry" of techDB "<tech_name>" conflicts with
a built-in constraint with the same name.
You may write out "constraintGroups" section to an
ASCII file, reopen the technology database in "a"
mode, and reload the file to update the database.
Another option is to rename this rule.
Can anyone figure out this problem, please?
Thank you so much.
From doing a bit of digging, I believe this is due to a change that was made in IC614 (not sure precisely which subversion) where the constraint groups used were mapped to the correct OpenAccess constraint group names. It affects technology databases that were compiled before this. I think it may have been that the technology database was compiled in IC613, and that's the problem.
I think doing a "Save" of the technology file from the technology library in Tools->Technology File and then doing a "Load" in Replace mode back to the same technology library would fix it. But you might want to check with the foundry first in case they have a newer version of the PDK. That's effectively what the instructions in the message are telling you to do.
In reply to Andrew Beckett:
Can you explain for me what <constraint group "foundry"> is and what <built-in constraint> is? What is "constraintGroup"?
In reply to Duy Hien:
If you dump the tech file, you'll see there is a section called constraintGroups and within that there's a definition of various groups,probably including one called "foundry" which is the base level constraint group. This is how sets of process rules are organized in the technology.
The constraint system supports both built-in constraints and custom constraint types. In this context however, it was because in older versions that particular constraint (that was mentioned in the error message) was not implemented by Cadence using the native OpenAccess constraint (I can't quite remember why, possibly due to legacy issues with an older version still), and so was implemented as a custom constraint rather than a built-in one. When we migrated to use the new built-in constraint in OA, there was a discrepancy, and hence the warning.
I believe this is the case - I've not fully read up on it, because this change was a few years ago and I've forgotten the precise explanation (the first paragraph is definitely correct though).