Forum Discussion
New ContributorIntel PCIe Hard IP Trouble With EFI
Avalon busing appears broken, then you can use the linux 'lspci -vvv' command to verify if the host has correctly set the PCIe endpoint Control register.
As example below, the software driver at host side should set the Memory Space Enable bit[1] and Bus Master bit[2] in Command register to 1.
bit[1] Memory_Space_enable must set (Mem+)
bit[2] Bus_Master must set (BusMater+)
ContributorHi Sir
Please double check everything is implemented correctly in the IP and Quartus design.
1) nPERSTL0 is prepoerly connect to PCIe core's pin_perst
2) refclk usually comes from the pcie edge connector from host, ensure this clock always stable before FPGA configuration.
3) CLKUSR - ensure CLKUSR is properly driven, range between 100Mhz-125Mhz, it should also stable before device configuration starts.
Page 28 of below user guide describe about CLKUSR:
(https://www.altera.com/content/dam/altera-www/global/en_US/pdfs/literature/dp/arria-10/pcg-01017.pdf)
This pin is used as the clock for transceiver calibration, and is a mandatory requirement when using transceivers.
This pin is optionally used for Hybrid Memory Cube (HMC) calibration, as well as a configuration clock input for synchronizing the initialization of more than one device.
This is a user-supplied clock and the input frequency range must be in the range from 100 MHz to 125 MHz.
4) Next, to rule out design issue, you can refer/use the C10 PCIe example design available at below link to test in your setup.
MZoraI went through steps 1 through 3 and everything appears fine. This is in the Intel Cyclone 10GX demo board and all of those look find according to the schematic. For step 4, I copied most of the reference settings into my design but I can't use it directly for what I'm doing since I want to use Avalon-MM rather then Avalon-ST.
Like I said, everything work fine with conventional BIOS boot, but Avalon busing appears broken after EFI boot when the card is used(Registers read and set).
This puzzles me because except for the ability to physically map the device into the address space above 32bit(in my case it's still below 32bits) and the boot code on the card such as video or PXE(which I'm not using and have no plan to use), I didn't think conventional vs EFI made any difference.
