LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Very large FPGA VI

Hello all,

 

I'm using LabVIEW 8.5.1 and FPGA-Toolkit 8.5.1. 

I created a FPGA-VI which uses 30MB(!) of disk space, but the size of front panel, block diagram, code and data is only 1,2KB (see picture).

FPGA_VI_30.MB

If I copy all code from the block diagram to a new VI, the file size shrinks to 1,3MB disk space.

Does anyone have an explanation? Is the VI corrupt?

 

Uli 

Message Edited by UliB on 09-18-2008 04:26 PM
0 Kudos
Message 1 of 5
(3,055 Views)
I am not certain about what is happening with your VI but something would make lots of sense.

 

I just posted this somewhere else, in case you're not familiar: In case you don't already know, once your code is written using LabVIEW, to be able to run on the FPGA machine, it has to be compiled, or even transformed, into a series of logic elements. The process starts by tranforming the LabVIEW code into VHDL (or verilog, I don't know which one they use) and then the Xilinx tool (company who makes the FPGA) transform this file into a complex series of logic operations (down to the level of AND and OR gate basically).

 

If you want to download the code again onto the board, it would make lots of sense to save all the work done on the HD to save yourself all the compile time the next time. My guess is that  the VHDL file, the bit file (raw info downloaded to the FPGA) and other parts or results from the process are saved along the way. Hopefully someone from NI can let us know if it is true.

0 Kudos
Message 2 of 5
(3,017 Views)

Hello OlivierL,

 

thank you for your reply.


OlivierL wrote:
..., it would make lots of sense to save all the work done on the HD to save yourself all the compile time the next time. My guess is that  the VHDL file, the bit file (raw info downloaded to the FPGA) and other parts or results from the process are saved along the way. Hopefully someone from NI can let us know if it is true.

You are right, the bit file is saved, but it is a separate file (I think ".lvbit", but I'm not at work, so I can't have a look.)  

As I told earlier, I copied the code to a new VI. Then I compiled it, but the size of the VI remained at 1.3MB. So I don't think there is something from the compilation in the VI.

 

Meanwhile I found two older Versions of the VI. The first one uses 12MB on disk, the second 26MB on disk, although there are only few difference in code between the versions.

 

Uli 

0 Kudos
Message 3 of 5
(2,994 Views)

Hello,

 

a mass compile reduced the file size to 1.3MB again.

According to this KB: How Can I Force a VI to Recompile? upgrading from 8.2 to 8.5 could be a reason. Maybe,...

 

Uli

0 Kudos
Message 4 of 5
(2,907 Views)

Hi Uli, 

 

It doesn't really gives you a reason why the original VIs was so big though. If you figure it out over time, let us know! I'd be curious to know what the VI kept in memory to be that size. It may as well be a bug from LV so I wouldn't spend too much time on it.

 

Olivier 

0 Kudos
Message 5 of 5
(2,887 Views)