• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Analyse the encounter timing Report

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 15473
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Analyse the encounter timing Report

kenambo
kenambo over 10 years ago

Hi All,


          I generated the timing report of my design using timeDesign command before doing CTS and after BTS.


And  I see many terms like Instance , Cell , Delay, Arrival time, and slew load etc.

I understand these terms .. but it shows same two instances and display one delay value and two slew and load values. How to interpret this report and If I want to see the same path after CTS means, is there a way to see the same path after CTS by timeDesign command.

Please clarify.
 Thanks.

  • Cancel
  • Kari
    Kari over 10 years ago
    can you post a snippet of your report so we can see what you mean?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kenambo
    kenambo over 10 years ago

    Hi

    This the report i mentioned in my previous post

             http://obrazki.elektroda.pl/6518927400_1428120288.png

    Sorry I dont know how to insert the snap. Please see the URL for the image.

    And can you please explain the terms clearly and how to analyze it completely. I am learning it by myself. Your reply will help me a lot.

    and how to see the timing of the same path before and after CTS.

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 10 years ago
    if you want to see the same path after CTS, you can do report_timing -from -to (using same start/endpoints as the preCTS report). I couldn't see enough of the timing report to answer your other question.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information