12-16-2013 07:50 AM
I am currently trying to run an implementation on my design.
Everything completes with out errors until I get to the Post Route Timing Summary Which gives me a critical Warning:
CRITICAL WARNING: [Route 35-39] The design did not meet timing requirements. Please run report_timing_summary for detailed reports.
Resolution: Verify that the timing was met or had small violations at all previous steps (synthesis, placement, power_opt, and phys_opt). Run report_timing_summary and analyze individual timing paths.
INFO: [Route 35-253] TNS is the sum of the worst slack violation on every endpoint in the design. Review the paths with the biggestWNS violations in the timing reports and modify your constraints or your design to improve both WNS and TNS.
INFO: [Route 35-20] Post Routing Timing Summary | WNS=-1.631 | TNS=-4.033 | WHS=-0.547 | THS=-1.767 |
So I know that My design is not meeting timing spec.
When I go back and look through the synthesis, place and opt and phys_opt they all complete successfully.
Then when I finally get to the timing summary analysis it will take around 9-10 hours to complete.
The Implementation process gets stuck on this part.
INFO: [Timing 38-91] UpdateTimingParams: Speed grade: -1, Delay Type: min_max, Constraints type: SDC.
INFO: [Timing 38-191] Multithreading enabled for timing update using a maximum of 8 CPUs
To invoke the timing Summary I am using all of the default values and only specifying the output log file for the timing report.
Is there anyway to speed up the timing analysis and summary portion of the implementation process?
12-16-2013 08:22 AM
12-16-2013 08:00 AM
12-16-2013 08:19 AM
So I need to run the implementation without the timing analysis and then when that finishes I can run the the timing analysis seperately and that should run In a better time?
Or do I have to upgrade to 2013.4 in order to get past the long run time for the timing summary ?
12-16-2013 08:22 AM