properly start FPGA lvbitx

[JensG69]

I strongly recommend the followin order of Invoke nodes when starting the FPGA bitfile:

This will abort the perhaps already running FPGA bitfile, which is necessary to download and start a new bitfile.

About VI-file names in an rtexe:

In my company we had some issues with VI-names when they contained special characters like german umlaute. As long as you stick to ASCII-Code there shouldn't be a problem.

Identical VI-names can be an issue if you set the option "Use LabVIEW 8.x file layout" under "Advanced"-options. If this option is not set there shouldn't be an issue with identical vi-names.

Regards, Jens

[GerdW]

Hi Steffen,

to add to Jens' suggestion:

I'm using this code to start FPGA on several cRIO chassis for years without any problems at all…

[Steffen01]

ok, thanks, will try tomorrow. There has to be a simple solution.

Guess when I deploy, it stops the cRio, then loads all vis into voilatile memory, thats why it works. Cannot remeber the name, put all the vis in memory, select startup vi, set lauch startup.rtexe false, see how that works.

[Steffen01]

compiled version does not work either. When I run it in Labview, on 2nd run after Reset the cRio sends

Exception code: 0x00000006 and then whats in reboot.rtf, then disconnects.

When I delete the lvbitx file on the cRIO and reboot, it does not come back. So I guess only when I run it from Labview it finds the lvbitx file on the PC and then runs it. That's why it only works from Labview.

There was something about replacing firmware/personality on the cRIO. There is a personality 2.0 lvbitx file on the crio, it I back this one up and replace it with mine?

[Steffen01]

got the guys from NI here today. They narrowed it down to one vi. Startup.rtexe runs when compiled without that vi. Hope I get an answer soon what caused it.

[Steffen01 · Accepted solution]

startup.rtexe did not start because issue with a shared variable in one vi. Got it working now.

Guess it would be nice to know the reason why.

[Steffen01]

in hindsight, there are a few discussions, startup.rtexe broken because of shared variables. I found them when I searched for how to fix corrupt shared variables library....