11-20-2014 04:13 AM
While loosley following the MicroZED chronicles I have been trying to get the XADC up and running.
I get the following error(when running the "Generate Block Design using Vivado 2014.2) and have no idea what it means or why I would get an error
[Ipptcl 7-5] XIT evaluation error: File writer encountered an error: c:/Xilinx/Vivado/2014.2/examples/Vivado_Tutorial/Projects/microzed_project_1/microzed_project_1.srcs/sources_1/bd/microzed_project_1/ip/microzed_project_1_xadc_wiz_0_0/interrupt_control_v2_01_a/hdl/src/vhdl/microzed_project_1_xadc_wiz_0_0_interrupt_control.vhd
I then get other errors like:
"[IP_Flow 19-1747] Failed to deliver file 'c:/Xilinx/Vivado/2014.2/data/ip/xilinx/xadc_wiz_v3_0/ttcl/interrupt_control_vhd.ttcl': ERROR: [Common 17-39] 'xit::puts_ipfile' failed due to earlier errors."
Which I guess is because of the first error.
If anyone could shed some light it would be much appreciated.
11-20-2014 04:44 AM
11-20-2014 05:20 AM
Thanks for responding ... but I don't think the link you sent is relevant. The link has the same error message but thats all. The error gives no information what so ever. Xilinx should want to sort issues like this so that the tool doesn't give useless error messages!(In an ideal world all errors would be handled correctly with reasons for why it has failed)
All my connections appear to similar widths, it has passed the "Validate design" check. I really am stuck.
It also produces the same error when I follow the MicroZed chronicles exactly. However I get 2 critical warnings, one about asynchrnous resets could lead to problems meeting timing and also about the unconnected net. See image attachment:
p.s. The reason I started playing around(i.e. not following the chronicles exactly) was because I was getting warnings that seem correct. I then added a reset block. But it all seems unrelated.
11-20-2014 10:19 AM - edited 11-20-2014 10:22 AM
The error happens due to large path size
Check below links and try the suggestions
11-21-2014 01:28 AM
I'm using Vivado 2014.2 has this been fixed in 2014.3?
It makes sense, as I started again and did the same design slightly differently and it all worked. I guess I used slightly shorter names.
IMO Vivado should, at the very least, check to see the file path length and notify the user that it has failed because the character length was too long.
11-21-2014 01:53 AM
Actually it is windows issue, not vivado and Vivado will give error on path length generally.
11-21-2014 07:57 AM
Really sorry to labour this point. I accept it is a Windows issue/limitation that is the root cause. But in my case I never got error messages about the file path length. It just stopped writing the file.
Therefore I had to spend time coming onto this forum to ask, you very helpful people, if you could shed any light on the issue.
Surely it would be better for Xilinx's reputation that it handles errors(knowing that it is a limitaion of Windows) like this better.
Time is money for most people, so the more user friendly a product is the better.