Errors

FPGA Interface C API Help 1.3

Edition Date: December 2010

Part Number: 372928D-01

»View Product Info

Functions of the FPGA Interface C API can return the following errors. All error codes have negative values. For any given error code, the equal and opposite positive value represents a warning, which alerts you to a similar problem or condition that does not cause a failure.

Note For any NiFpga_Status code returned that is not listed in this topic, you can look up the corresponding error string by following the directions found here.

Error Code	Name	Description
0	NiFpga_Status_Success	No errors or warnings.
−50400	NiFpga_Status_FifoTimeout	The timeout expired before the FIFO operation could complete.
−52000	NiFpga_Status_MemoryFull	A memory allocation failed. Try again after rebooting.
−52003	NiFpga_Status_SoftwareFault	An unexpected software error occurred.
−52005	NiFpga_Status_InvalidParameter	A parameter to a function was not valid. This could be a NULL pointer, a bad value, etc.
−52006	NiFpga_Status_ResourceNotFound	A required resource was not found. The NiFpga.* library, the RIO resource, or some other resource may be missing, or the NiFpga.* library may not be the required minimum version.
−52010	NiFpga_Status_ResourceNotInitialized	A required resource was not properly initialized. This could occur if NiFpga_Initialize was not called or a required NiFpga_IrqContext was not reserved.
−61003	NiFpga_Status_FpgaAlreadyRunning	The FPGA is already running.
−61024	NiFpga_Status_DeviceTypeMismatch	The bitfile was not compiled for the specified resource's device type.
−61046	NiFpga_Status_CommunicationTimeout	An error was detected in the communication between the host computer and the FPGA target.
−61060	NiFpga_Status_IrqTimeout	The timeout expired before any of the IRQs were asserted.
−61070	NiFpga_Status_CorruptBitfile	The specified bitfile is invalid or corrupt.
−61083	NiFpga_Status_ClockLostLock	A hardware clocking error occurred. A derived clock lost lock with its base clock during the execution of the LabVIEW FPGA VI. If any base clocks with derived clocks are referencing an external source, make sure that the external source is connected and within the supported frequency, jitter, accuracy, duty cycle, and voltage specifications. Also verify that the characteristics of the base clock match the configuration specified in the FPGA Base Clock Properties. If all base clocks with derived clocks are generated from free-running, on-board sources, please contact National Instruments technical support at ni.com/support.
−61141	NiFpga_Status_FpgaBusy	The operation could not be performed because the FPGA is busy. Stop all activities on the FPGA before requesting this operation. If the target is in Scan Interface programming mode, put it in FPGA Interface programming mode.
−61200	NiFpga_Status_FpgaBusyFpgaInterfaceCApi	The operation could not be performed because the FPGA is busy operating in FPGA Interface C API mode. Stop all activities on the FPGA before requesting this operation.
−61201	NiFpga_Status_FpgaBusyScanInterface	The chassis is in Scan Interface programming mode. In order to run FPGA VIs, you must go to the chassis properties page, select FPGA programming mode, and deploy settings.
−61202	NiFpga_Status_FpgaBusyFpgaInterface	The operation could not be performed because the FPGA is busy operating in FPGA Interface mode. Stop all activities on the FPGA before requesting this operation.
−61203	NiFpga_Status_FpgaBusyInteractive	The operation could not be performed because the FPGA is busy operating in Interactive mode. Stop all activities on the FPGA before requesting this operation.
−61204	NiFpga_Status_FpgaBusyEmulation	The operation could not be performed because the FPGA is busy operating in Emulation mode. Stop all activities on the FPGA before requesting this operation.
−61499	NiFpga_Status_InternalError	An unexpected internal error occurred.
−61703	NiFpga_Status_BadReadWriteCount	The number of elements to read or write must be less than or equal to the depth of the host memory DMA FIFO.
−63033	NiFpga_Status_AccessDenied	Access to the remote system was denied. Use MAX to check the Remote Device Access settings under Software»NI-RIO»NI-RIO Settings on the remote system.
−63040	NiFpga_Status_RpcConnectionError	A connection could not be established to the specified remote device. Ensure that the device is on and accessible over the network, that NI-RIO software is installed, and that the RIO server is running and properly configured.
−63043	NiFpga_Status_RpcSessionError	The RPC session is invalid. The target may have reset or been rebooted. Check the network connection and retry the operation.
−63100	NiFpga_Status_InvalidUsage	Invalid usage. The syntax is as follows: capigen.exe [-e] [<bitfile> [<output_directory> [<prefix_override>]]]
−63101	NiFpga_Status_BitfileReadError	The bitfile could not be read.
−63106	NiFpga_Status_SignatureMismatch	The specified signature does not match the signature of the bitfile. If the bitfile has been recompiled, regenerate the C API and rebuild the application.
−63192	NiFpga_Status_InvalidResourceName	Either the supplied resource name is invalid as a RIO resource name, or the device was not found. Use MAX to find the proper resource name for the intended device.
−63193	NiFpga_Status_FeatureNotSupported	The requested feature is not supported.
−63194	NiFpga_Status_VersionMismatch	The NI-RIO software on the remote system is not compatible with the local NI-RIO software. Upgrade the NI-RIO software on the remote system.
−63195	NiFpga_Status_InvalidSession	The session is invalid or has been closed.
−63198	NiFpga_Status_OutOfHandles	The maximum number of open FPGA sessions has been reached. Close some open sessions.