Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13035
  • 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

Reading noise dealy report

Ganga111AtFPS

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.

Parents

  • 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.

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.

Children
No Data

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.