Solved: Mixing Vivado versions for IP Packager

legendbb · ‎04-18-2018

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,

tedbooth · ‎04-19-2018

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.

Ted Booth - Tech. Lead FPGA Design Engineer
www.designlinxhs.com

syedz · ‎04-18-2018

@legendbb,

I just tried packaging IP in 2017.4 and used the IP in 2016.4 and it worked.

--Syed

---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------

tedbooth · ‎04-19-2018

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.

Ted Booth - Tech. Lead FPGA Design Engineer
www.designlinxhs.com

Mixing Vivado versions for IP Packager

Re: Mixing Vivado versions for IP Packager

Re: Mixing Vivado versions for IP Packager

Re: Mixing Vivado versions for IP Packager