If I add debug cores to a design in Vivado, the design has the potential to error out due to the 260-character path limit.
For example, if I am working in the Vivado 2012.2 tools on the example MIG DDR3 design targeting a Virtex-7 device, the following error occurs when I add the "debug core" to my design :
Implementing also fails at the beginning of the implementation flow.
Why is this happening?
Windows has a 260-character limit on path lengths and when the Debug Core is inserted, Vivado generates the extra hierarchy, causing the path to exceed 260 characters.
There are several ways to work around this issue:
In the Vivado 2012.3 tools, the path length of the Debug IP was significantly reduced to help avoid this Windows path length issue.
See also: (Xilinx Answer 52787)