06-12-2014 03:44 PM
So, I take the 2 TCL files created with 2014.1 (project and top-levle BD), and I am using to rebuild a project with VIVADO 2014.2.
Sounds like straight-forward task, so before I did this, I reloaded this project in GUI and wrote both TCL files. Then ran a Linux meld, and the BD is identical.
After I solved an error from the previous posting, I get the following error, see further.
The question is obvious, and I would like some to please explain to me in simple words what do I need to do. Don't just send me a link to the UG doc! I don't always have time to RTFM when a new tool comes out, yet not all docs are updated to 2014.2 release.
Attached is the BD tcl file. Thanks in advance for the help. Prompt response will be appreciated and kudoed.
# # Restore current instance
# current_bd_instance $oldCurInst
# create_root_design ""
ERROR: [BD 5-216] VLNV <www.ignisinnovation.com:user:arches_udp_ip:2.0> is not supported for this version of the tools.
ERROR: [Common 17-39] 'create_bd_cell' failed due to earlier errors.
"create_bd_cell -type ip -vlnv www.ignisinnovation.com:user:arches_udp_ip:2.0 inst_arches_udp_ip "
(procedure "create_root_design" line 123)
invoked from within
(file "./system_bd_eclipse.tcl" line 857)
06-12-2014 09:31 PM - edited 06-12-2014 09:32 PM
Is this your custom IP?
Did you make sure you add the custom IP to the IP repositories for vivado 2014.2?
In this case Vivado is not finding this specific IP in the IP repository and so you see this issue.
Can you add the custom IP to the IP repository?
06-13-2014 08:37 AM
This particular error turned out to be my TCL bug. Everything I do stored in a namespace, and the call to the namespace was incorrect.
Once I fixed it, I only had to clean up the errors of the drivers from my previous postings.
Sorry about that
06-15-2014 09:13 PM
Thanks for sharing the solution.
Please close this thread by marking the answer.
09-18-2014 10:02 PM
I met the same problem as yours, but I am still not clear about how you fix the issue after reading your reply. Could you please give an example? Thanks
09-19-2014 06:34 AM
It has been 3 months now, so you have to refresh my memory :o)
What exactly is the problem you are having?
04-08-2015 09:37 AM
I got exactly this error when I forgot to change the part number in my project setup tcl script. It seems if your block diagram is created for a different 7-Series part it will throw this misleading error message.
Check your part type. :-)
04-08-2015 11:51 AM
04-08-2015 02:29 PM