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

2014.3 Partial Reconfiguration - The initial configuration does not analyze the paths that are analyzed in the second configuration, which cause the timing violation


In my Partial Reconfiguration design, there are no timing violations in the initial configuration.

But in the second configuration, some timing violations occur on the interface paths, which are not analyzed in the initial configuration.  


This can occur when the loads of the static logic in the Reconfigurable Module (RM) are constant during the initial configuration, so the paths from static logic to constant in RM are not analyzed.
Because they are not analyzed in the initial configuration, the placement/routing of these paths is very poor and the static region uses too much of the interface budget.
When they are analyzed in the second configuration, all placement/routing is locked, and there is nothing the tools can do to fix the failing paths.
This issue is fixed in Vivado 2015.1.
AR# 63850
Date 03/23/2015
Status Active
Type General Article
  • Vivado Design Suite - 2014.3