UPGRADE YOUR BROWSER

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

Vivado IP Flows - Can I get debug information on what report_ip_status is doing?

Description

Sometimes the report_ip_status command takes more time than expected to complete.

It is not clear if it is a network issue, a license check issue, a problem with the IP core or something else. 

Is there an option to get more information about what is happening during the report_ip_status command?

Solution

In Vivado 2016.1 a parameter has been added to report runtime messages for report_ip_status.

The parameter name is:

ips.ipStatusDebugMsgs
.

The debug messages for report_ip_status will start with "IP_STATUS" and give runtimes for the report_ip_status processing steps.

For example:

set_param ips.ipStatusDebugMsgs 1

report_ip_status
INFO: [IP_Flow 19-4732] IP_STATUS: IP char_fifo; time to refreshLock(): 0.000000 seconds
INFO: [IP_Flow 19-4731] IP_STATUS: IP char_fifo; time to collect data: 0.010000 seconds
INFO: [IP_Flow 19-4732] IP_STATUS: IP clk_core; time to refreshLock(): 0.000000 seconds
INFO: [IP_Flow 19-4731] IP_STATUS: IP clk_core; time to collect data: 0.010000 seconds
INFO: [IP_Flow 19-4734] IP_STATUS: time to generate revision-only upgrade groups: 0.000000 seconds
INFO: [IP_Flow 19-4735] IP_STATUS: time to populateReport(): 0.000000 seconds
INFO: [IP_Flow 19-4736] IP_STATUS: total time taken for reportIPStatus(): 0.150000 seconds

AR# 66112
Date Created 12/04/2015
Last Updated 04/13/2016
Status Active
Type General Article
Tools
  • Vivado Design Suite