FPGA: Xilinx Versions supported by Linux Version

[T-REX$]

Hi Reinhard,

There's quite a lot of information here for me to catch up on, so forgive me if you've already tried this, or my understanding of the situation is incomplete. I'm not sure which bug report RichiewTheBard is referring to, but if this is a 32-bit only bug, and the Xilinx compiler is crashing looking for the libncurses shared object, then its likely that the 32-bit version of libncurses isn't installed on your machine. If that's the problem, it should be pretty easy to fix:

sudo yum install libncurses.i686

Let me know if that helps!

[T-REX$]

FYI,

The actual name of the rpm you might need is ncurses-libs.i686, so in reality, you might need to do

sudo yum install ncurses-libs.i686

Sorry about that.

[RSteinbrück]

Hi TJ,

Great, it works - like always when you care for it!

Could you maybe additionally answer the “Which of the Compilers (32 or 64 Bit?) is chosen and by whom (IDE, Server or Worker?)?” question from above? I guess from the performance point of view the 64 Bit compiler would be superior, due to access to more RAM.

Best Regards,

Reinhard

[T-REX$]

Hi Reinhard,

I'm actually not 100% sure on the logic involved for choosing the 32 vs 64 bit compiler. The decision is made independently for each target class. So I guess to answer the question, its made from the IDE/Driver, but not by the user.

I believe most, if not all, cRIOs will use the 32-bit compiler, while FlexRIO, VST, and some other devices will default to or require the 64-bit version.

[~Its_Me~]

Hello TJ,

I know this forum is aged. At work we still have a nI9074 I need to adapt the software. I do not have a WIN7 system available. The development PC is a WIN10 PC. I am running Labview 2018 on it. I tried to setup a few different Linux distributions running in VirtualBox, Fedora 39 as it is new and RPM based. CentOS 7.9 and CentOS 7.3 sadly none of them is able to compile. I did install the Labview 2018 FPGA ISE 14.7 package. I can start the worker the worker kan see the server. I can start a compile on the WIN10 development PC using Labview 2018 the worker will react  and I can see a logfile on the  virtual machine's linux install telling the compile has started and failed. The behavior is the same as described in this forum First I got the error:

 13:15:34Z|ERROR|SessionId=vgEl0ly|WorkerId=SF5nL1l|JobId=bSsO7yj|NI.LV.FPGA.CompileWorkerUI.UowQuitException: The step 'CoreGenerator' errored and we were asked to quit on error. ---> NI.LV.FPGA.CompileWorkerUI.UowQuitException: CoreGen process returned error code: (255, , )

so I did:

sudo yum install ncurses-libs.i686

This gives me the following error:

2023-12-05 22:00:24Z|INFO|SessionId=Ugez4o8|WorkerId=Sr6xuqt|JobId=dF9StXv||1|CoreGenerator|DbgStdErr|CoreGen process returned error code: (127, , /usr/local/natinst/NIFPGA/programs/xilinx14_7/ISE/bin/lin/coregen: error while loading shared libraries: libstdc++.so.6: wrong ELF class: ELFCLASS64 )

Please correct me if I am wrong, I think I made a little bit progress and now the compiler has got a lib to work with, and it is almost the correct one, I think it did find a lib but it needs a 32 bit version and not the 64 bit version. Is this correct? 

I hope you can help me, it is taking a lot of time. Thank you for the help!

[~Its_Me~]

Hello  RSteinbrück,

I think you did not did expect this question after this time 🙂 . 

When reading you post I wonder if you ran into the same problem as I did when you did install the ncurses lib? if you did and still know how you did solve it could you please share the information?

[RSteinbrück]

Hello ~Its_Me~,

yeah it's surprising, but good to know that this thread might still be of help.

According to

https://www.ni.com/de/support/documentation/compatibility/19/compatibility-between-xilinx-compilatio...

Xilinx ISE 10.1 is needed to compile FPGA code for the cRIO9074. For this version of the compile tools, there unfortunately is no Linux worker.

I would:

- get the latest ISE10.1 release (https://www.ni.com/de/support/downloads/software-products/download.labview-fpga-compilation-tool.htm...)

- try to install it on the Win10 development machine (even when it is not officially supported ...)

- if that does not work setup a Win7-VM as a compile worker

Have fun,

Reinhard

[~Its_Me~]

Hello Reinhard,

Thank you for the quick reply. I did check the site. and If I add the hardware type and Labview version used I get:

ISE 10.1 is the minimal version if I am correct? Or am I missing something?

EDIT:How can I tell Labview to use 10.1 and not 14.7 ? I could give it a try if I cant get the 14.7 to work.

thank you for the help!

[RSteinbrück]

You are right the compatibility checker tells: "LabVIEW 2018 FPGA Module Xilinx Compilation Tool for ISE 14.7". Actually I did not use that but did full text search on "9074", which lead to only one hit at the bottom in the "ISE 10.1" row what makes sense because it has a Xilinx Spartan-3 2M FPGA.

Try to install ISE10.1!

[RSteinbrück]

Concerning your question: "How can I tell Labview to use 10.1 and not 14.7 ? I could give it a try if I cant get the 14.7 to work."

The compile service decides which compile tool is needed based on the FPGA hardware. You can not chose anything. The compilation can only run when the available compile workers can provide the requested capability (= ISE10.1, Vivado2015.4, Xilinx 14.7,...).