07-12-2023 02:06 PM
There have been topics over the years about LabVIEW FPGA Compilers not working. One common theme was that there were issues using the local compiler server on Window10 PCs.
I'm trying to compile for the cRIO-9040 FPGA. I'm running LabView 2022 Q3. I have LabVIEW FPGA Module (32-bit) for 2022 Q3, and LabVIEW FPGA Compilation Tool for Vivado 2021.1 (Ver 2022 Q3) installed. I get the same errors that many have already received (see attached photos).
Are there still issues using the local compile server with Windows 10?
Solved! Go to Solution.
07-12-2023 02:22 PM
You mention installing LabVIEW FPGA Compilation Tool for Vivado 2021.1 but the configuration is looking for Vivado 2019.1
07-12-2023 02:24 PM - edited 07-12-2023 02:26 PM
So you are saying this isn't a case of the most recent tool has all the previous updates rolled into it?
I'll try anything at this point.
07-12-2023 02:48 PM
Not sure how the config was setup but that is what I see from your images.
07-12-2023 02:53 PM
I don't ever remember being asked what tool to use, but 2019.1 is the one it wanted. (Installing 2019.1 required I reboot my PC.) Anyway it's compiling now.
A couple people told me to download the latest tool which is 2021.1. Obviously it is not just a rollup of earlier versions.
Thanks for assist.
07-13-2023 07:46 AM
@stgislander wrote:
I don't ever remember being asked what tool to use, but 2019.1 is the one it wanted. (Installing 2019.1 required I reboot my PC.) Anyway it's compiling now.
A couple people told me to download the latest tool which is 2021.1. Obviously it is not just a rollup of earlier versions.
Thanks for assist.
The Vivado version is (automatically) based on a combination of LabVIEW version and product.
https://www.ni.com/en-us/support/documentation/compatibility/19/compatibility-between-xilinx-compila... has this information. The drop-downs are empty (I reported the issue yesterday).
Not sure why in your case it went for Vivado 2019.1. Your version of LabVIEW is reported as 2022Q3.
I typically install using NI Package Manager and that typically knows to put in the right Vivado version.