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, all. The problem is: I attempted to use command WRIte HIer_compare Dofile for comparison of two hierarchical designs: rtl and back annotation rtl after synthesis the first one (hierarchy was keeped). Conformal wrote out a hierarchical dofile script but without starting from the lower level module of hierarchy and progressing to the top root module. Given script verifies only the two top modules of hierarchical designs. And several warnings appears at running this script, so as: // Warning: Child module 'sub_module_name' used in Golden module 'top_module_name' 2 times, but in Revised module 'sub_module_name' 1 times (non-balanced). Skip 'sub_module_name' And after that appears in Conformal konsole: "? modules are not output for hierarchical compare due to non-balanced instantiations" "1 modules are output for hierarchical compare" And this module is the top. But I know that the hierarchies are equal and built, but the names of several corresponding instantiations slightly differs (for example sub_module_name for Golden and sub_module_name_1 for Revised) And this module is the top. So my question is: How compare two hierarchical designs by matching their instance-names, but not modules? Or what have I do if their names slightly differs? How can I balance instantiations? Please give me an advise. Thanks. With best regards, Valery Kartashev.
Hi Valery, When LEC runs hierarchical compare, it needs to be able to match the modules by name. So for this case, you need to use "add renaming rule" for the modules. For example: add re r mod1 "%s_1" "@1" -module -revised This wil rename the revised module name from sub_module_name_1 to sub_module_name to match the module name on the golden side. Lastly, if there is uniquification done on the gate netlist, you need to reflect this in LEC. The command is "uniquify -all" If the module name on the revised side is due to uniquification, then just use "uniquify -all" first before doing "write hier dofile". If the module names were changed by synthesis, then you need to use the add renaming rule. So give these two options a try and see if the write hier dofile will resolve the unbalanced instantiations. Regards, Yong Kim