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

Vivado Constraints - Vivado GUI out of memory crash when opening DCP saved after phys_opt_design due to wildcards expansion in XDC constraints


If your original XDC constraints use wildcards, phys_opt_design might not preserve the wildcards when writing out a checkpoint.

Instead, the wildcards in the constraints are expanded, which causes a much larger XDC file in the DCP. 

A use case has been found where wildcards used with -match_style ucf will cause the expansion.

This can lead to much more memory being required to open the .dcp than was originally required to process the design and constraints.

This can cause an issue in some cases in Vivado 2012.4 where when trying to open the post_route.dcp, Vivado tools will crash with a GUI memory related error.

The post_route.dcp can be opened in 2013.1. 


This is planned to be fixed in a future release.

Until this is fixed, the work-around is to avoid using "match_style ucf" and to evaluate the constraints to see if any constraints with wildcards are being expanded further than expected.

The following is an example constraint that is causing this issue:

set_multicycle_path -setup -start -from [get_pins {*CmdBurstCntY[*]/C} -hierarchical] -to [get_pins -match_style ucf "i_TopDDR3Ctrl_1/*"] 2

The issue was overcome by modifying this constraint to:

set_multicycle_path -setup -start -from [get_cells * -hierarchical -filter {NAME =~ *CmdBurstCntY[*]}] -to [get_cells * -hierarchical -filter {NAME =~ i_TopDDR3Ctrl_1/*}] 2

AR# 55052
Date 10/13/2014
Status Active
Type Known Issues
  • Vivado Design Suite
Page Bookmarked