Home > Community > Forums > Digital Implementation > Reading noise dealy report

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

 Reading noise dealy report 

Last post Wed, Feb 27 2013 6:55 AM by Kari. 1 replies.
Started by Ganga111AtFPS 13 Sep 2012 12:02 AM. Topic has 1 replies and 779 views
Page 1 of 1 (2 items)
Sort Posts:
  • Thu, Sep 13 2012 12:02 AM

    • Ganga111AtFPS
    • Top 500 Contributor
    • Joined on Fri, Jun 29 2012
    • Hyderabad, Andhra Pradesh
    • Posts 21
    • Points 545
    Reading noise dealy report Reply

    Hi all,

     Can any body explain how to analyse the following report.

    I got this report after running xtalk in ETS.

    ********************************************************************************
            Noise Delay Report
            Generated: Tue Sep 13 01:12:14 2011
    ********************************************************************************

    Report Options:
    --------------------------------------------------------------------------------
    Slack     : yes
    Delay     : max
    Sort by   : absolute delay
    Threshold : 10 (ps)
    --------------------------------------------------------------------------------
    Type   Uncertainty(ps)  Delay(NomMax/Max)      VictimNet
    R           295.524     616.136/911.661      tri_des_B/des3/u0/u2/p0694A:A1N {tri_des_B/des3/u0/n_676}

    Constituents:
          Offset(ps) Slew(ps) Xcap(fF)  Edge  Net
    Cpl:  4815.010   599.693    2.594     F   ~tri_des_B/des3/u0/n_676
    Cpl:  5789.055   195.862    1.625     F   tri_des_B/des3/u0/n_672
     

    Thanks in advance.

    Filed under:
    • Post Points: 20
  • Wed, Feb 27 2013 6:55 AM

    • Kari
    • Top 10 Contributor
    • Joined on Tue, Jul 15 2008
    • Cary, NC
    • Posts 690
    • Points 13,980
    Re: Reading noise dealy report Reply

    You can see that the victim net is labeled ( tri_des_B/des3/u0/n_676). 

    To find the agressor net(s), look at the "constituents" section. The agressor net is  tri_des_B/des3/u0/n_672. If you have a glitch or noise-on-delay for your victim net, this agressor is the one you want to separate it from. Likely, these two nets have a long parallel run. The "net" that matches the victim, but has a ~ in front of it, is all the other little things in the design that add up to SI effects, so it's not a real net you can look at in the design. Just address the real aggressor and you should be able to fix the SI problem.

    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by Ganga111AtFPS at 13 Sep 2012 12:02 AM. Topic has 1 replies.