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

Vivado 2013.3 set_max_delay constraint not being applied correctly when used in Out of Context (OOC) flow


When creating an OOC workflow, the set_max_delay constraint set in the DCP is not being retained correctly in the Top module.

If the set_max_delay value is larger than the clock period, then the value is dropped and the clock period is used for the path instead.


The timing system should not change the value of a constraint when a conflict occurs.

The issue is fixed in the 2014.4 release.

AR# 58210
Date 03/26/2015
Status Active
Type General Article
  • Artix-7
  • Kintex-7
  • Virtex-7
  • Vivado Design Suite - 2013.3
Page Bookmarked