LabVIEW 2020 FPGA Module Bug Fixes

Aperçu

The following items are notable issues fixed between the release of LabVIEW 2019 FPGA Module and LabVIEW 2020 FPGA Module, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabVIEW 2020 FPGA Module.

Bug Fixes

Bug Number

Legacy ID

Description

Details

123762 733478

Opening more than 127 concurrent FPGA Interface sessions causes a crash.

Attempting to open more than 127 concurrent FPGA sessions using the LabVIEW FPGA Interface API, the FPGA Interface C API, or the FPGA Interface Python API causes a crash.

Workaround:

Modify the value of the TableSegmentSize token in the nirio.ini file to be a power of two greater than or equal to the number of sessions required. For example, increase the value from the default of 128 to 256.

Reported Version:

LabVIEW FPGA Module 2018

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 16, 2019

229293 660205

When using the FPGA Interface C API, some debugging tools may report a dynamic memory leak.

When using the FPGA Interface C API, a memory leak may be reported by third-party debugging tools. This memory leak will only cause memory growth if the NiFpga_Initialize() and NiFpga_Finalize() functions are called continually or in a loop, and should not impact normal usage.

Workaround:

Call NiFpga_Initialize() and NiFpga_Finalize() only once in the application, during the program initialization and exit procedures respectively.

Reported Version:

LabVIEW FPGA Module 2017

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 20, 2018

223923

LabVIEW FPGA does not detect that an external IP source is already encrypted and will encrypt the file a second time.

If a user attempts to import an external IP that is already encrypted on some Xilinx Vivado FPGA targets, the LabVIEW FPGA compilation process fails to detect this and encrypts the file a second time.

Workaround:

Add UserRTL_ to the start of the external IP source file name to prevent LabVIEW FPGA from encrypting it.

Reported Version:

LabVIEW FPGA Module 2017

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 15, 2020

184098

Desktop Execution Trace Toolkit reports reference leaks when executing a VI that opens and closes FPGA VI references in simulation mode.

Desktop Execution Trace Toolkit reports reference leaks when executing VI that opens and closes FPGA VI references with the FPGA Target Execution Mode set to simulation.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW FPGA Module 2018

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 15, 2020

896190

Unintended increase in BlockRAM resource usage for FFT Express VI when using "Single Channel, Multiple Samples" Input Mode.

When using certain configurations of the FFT Express VI with the "Single Channel, Multiple Samples" Input Mode, there is a large increase in the amount of BlockRAM resources used by the Express VI. 

Workaround:

Use Xilinx IP or multiple parallel instances of the FFT Express VI in "Single Channel, Single Sample" Input Mode.

Reported Version:

LabVIEW FPGA Module 2019

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 15, 2020

124013

A FPGA session reference type definition pointing to a bitfile can cause LabVIEW to crash if a type definition for a data type in the FPGA interface is modified.

If a user updates a control type definition which is used in a LabVIEW FPGA bitfile, LabVIEW does not update any type definitions tied to that FPGA bitfile with the new type information. Attempting to run a VI using the FPGA bitfile type definition in this scenario will cause LabVIEW to crash.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW FPGA Module 2018

Resolved Version:

LabVIEW FPGA Module 2020

Added:

May 15, 2020

Additional Patch Information

These patches currently do not have any special instructions.