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 have to agree that FE trial route is doing a very good job to estimate the routability in a very short time.
However, when the area is tight and double-via is a strict requirement, I thought the trial route tend to give too optimistic report. As a result, a routable placement by trial router (no congestion/routing overflow reported by trial router) may end up failure in the actual nanoRoute stage. I thought that the trial route may not actually use the double vias provided in LEF file to do its job: it always apply single cut via even there is no single cut via defined inside the LEF file. Is this observation right? If it is, how can we work-around this issue? Your opinion is highly appreciated!
Can you look at what vias trialroute is using, and tell where they are coming from?
In reply to Kari:
The vias used by trialRoute are same set of vias, which come from my tech LEF file. In the trialRoute results, I saw a lot of vias are shorting to other nets. But the trialRoute report the design routable:
Remain cntH cntV
-1 0 0.00% 10 0.02%
0 1 0.00% 1587 2.43%
1 18 0.03% 7520 11.5%
When I tried the same placement with nanoRoute, I got thousands of shorts remainning. However, If I add a single cut via into my LEF file (my current LEF file ONLY have double cut cut vias), then, trialRoute and nanoRoute will give me consistant result: roughly routable ( nanoRoute will finish the route with one or two shorts).
In reply to Tongju:
This is an interesting problem! I've never seen a design where no single vias are allowed. My next suggestion would be to make sure you have enough kinds of double vias (north, south, east, west) to give the router the most flexibility. But I'm thinking this won't solve the entire issue. You should probably file a service request on Sourcelink.