You are not logged in.
When I was generating the bistream for the WARPLab reference design from http://warp.rice.edu/bigFiles/WARPLab_R … PGAv2.zip, the bitstream failed to be generated due to some time constraints not met:
xflow done! touch __xps/system_routed xilperl C:/Xilinx/11.1/EDK/data/fpga_impl/observe_par.pl -error yes implementation/system.par Analyzing implementation/system.par ******************************************************************************** ERROR: 1 constraint not met. PAR could not meet all timing constraints. A bitstream will not be generated. To disable the PAR timing check: 1> Disable the "Treat timing closure failure as error" option from the Project Options dialog in XPS. OR 2> Type following at the XPS prompt: XPS% xset enable_par_timing_error 0 ******************************************************************************** ******************************************************************************** ERROR: 1 constraint not met. PAR could not meet all timing constraints. A bitstream will not be generated. To disable the PAR timing check: 1> Disable the "Treat timing closure failure as error" option from the Project Options dialog in XPS. OR 2> Type following at the XPS prompt: XPS% xset enable_par_timing_error 0 ******************************************************************************** make: *** [implementation/system.bit] Error 2
Although this error can be removed by disable the "Treat timing closure failure as error" option from the Project Options dialog in XPS, I still keep worrying about if this time constraints error can impact the real time transceiver experiment.
I am not sure if Murphy had ever met this problem in XPS 10.1, as I am using XPS 11.5 to synthesize this project.
Thanks.
Offline
It depends which constraint failed. There's a timing report in the log above what you posted that highlights which constraint PAR couldn't meet.
Offline