07-30-2020 04:38 AM
I am designing a custom IP for which I am writing, right now, a new version.
Last tested version is the 5.0, while the one I am modifying is the 6.0.
The 5.0 version is already in use by a project, but now Vivado claims that I should upgrade the IP to the newer version 6.0. Also, it locks my 5.0 version IP.
How can I remove this annoying option ? I want to freely use my 5.0 version in my project and I want to be able to decide which version to use, not Vivado choosing for me..
07-30-2020 04:54 AM
It looks you are making both the versions available to Vivado , so by default tool prompts for upgrade.
One option is you can make only 5.0 available and switch the repo path to 6.0 only when needed. Does this work for you ?
08-05-2020 04:09 AM - edited 08-05-2020 05:55 AM
I am sorry if I will be a little be rude, but the software tool for custom IP customization is a huge pain (2019.2).
Most of the times the custom IP is not correctly refreshed and needs to be packaged again.
Many times the AXI interfaces names are renamed from upper case to lowercase, which leads to doubly associated clocks warnings. Must to waste more time to renaming or deleting old upper case references.
In case of having multiple versions of the same IP, even disabling most recent versions from IP catalog Vivado still claims that he wants the most recent one.
That said, the custom IP package handling it's full of bugs due to tasks synchronization issues, what makes the experience very frustrating and time wasting while working with this IDE.
And I am sure I am not the only one thinking this about it.