Anyone install windriver on linux yet?

[keen101]

Well, just requested a linux version of LabVIEW. Hopefully NI will send it....

The following is a modified version of the Makefile from the example code that allows it to be built through Eclipse on Linux:

cool. That would be ok, if you could get it to compile from Eclipse. I already have Eclipse installed. I've heard WindRiver is basically a modified Eclipse. If you could get it to work with Eclipse, then that should work. Keep me informed on any progress you make.

It's not on the software DVD.

Thanks. I didn't think it would be. I am going on a limb here, and gonna say that maybe we can get the Linux version of WindRiver by requesting it from frc team suport? I could be wrong. Maybe they haven't even perfected the Linux version yet. I really don't know. I can't seem to find documentation about it anywhere...

Though there is a native Linux version of LabVIEW, if I've understood the situation correctly, in order to program for a CompactRIO target you need to have the LabVIEW Real-time Module, which is Windows-only.

no, I'm pretty sure the real-time module is included with the linux version too.

If I made any comments about the Real-time module, it was that i am pretty sure the Real-time module on an everyday version of labview is very different from the FRC version. I think it's different because our cRIO's aren's standard cRIO's, they are custom built ones.

[pogenwurst]

Originally Posted by keen101

no, I'm pretty sure the real-time module is included with the linux version too.

http://digital.natinst.com/public.nsf/$CXIV/ATTACH-AEEE-7AVNNM/$FILE/readme_RT.html

Supported Platforms
The LabVIEW Real-Time Module supports Windows 2000/XP and Windows Vista (32-bit and 64-bit). The LabVIEW Real-Time Module does not support Windows NT/Me/9x.

http://www.ni.com/labview/requirements

LabVIEW Real-Time Module
LabVIEW Development System for Windows requirements plus:
200 MB additional available disk space

Apparently version 7.1 runs on Linux. That's no help, though.

[keen101]

The links you provided don't prove anything. Most of the documentation from ni is for windows anyway. that doesn't mean mac and Linux versions don't exist.

i remember seeing a real time module .rpm file with the linux tutorial. I could email it to you if you want to look at it. (if i still have it)

But, i have the feeling you just feel like arguing.

[pogenwurst]

Originally Posted by keen101

The links you provided don't prove anything. Most of the documentation from ni is for windows anyway. that doesn't mean mac and Linux versions don't exist.

i remember seeing a real time module .rpm file with the linux tutorial. I could email it to you if you want to look at it. (if i still have it)

But, i have the feeling you just feel like arguing.

I only intended to save you and others time.

I suspect that the RPM you're referring to is labview85-rte-8.5.1-1.i386.rpm. Unless I'm terribly mistaken RTE in this case stands for the LabVIEW Run Time Engine, which is used to deploy VIs on computers that don't have the full development system installed.

In any case, I will say no more, and wish you the best of luck with your search.

[keen101]

I only intended to save you and others time.

I suspect that the RPM you're referring to is labview85-rte-8.5.1-1.i386.rpm. Unless I'm terribly mistaken RTE in this case stands for the LabVIEW Run Time Engine, which is used to deploy VIs on computers that don't have the full development system installed.

In any case, I will say no more, and wish you the best of luck with your search.

well, i really don't know. I don't claim to know.

In either case i am going to assume to FRC version of LabVIEW for Linux is capable of programming the FRC nRIO just like the windows version. I'm going to assume they have included everything that would be needed.

[Roboj]

In either case i am going to assume to FRC version of LabVIEW for Linux is capable of programming the FRC nRIO just like the windows version. I'm going to assume they have included everything that would be needed.

This is not the case. There is no version of LabVIEW Real Time for Linux. As has been mentioned in other threads, it is possible to edit a program on LabVIEW for Linux but you need a Windows PC (or Windows VM) to build the application and use the interactive debugging capabilities targeted to the cRIO (i.e. the Real Time module)

[daltore]

This seems strange to me, there shouldn't really be an issue with realtime programming in Linux, there are entire realtime kernels out there (2 of my computers use them). Anybody know what the realtime module does that the regular LabView version doesn't?

[Greg McKaskle]

The realtime module implements the client protocol, the cross compiler, and integrates all of the configuration stuff for discovering the chassis, downloading, etc.

It isn't that these things can't be done with linux. They certainly can. Years ago there was an RT version for Mac OSX. But demand for the Mac and also for linux versions of RT seem to be low. With a product this complex, even testing on an OS adds up to significant time. So if there isn't apparent demand, it gets trimmed. Many of the developers at NI are linux fans and it isn't personal, it just comes down to supplying products that the majority of engineers need.

Greg McKaskle

[AustinSchuh]

I just succeeded in compiling and deploying code under Linux to the cRIO! I used wine to run the compiler and wput to upload it. I am going to write up a document on this in a bit and post it. I had to copy over the license file from Windows to get it working under Linux, so I'm not sure how that is going to work for people who don't install it under Windows first.

Off to work on getting the debugger working...

[pogenwurst]

Originally Posted by AustinSchuh

I just succeeded in compiling and deploying code under Linux to the cRIO! I used wine to run the compiler and wput to upload it. I am going to write up a document on this in a bit and post it. I had to copy over the license file from Windows to get it working under Linux, so I'm not sure how that is going to work for people who don't install it under Windows first.

Off to work on getting the debugger working...

Excellent!

The redistributable version from NI (there's a link to it earlier in the thread) that I mentioned I'd gotten running & building under Wine comes with a license, so that shouldn't be a problem.

[AustinSchuh]

I just got the debugger working using only my makefile and Hyperterminal! That was with a serial cable though. I'm going to talk to Brad about installing Telnet or something more secure so that I can get rid of the serial cable.

I figured out how to do it outside eclipse under Windows by launching wtxregd, tgtsvr, and then windsh, but the tgtsvr daemon won't work for me under wine, so that idea failed.

My brother and I are going to write a gdb interface on top of the kernel shell so we can use Clewn, a piece of code that integrates GDB in with VIM.

As soon as I clean up the loose ends that I still have left, I'm going to write up docs on the whole process and post them.

[keen101]

Was that only with WINE?

WINE is at least something, maybe also a VM like Virtualbox could work too.


But, is there anyway to get it working with the native version of Eclipse? I'd rather have a native program than something that works under WINE.

[AustinSchuh]

Originally Posted by keen101

Was that only with WINE?

WINE is at least something, maybe also a VM like Virtualbox could work too.

I was able to use QEMU accelerated with the kqemu kernel module to run XP to run the servers and connect to the cRIO. But I found that I was then using Windows under Linux, and that wasn't the route that I wanted to go down. If I am going to do that, I would rather just use XP. XP would at least be more responsive.

Originally Posted by keen101

But, is there anyway to get it working with the native version of Eclipse? I'd rather have a native program than something that works under WINE.

I am pretty certain that once I get it to act like gdb that it is possible to use Eclipse again. You can use Eclipse to run and debug normal Linux applications, and it uses gdb for that. Personally I dislike using anything other than VIM and Makefiles, so my goal is to get things working with VIM and my makefiles.

Until they give us Linux binarys, there is no way to avoid wine or a VM. I guess you could compile your own cross compiler, but that sounds like a lot of unnecessary work and that could introduce problems in the output executable. I find WINE to be just fine for running command line utilities from Windows, though not as good for GUIs. I ran the command line compilers for the previous year's controller using WINE without any problems. This was using a Makefile though, not using MPLAB.