topic Re: SDIO command timeout issue with SD8787 wifi chipset in i.MX Processors

SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Mon, 19 Aug 2013 11:58:45 GMT

Platform: sabre-lite imx6 Q board

Kernel: 3.0.35

Wifi chipset: Marvell SD8787 based wifi module

wifi driver : mwifiex

We are facing an issue in Wi-Fi bring-up on 3.0.35 kernel. The Wi-Fi module connected to sabre-lite board through SDIO interface.

The driver is able to load the firmware. But if we try to a data transfer the driver crashes with following message.

root@freescale /$ dhclient mlan0
Internet Systems Consortium DHCP Client V3.0.3b1
Copyright 2004-2005 Internet Systems Consortium.

Listening on Socket/eth0
Sending on   Socket/eth0
Listening on Socket/mlan0
Sending on   Socket/mlan0
Sending on   Socket/fallback
DHCPDISCOVER on mlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on mlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
mwifiex_sdio mmc1:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id (97.892473) = 0xce, act = 0x1c8c
mwifiex_sdio mmc1:0001:1: num_data_h2c_failure = 0
mwifiex_sdio mmc1:0001:1: num_cmd_h2c_failure = 0
mwifiex_sdio mmc1:0001:1: num_cmd_timeout = 1
mwifiex_sdio mmc1:0001:1: num_tx_timeout = 0
mwifiex_sdio mmc1:0001:1: last_cmd_index = 3
mwifiex_sdio mmc1:0001:1: last_cmd_resp_index = 2
mwifiex_sdio mmc1:0001:1: last_event_index = 4
mwifiex_sdio mmc1:0001:1: data_sent=0 cmd_sent=1
mwifiex_sdio mmc1:0001:1: ps_mode=1 ps_state=0
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on mlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13

Further looking into the issue, I have found a patch for "eSDHC misses SDIO interrupt when CINT is disabled" for imx processors.

https://patchwork.kernel.org/patch/2446091/

Does this patch is applicable to imx6 processors? If yes, do you have a patch for 3.0.35 kernel?

Thanks in advance,

Krishnan.

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Tue, 20 Aug 2013 13:28:12 GMT

Any pointers in this issue. Appreciate your help...

Re: SDIO command timeout issue with SD8787 wifi chipset

varsmolta — Tue, 20 Aug 2013 15:21:23 GMT

According to the /drivers/mmc/host/sdhci-esdhc-imx.c file in the imx6Q kernel, this patch should not be applied since that problem should not occur in i.mx6. Look here:

linux-imx6/drivers/mmc/host/sdhci-esdhc-imx.c at boundary-imx_3.0.35_4.0.0 · boundarydevices/linux-imx6 · GitHub

But just to double check, have you tried probing the SDIO DAT1 pin to see if it stays low until the card is reset? If this is the case, then the interrupt is not being serviced.

Also, according to this:

Linux/drivers/net/wireless/mwifiex/fw.h - Linux Cross Reference - Free Electrons

Timeout cmd id (97.892473) = 0xce, corresponds to the command HostCmd_CMD_11N_ADDBA_REQ, which is a Block Acknowledgement request cmd. This is an 802.11n feature (Block acknowledgement - Wikipedia, the free encyclopedia). Its possible that the mwifiex driver you are could be out of date. It is at least 2 yrs old according to here:linux-imx6/drivers/net/wireless/mwifiex at boundary-imx_3.0.35_4.0.0 · boundarydevices/linux-imx6 · GitHub. So would suggest updating this to a later version from the mainline linux kernel. You may not be able to do this because of other incompatibilities with the 3.0.35 kernel. So another approach is to load the 3.9 kernel for the sabrelite by following these instructions:i.MX6x SABRE Lite - Linux on ARM - eewiki and seeing if the problem persists.

Also, there is an updated firmware file for the 8787 chipset. Have you given this a try?: kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel. My guess is this fimrware will work with the latest 3.9 kernel.

Re: SDIO command timeout issue with SD8787 wifi chipset

varsmolta — Tue, 20 Aug 2013 15:24:53 GMT

Also to glean some more info (from here:RE: [PROBLEM] linux-3.2.7:mwifiex:when associating with ap ,there are some strange warning (Linux Wireless)):

In kernel .config file (or through menuconfig):

CONFIG_DYNAMIC_DEBUG=y

Re-compile the whole kernel tree, install and reboot. Before running wpa_supplicant, turn on debug:

mkdir /tmp/debug

mount -t debugfs debugfs /tmp/debug

echo "module mwifiex +p" > /tmp/debug/dynamic_debug/control

echo "module mwifiex_sdio +p" > /tmp/debug/dynamic_debug/control

cat /tmp/debug/mwifiex/mlan0/info

After command timeout happens,

cat /tmp/debug/mwifiex/mlan0/debug

Here is some debug info that the driver spits out: Linux/drivers/net/wireless/mwifiex/README - Linux Cross Reference - Free Electrons

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Wed, 21 Aug 2013 10:22:58 GMT

Hello varsmolta,

Thank you for the help.

The SDIO DAT1 line has been probed and that is toggling so we can rule out the interrupt related patch. I have enabled the debug option in kernel and

captured the debug info pls see the logs below.

Bringing up the new kernel may take some time so I kept that option to last one to try.

Meanwhile I have tried another sdio based wifi module on the board. This driver also giving same kind of issue.

The Wi-Fi driver was working with a different arm platform. This lead me to suspect sdio driver in host. What are the issues identified with sdio driver for i.MX6 ?

Did any one used SDIO based wifi module on an i.MX6 platform?

I want to close this doubt before switching to higher version of kernel..

Appreciate your help.

------------------

Logs

-------------------

After the association with AP

-----------------------------

root@freescale ~$ cat /tmp/debug/mwifiex/mlan0/info

driver_name = "mwifiex"

driver_version = mwifiex 1.0 (14.66.9.p96)

verext = w8787-Ax, RF878X, FP66, 14.66.9.p96, BT_SDIO

interface_name="mlan0"

bss_mode="Ad-hoc"

media_state="Connected"

mac_address="4c:aa:16:c2:0f:ca"

multicast_count="1"

essid="dlink"

bssid="1c:7e:e5:58:77:2b"

channel="6"

region_code = "10"

multicast_address[0]="01:00:5e:00:00:01"

num_tx_bytes = 0

num_rx_bytes = 0

num_tx_pkts = 0

num_rx_pkts = 0

num_tx_pkts_dropped = 0

num_rx_pkts_dropped = 0

num_tx_pkts_err = 0

num_rx_pkts_err = 0

carrier on

tx queue started

root@freescale ~$ cat /tmp/debug/mwifiex/mlan0/info

driver_name = "mwifiex"

driver_version = mwifiex 1.0 (14.66.9.p96)

verext = w8787-Ax, RF878X, FP66, 14.66.9.p96, BT_SDIO

interface_name="mlan0"

bss_mode="Ad-hoc"

media_state="Connected"

mac_address="4c:aa:16:c2:0f:ca"

multicast_count="1"

essid="dlink"

bssid="1c:7e:e5:58:77:2b"

channel="6"

region_code = "10"

multicast_address[0]="01:00:5e:00:00:01"

num_tx_bytes = 0

num_rx_bytes = 0

num_tx_pkts = 0

num_rx_pkts = 0

num_tx_pkts_dropped = 0

num_rx_pkts_dropped = 0

num_tx_pkts_err = 0

num_rx_pkts_err = 0

carrier on

tx queue started

root@freescale ~$ cat /tmp/debug/mwifiex/mlan0/debug

int_counter=0x0

wmm_ac_vo=0x0

wmm_ac_vi=0x0

wmm_ac_be=0x0

wmm_ac_bk=0x0

max_tx_buf_size=0x800

tx_buf_size=0x700

curr_tx_buf_size=0x0

ps_mode=0x1

ps_state=0x3

is_deep_sleep=0x1

wakeup_dev_req=0x1

wakeup_tries=0x0

hs_configured=0x0

hs_activated=0x0

num_tx_timeout=0x0

num_cmd_timeout=0x0

timeout_cmd_id=0x0

timeout_cmd_act=0x0

last_cmd_id=0x6 0x12 0xe4 0x71 0x28

last_cmd_act=0x3 0x7e1c 0xff 0x0 0x113

last_cmd_index=0x3

last_cmd_resp_id=0x8006 0x8012 0x80e4 0x8071 0x8028

last_cmd_resp_index=0x3

last_event=0x17 0x2b 0xa 0xb 0xa

last_event_index=0x3

num_cmd_h2c_fail=0x0

num_cmd_sleep_cfm_fail=0x0

num_tx_h2c_fail=0x0

num_evt_deauth=0x0

num_evt_disassoc=0x0

num_evt_link_lost=0x0

num_cmd_deauth=0x0

num_cmd_assoc_ok=0x1

num_cmd_assoc_fail=0x0

cmd_sent=0x0

data_sent=0x0

cmd_resp_received=0x0

event_received=0x0

cmd_pending=0x0

tx_pending=0x0

rx_pending=0x0

root@freescale ~$ cat /tmp/debug/mwifiex/mlan0/debug

int_counter=0x0

wmm_ac_vo=0x0

wmm_ac_vi=0x0

wmm_ac_be=0x0

wmm_ac_bk=0x0

max_tx_buf_size=0x800

tx_buf_size=0x700

curr_tx_buf_size=0x0

ps_mode=0x1

ps_state=0x3

is_deep_sleep=0x1

wakeup_dev_req=0x1

wakeup_tries=0x0

hs_configured=0x0

hs_activated=0x0

num_tx_timeout=0x0

num_cmd_timeout=0x0

timeout_cmd_id=0x0

timeout_cmd_act=0x0

last_cmd_id=0x6 0x12 0xe4 0x71 0x28

last_cmd_act=0x3 0x7e1c 0xff 0x0 0x113

last_cmd_index=0x3

last_cmd_resp_id=0x8006 0x8012 0x80e4 0x8071 0x8028

last_cmd_resp_index=0x3

last_event=0x17 0x2b 0xa 0xb 0xb

last_event_index=0x4

num_cmd_h2c_fail=0x0

num_cmd_sleep_cfm_fail=0x0

num_tx_h2c_fail=0x0

num_evt_deauth=0x0

num_evt_disassoc=0x0

num_evt_link_lost=0x0

num_cmd_deauth=0x0

num_cmd_assoc_ok=0x1

num_cmd_assoc_fail=0x0

cmd_sent=0x0

data_sent=0x0

cmd_resp_received=0x0

event_received=0x0

cmd_pending=0x0

tx_pending=0x0

rx_pending=0x0

After the ping command

-------------------------

root@freescale ~$ cat /tmp/debug/mwifiex/mlan0/debug

int_counter=0x0

wmm_ac_vo=0x0

wmm_ac_vi=0x0

wmm_ac_be=0x0

wmm_ac_bk=0xf

max_tx_buf_size=0x800

tx_buf_size=0x700

curr_tx_buf_size=0x0

ps_mode=0x1

ps_state=0x0

is_deep_sleep=0x1

wakeup_dev_req=0x0

wakeup_tries=0x0

hs_configured=0x0

hs_activated=0x0

num_tx_timeout=0x0

num_cmd_timeout=0x1

timeout_cmd_id=0xce

timeout_cmd_act=0x1c00

last_cmd_id=0x6 0x12 0xe4 0x71 0xce

last_cmd_act=0x3 0x7e1c 0xff 0x0 0x1c00

last_cmd_index=0x4

last_cmd_resp_id=0x8006 0x8012 0x80e4 0x8071 0x8028

last_cmd_resp_index=0x3

last_event=0xb 0xb 0xb 0xb 0xa

last_event_index=0x4

num_cmd_h2c_fail=0x0

num_cmd_sleep_cfm_fail=0x0

num_tx_h2c_fail=0x0

num_evt_deauth=0x0

num_evt_disassoc=0x0

num_evt_link_lost=0x0

num_cmd_deauth=0x0

num_cmd_assoc_ok=0x1

num_cmd_assoc_fail=0x0

cmd_sent=0x1

data_sent=0x1

cmd_resp_received=0x0

event_received=0x0

cmd_pending=0x0

tx_pending=0x21

rx_pending=0x0

Tx BA stream table:

tid = 0, ra = 1c:7e:e5:58:7

Re: SDIO command timeout issue with SD8787 wifi chipset

varsmolta — Wed, 21 Aug 2013 14:43:25 GMT

On the sabre-lite which SDIO interface are you using (i.e. the number SDx?) Have you set up the pad configs properly? I know the Nitrogen6x (also from boundary devices) uses SD2: http://boundarydevices.com/differences-sabre-lite-nitrogen6x-and-som/. Perhaps EricNelson can show you how to configure the SD pads correctly on sabre-lite?

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Thu, 22 Aug 2013 09:50:46 GMT

I am using SDHC3 interface which is already available in sabre-lite. The wifi module is an evaluation module which is plugged on mmc slot.

The IO pad configuration for SDHC3 looks fine (sdhc mode, 100k pull up, 50Mhz speed).

One more thing I noticed is mlan0 Tx count=0, means no packets are getting transmitted from device. But the Rx packets count shows non zero value.

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Thu, 22 Aug 2013 13:24:52 GMT

Thanks for the help...

I have added debug messages in sdio host controller side driver and ensured CMD52 and CMD53 are happening without any error messages.

Further debugging to this issue its visible that the driver hangs after a call to assert firmware. We are seeing the same behavior with the other module also.

I have also checked out the latest firmware and tried but issue remains the same.

Any pointers ???

Re: SDIO command timeout issue with SD8787 wifi chipset

varsmolta — Thu, 22 Aug 2013 14:36:22 GMT

Can you elaborate what you mean by "assert firmware"? Can you pinpoint to a line (function) in the sdio driver where it is hanging?

Also, I believe if you are using the sabre-lite, you need the set_power callback defined: linux-imx6/arch/arm/mach-mx6/board-mx6_nitrogen6x.c at boundary-imx_3.0.35_4.0.0 · boundarydevices/linux-imx6 · GitHub

There is a similar issue reported on the wandboard here: [meta-fsl-arm-extra] linux-imx (3.0.35): fix sdhc platform data - Patchwork. Not quite sure if it applies to you

Re: SDIO command timeout issue with SD8787 wifi chipset

raymondwang — Mon, 26 Aug 2013 05:36:00 GMT

I tried with AzureWare NH-387 module which is also Marvell SD8787 based wireless module on iMX6 sabresd board.

It does work.Fortunately I got marvell newer driver 14.66.35.p16. Both sta and uap work on iMX6 android platform.

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Mon, 26 Aug 2013 10:13:40 GMT

Hi varsmolta & raymond

Thanks a bunch for your help.

I have taken mwifiex driver in 3.2.39 kernel to 3.0.35 kernel and now device working fine in Adapter mode. This proves that no issue on processor interface side.

Now I need to enable uAP support on 3.0.35?

I have checked out 3.10 kernel and analyzed the changes with 3.0.35. Looks like a lot of changes happened in mainline.

Can you suggest a starting point where I can start down porting ? A of list of changes will help me...

Re: SDIO command timeout issue with SD8787 wifi chipset

varsmolta — Mon, 26 Aug 2013 13:59:11 GMT

Mainline kernel should run on i.mx6. Look here: http://eewiki.net/display/linuxonarm/i.MX6x+SABRE+Lite

You won't get hw acceleration or gstreamer plugins though

Re: Re: SDIO command timeout issue with SD8787 wifi chipset

raymondwang — Wed, 28 Aug 2013 02:57:36 GMT

I'd like to share my driver porting on iMX6 android 4.2.2 with you.

1. my wireless relevant code on BoardConfig.mk:

TARGET_KERNEL_MODULES := \

kernel_imx/net/wireless/cfg80211.ko:system/lib/modules/cfg80211.ko

BOARD_WPA_SUPPLICANT_DRIVER := NL80211

WPA_SUPPLICANT_VERSION := VER_0_8_X

BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mrvl8787

BOARD_HOSTAPD_DRIVER := NL80211

BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mrvl8787

BOARD_WLAN_DEVICE := mrvl8787

BOARD_WLAN_VENDOR := MRVL

WIFI_SDIO_IF_DRIVER_MODULE_PATH := "/system/lib/modules/mlan.ko"

WIFI_SDIO_IF_DRIVER_MODULE_NAME := "mlan"

WIFI_SDIO_IF_DRIVER_MODULE_ARG := ""

WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/sd8xxx.ko"

WIFI_DRIVER_MODULE_NAME := "sd8xxx"

WIFI_DRIVER_MODULE_ARG := "drv_mode=5 cfg80211_wext=0xc sta_name=wlan uap_name=wlan wfd_name=p2p max_uap_bss=1 fw_name=mrvl/sd8787_uapsta.bin"

WIFI_DRIVER_FW_PATH_PARAM := "/proc/mwlan/config"

WIFI_DRIVER_FW_PATH_STA := "drv_mode=5"

WIFI_DRIVER_FW_PATH_AP := "drv_mode=6"

WIFI_DRIVER_FW_PATH_P2P := "drv_mode=5"

2. Attached files:

wifi.zip->/hardware/libhardware_legacy/wifi

marvell.zip->/hardware/imx/wlan

You should note that I just write different drv_mode to sd8xxx.ko driver to change different sta/uap/p2p mode. Details in wlan_src/readme_mlan:

The bit settings of drv_mode are,

Bit 0 : STA

Bit 1 : uAP

Bit 2 : WIFIDIRECT

3.Add a framework overlay file on product makefile

/frameworks/overlay/core/res/res/values/config.xml

Edit that option:

<!-- List of regexpressions describing the interface (if any) that represent tetherable

Wifi interfaces. If the device doesn't want to support tethering over Wifi this

should be empty. An example would be "softap.*" -->

<string-array translatable="false" name="config_tether_wifi_regexs">

</string-array>

Note that bolded "wlan.*" match my wlan interface name "uap_name=wlan" (BoardConfig.mk). Since Android does not support WiFi station and uAP mode simultaneously, It does not matter we have the same interface name for station and uAp (sta_name=wlan uap_name=wlan).

Hope these material can help you!

Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Wed, 28 Aug 2013 16:02:00 GMT

Thanks for the link, let me give a try...

Re: Re: SDIO command timeout issue with SD8787 wifi chipset

krishnanp — Wed, 28 Aug 2013 16:10:00 GMT

Hello raymond,

These configuration shall help me in enabling the AP mode after porting the driver to 3.0.35.

thanks for the details

Re: SDIO command timeout issue with SD8787 wifi chipset

soursunny — Fri, 08 Nov 2013 05:27:30 GMT

there are something wrong....??

make: *** No rule to make target `out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/lib_driver_cmd_mrvl8787_intermediates/export_includes', needed by `out/target/product/sabresd_6dq/obj/EXECUTABLES/hostapd_intermediates/import_includes'. Stop.

Re: SDIO command timeout issue with SD8787 wifi chipset

raymondwang — Fri, 08 Nov 2013 05:48:41 GMT

marvell\wpa_supplicant_8_lib

The private static library is located at marvell\wpa_supplicant_8_lib

you can compile it manually or Add it's Android.mk to your whole building tree.

Re: SDIO command timeout issue with SD8787 wifi chipset

soursunny — Fri, 08 Nov 2013 06:59:22 GMT

i dont' know how to add it.

it seems that Boardconfig.mk has

WPA_SUPPLICANT_VERSION := VER_0_8_X

and wpa_supplicant_8_lib\android.mk

LOCAL_PATH := $(call my-dir)

ifeq ($(WPA_SUPPLICANT_VERSION),VER_0_8_X)

why can't it compile automatic ?

Re: SDIO command timeout issue with SD8787 wifi chipset

raymondwang — Fri, 08 Nov 2013 08:24:13 GMT

You can refer to broadcom library in hardware/broadcom/wlan/bcmdhd/wpa_supplicant_8_lib

Re: SDIO command timeout issue with SD8787 wifi chipset

soursunny — Mon, 11 Nov 2013 02:43:12 GMT

/ # mmc1: new high speed SDIO card at address 0001

vendor=0x02DF device=0x9119 class="0" function=1

wlan_sdio_poll_card_status failed, tries = 100, cs = 0xc

WLAN: FW download with helper poll status timeout @ 0

wlan_dnld_fw fail ret=0xffffffff

WLAN: Download FW with nowwait: 0

Firmware Init Failed

woal_add_card failed

wlan_sdio: probe of mmc1:0001:1 failed with error -1

FW download fail?