LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV2013 FPGA Linux Compile Worker errors (Xilinx 14.4)

Hi,

 

Until today, we had a nice working LV2012 Win7 and Xilinx 13.4 Linux Worker remote compilation system.

Necessity mandated an upgrade to LV2013 FPGA for Win7. Which mandated a Linux distro upgrade to RH6.3x64 per the documentation.

 

Now, our FPGA code won't compile successfully on the Linux Worker 14.4 x64, but will succeed on Win7 local worker.

 

Enclosed are our xilinx.log file and a terminal capture .txt of the compilation errors from Linux Compile Worker run.

 

Installation had no errors or warnings, and the Linux Compile Worker connects to the Win7 Server successfully.

 

Please help, as without this optimization our code compile times are 2-3x longer.

Our FPGA is NI-7962 FPGA (Vertex 5)

 

Thanks,

John

 

Download All
0 Kudos
Message 1 of 26
(5,740 Views)

Hello carskie,

 

When you compile your code do you get some error code?

 

Also, please make sure that you have installed these software at the following order:

 

- LabVIEW 2013

- LabVIEW FPGA and RT Module

- LabVIEW Xilinx Compilation Tools

- LabVIEW NI RIO driver.

 

Carmen C.

0 Kudos
Message 2 of 26
(5,690 Views)

Hey John,

 

The thing that stands out in that log (or console spew Smiley LOL ) is this:

(path: /usr/local/natinst/NIFPGA/jobs/SObThva_kPn8yk4) did not finish properly because of an exception: The step 'CoreGenerator' errored and we were asked to quit on error

Do all compilations fail with this error (please try a blank VI)? I'll take another pass at the log file and see if I notice anything out of place.

Cheers!

TJ G
0 Kudos
Message 3 of 26
(5,680 Views)

OK, looks like the actuall error is:

Coregen attempt 4 of 4 for xco file:/usr/local/natinst/NIFPGA/jobs/SObThva_kPn8yk4/core_BuiltinFIFOCoreFPGAwFIFOn0/ReallyLongUniqueName_ReallyLongUniqueName.xco failed with CoregenExitCode=System.Tuple`3[System.Int32,System.String,System.String]

 

I'd still like to know the result of a blank compilation... but it sounds like you might have a FIFO in your design set to use "Built In" or "Target Optimal" logic? Another test would be to change this to "Slice Fabric".

Cheers!

TJ G
Message 4 of 26
(5,672 Views)

@CarmenC

 

That's the install order we used. Again, the Windows local compile produces no errors.

 

@T-REX

 

We'll try a blank VI, thanks. Checking with the author re: FIFO logic states.

 

Best,

John

 

0 Kudos
Message 5 of 26
(5,664 Views)

@T-REX

 

The blank VI Linux Compile also failed. The relevent logs are attached. Thanks for taking a look.

FWIW we are using a target optimal FIFO in our actual application VI.

 

Best,

John

Download All
0 Kudos
Message 6 of 26
(5,658 Views)

Hey John,

 

Knowing that this happens with a blank VI eliminates a lot of possibilities, so thanks for running that. I've got a couple more steps to try on the worker machine side.

 

  1. Please run the following: /usr/local/natinst/NIFPGA/programs/xilinx14_4/ISE/bin/nt64/xtclsh
    • Once you see the TCL prompt, please try a basic command like "puts hello"
    • If you get any errors along the way, its likely that the Xilinx install had a hiccup somewhere, and we didn't catch it.
  2. Please also run this: /usr/local/natinst/NIFPGA/programs/xilinx14_4/common/bin/xinfo
    • This should create a report at $HOME/xinfo.txt that you can send in

 

If there is any information in the report that you're uncomfortable sharing on a public forum, please feel free to PM me, and we can set up another transfer method.

Cheers!

TJ G
Message 7 of 26
(5,627 Views)

Thanks for getting back with more tests. The TCL prompt didn't evoke any errors and returned a friendly "hello" using puts hello.

 

Attached is the output from xinfo.

Note that the path to these files is slightly different than what you provided:

 

/usr/local/natinst/NIFPGA/programs/xilinx14_4/ISE/bin/nt64/xtclsh

mine is:

/usr/local/natinst/NIFPGA/programs/xilinx14_4/ISE/bin/lin64/xtclsh

 

/usr/local/natinst/NIFPGA/programs/xilinx14_4/common/bin/xinfo

 

mine is:

/usr/local/natinst/NIFPGA/programs/xilinx14_4/common/bin/lin64/xinfo

 

Best,

John/Carskie

0 Kudos
Message 8 of 26
(5,608 Views)

Sorry about the paths mixup. I copied from my Windows machine, and edited the path to match where it should be in Linux... forgot the end of the path changes too, but it looks like you figured it out just fine. According to your xinfo log, you're on CentOS 6.4, which we never tested (just RHEL 6.3). I'm downloading the CentOS 6.4 Live ISO now, and should be able to get a VM all set up here to see how things behave on my side with the same setup (the xinfo log should have everything I need to reproduce your setup).

 

I'd appreciate it if you could warn me of any special installation steps you had to do to get the installer to run. Did you need any additional packages or dependencies to use our installer, or did everything run fine on CentOS out of the box?

 

Also, do you see anything in "/usr/local/natinst/NIFPGA/compilation"? If there are any folders, could you zip and attach anything with a lvXilinxLog.txt in it? -- Thanks.

Cheers!

TJ G
Message 9 of 26
(5,574 Views)

re: paths, no worries, that was easy.

 

as far as any customization to the install process - after switching from CentOS 5.6 to CentOS 6.4 I followed the install instructions as written with no errors or warnings.

 

"/usr/local/natinst/NIFPGA/compilation" does not exist in my installation

 

Thanks!

0 Kudos
Message 10 of 26
(5,562 Views)