From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

IP Builder Error

Solved!
Go to solution

Using IP builder for NI 7932R and cRIO-9068 yields the same result, independent of the VI that I select. I've tried with a simple VI that connects a constant to an indicator and the result is the same. The quick estimate always works fine. I have tested this on 2 separate VMs that run LabVIEW 2015 sp1 with the Vivado 2014.4 tools.

 

This is what the summary says:

 

An error occurred in the build. FPGA IP Builder: Internal error returned from Xilinx fuse. Contact National Instruments for technical support.

 

 

The last part of the log report reads as follows:

 

Compiling architecture structural of entity xil_defaultlib.m319c0140_toph [m319c0140_toph]

gcc.exe: Internal error: Aborted (program collect2)

Please submit a full bug report. See <URL:http://www.mingw.org/bugs.shtml> for instructions.

 

An error occurred in the build. Internal error returned from Xilinx fuse. Contact National Instruments for technical support.

Javier Ruiz - Partner at JKI
jki.net
vipm.io
0 Kudos
Message 1 of 5
(4,823 Views)

Hi jarcTek,

Does this problem happen with any FPGA VI, or only those under the IP Builder? What operating system is this happening on and are the Vivado 2014.4 tools installed locally on that system? That error message can occur on systems where the Vivado Compilation Tools are not supported, such as Windows 8 or Windows 10. 
http://www.ni.com/white-paper/52818/en/
http://www.ni.com/white-paper/14281/en/

If you have access to it, could you try the Cloud Compiler and see if that works properly for you? This will take your local installation of the Vivado 2014.4 Compilation Tools out of the equation so we can see if there might be another potential issue.
http://www.ni.com/white-paper/52328/en/ 

Charlie J.
National Instruments
0 Kudos
Message 2 of 5
(4,782 Views)

Thank you for your reply Charlie.

 

We are using Windows 10, so that might be the issue. I am surprised that the Xilinx Comile Tools installer would let me install even if it is known that Windows 10 is not supported. The problem seems to happen only with IP Builder, which is using the local compile tools. Is there a way to redirect IP Builder compilations to use the Cloud Compile Tools?

 

Thanks,

Javier Ruiz - Partner at JKI
jki.net
vipm.io
0 Kudos
Message 3 of 5
(4,773 Views)
Solution
Accepted by topic author jarcTek

Hi jarcTek,

I just double-checked with a colleague, and it turns out the IP Builder has to use local compile tools and will not work with Cloud Compile or a Compile Server. That being said, your normal compilations outside of Component-Level IP or the IP Builder should work with Cloud Compile. 

For the IP Builder, I would recommend installing on a Windows 7 Virtual Machine just to confirm that this is the problem you are encountering. If so, you will unfortunately need to downgrade or keep a system/VM which can run the IP Builder around.

The Compilation Tools support is due to the fact that the Xilinx Compiler we use does not support Windows 8 or 10. I am not sure why we don't have the installer throw a warning, but the installer may not check what operating system it is running on, unfortunately, and therefore could not warn you.
http://digital.ni.com/public.nsf/allkb/8FDE6923DA3C069786257A36005C3EEF

Charlie J.
National Instruments
0 Kudos
Message 4 of 5
(4,768 Views)

Thanks Charlie for the reply.

 

Javier Ruiz - Partner at JKI
jki.net
vipm.io
0 Kudos
Message 5 of 5
(4,752 Views)