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

2013.1 - Vivado Timing - report_timing causes Vivado to crash

Description

When I open my synthesized design and run a standard report_timing command:

report_timing -delay_type min_max -max_paths 10 -sort_by group -input_pins -name timing_1

The following crash occurs:

#
# An unexpected error has occurred (11)
#
Stack:
<stack details>

Solution

This crash was caused by a set_input_delay constraint without an associated clock on an I/O port combined with a max_delay constraint on the same port. If a clock is not specified in a set_input_delay constraint, the tools are generally able to find the right clock and do this for you, but when there is a max_delay constraint on the same port, this causes a crash.

The crash is targeted to be resolved in the 2013.2 release. In the meantime, the workaround for this is to create a virtual clock to associate with the set_input_delay constraint.
AR# 55814
Date Created 05/01/2013
Last Updated 08/06/2013
Status Active
Type General Article
Tools
  • Vivado Design Suite