--- Quote Start ---
Have you checked if the FPGA has been programmed successfully and if the board has been enumerated properly in the PC? If using Linux, run the lsmod command and check if the driver is loaded. Have you checked if the device ID in the driver matches with the one in the board?
--- Quote End ---
I second eapenabrm's suggestions.
1. Make sure the FPGA is programmed with the correct image. A simple way would be to connect a counter signal to an LED so it keeps blinking.
2. Check if lspci shows the Altera FPGA as a device ( On linux) or on the device manager ( on windows). Again check the device id in the PCIe QSYS component or what is returned by lspci are the same and make sure your driver is looking for the same device.
3. For the reads, I had made a mistake in connecting my QSYS components. The slave attached to the PCIe component did not return a readdatavalid, whereas the PCIe component expected it. Thus, I never "read" anything back. After I changed it, the reads started to work.
4. I would also suggest using a signal tap to monitor the BAR (register interface). You can trigger on reads or writes, while the driver is running. You can then see if the behaviour of the system is as expected on not.
I used the following steps to setup the driver, and not their scripts
rmmod altera_dma.ko
rf /dev/altera_dma
cat /proc/devices # choose a device number that isn't already taken. In this case I have used 243
mknod /dev/altera_dma c 243 0
chmod 0644 /dev/altera_dma
ls -al /dev/altera_dma
insmod altera_dma.ko
rm -f ./user/user
gcc ./user/user.c -o ./user/user
./run
Honored Contributor
