LabVIEW
Driver Xilinx Artix7
Hi AP,
long way to get an answer: call NI tech support, then call Xilinx tech support, then call NI tech support again… 😄
(Note: there is some sarcasm in this answer…)
Short way to get an answer: Why do you think NI should have drivers for your hardware? They bundle their resources to support their own hardware!
Hi AP,
did you already talk with NI?
I don't think it's reasonable to buy LabVIEW - atleast not before you had your conversation with NI tech support!
I don't know how to do a PCIe Windows driver.
Nor do I.
I guess you will find relevant information at MSDN!
There might be some confusion about what the OP wants to do and what can be done.
So there is a board which uses a Xilinx FPGA chip to implement the PCIe interface I would assume. And the OP wants to interface this to LabVIEW.
Most likely this is not about interfacing the LabVIEW FPGA module to the FPGA chip on the board to allow LabVIEW to deploy compiled FPGA code. If this would be the intend of the OP we can stop here as that is simply impossible without lots and lots of inside knowledge about LabVIEW and Xilinx, that only some engineers inside NI do have.
More likely this is about writing a driver that can access the hardware resources on the board. For that you first need a kernel mode device driver which initializes the hardware, manages all the read and write access to the board, as well as more advanced features like shared memory and DMA transfer if required. And developing a kernel mode device driver for any OS isn't something any programmer can do, nor which would be done in a few days of programming.
You need to get the according DDK, a good C compiler toolchain and lots and lots of patience to get this even halfway working. To make it a professional grade device driver is even more complicated (much more debugging: "It works!" is only maybe 10% of the work to get it really finished! And you also need to sign it in order to be able to install it in modern OSes (Windows 8 or 10 or MacOSX), so you would need to get a certificate from one of the official Certificate Authorities.
The VISA driver wizard can ease this somewhat, as you do not need to develop a kernel device driver but rather operate in user space. You still need to know exactly what registers and memory addresses you need to access in what way but since you developed the board, that should be peanuts, right! However this approach does have certain drawbacks as all the board specific work is done in user space andthe VISA Register Access API doesn't support advanced features like DMA etc. If you only need to read and write some registers and memory addresses this might be not a problem but for performance high speed data transfer this would be a serious limitation.
