What is the best way to secure a bitfile so that it is not possible to reverse engineer? I assume the flash that holds the bitfile cannot be read? Does any of the VIs also contain the bitfile embedded?
Does anyone have any experience of creating an app to automatically download the bitfile (e.g. from an automated installer). Trying to make upgrades as smooth for the customer as possible...
When running as a target (not with dev environment running), is it still posible for the bitfile to be loaded to the FPGA from a place other than the flash? Normally, the flash will hold the bitfile that is needed, but is it the case that it is also stored in the rtstartup.exe? If so, can this option be turned on/off?
When I later updated the flash with a new, recompiled bitfile (using RIO Device Setup tool) it seems the previous version of the bitfile was enabled again (rtstartup.exe was not copied over to the target after the recompile). The rtstartup.exe is 151 kB larger than the bitfile, so this seems plausible.
Applies to LV 8.5
This is an old thread but in case anyone else wanted to know.
We are using a win dll cretaed in labview 2010 as the go between for PC (dotnet 4.0) and the RT/FPGA.
There are prebuilt vi's to upload and download bitfiles. We made and exported two commands in the dll (vi's with a filename as a param) to call these prebuilt these vi's and can upload or download new bitfiles at will, all you need to do after that is a restart.
Hope this helps