05-22-2007 10:05 AM
05-29-2007 09:35 AM
Richard Keromen
05-30-2007 02:06 AM
Hi Richard !
Euhh i knew that....
If I want to use different bitfiles, I must open the reference for each bitfile and close the reference at the end...
What i wanted to do is to give the bitfile as an input of the open function and to have general properties / methods to acceed to the variables but i search and i think that's not possible ... but I think that could be a good idea for further FPGA improvments...
Thanks, sorry i posted the message twice...
06-18-2010 07:45 AM
Hi,
3 years elapsed and still looks like no solution. KaBooOoom is absolutely right. Right-clicking on VI icon can be good for academic games, but I'm developing comertial compiled applications and it is really big problem. It drives me really angry on the whole stuff if it is not possible to download different bitfiles on demand. Factory workers do not care about some external tools for downloading bitfiles...
08-23-2010 05:28 PM
This is going to be a rather huge problem for me. We are developing an ATE system that will test multiple units that require different FPGA configurations. Not having the ability to programatticly load a bitfile is a major drawback. We're using Teststand and it sure would be nice to have the bitfile loaded to the FPGA when a sequence file is opened.
08-24-2010 12:26 PM
Hello,
I know it is possible to download a Bitfile to one or more FPGA targets by using a specific VI called “Download Bitfile.vi”. This VI can be found in the “NI-RIO System Replication Tools”. You can find more information about this by following this link : FPGA Target System Replication.
Alternatively, it is possible to download a Bitfile to a target without using LabVIEW FPGA. I advise you to follow this link if you are interested : How Do I Download a Bitfile to My Target Without LabVIEW FPGA?
I hope this information helped you.
Best Regards
Guillaume H.
National Instruments France
08-24-2010 02:24 PM
It is possible to download bitfile, but 1 combination of bitfile (1 specific compiled VI) + 1 exact HW target creates 1 unique FPGA reference, at least till LV2009. Iˇm not sure yet about dynamic FPGA reference in LV2010. But in LV2009 it meant that litle bit different VI, even with the same interface (read/write controls) had to go on another wire, i.e. with different serving diagrams. And also exactly the same VI compiled for 2 different targets had to be served on two distinct wires with different diagrams.
08-25-2010 02:15 AM
Hello,
You will indeed need different pre-compiled Bitfiles in order to download them on the FPGA target using the « Download Bitfile.vi » VI.
You will also need slightly different VIs for different FPGA board, due to hardware differences.
Best regards,
Guillaume H.
National Instruments France
08-25-2010 02:27 AM
Yes, and this is what we complain about - different bitfiles can be opened with different Open FPGA reference functions with __absolute__ path only (it is real pain! compiled exe doesnot work from any other path in computer then the original source path), and "slightly different" VIs to handle different bitfiles or FPGA boards, when the interface is the same - it is too strict and unnessecary - it could be much more flexible!