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.
Ive been trying to do some DRC fixing in Cadence Ecounter. The basic
problem I am facing is offgrid/nogrid routing errors. I tried setting
the routeOngrid option true and routed the design again. But still there
is no significant reduction in the number of errors. The total number
of DRC errors is in the range of 1 million plus of which 900,000 odd are
nogrid violations and 100,000 odd are offgrid. Can anyone please tell
me about things I could do in routing by which I can fix these errors?
Is routing/incremental routing the only way to fix DRC errors in
Encounter? Any suggestions/replies are appreciated
Searching the online documentation for "tracks" <install_dir>/doc/fetxtcmdref/fetxtcmdrefTOC.html verifyTracks & generateTracks Until you can get verifyTracks relatively clean nanoRoute is going to give you nothing but grief.generateTracks is a good place to start, it will redefine your routing grid from scratch.To visualize whats really going on use the gui and turn on the tracks. walk through the individual routing layers.setLayerPreference trialTrack -isVisible 1If things are still not lining up check your lef and follow the guidelines under .<install_dir>/doc/lefdefref/OptimizingLEFTechnology.html<install_dir>/doc/socelibdev/socelibdevTOC.html
In reply to fitz:
Thanks for your reply. I did run the verifyTracks command on the trial routed database. Turns out 6000 odd standard cell pins which have been placed offtrack, which eventually escalated into the huge number of off gid DRC errors. But, what could be the reason as to so many pins being placed off track. Is there a fundamental mismatch between LEF and standard cell lib?
In reply to metalhead:
I just ran verifyTracks on an old 65nm block .... STMicro good vendor!#Start checking floorplan tracks ...#Start checking preferred tracks integrity ...#Checking preferred tracks integrity done.#Start checking pin accessing against defined tracks ...# M1 H Track-Pitch = 0.200 Line-2-Via Pitch = 0.190# M2 V Track-Pitch = 0.200 Line-2-Via Pitch = 0.200# M3 H Track-Pitch = 0.200 Line-2-Via Pitch = 0.200# M4 V Track-Pitch = 0.200 Line-2-Via Pitch = 0.200# M5 H Track-Pitch = 0.200 Line-2-Via Pitch = 0.200# M6 V Track-Pitch = 0.800 Line-2-Via Pitch = 0.800# M7 H Track-Pitch = 0.800 Line-2-Via Pitch = 0.800# AP V Track-Pitch = 5.000 Line-2-Via Pitch = 5.700#Build pin access layout completely##Total number of pins = 6113965# Total number of on-track standard cell pins (via accessing) = 6113965 (100.00 percent)# Total number of off-track standard cell pins (via accessing) = 0#Total number of pins blocked by SNET = 0#Check tracks done and successfully.Notice the Track-Pitch's are all multiples and everything lines up nicely.Normally the routing grid is correctly defined by the "floorplan" sizing command, but just in case try the "generateTracks" command to regenerate the routing grid and recheck with "verifyTracks".If that doesn't work you have some research to do. Start with the <technology>.lef which defines the basic metal routing PITCH and standard cell SITE CORE size.The SITE CORE X dimension is usually the same as the vertical M2 PITCH so that M2 wires can directly via down to an M1 pin.Typically the vertical routing grid is offset from the placement site array by half a pitch.LAYER M2 TYPE ROUTING ; DIRECTION VERTICAL ; PITCH 0.2 ;SITE CORE CLASS CORE ; SYMMETRY X Y ; SIZE 0.2 BY 2.6 ;END COREDebugging blind is very difficult, but if you look at at the previously mentioned guideline documentation you should get the overall picture.