PCIe a10_hip Several issues: MSI-X conduit/signals not exposed in non-SRIOV mode, no Gen3@8Gbps training (can't get past 5Gbps), Configuration space "capabilities" enabled but not selected in PD, etc.
I have several posts/questions raised on the FPGA Tools community because I assumed I was having issues configuring the PCIe IP in Platform Designer. Just in case this is the better forum I'll raise them again in this single post:
a) with SR-IOV enabled the link won't train at 8Gbps, links-up at 5Gbps. Same core with SR-IOV not enabled works fine. Is/are there control signals I need to toggle/set at the top-level when SR-IOV is enabled?
b) with SR-IOV "not" enabled, and MSI-X "enabled", I can't get the MSI-X conduit/signals exposed to the application layer (note: MSI-X does appear enabled in the PCIe Capabilities Space - enumerated with it enabled). If SR-IOV is turned on (single PF, no VFs) and MSI-X is enabled I get those signals (app_msix_xxxx).
c) with SR-IOV "not" enabled the Virtual Channel capabilities is exposed in the PCIe config space, but I did not enable anything related to VC in Platform Designer.
d) there is another question on this forum about supporting more than 64 non-posted tags when configuring the H-IP for three PFs, please see that one if you think you have an answer for it.
Update: 12/04/18 - I was looking into a few of my questions further, some thoughts based on the lettering above:
b) With an Avalon-MM DMA environment selected the MSI-X signals appear at the application layer, along with additional control signals I can see in an errata but not in the manual's signal list (such as msix_control[15:0]).
c) it looks like the VSEC is related to the support for CvP. In SR-IOV this capability does not appear to be supported. Also, on another post I see with SR-IOV that the AER capability is always in the config space (I have not checked whether or not the "Enable Advanced Error Reporting" configuration (on/off) affects whether it indicates enabled (supported) or not.
More to follow...