Home > Community > Forums > Logic Design > using RTL Compiler as Static Timing Analysis

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: *

 using RTL Compiler as Static Timing Analysis 

Last post Wed, Nov 29 2006 2:34 PM by archive. 6 replies.
Started by archive 29 Nov 2006 02:34 PM. Topic has 6 replies and 2694 views
Page 1 of 1 (7 items)
Sort Posts:
  • Wed, Nov 29 2006 2:34 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    using RTL Compiler as Static Timing Analysis Reply

    I set up the libraries, read the netlist, read the SDC. Now I want to access the paths which are unconstrained. But I cannot find a corresponding command. Is it possible to generate the list of unconstrained paths using "report timing" command?


    Originally posted in cdnusers.org by sporadic crash
    • Post Points: 0
  • Thu, Nov 30 2006 1:36 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    Hi,
    The command "report timing -lint -verbose" will give you all unconstrained input and outputs.


    Originally posted in cdnusers.org by Stalker
    • Post Points: 0
  • Mon, Dec 11 2006 12:17 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    Thank you very much for the kind info.


    Originally posted in cdnusers.org by sporadic crash
    • Post Points: 0
  • Thu, Jan 4 2007 12:03 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    Additional question regarding this issue:

    Maybe it will be ridiculuous to ask, but does setting cost groups/path groups in the flow stated in the first posting of this thread (ie. setup lib, read netlist, read SDC, gen reports) have effect on the timing results?

    Does the timing analyzer engine in RC take cost/path groups into account?


    Originally posted in cdnusers.org by sporadic crash
    • Post Points: 0
  • Sat, Jan 6 2007 9:36 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    I put my question other words:

    when I use RC as an STA Tool, does the change of cost/path groups in a design have an effect on timing analysis calculations? For ex:
    1. setup lib, read netlist, read SDC
    2. define a cost/path group setting
    3. report_timing
    4. change cost/path groups
    5. report_timing

    Can the timing analyzer inside RC called by report_timing generate different results? Does any change on cost/path groups change the behavior of analysis?

    Please note that I DON'T USE RC for synthesis but for [b]static timing analysis[/b].


    Originally posted in cdnusers.org by sporadic crash
    • Post Points: 0
  • Fri, Jan 19 2007 7:48 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    Greetings Sporadic Crash, as far as I know, cost groups should have no effect on delay calculation. Cost groups serve two main purposes in my mind: + guide the optimization engine when a slow memory or part of the logic is affecting the targets for the whole design + for reporting purposes if you need to categorize based on some criteria good luck, G-


    Originally posted in cdnusers.org by grasshopper
    • Post Points: 0
  • Tue, Jan 23 2007 10:59 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: using RTL Compiler as Static Timing Analysis Reply

    One of the thing that happen when you create path groups is that a path that used to be reported in a default group is not anymore so the path orders might be different but if you do a report_timing point to point it should still be the same before and after just the group might be different.


    Originally posted in cdnusers.org by evenditti
    • Post Points: 0
Page 1 of 1 (7 items)
Sort Posts:
Started by archive at 29 Nov 2006 02:34 PM. Topic has 6 replies.