Tx2 Wi-Fi can't work

Hi,

My Tx2, host tools chain using Jetpack 3.3, rootfs using Jetpack 3.1(including apply_binaries.sh and nv_tegra/).

There is “mmc1: Timeout waiting for hardware interrupt.” in dmesg.

worker@master:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted
worker@master:~$ sudo iwconfig
usb0      no wireless extensions.

lo        no wireless extensions.

dummy0    no wireless extensions.

wlan0     no wireless extensions.

can1      no wireless extensions.

tunl0     no wireless extensions.

can0      no wireless extensions.

eth0      no wireless extensions.

worker@master:~$ dmesg
[ 3881.583200] 
               Dongle Host Driver, version 1.201.82 (r)
               Compiled in drivers/net/wireless/bcmdhd on Dec  6 2018 at 15:34:56
[ 3881.596878] wl_android_wifi_on in
[ 3881.600220] wifi_platform_set_power = 1
[ 3881.876419] mmc1: queuing unknown CIS tuple 0x80 (5 bytes)
[ 3881.948078] sdhci-tegra 3440000.sdhci: Tuning already done, restoring the best tap value : 21
[ 3881.957048] F1 signature read @0x18000000=0x17214354
[ 3881.965467] F1 signature OK, socitype:0x1 chip:0x4354 rev:0x1 pkg:0x2
[ 3881.972388] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
[ 3891.991985] mmc1: Timeout waiting for hardware interrupt.
[ 3891.997384] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 3892.003207] sdhci: Sys addr: 0x00000000 | Version:  0x00000404
[ 3892.009027] sdhci: Blk size: 0x00007040 | Blk cnt:  0x0000001e
[ 3892.014850] sdhci: Argument: 0x9d000020 | Trn mode: 0x00000022
[ 3892.020671] sdhci: Present:  0x01fb0106 | Host ctl: 0x00000006
[ 3892.026492] sdhci: Power:    0x00000001 | Blk gap:  0x00000000
[ 3892.032312] sdhci: Wake-up:  0x00000000 | Clock:    0x00000007
[ 3892.038133] sdhci: Timeout:  0x0000000e | Int stat: 0x00000000
[ 3892.043953] sdhci: Int enab: 0x00ff0033 | Sig enab: 0x00fc0033
[ 3892.049774] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 3892.055594] sdhci: Caps:     0x3f6cd08c | Caps_1:   0x18006f73
[ 3892.061415] sdhci: Cmd:      0x0000353a | Max curr: 0x00000000
[ 3892.067235] sdhci: Host ctl2: 0x0000300b
[ 3892.071147] sdhci: ===========================================
[ 3892.076999] dhdsdio_membytes: membytes transfer failed
[ 3892.084195] dhdsdio_membytes: FAILED to set window back to 0x18100000
[ 3892.090635] dhdsdio_download_code_file: error -1 on writing 2048 membytes at 0x00180000
[ 3892.098654] _dhdsdio_download_firmware: dongle image file download failed
[ 3892.108900] dhdsdio_htclk: Failed access turning clock off: -35
[ 3892.114818] dhd_net_bus_devreset: dhd_bus_devreset: -35
[ 3892.120503] dhd_open : wl_android_wifi_on failed (-35)
[ 3892.125639] wl_android_wifi_off in
[ 3892.129042] tegra_sysfs_off
[ 3892.131828] tegra_sysfs_rf_test_disable
[ 3892.135682] dhd_prot_ioctl : bus is down. we have nothing to do
[ 3892.141608] dhd_net_bus_devreset: dhd_bus_devreset: -35
[ 3892.147175] sdhci-tegra 3440000.sdhci: Tuning already done, restoring the best tap value : 21
[ 3892.156741] wifi_platform_set_power = 0
[ 3892.364449] 
               Dongle Host Driver, version 1.201.82 (r)
               Compiled in drivers/net/wireless/bcmdhd on Dec  6 2018 at 15:34:56
[ 3892.378118] wl_android_wifi_on in
[ 3892.381457] wifi_platform_set_power = 1
[ 3892.656495] mmc1: queuing unknown CIS tuple 0x80 (5 bytes)
[ 3892.727908] sdhci-tegra 3440000.sdhci: Tuning already done, restoring the best tap value : 21
[ 3892.736871] F1 signature read @0x18000000=0x17214354
[ 3892.745280] F1 signature OK, socitype:0x1 chip:0x4354 rev:0x1 pkg:0x2
[ 3892.752233] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
worker@master:~$

Hi Chun.liu,

I feel it is not good to use Jetpack3.3 + Jetpack3.1 rootfs.

As you know, all our QA is based on same rootfs+ kernel.

Any reason why you must use it? Also, could you try to verify this issue on Jeptack3.3 with full BSP?

Hi, WayneWWW

We had spent some time on rebuilding our rootfs based on Jetpack3.1 rootfs, don’t want to rebuild it.

But to support security feature, we need to use Jetpack 3.3 tools

The wifi works with full Jetpack 3.3(or 3.1) BSP.

Thanks!

Hi, WayneWWW

I fixed this issue.

coherent_pool=64M trigger this issue.

[    2.802212] mmc1: Unable to allocate ADMA buffers - falling back to standard DMA
worker@master:~$ cat /boot/extlinux/extlinux.conf 
TIMEOUT 30
DEFAULT primary

MENU TITLE p2771-0000 eMMC boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 coherent_pool=64M quiet text 3