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

Vivado Timing - get_timing_paths returns more paths than report_timing_summary reports


In my timing summary report there are 460012 TNS Total Endpoints.

If I do an llength [get_timing_paths -nworst 1 -max_paths <very_large_number>],  there are 460014 timing paths returned.


What is the reason for this inconsistency?


In this example, there are two endpoints that are reached by two clocks, hence they have paths in multiple path groups.

In report_timing_summary, each endpoint is counted only once when reporting the design level metrics. 

In report_timing/get_timing_paths, paths are reported per path group. 

So multiple paths are reported to each of the above endpoints.

AR# 57018
Date Created 08/06/2013
Last Updated 01/21/2015
Status Active
Type General Article
  • Vivado Design Suite