Jump to content

Error 74 - Open FPGA Ref with .bit file


Recommended Posts

Using VIPM, if you build a VI package that contains a VI which contains a FPGA Open Reference node that links to a bitfile (*.lvbitx) instead of a VI in the project, VIPM will return error 74 from a Library:Open node. This problem only occurs when building a package using LabVIEW 2012 or later. It does not occur in LabVIEW 2011 or earlier.


This issues is caused by a change in behavior of a private Invoke node (Linker.Read Info from File) which is used upstream in the OpenG Builder library. This method returns a list of components (subVIs, controls, TypeDefs, etc.) used in a VI. In LabVIEW 2011 and earlier this method when run on a VI containing a FPGA Open Reference node that links to a bitfile (*.lvbitx), does not include the bitfile in the list of components. Starting with LabVIEW 2012 the bitfile (*.lvbit or *.lvbitx) is included in the list. The type of component returned by the Linker Read Info from File method for a bitfile is XNode Build Dependency. This type did not exist prior to LabVIEW 2012.


The Type field from the Invoke node is mapped to the Type (new) field in the Open G Builder cluster, but the OpenG Builder library was not updated to account for this change in behavior. Therefore based on the old code, it incorrectly maps a bitfile (Type: XNode Build Dependency) to Type (new): Ladder Diagram in the OpenG Builder cluster. In addition OpenG Builder contains a more coarse Type field in its cluster, and the XNode Build Dependency type is incorrectly mapped to a Library instead of an External Subroutine in this field.





Update Read Linker Info__ogb.vi in the OpenG Builder library (ogb.llb) to account for this change and correctly map a bitfile to External Subroutine. This alleviates the downstream issue of trying to open the bitfile as a library in Library:Open.


In VIPM this VI is stored in a support library (ogb_2009.llb) which is located in ..\JKI\VI Package Manager\support. To fix the issue, replace the existing file with the updated attached file and restart VIPM.


Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.