LabVIEW
LabVIEW on Raspberry Pi 3
@pallen wrote:
Interesting.
Step by step of a build and test in QEMU, including some links to images: https://withinrafael.com/2018/02/11/boot-arm64-builds-of-windows-10-in-qemu/
Still not sure if LabVIEW or any other Windows software would run this way, but it would be cool if it did.
Just to make sure we're on the same page here, that test does the opposite of what we want (run arm on intel, not intel on arm).
I actually got a ARM android VM running once on Windows (mostly simple downloads though). QEMU is pretty neat. On Intel Linux it's pretty efficient too, as AFAIK it makes use of low level virtualization options of the CPU. I don't thing that is possible on ARM. So ARM QEMU emulation of a x86 Windows application will be dreadfully slow. The GitHub repos mention single core 300 MHz PC slow... Although both the RPi2 and the RPi 3 page mention that (I'd assume the RPi 3 to be faster). I'd take it though, we all worked on 300 MHz PCs ten years ago.
Search LabVIEW like a graph!
@Hooovahh wrote:
wiebe@CARYA wrote:Do you have anything sharable about the Linux RT\Wine solution? Was that a Linux RT x86 or ARM system?
It is x64 binaries only at the moment.
That is funny, as most RPi resources I've seen are x86 only, no x64! But it seems it's a package manager thing? Or because the cDAQ-9123 is x64?
@Yamaeda wrote:
Maybe you can get the Windows on ARM with x86 emulation targeted for the elusive Andromeda device and you should be able to run native windows programs on it, maybe even LV.
/Y
That would be fun of course, but I'd prefer LabVIEW on 30 RPi's (or 130 RPi zeros) over 1 Andromeda device.
Of course the Andromeda device might actually run LabVIEW, not just a LabVIEW application.
wiebe@CARYA wrote:
@Hooovahh wrote:
wiebe@CARYA wrote:Do you have anything sharable about the Linux RT\Wine solution? Was that a Linux RT x86 or ARM system?
It is x64 binaries only at the moment.
That is funny, as most RPi resources I've seen are x86 only, no x64! But it seems it's a package manager thing? Or because the cDAQ-9123 is x64?
NI build the cDAQ Linux RT image and I'm assuming they just picked one architecture and went with it. The OPKG package manager does have a very basic support for multi-architectures but I think the packages need to be named differently. So if you want Wine 32-bit you need all the dependent packages to be 32-bit and all the ones installed are 64-bit. Finding the 32-bit equivalent of all the dependencies, then installing them, and making sure they don't step on the foot of the existing libraries that are 64-bit was a challenge.
wiebe@CARYA wrote:
I'm not sure how this is different from Windows IoT. Perhaps it's the same?
As far as I can tell it isn't the same. Windows IoT is an ARM based version of Windows that is stripped down, and just runs ARM built applications. And Windows 10 on ARM seems to be Windows 10 made for ARM with WOW emulation to be able to run x86 applications. If you install this on a Pi then you can just run x86 applications like LabVIEW Run-Time and your programs...maybe I haven't tried it as I don't have access to a Pi 2/3 just a zero which is on a different platform and likely doesn't have support just like Windows IoT doesn't support the zero.
Here is a video installing Windows 10 on ARM on a Pi, and then installing and running Microsoft Word 32-bit. Driver support is still crappy, USB "is buggy" and no ethernet or WIFI yet. I did see a work around involving a modem emulator and getting internet through another device, but wow that was a lot of work. As soon as there are native ethernet drivers I could see this being useful for things like an HMI, or displaying current running test data.
wiebe@CARYA wrote:
@pallen wrote:
Interesting.
Step by step of a build and test in QEMU, including some links to images: https://withinrafael.com/2018/02/11/boot-arm64-builds-of-windows-10-in-qemu/
Still not sure if LabVIEW or any other Windows software would run this way, but it would be cool if it did.
Just to make sure we're on the same page here, that test does the opposite of what we want (run arm on intel, not intel on arm).
It is sorta the opposite. That link shows how to setup QEMU with the Windows 10 on ARM. The same OS I proposed putting on the Pi to run x86 applications. So using QEMU you could load up that OS into a virtual machine, and see if LabVIEW can run in it. If it can then presumably you could run LabVIEW on the Pi running the same OS. Using QEMU is just a way to test out that environment in something more easily accessible like a standard Windows desktop.
@Hooovahh wrote:
wiebe@CARYA wrote:
I'm not sure how this is different from Windows IoT. Perhaps it's the same?
As far as I can tell it isn't the same. Windows IoT is an ARM based version of Windows that is stripped down, and just runs ARM built applications. And Windows 10 on ARM seems to be Windows 10 made for ARM with WOW emulation to be able to run x86 applications. If you install this on a Pi then you can just run x86 applications like LabVIEW Run-Time and your programs...maybe I haven't tried it as I don't have access to a Pi 2/3 just a zero which is on a different platform and likely doesn't have support just like Windows IoT doesn't support the zero.
Here is a video installing Windows 10 on ARM on a Pi, and then installing and running Microsoft Word 32-bit. Driver support is still crappy, USB "is buggy" and no ethernet or WIFI yet. I did see a work around involving a modem emulator and getting internet through another device, but wow that was a lot of work. As soon as there are native ethernet drivers I could see this being useful for things like an HMI, or displaying current running test data.
OK, that's cool. One more thing to try at some point.
@Hooovahh wrote:
wiebe@CARYA wrote:
@pallen wrote:
Interesting.
Step by step of a build and test in QEMU, including some links to images: https://withinrafael.com/2018/02/11/boot-arm64-builds-of-windows-10-in-qemu/
Still not sure if LabVIEW or any other Windows software would run this way, but it would be cool if it did.
Just to make sure we're on the same page here, that test does the opposite of what we want (run arm on intel, not intel on arm).
It is sorta the opposite. That link shows how to setup QEMU with the Windows 10 on ARM. The same OS I proposed putting on the Pi to run x86 applications. So using QEMU you could load up that OS into a virtual machine, and see if LabVIEW can run in it. If it can then presumably you could run LabVIEW on the Pi running the same OS. Using QEMU is just a way to test out that environment in something more easily accessible like a standard Windows desktop.
I don't think so, could be wrong.
He's says he running on a Intel Core i7 4770K, not ARM. And simulating Windows 10 (arm64) ESDs.
wiebe@CARYA wrote:
I don't think so, could be wrong.
He's says he running on a Intel Core i7 4770K, not ARM. And simulating Windows 10 (arm64) ESDs.
Right so again correct me if I'm wrong, but using an Intel Core i7 in a normal Windows 10 Home/Pro 64-bit you can install a virtual machine. That virtual machine can emulate an ARM processor, and you can install the Windows 10 on ARM OS on it. So the host OS is Windows 10 64-bit, and the guest OS is the Windows 10 on ARM. In this VM you can try to install the LabVIEW run-time because this is the same Windows 10 on ARM OS that you can try to install on a Raspberry Pi, and it should be able to use WOW for x86 applications. If you can install any x86 software in Windows 10 on ARM then you should be able to install LabVIEW and any other software in the OS whether it is on a Pi or in the VM.
The site he links to to download the arm64 (ESDs) is the same website another tutorial links to, to put Windows 10 on ARM on a Pi. It is the same OS and same ISOs.
@Hooovahh wrote:
wiebe@CARYA wrote:
I don't think so, could be wrong.
He's says he running on a Intel Core i7 4770K, not ARM. And simulating Windows 10 (arm64) ESDs.
Right so again correct me if I'm wrong, but using an Intel Core i7 in a normal Windows 10 Home/Pro 64-bit you can install a virtual machine. That virtual machine can emulate an ARM processor, and you can install the Windows 10 on ARM OS on it. So the host OS is Windows 10 64-bit, and the guest OS is the Windows 10 on ARM. In this VM you can try to install the LabVIEW run-time because this is the same Windows 10 on ARM OS that you can try to install on a Raspberry Pi, and it should be able to use WOW for x86 applications. If you can install any x86 software in Windows 10 on ARM then you should be able to install LabVIEW and any other software in the OS whether it is on a Pi or in the VM.
The site he links to to download the arm64 (ESDs) is the same website another tutorial links to, to put Windows 10 on ARM on a Pi. It is the same OS and same ISOs.
Ok, that is possible.
Sounds more like adding a problem then finding a solution to me though. But sure, it's another possible route to success...
I'd be worried that even if it works, how do we know the emulated emulator isn't just using the cpu? And emulation will be slow, emulating an emulator will be terrible slow.
First of all, thank you all for your comments and ideas. 
I did a lot of research during this period, and I found a very new project. I tried that it works.
Using this interface, you can deploy Windows 10 to Raspberry Pi 3 thanks to WoA Deployer.
My other aim was that Labview exe. files work on Raspi whose OS is Windows 10. In this case, i can not solve a problem that is in picture. If you have any idea, could you help me in this step ?
+ In addition, Let's say that OS of Raspberry Pi was Raspbian. If I downloaded LVRTE for Linux, could .exe file works successfully on Raspberry Pi ?
@bestecf wrote:
+ In addition, Let's say that OS of Raspberry Pi was Raspbian. If I downloaded LVRTE for Linux, could .exe file works successfully on Raspberry Pi ?
No this won't work, you will have an x86 Linux made binary trying to be ran on an ARM processor. It doesn't matter if the operating system is Linux, you won't be able to install it and run it. I've also never seen that install error before. But I'd also try to start small and try running a LabVIEW EXE with the run-timeless install I linked to earlier. Also try other NI run-time installers, it is possible it was a bad download.
