Tegra-pcie 10003000.pcie-controller: PCIE: no end points detected

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hi ,
I use TX2 board and M2.E connector is mounted with a wifi card. When I tried lspci, I did not see any thing.

~$ dmesg | grep pci
[ 0.464638] GPIO line 459 (pcie0_lane2_mux) hogged as output/low
[ 0.473365] iommu: Adding device 10003000.pcie-controller to group 49
[ 0.473397] arm-smmu: forcing sodev map for 10003000.pcie-controller
[ 1.129032] tegra-pcie 10003000.pcie-controller: 4x1, 1x1 configuration
[ 1.130125] tegra-pcie 10003000.pcie-controller: PCIE: Enable power rails
[ 1.130590] tegra-pcie 10003000.pcie-controller: probing port 0, using 4 lanes
[ 1.134048] tegra-pcie 10003000.pcie-controller: probing port 2, using 1 lanes
[ 1.278487] ehci-pci: EHCI PCI platform driver
[ 1.278549] ohci-pci: OHCI PCI platform driver
[ 1.552900] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[ 1.964980] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[ 2.368618] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[ 2.370655] tegra-pcie 10003000.pcie-controller: link 0 down, ignoring
[ 2.770508] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[ 3.172846] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[ 3.574982] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[ 3.577016] tegra-pcie 10003000.pcie-controller: link 2 down, ignoring
[ 3.781983] tegra-pcie 10003000.pcie-controller: PCIE: no end points detected
[ 3.782319] tegra-pcie 10003000.pcie-controller: PCIE: Disable power rails

Any input would help. Thanks.

2

Even if firmware were required this should at least show up. Is this a dev kit carrier board? Is there any kind of adapter between the m.2 slot and the card? Have you been able to test this on any other computer?

3

THis is on TX2 carrier board only. Yes there is a adapter board between M2.E and the Wifi card. In other intel platform, it is working in the stable manner.

4

There may be a signal quality issue in this case. Logs of this most likely would show up in bootloader stages even if not in the Linux kernel. You’ll want to provide a full boot log via serial console (which shows boot content prior to Linux starting…dmesg can only show what the Linux kernel sees). Some serial console info here:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

6

Which release are you using? Probably missing this patch.

1 Like