11-06-2009 12:02 PM
Hi there,
I need help when upgrading from LVFPGA8.2 to LVFPGA8.6.1.
This is what I did:
1. Remove FPGA card.
2. Uninstall old LabView version.
3. Install LabView 8.6.1.
4. Install FPGA 8.6.1.
5. Install NI-RIO 3.1.1.
6. Install patch for 8.6.1.
7. Mass compile the directory I want to work on.
I confirmed all the installation by checking "Measurement & Automation".
I opened up old project file and recompiled FGPA vi and it finished successfully. But when I tried to run the host vi, it poped up message indicating the related FPGA vi needs to be compiled??
Please help and thanks in advance.
11-06-2009 04:04 PM
In your host VI are you specifying the 'Open FPGA Reference' by bitfile or by VI? I believe I've seen this error in the past when the Open FPGA Reference was bound to a bitfile compiled from an older LabVIEW version rather than the re-compiled FPGA VI...
-Bob
11-06-2009 04:12 PM
Bob thanks for the reply. All my host vis are bound to FPGA vis not bitfiles.
11-06-2009 05:35 PM
Actually I tried to bind the host vi to the bitfile instead of vi itself and it worked. But the bitfile name is scrambled and hard to track when you have many vis.
Obviously the FPGA vi is not linked to the bitfile correctly.
11-09-2009 12:33 PM
Hi kvzhang,
What happens when you replace the Open FPGA Reference with a new one?
11-09-2009 01:00 PM
Kyle,
Can you explain a little bit what you meant by "replace the Open FPGA Reference with a new one"? A new "Open FPGA Reference" or a new FPGA vi associated with that "Open FPGA Reference"?
Kevin
11-09-2009 01:02 PM
Hi Kevin,
Just a new Open FPGA Reference. I'm just curious to see if we'll see the same issue.
11-09-2009 03:14 PM
Kyle,
I tried replacing with a new "Open FPGA Reference" and it showed the same result - showing the just compiled FPGA vi needs to be recompiled.
Also I noticed another thing maybe or maybe not related to this:
1. I save host vi and project explorer buy clicking "save-ALL".
2. When I open up the same project and then same host vi again, the vi and project explorer window showed an extra "*" next to it's name - meaning something has changed. But I haven't touched anything except just double clicking to open it.
Kevin
11-09-2009 04:49 PM
Hello Kevin,
Try performing a force compile on the VI hierarchy:
Following the force compile, save all changes. Now when you close and open the project and VI do you still see a "dirty-dot"?
Kind regards,
-Bob
11-09-2009 06:26 PM
Bob,
I tried force compile my top level FPGA vi based on your suggestion but it ended up with the message "Not enough memory to complete this operation".
After clicking "OK" the LabView exited by itself compeletely.
The computer I'm using is a Intel Core 2 CPU with 2.4GHz and 3.2G RAM.
Kevin