03-11-2014 10:14 AM
I have been compiling FPGA code in Labview 2013 for the NI myRIO and can successfully get a working code. however when i try to use it on another computer the .lvbitx file name changes from the one that is in the build specification. i have tried selecting the newly named file through the build specification but when check the signature it says "the bitfile does not match".
is there some reason for this?
03-12-2014 05:00 AM
Hi stuwatt,
That is strange behaviour. What happens if you rename the bitfile to match the build specification?
Best Regards,
Chris
03-12-2014 05:28 AM
Hi stuwatt,
As a follow up question, do you actually call the FPGA bitfile from a real-time VI on the RIO or is this a stand alone FPGA bitfile?
Best Regards,
Chris
03-12-2014 10:55 AM
Thanks for your reply.
I tried changing the build spec but it didnt work.
I am calling the bitfile from a real-time VI on the myRIO. i have the reference set up to use the bitfile rather than refering through an FPGA VI.
03-12-2014 11:10 AM
Hi stuwatt,
What happens if you actually change the name of the bitfile, rather than the build spec itself?
Best Regards,
Chris
03-12-2014 11:38 AM
The following link might be of interest to you w.r.t. the name change:
http://digital.ni.com/public.nsf/allkb/B76C5ED987F464EC862579750059A761
I've followed that advice hundreds of times with cRIO and sbRIO code without seeing any signature errors.
03-26-2014 07:09 PM
Thanks for the replies. I took a look into all the suggestions but i can only get one of 2 FPGA codes to work. i have attached the code in a zip folder if anyone is willing to have a look and give some insight i would be very greatful.
i can get "FPGA Blip Generator" to match by changing the bitfile name in the build spec or vice versa however "FPGA - 4 - Final w sub" still wont match.
Cheers