failure to compile FPGA example on PCIe-1473R

[dleventhUM]

I am running Windows 10, LabView 2020 32- and 64-bit (32-bit to write FPGA code, 64-bit to execute), PCIe-1473r framegrabber. I have software that ran and compiled in previous versions in LabView built on the 10-Tap 8-bit Camera with DRAM example. I can still run the software in LV 64-bit using previously compiled bitfiles. However, I want to modify it and cannot compile in 32-bit LV any more.

I keep getting error -61499

"Details: An internal software error in the LabVIEW FPGA Module has occurred. Please contact National Instruments technical support at ni.com/support.

Additional information: socketed clip signal could not be assigned to an FPGA signal on the target."

I am using the compile cloud due to the compatibility issues between the Vivado compiler and Windows 10. The compile cloud works fine to compile FPGA code on a PCIe-7852, so it's not the compiler itself. I tried compiling the "10-Tap 8-bit Camera with DRAM" example that came with LV 2020, and that gives the same error when I try to compile my code. I've tried everything on this page: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019M8ESAU&l=en-US (except reinstalling the RIO drivers)

What am I missing? I assume if I can get the example to compile, my code will compile.

[dleventhUM]

so with further investigation, I'm pretty sure it's because Xilinx Compilation Tool for ISE 14.7 is not compatible with Windows 10, but needs to be installed locally to compile the CLIP with the FPGA code, even when using a remote compile server.

Is there a workaround for this other than setting up a Windows 7 machine to do the compiling?

[UliB]

If you have an active software subscription license or service agreement, you could use the NI FPGA Compile Cloud Service.

See: https://www.ni.com/en-us/support/documentation/supplemental/14/compile-faster-with-the-labview-fpga-... 

[dleventhUM]

Thanks for the suggestion. I have done that, and it works to compile FPGA code as long as it doesn't use CLIP.

From: https://www.ni.com/en-us/support/documentation/compatibility/17/labview-fpga-module-compatibility-wi...

"Features Requiring Local Installation of the Xilinx Tools

The following features in the LabVIEW FPGA Module require that the Xilinx compilation tools are installed locally as these features rely on functionality from these tools to work properly. As such, they may be impacted the most from any compatibility issues.

• IP Integration Nodes (IPIN)
• Component Level IP (CLIP)
• Xilinx IP Functions
• Third-Party Simulation using ISIM (ISE) or XSIM (Vivado)
• Project Export for Vivado Design Suite
• Local compilation"

I'm wondering if there's a workaround to create whatever files the compiler would create for the CLIP somewhere else (or maybe find them in a previously compiled version) and move them to the current version? I tried to reconfigure the CLIP (following https://www.ni.com/docs/en-US/bundle/labview-2020-fpga-module/page/lvfpgaconcepts/fpga_clip_tutor_de...), but it throws an error without the compilation tools.

It seems like this can be done on a Windows 7 machine, but then I have to get Windows 7 set up and convince IT to let me put it on the network. Is there any other way to create the CLIP files and add them to the project without doing it on the same machine running the compilation?