Compilation Error in LabVIEW FPGA

[Marvin9]

During compilation with LabVIEW 2016 and Vivado 2015.4 compilation tool error shows up with the smartheap library. It shows out of memory. Also asks to free up some memory before continuing.

[Marvin9]

The same code compiles just fine with both LabVIEW 2015 32 bit and LabVIEW 2015 SP1 32bit. It just does not compile properly with LabVIEW 2016 32 bit with latest Vivado compilation tool. Anybody know why this might be the case?

[lagelian]

Hi Marvin9, 

What is your OS? What device are you compiling onto? 

Angela L.

[Marvin9]

The operating system is Windows 7 Enterprise. The hardware is NI cRIO 9039 with some c series modules.

[lagelian]

- Have you tried compiling using the NI Cloud Compile Service? It will offload your FPGA to a different server so you shouldn't experience any issues with compilation 

- Are you able to compile example code? 

- There aren't many known issues of code being able to compile in 2015 but not 2016..could you possibly attach a screenshot of the exact smartheap error you are seeing? Another option is to attach your code and see if we are able to reproduce the error on our end. 

Angela L.

[natasftw]

Is this during the intermediate steps or the longer compile process?

Do you see the same behavior with just an empty VI?

[Marvin9]

smaller and medium size codes compile properly with LabVIEW 2016. Any code little more than medium size does not compile. It shows out-of-memory at the synthesis step.

I tried to compile on the cloud it did not work. I ran a code compilation on the cloud with LabVIEW 2016 for 11 hours and it stayed stuck on the synthesis step. This same code took about 3 hours with local compiler and LabVIEW 2015.

[lagelian]

That's interesting. I wonder if there's a difference between the Xilinx Compilation Tool versions that isn't allowing the compilation. Are you compiling on an 64-bit OS? 

[Marvin9]

Yes its a 64 bit Windows 7 Enterprise with 16 GB of memory.

[Marvin9]

Anybody has any idea why LabVIEW 2016 compilation tool would fail to compile the same code easily compiled with LabVIEW 2015.