04-18-2018 12:18 PM
I have some IPs created in 2017.1, and deployed in projects in 2017.3, don't see ip lock icon after IP upgrades.
I am able to edit IP in either 2017.1 and 2017.3, haven't seen any issue yet, for projects both in 2017.1 and 2017.3.
Now I'd like to try 2018.1. If I repack my IP in 2018.1. Can it still be used in project in earlier versions of Vivado?
I know I can test out myself, but appreciate any comments for this practice.
Thanks,
04-19-2018 06:44 AM
I don't see any issues as long as your custom IP is pure HDL. If you use any Xilinx IP in the custom IP, then you could have problems moving between versions of Vivado.
04-18-2018 09:03 PM
I just tried packaging IP in 2017.4 and used the IP in 2016.4 and it worked.
--Syed
04-19-2018 06:44 AM
I don't see any issues as long as your custom IP is pure HDL. If you use any Xilinx IP in the custom IP, then you could have problems moving between versions of Vivado.