--- Quote Start ---
Hi,
So, I m working on top of a third party HDL framework, which is written specifically to be build on Quartus 16.1. It uses some of quartus IPs, (AlteraNative PHY just to name one, generated with Quartus 16.1). The build script organizes all these IPs and other design files, to make necessary quartus files(including qsf file and qpf files) and builds the same.
So my question specifically is,
1) Does building a project with QIPs generated and constrained for Quartus 16.1, cause timing closure to be difficult, building with 16.0?.
The reason for the question, is lack of license support for 16.1, and hence I m evaluating the need for license upgrade, and to conclude that the difference in the quartus versions could be a reason for the timing violation(The same design had easy timing closure with previous version of framework which was constrained for a previous version of Quartus).
Thanks in advance
Jeebu
--- Quote End ---
Generally it is recommended to compile/use the IP generated in a specific version ie 16.1 in same Quartus version 16.1 or newer. If you use the IP with older Quartus version, it might not be compatible.
Best Regards,
bfkstimchan
(This message was posted on behalf of Intel Corporation)
Honored Contributor
