LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FPGA C API Interface - NiFpga_Open error: -52008

Hello,

 

- I've compiled a bitfile for my NI7971R using Labview 2024 Q3.

- Base on PXIe 8861, NI RT LINUX 24 Q3

- Generated the neccesary files using C API Interface.

- Created a C console project and tried to connect to the FPGA.

 

My problem occurs when I run the code:

 

NiFpga_MergeStatus(&status, NiFpga_Open(NiFpga_FPGA_Bitfile,
			                NiFpga_FPGA_Signature,
			                "RIO0",
			                0,
			                &session));

// NiFpga_Initialize(); is called before NiFpga_Open, and it runs properlly.

 

I'm encountering error code -52008 when calling NiFpga_Open().
NiFpga_Initialize() is called beforehand and runs properly.

The status variable gives me the error -52008, which is not defined in the FPGA Interface C API error codes.

So, what does -52008 mean, and how can I resolve it?

Thanks.

0 Kudos
Message 1 of 5
(148 Views)

Something with the NI Platform Services is not right! The error range -52000 to -52031 is assigned to the NI Platform Services layer. NI-PAL is the underlaying driver system that manages everything hardware related for all NI software drivers. This is about accessing physical memory, DMA, Interrupts and PCI handling. PCI in this context is anything PCI related, this also includes the various PCI technologies used inside the chipset to interconnect various peripheral hardware including things like USB, memory management and more.

 

-52008 has as error message "An unexpected operating system error has occurred"

 

So either the NI PAL driver framework is not properly installed or damaged or some other part of the software driver architecture has a problem.

 

Is this on the same machine that you did your LabVIEW development on?

Does it work when you try to load the bitfile in a LabVIEW application?

If it is on a different machine, are you sure you installed the FlexRIO driver and any board specific RIO support driver package?

 

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 5
(111 Views)

Thank you very much for your response.
Here are the software versions used for both the hardware and the tools that generated the necessary files.
Could you please help me check if everything is compatible?

Thanks!

 

johndoept777_1-1744182757572.pngjohndoept777_2-1744182777153.png

johndoept777_4-1744182817872.pngjohndoept777_5-1744182833058.pngjohndoept777_6-1744182867272.png

 

johndoept777_7-1744182928253.png

 

0 Kudos
Message 3 of 5
(84 Views)

I can't really see real inconsistencies with this setup, except that you seem to have installed pretty much anything that your Software Bundle contains. I doubt that you need even half of that.

 

One thing that kind of seems slightly suspicious is the real-time firmware version 24.0, while almost everything else is 24.3 (respectively 2024 Q3) or better. I would start trying to see if there is a newer firmware version for your controller and if that doesn't help I would in fact install a later version of DAQmx, both on your development PC and then from there also update the DAQmx installation on your controller. The new DAQmx will also cause updates of the NI PXI Platform Services which is where NI-PAL is located in.

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 5
(80 Views)

Thank you again.
When I use LabVIEW 2024 Q3 and load the bitfile to the target FPGA module, everything works as expected without any issues.
Do you have any suggestions on what might be causing the error when using LabVIEW 2023 Q3, or anything I should check?

 

johndoept777_0-1744190239873.png

 

0 Kudos
Message 5 of 5
(65 Views)