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# 41455

ISE SmartXplorer - Timing score reported by SmartXplorer is different with that in the PAR report.


In some cases, when I run SmartXplorer, the Timing Score reported is not zero.

However, after I copy the results and re-run the Place and Route (PAR) flow, the timing score in the PAR report (*.par) is zero.


The reason for this difference is that the timing score reported in SmartXplorer is coming from the timing report (*.twr), not from the PAR result.

The unconstrained timing report may include hold errors that are not explicitly covered by user timing constraints. 

For more information on this issue, pleas see (Xilinx Answer 37292) 


If you set the -u switch for trace, and there is a timing error in unconstrained paths, SmartXplorer will report a different timing score than the PAR result.


This issue also occurs when the -a switch is used in the trace options (-to) for the SmartXplorer command.

If you remove the -a switch then the correct timing score is reported in the SmartXplorer Summary.

AR# 41455
Date Created 03/25/2011
Last Updated 02/24/2015
Status Active
Type General Article
  • FPGA Device Families
  • ISE Design Suite