Home > Community > Blogs > Logic Design > tips for fixing timing violations and adopting best practices in optimization with rtl compiler
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the Logic Design blog (individual posts).
 

Email
* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

Cadence Contacts

Global Office Locator
Find Offices worldwide »

Sales Inquiry
Request for Product information »
Cadence Channel Partners »

Corporate Headquarters
Cadence Design Systems, Inc.
2655 Seely Avenue
San Jose, CA 95134
Phone: 408.943.1234
* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Tips for Fixing Timing Violations and Adopting Best Practices for Optimization with RTL Compiler

By Sumeet Aggarwal on August 7, 2012Comments(0)Filed under: Logic Design, Synthesis, RTL compiler, rc, Functional Verification, fixing timing violations, boundary optimizations, optimizations

Best Practices for Optimization

What should be my considerations while preparing data? Libraries, HDL, Constraints...

A good result from a synthesis tool depends greatly on the input data. An old saying "garbage in garbage out" is also true for RTL Compiler. Before attempting to run synthesis, the user should check the input data, pay attention to the warning messages and correct any obvious issues.

How do I set and achieve my optimization goals?

There is no ‘one-size-fit-all' recipe for optimization; the recommended flow is to run the design through the baseline flow once with the ‘synthesize -to_map' command, analyze the result, then fine tune the flow if needed. So, how do I set and achieve my optimization goals?

Which approach is better?

 

 Top-down vs. Bottom-up OR Wireload Model vs. PLE

To know more: Read Cadence Application Note on RC Optimization Best Practices

 

Fixing Timing Violations

How do I validate timing constraints? How do I analyze violating paths?

Let me guess some strategies for fixing violations... can the following tips help?

Creating different cost groups for I/O paths

OR

Using multiple incremental synthesis and using path_adjust and changing datapath structure

OR

Idealize high fanout nets and setting initial_target

To know more: Read Cadence Application Note on Tips for fixing the timing Violations in RC

 

Boundary Optimizations in RC

What are different types of boundary optimizations in RC?

How can I control it?

What are formal Verification considerations?

To know more: Read Cadence Application Note on Boundary Optimizations in RC

 

Note: To access above docs, click a link and use your Cadence customer credentials to logon to the Cadence Online Support (COS) web site.

Cadence Online Support website http://support.cadence.com/ is your 24/7 partner for getting help and resolving issues related to Cadence software. If you are signed up for e-mail notifications, you've likely to notice new solutions, Application Notes (Technical Papers), Videos, Manuals, etc.

You can send us your feedback by adding a comment below or using the feedback box on Cadence Online Support.

Happy Learning!

Sumeet Aggarwal

Comments(0)

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.