The question about PCIE

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hi,

I connected the AW WLAN+Bluetooth Module to TX2 by miniPCIE.
The module is M.2 interface, I connected to TX2 through M.2-to-miniPCIE.
Before install driver, I will check device has been detected or not.
Then TX2 con’t recognize the PCIE device.
When I input command (lspci), it output nothing:

~$ lspci
~$ sudo lspci
~$ sudo lspci -vvvv
~$ lspci

What should I do?
Thanks.

2

The module uses Marvell 88W8997 chip.

3

And the same question with rtl8821ce by miniPCIE.
Does anyone know where is wrong?

4

Can you please share the ‘dmesg’ output?
Also, please try adding “nvidia,disable-clock-request” to all the sub-nodes (“pci@1,0”, “pci@2,0” and “pci@3,0”) of “pcie-controller@10003000” ? and update that log as well?

5

Hi vidays,

The “dmesg | grep pci” command shows as follow,

ISBU:~$ dmesg | grep pci
[    0.483393] iommu: Adding device 10003000.pcie-controller to group 49
[    0.483419] arm-smmu: forcing sodev map for 10003000.pcie-controller
[    0.887454] tegra-pcie 10003000.pcie-controller: 4x1, 1x1 configuration
[    0.888636] tegra-pcie 10003000.pcie-controller: PCIE: Enable power rails
[    0.889076] tegra-pcie 10003000.pcie-controller: probing port 0, using 4 lanes
[    0.892515] tegra-pcie 10003000.pcie-controller: probing port 2, using 1 lanes
[    1.415527] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    1.822488] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    2.229583] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    2.231616] tegra-pcie 10003000.pcie-controller: link 0 down, ignoring
[    2.636557] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.043917] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.437554] ehci-pci: EHCI PCI platform driver
[    3.437601] ohci-pci: OHCI PCI platform driver
[    3.468576] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.470606] tegra-pcie 10003000.pcie-controller: link 2 down, ignoring
[    3.693098] tegra-pcie 10003000.pcie-controller: PCIE: no end points detected
[    3.697947] tegra-pcie 10003000.pcie-controller: PCIE: Disable power rails

After adding “nvidia,disable-clock-request” to all the sub-nodes (“pci@1,0”, “pci@2,0” and “pci@3,0”) of “pcie-controller@10003000”. The log stays the same as above.

ISBU:~$ dmesg | grep pci
[    0.483673] iommu: Adding device 10003000.pcie-controller to group 49
[    0.483701] arm-smmu: forcing sodev map for 10003000.pcie-controller
[    0.831335] tegra-pcie 10003000.pcie-controller: 4x1, 1x1 configuration
[    0.832504] tegra-pcie 10003000.pcie-controller: PCIE: Enable power rails
[    0.832957] tegra-pcie 10003000.pcie-controller: probing port 0, using 4 lanes
[    0.836624] tegra-pcie 10003000.pcie-controller: probing port 2, using 1 lanes
[    1.390285] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    1.798424] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    2.205934] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
[    2.207968] tegra-pcie 10003000.pcie-controller: link 0 down, ignoring
[    2.613185] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.020087] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.372977] ehci-pci: EHCI PCI platform driver
[    3.373029] ohci-pci: OHCI PCI platform driver
[    3.571539] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
[    3.573592] tegra-pcie 10003000.pcie-controller: link 2 down, ignoring
[    3.774216] tegra-pcie 10003000.pcie-controller: PCIE: no end points detected
[    3.774556] tegra-pcie 10003000.pcie-controller: PCIE: Disable power rails
6

Well, the log shows that the link didn’t come up with respective cards.
Since you mentioned that the cards are of miniPCIe form factor, how are they connected to Jetson board as it has only CEM slot and M.2 Key-E slot? If you are using any kind of adapters, please make sure that they are in good working condition.

7

Hi,

Sorry, We got it wrong.
We used a transverter, that transformed miniPCIe to M.2, and connected to Jetson board M.2 interface.
Now the question we are facing is we can’t see any output for “lspci” command.
So we want to know whether the question caused by the WLAN+Bluetooth module, TX2 devkit or the OS.
Thanks.

8

Even in this case, if the log looks the same as the old one, then, I think the converter is not able to establish the link properly.