回應： Labview on Win 10 ARM 64 on Raspberry PI

[Cheaterlow]

Hello follow Raspberry Fans and Labview Cracks,

even though everyone in the Forums (here as well as in Win10 Forums and the Raspi Forums) told it is not possible to run a Labview application directly on the PI (with a "Head"), i've managed to do it and the performance from my pov is acceptable.

Short How to

Win10 19H2, WOR Project, "handinstall" the packages of the installer

I will make a proper "How to" when its working properly.

Now to the problems, but first some things to know:

The Win10 64 ARM uses an emulator to run x86 apps, which is according to the Windows forums capable to emulate SSE2 insctructions.

HWInfo32 also showed MMX, SSE and SSE2 as green (7.02)

First i used LV2020. The installation of the run time was a bit tricky but i could manage it. But the .exe than give back an Error related to SSE2.

Than is used a LV2014 Installation (used the same vi saved as downgrade vom 2020) and build it with disabled SSE2 optimization and it WORKED !

The Question now is: can i disable the SSE2 stuff somehow (i tryed already via XML editing in the .lvproject-->nope, the option is gone in advanced since LV2017...) in the LV2020 app builder?

How does Labview figure out, if SSE2 instruction is supported--> i might can trick it so its think its supported (maybe).

Any other suggestions are also welcome. (P.S. I know of the Linx toolkit and the web module solution)

Best regards

Cheaterlow

[billko]

Maybe NI should listen in on this topic.  You may be creating a roadmap for them!

[wiebe@CARYA]

---

@Cheaterlow wrote:

How does Labview figure out, if SSE2 instruction is supported--> i might can trick it so its think its supported (maybe).

Any other suggestions are also welcome. (P.S. I know of the Linx toolkit and the web module solution)

---

Probably (haven't tested it), but (also probably) not officially.

If you turn on scripting and the secret scripting options, 3 SSE compiler options show up. There's also a VI flag for SSE, but that probably won't suffice or it would be impractical.

I've seen other successful attempts of 'a' LabVIEW exe running on a RPi under Windows. I think the problem is running LabVIEW development on it.

A more detailed instruction would be nice.

Getting GPIO working would be nice.

I keep getting stuck in getting the RPi image... I subscribed to the insider program, but it keeps telling me to subscribe. I'm not sure if that's still an issue.

[rolfk]

---

@Cheaterlow wrote:

How does Labview figure out, if SSE2 instruction is supported--> i might can trick it so its think its supported (maybe).

---

That is usually done by executing the cpuid assembly instruction and evaluating the returned register values for certain flags. There is no hope to fake this; unless your x86 simulator does properly emulate this AND implement the actual SSE functionality, there won't be any hope.

[wiebe@CARYA]

---

wiebe@CARYA wrote:

I've seen other successful attempts of 'a' LabVIEW exe running on a RPi under Windows. I think the problem is running LabVIEW development on it.

---

Windows 10 and LabVIEW on Raspberry Pi4 - YouTube and Labview for raspberry pi 3 - NI Community.

That is on a RPi3. Also, the more people try, succeed and document it, the better.

[Cheaterlow]

So i tryed several things and it looks like it wont work with a newer LV version.

Can anybody tell if :

app.compiler.sse1 code generation

app.compiler.sse2 code generation

app.compiler.sse runtime optimization

are still considered during application building?

Thank you

[wiebe@CARYA]

Are you getting the SSE error? Or another error?

[Cheaterlow]

Yes i'm still getting SSE error

[hugoshih]

You should think about why other people don't want to discuss this issue in this forum?

[rolfk]

---

@hugoshih wrote:

You should think about why other people don't want to discuss this issue in this forum?

---

I can tell you why I haven't. I don't have time to tackle yet another project besides my work, family and other LabVIEW interests. 😁 Also for my own personal feelings, this exercise has little other merits than to show off how well one can hack things. It's to involved and complicated to be a viable option for Joe average to use. Even if NI should decide to create a fully supported option for this, it would be a one time thing, not something they could and would support long term as it is simply to much effort to keep that running over the years.

Don't suspect conspiracies, when there are other much more profane reasons for something. 😁