The PCIE device cannot be identified. Procedure

[Andyyyyy]

I have a device with PCIE interface. After I load it to Xavier, it is wrong. I am using “lspci-vvv” to check the PCIE card status, and the two bar space addresses are not allocated correctly. unassigned> ".

I’m going to ignore this problem and I’ll compile my source code into a *. Ko file and then apply “insmod” to load the driver.The driver can be loaded properly, but the sample program cannot be run because of the state of the PCIE interface.

I use “dmesg” to see the information that comes with installing the driver. I’ve read “cant’ enable device: Bar 0 [mem 0x00000000-0x000fffff] not claimed”. This is a deadly problem.

The PCIE card chip is SmartFusion2 SoC FPGA PCIe.

[kayccc]

Duplicated with The PCIE device cannot be identified. Procedure - Jetson & Embedded Systems / Jetson AGX Xavier - NVIDIA Developer Forums

[Andyyyyy]

Sorry, I don’t think I should put this case in the “kernel” category

[Andyyyyy]

*******************************************Jetson agx xavier arm64 info
0005:01:00.0 Non-VGA unclassified device: Actel Device 11aa
Subsystem: Actel Device 0000
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 0
Region 0: Memory at (32-bit, non-prefetchable) [disabled] [size=1M]
Region 1: Memory at (32-bit, non-prefetchable) [disabled] [size=64K]
Capabilities:

*******************************************X86 info
19:00.0 Non-VGA unclassified device: Actel Device 11aa
Subsystem: Actel Device 0000
Control:I/O0 Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- FastB2B- DisINTx-
Status: Cap+66MHZ- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- SERR- <PERR- INTx-
Latency:0,Cache Line Size:32 bytes
Interrupt:Pin A routed to IRQ 11
NUMA node:0
Region 0:Memroy at b5c00000(32-bit,non-prefetchable) [size=1M]
Region 1:Memroy at b5d00000(32-bit,non-prefetchable) [size=64K]
Capbilities:

[Andyyyyy]

Is there a better solution now?

[WayneWWW]

Feel like pcie device driver problem. Maybe dig into driver code and see what goes wrong.

[Andyyyyy]

Hi Wayne

I have checked the source code of PCIE device driver. In my opinion, it is not the problem of driver source code, but the incompatibility between ARM platform and “SmartFusion2” device.

I tried Xilinx’s FPGA PCIE device and it works.