We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 1628

11.1 Known Issue - PAR, Timing - The timing portion of a ".par" report and delays in the ".dly" report appear to conflict


When I run PAR and look at the timing statistics in the PAR report (.par), there are a large number of long pin delays. However, when I look in the delay report (.dly), there are only a short list of delays that do not seem to match up.

What does the large list of pin delays indicate? Why is there a difference between the pin delays in the ".par" report and the net delays in the ".dly" report?


The timing result overviews in these files differ because each file contains timing information related to either pin delay (from the PAR report) or net delay (from the delay report).

The ".par" results file is connection-based or pin-based, as is stated in the header for that portion of the report. This report includes each driver-to-load connection. If a net has a fanout of 10 (10 loads for one driver) that are in a given range of delay, the PAR report counts all 10 in its delay statistics.

By contrast, for the same net, the ".dly" file indicates that only one net has a delay in the same range. The reported value for this net is the longest delay path for the one net; this is the worst path of the 10 possible paths for this net.

AR# 1628
日期 12/15/2012
状态 Active
Type 综合文章
  • ISE - 10.1
  • ISE Design Suite - 11.1
  • ISE Design Suite - 11.2
  • More
  • ISE Design Suite - 11.3
  • ISE Design Suite - 11.4
  • Less