12-07-2018 06:23 AM
I am just trying to re-package a custom IP after some changes. Unfortunately for this specific IP, we don't have a packaging TCL script so I tried using the IP-Packager GUI... I finally managed to re-package my IP but I have my doubts about this crappy piece of software.
1. If Press "Ports and Interfaces > Merge changes from Ports and Interface Wizards" while some file paths in "File groups" are not correct, Vivado crashes fatally and without any exception message.
--> If files are missing, I expect an error message and not just a silent disappearance of the whole Vivado environment.
2. Okay, so I fixed the file paths first and did "Ports and Interface > Merge changes from Ports and Interface Wizard" afterwards. This crashed on the first try but on the second one it worked. Does not look like stable sotware, but hey, it worked...
The only thing I don't understand: All files outside the IP-Directory we are referencing using relative paths are removed from File Groups.
--> Why? I don't see why "File Groups" are even touched if I only update ports according to the VHDL code...
3. Okay, so I added the missing file back again. By accident I created a new file group instead of a file, so I wanted to delete this empty file-group I don't use. And guess what... Again Vivado crashed and disappeared without any message.
--> Obviously deleting empty file groups does not work
As written, after some try-and-error I could get my IP packaged. But why is this GUI so buggy? I mean, we are living in 2018 and exception handling was invented some years ago to handle expected and unexpected exceptions in Software gracefully... Why not in Vivado?
I could accept the bad quality in the first years of Vivado, it's a complex tool so some problems are expected. But I would expect the quality of this tool to increase. Unfortunately I feel the inverse...
Dear Xilinx... really, software quality is an issue... REALLY!
12-12-2018 10:50 AM
Sorry you're having issues with the IP Packager in Vivado.
Could you tell me what version of Vivado you are using and if you've referenced any user guides?
Generally crashes produce log files like hs_err_pid#####.log, could you attach one that's generated? It'll be in the directly where Vivado was launched, if it was launches on Windows from the Start Menu, it'll be in the %APPDATA%/Xilinx/Vivado
12-13-2018 12:52 AM
Attached you can find the .log files and additionally the .dmp files because the log-files do not contain any information.
I appreciate that you request the log-files to fix the problem in the tool.
However, I would even more appreciate it if Xilinx could fix the problems in their development process for Vivado. We experience similar issues quite often with Vivado in general. For me this does not look like the process in place produces acceptable software quality.
BTW: Your forum does not accept uploading *.dmp files produced by Vivado on crashes... I guess it would make sense to enable all file-types produced by Vivado.
12-13-2018 08:41 AM
Thanks for the logs. This is quite helpful. To make sure I can reproduce it could you tell me what version of Vivado you're using, and provide the vivado.log and vivado.jou files. Once I'm able to reproduce I can send the issue to engineering to begin fixing it for the next release.
02-06-2019 07:15 AM
02-06-2019 11:11 PM
I provided all the information to reproduce the issue (see #1 of my initial post):
- In IP-Packager, add some wrong paths to the "File groups" (in my case it was a path to VHDL design files)
- Change some of the VHDL files in the IP core (e.g. add a port)
- Execute ther "Merge changes from Ports and Interfaces" Wizzard
So what additional information do you expect? Shall I provide the VHDL file to package?