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; I got some drc violations after P&R. Here are the descriptions about the problems. If anybody can take a look at it and give some advice, it will be much appreciated. Thank you Seonho 1. Type 1 violation (1) Minimum metal distance rule between wide metals At first it is not wide metal. But, as via1 added to the metal, it becomes wide metal. But, P&R tool doesn’t consider this final structure as a wide metal. That’s how this violation took place. So, if we have option by which we can make the tool recognize this, this problem will be resolved. (2) As you can see, one metal route is in the core and another wide metal is in the RAM. Since the metal in the RAM is wide, wide metal distance rule should be applied. But P&R tool applied the normal metal rule. I think this is happening either because lef file of the RAM is not complete or RAM block is not flattened so P&R tool doesn’t recognize the final structure. So, could you tell me how we can resolve this problem? 2. Type 2 violation (1) This is via farm rule violation. I think this happens because there is no such rule specified in the lef file. 3. Type 3 violation (1) Minimum number of vias on a wide metal. Basically, I thought only the number is important. But, since HERCULES gives this error, I think the configuration or alignment is also important. But, in the lef file, no specification about the configuration is made. Could you tell me if we can handle this problem in P&R tool?
Semicond, Here is an answer from Cadence engineering: #1.1 NR should recognize this as violation if the wide spacing rule (RANGE) rule is defined in LEF. If not, it could be a bug or the user used a very old version of NR where an option was required to support this. #1.2 NR should recognize this violation unless the RAM abstract is not properly defined or the setting in the LEF file, USEMINSPACING OBS ON. If this is set to on, then NR will use minimum spacing against obstruction. #2.1 The user answers his/her own question. #3.1 Which wide metal the user was talking about? Is it for special net? If it is, then the via gen rule might have not been defined properly. If it is in regular nets, then the LEF might have not contained MINCUT rule.