I’m trying to connect a m.2 WiFi module (Laird ST60-2230C-PU) to the Jetson Nano (on the original A01 devkit carrier board), however I am unable to detect the device on pci, here’s a grep of dmesg for pcie with the device connected:
[ 0.997175] tegra-pcie 1003000.pcie: 4x1, 1x1 configuration [ 0.998454] tegra-pcie 1003000.pcie: PCIE: Enable power rails [ 0.998826] tegra-pcie 1003000.pcie: probing port 0, using 4 lanes [ 1.002680] tegra-pcie 1003000.pcie: probing port 1, using 1 lanes [ 1.435917] tegra-pcie 1003000.pcie: link 0 down, retrying [ 1.847623] tegra-pcie 1003000.pcie: link 0 down, retrying [ 2.259908] tegra-pcie 1003000.pcie: link 0 down, retrying [ 2.262013] tegra-pcie 1003000.pcie: link 0 down, ignoring [ 2.367380] tegra-pcie 1003000.pcie: PCI host bridge to bus 0000:00 [ 2.378415] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt [ 2.378424] pcie_pme 0000:00:02.0:pcie001: service driver pcie_pme loaded [ 2.378522] aer 0000:00:02.0:pcie002: service driver aer loaded
If the device is not connected at all I don’t see the several “retrying” messages, so it seems like the module is almost detected. Does anyone have any experience with m.2 wifi modules like this? The module works just fine on the TX1, so expected it to have no problem on the Jetson Nano. The m.2 slot is confirmed working with the recommended intel m.2 WiFi module.
I’ve set the WiFi enable GPIO to the correct state for this module (which shouldn’t affect the PCIE detection anyway), and I’ve even masked off all non-functional pins on this module with kapton tape to eliminate the possibility that some pin voltage initialization state was affecting the initialization of the module. Anyone have any other ideas?