Home > Community > Blogs > Digital Implementation > demo calling global timing debug for a single path
 
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 Digital Implementation blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Demo: Calling Global Timing Debug for a Single Path

Comments(2)Filed under: Digital Implementation, STA, screencast, SoC-Encounter, Global Timing Debug

Global Timing Debug has been a very popular capability within SoC-Encounter.  Once you start using it, it becomes hard to go back to looking at text reports.  The high level philosophy of Global Timing Debug is to assess not just the worst path in the design- but all of the failing paths to get a feel for the categories of problems which are blocking timing closure.

That said, I find that Global Timing Debug visualizes a single path extremely well.  In addition to highlighting the path in the layout window, it adds useful details that are hard (or impossible) to extract from the textual report.  For example:

  • It clearly states the clock skew for the path.
  • It shows the relative contribution to path delay for each instance in the path and colorizes the instances based on cell type.
  • It reports the SDCs which potentially affect the path with line numbers from the SDC file.
  • It provides a "Timing Interpretation" which gives suggestions on things to look for when analyzing why a path is failing.

For these reasons and more, it is often useful to bring up a single specific path within Global Timing Debug.  For example, if you've got a worst path text report from your signoff timing tool and you'd like to see that exact start/endpoint path visualized within Global Timing Debug.  The following screencast shows how you would use "report_timing -machine_readable" to output a .mtarpt file that can be read into Global Timing Debug:

I'll be doing future screencasts on Global Timing Debug, but I hope this targeted example is useful.

Question of the Day: What is your favorite part of Global Timing Debug?  What features would you like to see added?

 

Comments(2)

By Kari on October 10, 2008
Hi Bob, great demo. I suggested this very thing to someone the other day. My favorite parts of Global Timing Debug are getting a quick visual look at the failing paths (sometimes that's all you need to see what's wrong), the list of SDCs affecting the path, and the Timing Interpretation.


By Valerie on October 28, 2008
Hi Bob, great demo!  I posted this link to our lab PDLs for Encounter floorplanners and block builders.  I will let you know if I receive any request for additional features/information.

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.