Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Visitor
czahner
Posts: 3
Registered: ‎05-01-2012
0

Generate Post-Place & Route Static Timing fails without reason.

I am attempting to run the Generate Post-Place & Route Static Timing process. Every process up to that point completes successfully.  Here is the output from running the Generate Post-Place & Route Static Timing process:

 

Started : "Generate Post-Place & Route Static Timing".
Running trce...
Command Line: trce -intstyle ise -v 3 -s 3 -n 3 -fastpaths -xml XC6SLX150.twx XC6SLX150.ncd -o XC6SLX150.twr XC6SLX150.pcf -ucf XC6SLX150.ucf
Loading device for application Rf_Device from file '6slx150.nph' in environment
/opt/Xilinx/13.1/ISE_DS/ISE/.
   "XC6SLX150" is an NCD, version 3.2, device xc6slx150, package fgg676, speed
-3

Analysis completed Tue May  1 10:30:03 2012
--------------------------------------------------------------------------------

Generating Report ...

Number of warnings: 0
Total time: 9 secs 

Process "Generate Post-Place & Route Static Timing" failed

 After looking at this post, I verified my .xpi file contents:

 

PROGRAM=PAR
STATE=ROUTED
TIMESPECS_MET=YES

 Does anyone have further advice on how to get this process to complete?

 

 

Visitor
czahner
Posts: 3
Registered: ‎05-01-2012
0

Re: Generate Post-Place & Route Static Timing fails without reason.

Also, the FPGA is a Spartan-6. The OS is Red Hat.
Xilinx Employee
bwade
Posts: 609
Registered: ‎07-01-2008
0

Re: Generate Post-Place & Route Static Timing fails without reason.

I suggest that you take this question to the Timing Analysis forum which covers TRCE issues.

Moderator
endab
Posts: 149
Registered: ‎11-06-2007
0

Re: Generate Post-Place & Route Static Timing fails without reason.

What happens if you run TRCE from command line? You can more information on this in the the command line reference guide page 177.
http://www.xilinx.com/support/documentation/sw_manuals/xilinx13_4/devref.pdf