cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
395 Views
Registered: ‎10-21-2018

timing fails during implementation

When i try to generate bitstream, the bitstream is succesfully generated giving a timing failed warning. can someone suggest how to work around it? The timing summary is as given below.timing_summary.png

0 Kudos
3 Replies
Highlighted
Xilinx Employee
Xilinx Employee
364 Views
Registered: ‎05-14-2008

Simple answer: Try different Implementation strategies.

If this does not help, you need to look into the timing path details (go to the "Intra-Clock Paths" category with a red dot in the timing report and check the timing paths details) and analyze why the timing fails on those paths. Based on different issues that result in bad timing, there are different solutions.

You can refer to UG949 for different timing issues and the corresponding solutions.

-vivian

 

-------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------------------------------
如果提供的信息能解决您的问题,请标记为“接受为解决方案”。
如果您认为帖子有帮助,请点击“奖励”。谢谢!
-------------------------------------------------------------------------------------------------
Scholar
Scholar
353 Views
Registered: ‎08-07-2014

@sahithigurram25,

You may also refer to the Xilinx Timing Closure User Guide, UG612.

It will clear up your fundamentals on timing closure.

--------------------------------------------------------------------------------------------------------
FPGA enthusiast!
All PMs will be ignored
--------------------------------------------------------------------------------------------------------
0 Kudos
Highlighted
Teacher
Teacher
348 Views
Registered: ‎07-09-2009

what the tools are trying to tell, is that you code will not work, and if I remember, it will not make a bit file for you .

 

You need to look at the timing rpeorts and the implimentatoin, see if your code has made what you expected it to, and where you can speed things up,

    

having said that, the number one cause I see, is people have more than one clock and clock interactoins they did not realise,

    and the tools are trying to meet all the timming requirments, including those that are not relavent.

        look in the cross clock report,

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos