EDT, Inc.
2019 April 29
28
VisionLink F-series
Troubleshooting
For best performance, install your EDT board in a bus that is not shared with any other devices and that meets the
board’s speed requirements, as discussed in
Problems With Your Applications
In applications using EDT libraries, a mismatch between driver and library software versions can cause application or
system failures. Thus, when updating a device driver, always recompile and relink applications which use EDT libraries.
Use the PDVDEBUG and EDTDEBUG environment variables to enable debug console output from the EDT libraries.
Both libraries are documented on the EDT website.
Applications that use the EDT digital imaging library can set the PDVDEBUG environment variable to 1 or 2. A value of
1 turns on call trace information from most (though not all) library routines; a value of 2 enables more verbose trace
information. A value of 0 turns off debug output. Setting the EDTDEBUG environment variable to one or two will provide
even more detailed debug output from the underlying EDT DMA library.
The EDT message handler library provides generalized error- and message-handling for EDT software libraries and can
be helpful in debugging your programs. See the EDT message handler library in the API for specific routines and usage.
Before seeking technical support, try to reproduce the problem with such EDT applications as
take, simple_take,
or
vlviewer
; if you cannot do so, then compare your code with EDT code to see if you can find the issue.
A simple example program that demonstrates the problem also is helpful.
Problems With Threads
The driver and libraries for your VisionLink product use threads. If you are using third-party software that is not thread-
safe, contact your third-party vendor to determine if a thread-safe version is available.
Problems With Firmware
You may need to update the PCIe interface flash memory with
pciload
under these conditions...
•
If you install a new device driver or switch to an FPGA configuration file with special functionality;
•
If your firmware becomes corrupted;
•
If the board is not seen in the system or is missing functionality that is in newer boards;
•
If the firmware loaded on the board does not match the camera mode.
Firmware: FPGA Configuration (.bit) Files on page 22.
