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
Attachments:
XilinxLog.txt ‏61 KB
xilinx14.4_terminal_spew.txt ‏16 KB

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
Attachments:
xinfo.txt ‏57 KB

Similar Messages

Fpga compile worker error (file not found)

Hi
I try to get started with the FPGA functionality of cRIO and got stuck. This seems to be no issue of the cRIO(9014) but of the Xilinx software together with NI.
I am running an English LV 2011 ( many previuos versions installed as well) on a German Windows XP prof. 32 bit.
I was setting up a little project and when it came to compiling ran into errors. First I asked a colleague than I checked the NI support web site. Next time I'll contact the NI local support, but maybe some of you guys hast a faster answer before.
1. I want to run a local compile server. I can start it from start> programs>NI> FPGA. Up pops a question whether I want to allow others to connect remotly. The answer seems to make no difference.
I do not see any icon in the task bar or elsewhere. SHOULD I see a process running in the task manager ?
2. The NI Service locator seems to be running http:/localhost:3580/dump shows a table like attached. SHOULD I see the server running here ?
3. If I start the Compile Worker after some seconds I get a message saying something like file not found. I think, compile server error is only a followup.
I have already re-installed the Xilinx-Tools from the down loaded iso. (that having started yesterday night ......) .
I attach as well the log file. (would have liked, but three is the max)
That whole system of compilation seems to be not very stable when I see all the posts, but I have not found these specific errors.
So I still hope someone has an idea.
Thanks in advance
Gabi
7.1 -- 2013
CLA
Attachments:
ServiceLocator.jpg ‏47 KB
XilinkNotFound.jpg ‏101 KB
FPGA Fehler.jpg ‏44 KB

Gabi Tillmann wrote:
Second thoughts:
Is it really worth using that so highly promoted FPGA on cRIO ???? We'll see.
This Question is technically wrong!
Whenever you are using the C-Series IO-Modules of the cRIO you are using the FPGA, even in ScanMode where NI RIO loads pre-defined bitfiles onto the FPGA.
The FPGA provides you ns Timing, it gives you nativly true parallelism, you are directly programming the bahaviour of FlipFlops, LUTs, Registers and so on.
It gives you the ability to programm hardware without the need to understand complex HDL languages.
The cRIO is besides PXI the most flexible and powerful (908x) platform NI offers. The decision to use an FPGA or to use a cRIO should not be "because it's there".
The decision to use an FPGA-based Platform depends on the complexity of the application, just think about custome beahviour of IOs or custom triggering.
Christian
P.s.: Great that you solved your compiler issue.

FPGA Compile error on remote compile worker - but not on local!?

When i compile using Rebuild for building my VI to FPGA on NI cRio-9082 I get this:
Then I kill the compile worker on the develop machine, to use remote compile worker.
Then i get this:
Should the timing constrains not be the same?
Last lines in Xilinx log:
Process "Generate Post-Place & Route Static Timing" failed
done.

Mauritius,
Brad and I took a closer look at the Xilinx log and we see a line printed that will hopefully help us narrow down the problem. Immediately after completion of the Analysis phase the log has the following line recorded:
*** glibc detected *** /usr/local/natinst/NIFPGA/programs/xilinx13_4/ISE/bin/lin/unwrapped/trce: double free or corruption (!prev): 0x09fd05e0 **
It seems there is a problem with the linux worker attempting to free the same memory twice which may be causing the compiler to exit during the mapping phase. We have a few more questions and would like to take a closer look into things for you.
1. Will any other designs compile succesfully on this linux worker (even very basic VIs)?
2. If other designs compile, will a simpler version of this design still fail consistently?
3. If the failed compilation seems to be design specific, would you be willing to provide your design for us to try and reproduce the failure?
Feel free to personal message me if necessary.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

FPGA Compilation fails with Xilinx "Block Memory Generator 8.1" configured with a Coefficient File

Hello All,
I have a SubVI that uses block memory, which has been created using Xilinx "Block Memory Generator 8.1". I have configured this block memory to be a "Single Port ROM", and I use a coefficient file to initialize the memory contents. In simulation mode, everything works as it should.
Next, when I try to compile the top-level VI, I get the following error:
http://www.cs.nyu.edu/~aditya/Compilation_Log_100.txt
http://www.cs.nyu.edu/~aditya/Dividing (This is the coefficient file)
Essentially, the compiler is looking at an ill-formed path to find the coefficient file.
My environment:
-- LabView 2014 f1 (32 Bit)
-- FPGA module 2014
-- RT Module 2014
-- Xilinx Vivado 2013.4
-- NI RIO Drivers 14
-- Development Machine and Conpile Server: Windows 7 Professional, 32GB RAM
-- Compile Worker running Linux, with Xilinx Compile tools installed
Is this a bug, or am I doing something wrong? Thanks!
Best,
Aditya

Next, I tried compiling on the windows machine itself. And here is the error that I get. (See attached image).
Thanks!
best,
aditya
Attachments:
Capture.PNG ‏18 KB

FPGA Compile Farm Error -61319

Hello,
I am having problems compiling FPGA code, I am getting error -61319 when the compile fails. Most frequently it times out during the "estimating resouces planAhead" stage and sometimes in the synthesis stage. I am using:-
Labview 2012 SP1
Xilinx 13.4 Compilation Tool
Windows 7 with 2 GB of RAM
I have tried reinstalling the Labview FPGA Xilinx module, to no avail. I have tried compiling different projects that have compiled previously, with no success! I have compiled successfully with this PC previously, although I am not sure if I have since changing to 2012.
I have tried searching for information related to -61319 but all I can find is the error text that accompanies the fault code in the details window. Two images below show the error code I am receiving.
Any help/advise gratefully received.

Hi,
BODGER:
I'm sorry that you're still having difficulties! In terms of putting the 2011 back on RIO boards, that shouldn't be too much of a problem, you will just have to format them and reinstall the RIO 2011 software.
MATHIEU:
What do you mean by "open the compile worker"? On my machine, when I run the exe as you suggested, I just get a pop up saying "compile worker running" in the system tray; it should not open any kind of window.
BOTH OF YOU:
Please would you run me through, with screenshots, a step by step process of what you're doing to compile the VI, from the project to when you get the error? I've run out of information on the database as it is, so I'd like to take as much information as I can to our specialists to see if they have any ideas.
As I say, I'm sorry that you're both running in to issues and I will do my best to help you resolve these with the information which you give me.
Best wishes,
Chiara A
Applications Engineer with NI UK & Ireland

Procedure with recursive query working in 11g compiles with error in 10g

Hi, All,
I have a procedure that recursively selects tree-like table (with ID-ParentID relationship). Query itself works perfectly and exactly like I need in 11g and procedure containing it compiles well. But when I try to create the same procedure in 10g then I get a message that procedure compiled with error. I have no other suspicions but on the WITH part of the procedure.
The exact query is here (destination_tariff_zones is the tree-like table which refers to itself by parent_destination_tariff_zone_id):
+ open dtzl_cur FOR
with dtree (nm, iid, alevel, wldcard, dtzindex)
as (select dtz.iname, dtz.iid, 0, dtz.wildcard, rcdi.iindex
from destination_tariff_zones dtz, rating_cube_dimension_indices rcdi, rating_cube_dimensions rcd
where dtz.parent_tariff_zone_id is null and
dtz."rc_dimension_index_id" = rcdi.iid and
rcdi."rc_dimension_id" = rcd.iid and
rcd.rating_cube_id = rc_id and
rcd.dimension_type_id = dim_type
union all
select dtz.iname, dtz.iid, dtree.alevel + 1,
cast ((dtree.wldcard || dtz.wildcard) as varchar2(20)), rcdi.iindex
from dtree, destination_tariff_zones dtz, rating_cube_dimension_indices rcdi, rating_cube_dimensions rcd
where dtree.iid = dtz.parent_tariff_zone_id and
dtz."rc_dimension_index_id" = rcdi.iid and
rcdi."rc_dimension_id" = rcd.iid and
rcd.rating_cube_id = rc_id and
rcd.dimension_type_id = dim_type)
select iid, nm, wldcard, dtzindex
from dtree
order by wldcard;+
Is there any difference between how 11g and 10g handle WITH statements?
Please advise.
Thank you very much in advance,
Max

Max Afanasiev wrote:
then is there any alternative to implement what I need?You can look at using CONNECT BY to emulate a recursive query. If you can post the following we may be able to help:
1. Sample data in the form of CREATE / INSERT statements.
2. Expected output
3. Explanation of expected output (A.K.A. "business logic")
4. Use \ tags for #2 and #3. See FAQ (Link on top right side) for details.

LabVIEW 2013 SP1 Compile Worker Fails

Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg ‏41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

dfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

LabView Crashing and compile server error.

Hi,
I'm having some errors when I compile code for my FPGA (PXI-7831R). I am using LabView 8.2.1.
Sometimes labView crashes completely and sometimes it comes up with a compile server error.
My code contains 3 VI's. The first send sends digital output and reads digital input 10 times and then called another VI to save these results. The second VI repeats the first VI 10 times.
When the first VI is compiled on its own it works (including the saving data VI which saves it to a FIFO) but when the second VI is compiled, that is when it errors.
I have attached the compile server errors and the screen dumps of when labView crashes.
Can anyone suggest what I am doing wrong?
Thanks.

ok. Let me try and make my problem a little clearer....
I have now combined all the VI's into one.
It is supposed to write to the digital output and read from the digital outputs 10times at a rate of 10us and store the data to the FIFO. This process is then repeated at a rate of 80ms for 8 times.
I have attached a word document with an explanation on the error.
Attachments:
lvlog07-26-07-12-04-50.txt ‏3 KB
Problem Explaination.doc ‏61 KB
f623_appcompat.txt ‏93 KB

"LabVIEW FPGA: The compilation failed due to timing violations, but there is no path information because the timing violations are not of type PERIOD

The compilation of my labview fpga vi fails with the error message "LabVIEW FPGA: The compilation failed due to timing violations, but there is no path information because the timing violations are not of type PERIOD".
In the 'final timing (place and route)' report, the requested frequencies are all below the maximum frequencies and the compilation error message is only displayed at the very end on the 'summary' page.
I tried to optimize my labview fpga vi with pipelining, but had no success.
Can anybody offer some advice on how to debug fpga code with this error? Is this really a timing error or something else?
Software:
Labview 2011, fpga 2011, xilinx tools 12.4 sp1
Hardware:
NI PXIe-1071 Chassis
NI PXIe-8108 Embedded controller
NI PXIe-7965R FPGA FlexRIO FPGA module
NI 5761 250 MS/s 14 bit Analog input digitizer
The Xilinx log of the compilation run is attached.
Also, this issue was already discussed in this thread ~6 months ago, but no satisfying answer was offered so far...
Thanks,
Fabrizio
Attachments:
xilinxlogc.txt ‏2313 KB

Hi Kyle,
the problem is: I have one computer which compiles the VI successfully and a second one which shows that error. Both use the same software setup (LV2011SP1+RT+FPGA from DS2012-01). Both use the same project file - atleast SVN shows no difference.
- You can have one FPGA VI where one computer is compiling successful and a second one complains. (Btw. I have a SRQ running in Germany on this topic.)
- More problems: After successful compiling on first computer and transferring all to second computer (using SVN, including the full project folder with all files like bitfiles, lvproj, and everything) the second computer is unable to start the RT executable due to error "FPGA VI needs to recompile". Solution so far: Call the FPGA-OpenReference with the bitfile instead of the VI (as I used to do until now)...
- More problems: After modifying the FPGA-OpenReference to use the bitfile (on the 2nd computer) and transferring all the files back to the 1st computer (using SVN as before, including the whole project) the 1st computer complains: FPGA-OpenReference is creating a different reference than is used in the VI. So what happens here? On one computer my VI is ok, the reference is typed correctly. Transferring all the files to a different computer the VI isn't ok anymore due to changes of the reference??? You know: all files are the same: lvproj, FPGA bitfile didn't change, cRIO reference didn't change...
All those problems didn't occur on my RT-FPGA projects in LV2010SP1. I'm not pleased...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

VMWare Server 2 Module compilation Module error 2.6.30-ARCH x86_64

Hello,
i completely changed my envoirenment to arch linux, including my homeserver.
most things are absolutely cool with arch, but now i have a problem with installing VMWare Server 2.
When running the installer vmware-config.pl i got following output:
bash~./vmware-config.pl
Making sure services for VMware Server are stopped.
Stopping VMware autostart virtual machines:
Virtual machines failed
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent failed
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes] yes
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.30-ARCH/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.30-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.30-ARCH'
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config2/vmmon-only/linux/driver.c:31:
/tmp/vmware-config2/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait'
include/linux/poll.h:67: note: previous declaration of 'poll_initwait' was here
In file included from /tmp/vmware-config2/vmmon-only/./include/vmware.h:38,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:99:
/tmp/vmware-config2/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config2/vmmon-only/./include/vcpuset.h:103,
from /tmp/vmware-config2/vmmon-only/./include/modulecall.h:37,
from /tmp/vmware-config2/vmmon-only/./common/vmx86.h:33,
from /tmp/vmware-config2/vmmon-only/linux/driver.h:29,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:101:
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config2/vmmon-only/./include/vm_asm_x86_64.h:39,
from /tmp/vmware-config2/vmmon-only/./include/vm_asm.h:41,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:103:
/tmp/vmware-config2/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config2/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config2/vmmon-only/./include/vm_asm.h:41,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:103:
/tmp/vmware-config2/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config2/vmmon-only/linux/driver.c:119:
/tmp/vmware-config2/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
/tmp/vmware-config2/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU':
/tmp/vmware-config2/vmmon-only/linux/driver.c:1423: error: too many arguments to function 'smp_call_function'
/tmp/vmware-config2/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
/tmp/vmware-config2/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid'
/tmp/vmware-config2/vmmon-only/linux/driver.c:2007: error: too many arguments to function 'smp_call_function'
make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.30-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and
"http://www.vmware.com/go/unsup-linux-tools".
Execution aborted.
so iam a beginner and can not figure out where the problem is.
i looked around the internet and on the arch wiki but didnt find a sollution - there are often problems with module compilation with newer kernels, therefore there a patches, but not for my kernel.
some people say, that VMWare Server 2 modules compiling fine with the 2.6.30 kernel.. maybe i have another problem.
is this path correct for kernel headers?
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.30-ARCH/build/include]
I hope someone can help me.

cool, i found a patch and installation works fine now !
vmware-server.2.0.1_x64-modules-2.6.30-fix.sh
and
vmware-server.2.0.1_x64-modules-2.6.30-fix.patch
what i did:
wget both files to /tmp
#cd /tmp
#vi vmware-server.2.0.1_x64-modules-2.6.30-fix.sh
and change the VMMODDIR variable to my fits (cause i installed vmware server somewhere else)
#./vmware-server.2.0.1_x64-modules-2.6.30-fix.sh
#cd vmwareserverdir/bin/
#./vmware-config.pl
source: http://communities.vmware.com/message/1286903
Last edited by crabmeat (2009-08-18 13:18:47)

LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has occurred

Hi,
I am trying to build a LabView FPGA VI. During compilation, I always get error stating "LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has occurred. Please contact National Instruments technical support at ni.com/support". At the time, comiplation process is almost at the end. "Final Timing (place and route)" shows as completed. When Checked the Xilinx log session, at the end it states that " Process "Generate Programming File" completed successfully". However, I do not see any generated bitfile.
When clicked on error details, it shows following:
LabVIEW: An unknown error occurred.
Error -2629 occurred at Error occurred while loading XML string. Invoke Node in niFpgaXml_PrettyPrint.vi->niFpgaWriteBitfileXml_Core.vi->niFpgaCompileWorker_CreateBitfile.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:6460001
Possible reason(s):
LabVIEW: An unknown error occurred.
I tried multiple times but so far no luck to generate bitfile for this VI. What could be wrong here?
I am using Labview 2013

Hi Mark,
Here is the device utilization Summary. My development system is running with Windows-7 (32 bit) with 3GB RAM and Labview 2013.
Device Utilization
Total Slices: 90.0% (11970 out of 13300)
Slice Registers: 40.7% (43258 out of 106400)
Slice LUTs: 71.6% (38103 out of 53200)
DSP48s: 1.4% (3 out of 220)
Block RAMs: 22.1% (31 out of 140)
Timing
40 MHz Onboard Clock
: 40.00 MHz (57.90 MHz maximum)
80MHz (Used by non-diagram components)
: 80.00 MHz (100.19 MHz maximum)
--WillsG

Compiler(iropt) error: connect_labelrefs: undefined label L77000157

after compiling with:
cc -xopenmp -xO3 tema3.c
im getting the following error:
compiler(iropt) error: connect_labelrefs: undefined label L77000157
cc: iropt failed for tema3.c
I guess its some kind of bug...Can someone tell what does the error mean and if theres a workaround?
also the program works on debian linux using intonecc

You have run into an internal compiler error in the optimizing phase. The bug has probably already been fixed in a patch. Get the latest patches for your compiler version here:
http://wwws.sun.com/software/products/studio/patches/index.html
If you are using the C compiler, get the C compiler patch and the "common compiler components (code generator) patches.
For a temporary workaound, try compiling at the lower optimization level -xO2, or without optimization (no -xO option).

Compilation failed due to a compile server error

I was using LABView 8.0 with RT and FPGA module without problems.
I updated windows on 2006 April 18th and now I cannot compile any FPGA VI. Even the older one I compiled with the same computer previously.
When I take EXACTLY the same project to another computer, it compiles just fine and when I take the bitfile back, my corrupted system can run with the bitfile.
I fear the problem is with windows. I reinstalled LABView TOTALLY and still have the same error when trying to compile.
According to the knowledge base I checked the HKEY and it doesn't change anything.
Here is the error message:
Status : compilation failed due to a Compile Server error
Error -61499 occured at nirviExtractVHDLHierarchy.vi when called from nirviBuildprjFile.vi
Possible reason(s)
LABView FPGA : An internal software error in ALBView FPGA Module has occured. Please contact NI support
Details : Error 7 occured at Open File reading C : \ NIFPGA80\srvrtmp\localhost\Eight...name of the bitfile ...\scripts\toplevel_gen_synth_lvfpga.txt
Note : I checked this folder, it doesn't exist, thus it has never been created like the previous. After April 18th, not any new folder has been created.
Possible reasons : File moved or deleted, incorrect filepath,...
NI-488 : Non-existent board
Note : I have nor use none of this nowhere !
Start time - Stop time : 12 seconds

In order to try and isolate the problem can you perform a few tests.
1) Set up a remote compile and use the machine that is not working as the client and the machine that is working as the server.
1.a) You can configure the client machine to use another machine as the compile server by going to Tools>>FPGA Module Options...>>Configure Compile Settings and change the machine from 'localhost' to the machine that you want to act as the server.
1.b) On the server machine open the Compile Server manually by going to the Windows Start Menu>>All Programs>>National Instruments>>LabVIEW 8.0>>LabVIEW FPGA Utilities>>Compile Server
1.c) Try and compile the VI. It should generate code on the client machine and send the generated code to the server. Wehn the server receives the code it will compile it and return the bitfile when complete.
2) Set up a remote compile and use the machine that is not working as the server and the machine that is working as the client.
2.a) Follow the instructions in part 1, but switch the client and server machines.
These tests should help us isolate if the problem is with the Compile Server, or the code generation.
Regards,
Joseph D.
National Instruments

Choosing the compile worker

I have installed a remote compile worker on a linux PC as described here.
The compile worker on the remote PC can connect to the compile server on the local development PC (running widows).
Now, when I perform a compilation the local compile worker is chosen by default.
How can I select the remote one?
My configuration is the following
Development PC: Windows 7, LabVIEW 2010, Xilinx 11.3
Remote PC: Linux (Ubuntu10.10, I know it is not supported by NI), LabVIEW 2012 compile worker, Xilinx 13.4
Is there any compatibility issue between LabVIEW 2010 and LabVIEW 2012? Or between the Xilinx software?
Thank you
Solved!
Go to Solution.

In my case, the "antec" system named in the screen shot is the remote compile worker that I use to generate my bitfiles. It may also be functioning as the server too but from my development machine (WinXP) it looks like the worker. On the "antec" machine (Win7), compiles there are configured to use the local worker and the server is configured to allow remote systems to connect and request service. Beyond that, it all just works. It took a while to get the firewalls on the two machines setup to allow it all to work though.

Force the Compile Worker to Work Faster

The process of creating the FPGA bit files takes a long time even with a simple FPGA design. I monitor the system resources when the Compile Worker creates the bit file. Only a few percentage of the CPU is being used. Is there a way to force the Compile Woker works faster because there is system resources available?
My system is dual Xeon 6 Physical Core with 16Gb RAM, running LabVIEW 2011 version 90 days come with the Evaluation Rio single board.
Solved!
Go to Solution.

The FPGA code compilation is performed not by the LabVIEW compiler but a compiler from Xilinx, specific to their FPGA chipsets.
The problem you see is the Xilinx compiler is single thread, and therefore will only use one core, and also can be seen at times to 'dawdle'. There's nothing you can do to push the compiler to work harder by encouraging the use of other resources. If you cores are 3.2GHz each, then compiling on your dual Xeon 6 will be no faster than on a single-core 3.2GHz CPU.
What you need for minimizing your compile times is the fastest core you can get!
Thoric (CLA, CLED, CTD and LabVIEW Champion)

LV2013 FPGA Linux Compile Worker errors (Xilinx 14.4)

Similar Messages

Maybe you are looking for