by support »
Hello,
When things work properly, Xillybus' driver generates device files as /dev/xillybus_{something}. These files don't store anything, but are a means for communication with the hardware.
In your case, it seems like the device files weren't created. And indeed, you weren't allowed to create a file under /dev/ as non-root. Once you gained root privileges, you wrote the data into the disk until it got full. Judging by the impressive rate (5.8 GB/s), all data went to the disk cache in RAM. I suppose you saw some disk activity soon after this.
Same explanation for /dev/xillybus_source.
Why the device files were absent is a question in itself. If the FPGA was loaded properly before the computer's powerup, check if the PCIe device was detected with lspci. Also take a look on the logs (e.g. with dmesg).
Regards,
Eli
Hello,
When things work properly, Xillybus' driver generates device files as /dev/xillybus_{something}. These files don't store anything, but are a means for communication with the hardware.
In your case, it seems like the device files weren't created. And indeed, you weren't allowed to create a file under /dev/ as non-root. Once you gained root privileges, you wrote the data into the disk until it got full. Judging by the impressive rate (5.8 GB/s), all data went to the disk cache in RAM. I suppose you saw some disk activity soon after this.
Same explanation for /dev/xillybus_source.
Why the device files were absent is a question in itself. If the FPGA was loaded properly before the computer's powerup, check if the PCIe device was detected with lspci. Also take a look on the logs (e.g. with dmesg).
Regards,
Eli