Leaderboard

Hi, Didn't know the Zybo. Looks great. Well the fact is, NI is providing on ni.com a kind of NILinuxRT x86_64 recovery image for PXI with lvrt 2015 installed inside. I'm working on it for home-learning needs since a couple of weeks. Just a hobby. I was curious on the technical faisability and basically only checked the data transfer mechanisms. Maybe there is some more important part of code to try. Or more killer bugs. But here's what I managed to run with the NILinuxRT-VM theme in mind : - About Linx 2014 on a raspberry : an upgrade to 2015 means to a "RTPlatforms.cpp" error by the lvrt binary. Guess it's not quite the same. Maybe a special compilation for this target ? - Chroot the recovery on a standard and virtualized Linux Mint with the LINX method. Works well. We've got quite the same functionnalities as LINX, but not the RT code : standard code (no RT), run-in-source, build-and-deploy. But not the timed-loop (don't know why, even with fake-hwclock. Got an err -825 CPU issue). - Run the recovery on a VM in Virtual Box. Quite simple to do with some lucky tricks. It's better : timed-loop, RT Fifos, source-build and deploy are fine. We can add the network streams and the shared variable client easily (not the server). It was running well during a single day. - Installed it on a real x86 singleboard, a lattepanda. Maybe an Edison could fit. It's running. Noticed the Arduino device inside is recognized by the kernel (didn't check for the other peripheral devices). Just starting with it. Really fun. All of them runs the real-time engine. The last 3 items are not 2015 locked. It is upgradable for 2015 SP1, 2016 and so on. (-License point) For all of them, MAX is not an issue. It begins as it seems that LabVIEW needs to declare the shared variables in MAX to operate the networked variable engine server on the target. So the target-VM must (at least) be detected in MAX to obtain an equivalent of a full autonomous device. Much harder. I'm still discovering about this (MAX see hardly my VM). fmorandat