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 the database, which is physical optimized using the EDI flow & I want to further optimizations to reduce the slack, which i think is difficult in EDI,
I thought of picking up RTL physical flow for further optimization. I tried to compare the timing of the same design in RC Physical. But i see a humoungus difference between the EDI & RC-Physical (RC200 license).
In EDI WNS i noticed as -98ps.
In RC WNS is -735ps
the load cap seen on the first few comparisions of Cells are as follows 6.1 fF & 2.5fF & the corresponding caps for the cells are 3.4 fF & 0.783fF.
Realized that the Net Length Calculations in EDI & RC are different. How to find out the Net Lengths in RC ?
there are indeed differences in the way RCP handles some of the nets and EDI. These differences are mostly related with signals such as reset, scan enable, high fanout nets, etc. In your case, the concerning aspect is that when things do not correlate, you would normally expect more optimism in synthesis and not the other way round as described in your example. The following report subcommands can provide you additional detail on the calculation
net_cap_calculation - reports how the capacitance of the net is calculatednet_delay_calculation - reports how the net delay is calculatednet_res_calculation - reports how the resistance of the net is calculatednets - prints a nets report
The first thing I would look at are
(1) Version of RC(2) Version of EDI(3) Are u using same netlist ?(4) Are u using same SDC ?(5) Are all constraints accepted cleanly ?(6) Are u looking at same corner ?
Remember when using RCP, the GUI can be very handy.
report timing -gui. . .
will show you the path in the GUI. Is it reasonably similar to what EDI is showing ? If not, why ?
Last but not least, be careful when you assumeRCP will reduce slack. RCP will determine the physical dependencies more accurately hence produce a better netlist (better util, TNS, power, etc.) That being said, if your critical path is a flop to a flop without logic in between, there is not much RCP can do to make that better. Hope this is useful.