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 am having a discussion with Cadence R&D (via an AE) about "resetting" the Concept-HDL menus. When you select Tools->Customize, then the Menus tab, form is displayed. On this form there is a "Reset" button. The discussion is about what is expected when the reset button is pressed.I feel that the menu should revert to what it would be if the user had no Concept menu in their $HOME/cdssetup/concept folder. I.e. if there is any CDS_SITE customization or if the user had modified the menus in CDS_ROOT, those changes would appear the next time you start the tool. This means that resetting should simply delete the _menu and _keys files in $HOME/cdssetup/concept.What actually happens is that a menu is created in $HOME/cdssetup/concept folder that is the same as the installation menu. There are several problems with this.1 - the menu that is created is not a copy of the $CDSROOT/share/cdssetup/concept/concepthdl_menu.txt file. If the user has changed this file (they shouldn't) the changes are not in the reset menu.2 - the menu that is created overrides any menu the user has defined in $CDS_SITE. I.e. they don't get what they would have if there were no $HOME/cdssetup menu.3 - if you are using multiple versions of Concept-HDL, starting a version that is not the same as the one the menu was created from gives an error and you have to reset the menus again.What do you feel should happen when the "Reset" button is pressed?A - the $HOME/cdssetup/concepthdl_menu (and _key) file is deleted.B - a copy of $CDSROOT/share/concepthdl_menu ( and _key) files are made in $HOME/cdssetup/concept.
I agree with your opnion, pressing the reset should delete, $HOME/cdssetup/concepthdl_menu (and _key) files. I have had to instruct internal users on how to find and manually delete these files. I would much rather have had them just be able to hit the reset and have it taken care of/deleted. Randy
I would vote for option A. This would rectify the issues that arise when a user needs to switch back and forth between different releases. As it stands now, if a user is 15.7, does a reset, then switches to 16.0, the menus are 15.7 menus and they will get errors during load. Another reset reverses the problem. Clearing out the menu and key files with a reset would resolve this issue.I vote for A.