Short of the story is that, I am stuck here, I need my FPGA to be visible in the lspci list without restarting the linux. Here it is mentioned that the fakephp driver was removed from mainstream linux since PCI core has similar functionality, but he never mentioned how. modprobe fakephp worked and driver loaded but somehow I didn't get this fake device in my device list. After solving a couple of deprecated function problems, it is compiled for Linux Kernel v5.4. For that I took the fakephp.c driver from an old linux repo and ported it to ours. I also learned that there was a method in old linux times (v2.6) called adding a Fake PCIe Device which physically doesn't exist to solve this problem. Or there is no device or bus to set power off and on back like echo 0 > /sys/bus/pci/slots/./power But the rescan command never does that.Īlso in the system there is no pcie device to execute echo 1 > $pcidevice/remove in order to make rescan functional. But I couldn't find a solution for this so far.Īccording to the Texas Instrument support forum, they said if the PCIe link is not trained at the boot time, rescan command never works.Īt the boot time, while linux loads a pci driver, it tries to establish a PCIe link, I can see that with an oscilloscope, PERST pin is asserted and PCIE_CLK generated for a while and then stops if it can not detect any device. Somehow I need to tell the linux that whatever it's doing at the boot time, please do it again at runtime. With Bvckup 2, there aren’t any cloud services involved, there’s no file versioning, and it won’t compress any folders. Rebooting the linux is not an option for us. In this review, I will be telling you why Bvckup 2 is possibly the simplest and easiest unidirectional file synchronization you will ever have used and yet, it still packs a punch. When I first execute echo "1" > /sys/bus/pci/rescan as suggested here and here and then lspci, I still get nothing.īut if I reboot the linux without reseting the FPGA, it starts being visible in the lspci list. Its not as bad as it may sound, however enumerating files doesnt give you their security descriptors. but then it means that the app needs to rescan the source to understand what changed. Once the Linux is fully booted, we configure the FPGA and only after that it starts acting as a PCIe endpoint (device).Īt this point, when I run lspci -> it returns nothing. I will make bvckup itself expand such variables if they are present in pre/post-command line, but this will be in the next version. When we power up the board, the FPGA is not yet configured, so it acts as if it was not on the PCIe bus. This board has one PCIe bus and that one is connected to an FPGA. We have an embedded board that has an iMX8M-Plus Processor and Linux v5.4.161.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |