Home » News & Events » Technology

QCA9377 doesn't work on xavier

Mar 04, 2024

Hi,

We are facing some issue with QCA9377. The QCA9377 uses M.2 E which uses PCIe for wifi and USB for BT. When ath10k_pci driver probes, it first sees “PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0000(Receiver ID)”. Then, got "failed to receive control response completion, polling… " error.

The full kernel error dmesg:

[    6.935042] ath10k_pci 0003:01:00.0: enabling device (0000 -> 0002)

[    6.935646] ath10k_pci 0003:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0

[    6.936128] pcieport 0003:00:00.0: AER: Multiple Corrected error received: id=0000

[    6.936267] pcieport 0003:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0000(Receiver ID)

[    6.939628] pcieport 0003:00:00.0:   device [10de:1ad2] error status/mask=00000001/0000e000

[    6.939825] pcieport 0003:00:00.0:    [ 0] Receiver Error         (First)

[    6.972170] pcieport 0003:00:00.0: AER: Multiple Corrected error received: id=0000

[    6.972324] pcieport 0003:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0000(Transmitter ID)

[    6.972531] pcieport 0003:00:00.0:   device [10de:1ad2] error status/mask=00001001/0000e000

[    6.972690] pcieport 0003:00:00.0:    [ 0] Receiver Error         (First)

[    6.972863] pcieport 0003:00:00.0:    [12] Replay Timer Timeout  

[    6.972979] pcieport 0003:00:00.0: AER: Corrected error received: id=0000

[    6.972997] pcieport 0003:00:00.0: can't find device of ID0000

[    7.098806] pcieport 0003:00:00.0: AER: Multiple Corrected error received: id=0000

[    7.098861] pcieport 0003:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0000(Receiver ID)

[    7.099074] pcieport 0003:00:00.0:   device [10de:1ad2] error status/mask=00000001/0000e000

[    7.099328] pcieport 0003:00:00.0:    [ 0] Receiver Error         (First)

[    7.099475] pcieport 0003:00:00.0: AER: Corrected error received: id=0000

[    7.099495] pcieport 0003:00:00.0: can't find device of ID0000

[    7.136562] pcieport 0003:00:00.0: AER: Multiple Corrected error received: id=0000

[    7.136591] pcieport 0003:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0000(Receiver ID)

[    7.136871] pcieport 0003:00:00.0:   device [10de:1ad2] error status/mask=00000001/0000e000

[    7.137044] pcieport 0003:00:00.0:    [ 0] Receiver Error         (First)

[    7.269652] ath10k_pci 0003:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0003:01:00.0.bin failed with error -2

[    7.269886] ath10k_pci 0003:01:00.0: Falling back to user helper

[    7.270861] ath10k_pci 0003:01:00.0: Direct firmware load for ath10k/cal-pci-0003:01:00.0.bin failed with error -2

[    7.271049] ath10k_pci 0003:01:00.0: Falling back to user helper

[    7.275733] ath10k_pci 0003:01:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 0000:0000

[    7.275740] ath10k_pci 0003:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0

[    7.276884] ath10k_pci 0003:01:00.0: firmware ver WLAN.TF.1.0-00002-QCATFSWPZ-5 api 5 features ignore-otp crc32 c3e0d04f

[    7.341669] ath10k_pci 0003:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0042,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA9377/hw1.0/board-2.bin

[    7.342629] ath10k_pci 0003:01:00.0: board_file api 1 bmi_id N/A crc32 544289f7

[   10.668806] ath10k_pci 0003:01:00.0: failed to receive control response completion, polling..

[   11.692915] ath10k_pci 0003:01:00.0: ctl_resp never came in (-110)

[   11.693166] ath10k_pci 0003:01:00.0: failed to connect to HTC: -110

[   11.709420] ath10k_pci 0003:01:00.0: could not init core (-110)

[   11.709799] ath10k_pci 0003:01:00.0: could not probe fw (-110)

I am pretty sure that ASPM is disabled. This is confirmed by lspci -vvv which shows the following in both the host and device:

LnkCtl:	ASPM Disabled

I tried set nvidia,max-speed to 1 and 2, none of them works.

It seems my issue is similar to this post:

Also, note that I have placed a different M.2 E pcie wifi module (from NXP/Marvel), and this one works. So, for sure this is NOT caused by hw issue.

I did tried different QCA9377 firmwares. One of them is part of rootfs of nvidia L4T. But none of them work.

Regards.