LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

loading different bitx file

Solved!
Go to solution

I plan to have two FPGA VIs.  They are identical in terms of controls and indicators that are on their front panels, but the logic is different.  I want to compile them into two seperate bitx file and the host VI will select the correct bitx file at run time.  If I do that, do I just put two open FPGA reference nodes into two different cases of a case structure?  Is that the correct way?  Would there be a conflict in the FPGA referfernce, since I am opening two different bitx file?  What is the proper way of doing this?  Thanks!

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 1 of 3
(2,818 Views)
Solution
Accepted by topic author jyang72211

What version of LabVIEW are you using?  If 2013, it got a lot simpler (Open Dynamic Bitfile Reference).  You just need to supply a reference for the "Interface" of the FPGA.  Since they are using the same, just create a constant from the Type input, right-click on the constant and select "Configure FPGA Reference...".  A dialog will pop up, choose to import from a bit file.  So you can now call any FPGA bit file dynamically (just supply the bit file location) as long as it has the same interface.

 

If you are using an older version of LabVIEW, well, the best method I have found is to open a reference inside of a case structure to the specific bitfile you want.  Just pass the reference out of the case structure.  Since they have the same interface, you shouldn't have any issues.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 2 of 3
(2,809 Views)

The new function in 2013 is exactly what I need.  I will be using LabVIEW 2011 for that project though, so I will use a case structure then.  Thanks!

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 3 of 3
(2,766 Views)