WL1801MOD: Issues integrating Wilink to Linux

Which kernel version are you using? And, which build tools are you using? Also, which host processor?

Thanks

Raul Matos , thanks for posting our issue here.
Hari Nagalla:
- kernel version: 4.14.59
- build tools: yocto (rocko)
- host processor: AM3352

Specifically:
- kernel version: 4.14.49-rt37 from: git.ti.com/.../ti-rt-linux-4.14.y
- SRCREV: "0184cb49ab"

Hi,
Can you list contents of /lib/firmware/ti-connectivity/

Saurabh

Hi, Saurabh,
Thanks for your reply.

This is the content (output of ls -lah /lib/firmware/ti-connectivity):

total 8.7M
drwxr-xr-x 2 root root 4.0K Jun 16 2016 .
drwxr-xr-x 73 root root 12K Sep 19 20:19 ..
-rw-r--r-- 1 root root 48K Jun 16 2016 TIInit_7.2.31.bts
-rw-r--r-- 1 root root 190K Jun 16 2016 wl1251-fw.bin
-rw-r--r-- 1 root root 752 Jun 16 2016 wl1251-nvs.bin
-rw-r--r-- 1 root root 268K Jun 16 2016 wl1271-fw-2.bin
-rw-r--r-- 1 root root 267K Jun 16 2016 wl1271-fw-ap.bin
-rw-r--r-- 1 root root 266K Jun 16 2016 wl1271-fw.bin
lrwxrwxrwx 1 root root 14 Jun 16 2016 wl1271-nvs.bin -> wl127x-nvs.bin
-rw-r--r-- 1 root root 274K Jun 16 2016 wl127x-fw-3.bin
-rw-r--r-- 1 root root 255K Jun 16 2016 wl127x-fw-4-mr.bin
-rw-r--r-- 1 root root 256K Jun 16 2016 wl127x-fw-4-plt.bin
-rw-r--r-- 1 root root 271K Jun 16 2016 wl127x-fw-4-sr.bin
-rw-r--r-- 1 root root 347K Jun 16 2016 wl127x-fw-5-mr.bin
-rw-r--r-- 1 root root 345K Jun 16 2016 wl127x-fw-5-plt.bin
-rw-r--r-- 1 root root 363K Jun 16 2016 wl127x-fw-5-sr.bin
-rw-r--r-- 1 root root 262K Jun 16 2016 wl127x-fw-plt-3.bin
-rw-r--r-- 1 root root 912 Jun 16 2016 wl127x-nvs.bin
-rw-r--r-- 1 root root 279K Jun 16 2016 wl128x-fw-3.bin
-rw-r--r-- 1 root root 259K Jun 16 2016 wl128x-fw-4-mr.bin
-rw-r--r-- 1 root root 264K Jun 16 2016 wl128x-fw-4-plt.bin
-rw-r--r-- 1 root root 278K Jun 16 2016 wl128x-fw-4-sr.bin
-rw-r--r-- 1 root root 351K Jun 16 2016 wl128x-fw-5-mr.bin
-rw-r--r-- 1 root root 353K Jun 16 2016 wl128x-fw-5-plt.bin
-rw-r--r-- 1 root root 371K Jun 16 2016 wl128x-fw-5-sr.bin
-rw-r--r-- 1 root root 260K Jun 16 2016 wl128x-fw-ap.bin
-rw-r--r-- 1 root root 267K Jun 16 2016 wl128x-fw.bin
-rw-r--r-- 1 root root 266K Jun 16 2016 wl128x-fw-plt-3.bin
-rw-r--r-- 1 root root 1.1K Jun 16 2016 wl128x-nvs.bin
lrwxrwxrwx 1 root root 14 Jun 16 2016 wl12xx-nvs.bin -> wl127x-nvs.bin
-rw-r--r-- 1 root root 625K Jun 16 2016 wl18xx-fw-2.bin
-rw-r--r-- 1 root root 658K Jun 16 2016 wl18xx-fw-3.bin
-rw-r--r-- 1 root root 728K Jun 16 2016 wl18xx-fw-4.bin
-rw-r--r-- 1 root root 405K Jun 16 2016 wl18xx-fw.bin

While we wait for Saurabh's comment.

Wendell and Fabio, please test the following:

a) Verify that the MMC and WL_EN pin muxes are configured correctly matching to the wiring on the board.
b) Check with a scope if WL_EN is getting asserted..
c) MMC probe happens during kernel boot up.. Please check the MMC card is identified.. you should see a message like below. If, not MMC probe itself has failed at kernel bootup…
mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
mmc1: new high speed SDIO card at address 0001
d) Try with slower MMC/SDIO speed, let us say 1MHz, by setting ‘max-frequency’ to 1MHz in dts file.

Hi Raul,

a) WL_EN as well as IRQ pin muxing are described bellow and it matches with the board's wiring:

  wlan_pins_default: pinmux_wlan_pins_default {
     pinctrl-single,pins = <
       0x08C ( PIN_OUTPUT_PULLDOWN | MUX_MODE7)  /* (V12) WLAN_EN    gpmc_clk.gpio2[1] */
       0x088 ( PIN_INPUT           | MUX_MODE7)  /* (T13) WLAN_IRQ   gpmc_csn3.gpio2[0] */
     >;
  };

  wlan_pins_sleep: pinmux_wlan_pins_sleep {
     pinctrl-single,pins = <
       0x08C ( PIN_OUTPUT_PULLDOWN | MUX_MODE7)  /* (V12) WLAN_EN    gpmc_clk.gpio2[1] */
       0x088 ( PIN_INPUT           | MUX_MODE7)  /* (T13) WLAN_IRQ   gpmc_csn3.gpio2[0] */
     >;
  };

b) Fabio verified that WL_EN goes from down (0v) to up (3v3) during the boot, and it stays up unless the board is powered own or reseted.

c) In my case, mmc1 (detected by Linux) is mmc2 in hardware; SDIO is configured via mmc0 (Linux) / mmc1 (hw); however, the "mmc0: queueing ..." is not presented, only the second message is presented:

[    1.386925] mmc0: new high speed SDIO card at address 0001

d) max-frequency was tried but no go; the following is the rest of pin mux config I'm trying to use:

  mmc0_pins_default: pinmux_mmc0_pins_default {
     pinctrl-single,pins = <
       0x100 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G17) mmc0_clk.mmc0_clk */
       0x104 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G18) mmc0_cmd.mmc0_cmd */
       0x0fc ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G16) mmc0_dat0.mmc0_dat0 */
       0x0f8 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (G15) mmc0_dat1.mmc0_dat1 */
       0x0f4 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (F18) mmc0_dat2.mmc0_dat2 */
       0x0f0 ( PIN_INPUT_PULLUP | MUX_MODE0 ) /* (F17) mmc0_dat3.mmc0_dat3 */
     >;
  };

  mmc0_pins_sleep: pinmux_mmc0_pins_sleep {
     pinctrl-single,pins = <
       0x100 ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (G17) mmc0_clk.mmc0_clk */
       0x104 ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (G18) mmc0_cmd.mmc0_cmd */
       0x0fc ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (G16) mmc0_dat0.mmc0_dat0 */
       0x0f8 ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (G15) mmc0_dat1.mmc0_dat1 */
       0x0f4 ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (F18) mmc0_dat2.mmc0_dat2 */
       0x0f0 ( PIN_INPUT_PULLDOWN | MUX_MODE7 ) /* (F17) mmc0_dat3.mmc0_dat3 */
     >;
  };

  wlan_en_regulator: fixedregulator1 {
     compatible = "regulator-fixed";
     regulator-name = "wlan_en_regulator";
     regulator-min-microvolt = <1800000>;
     regulator-max-microvolt = <1800000>;
     startup-delay-us = <70000>;

     gpio = <&gpio2 1 GPIO_ACTIVE_HIGH>;
     enable-active-high;
  };

&mmc1 {
  dmas = <&edma_xbar 12 0 1
          &edma_xbar 13 0 2>;
  dma-names = "tx", "rx";
  status = "okay";
  vmmc-supply = <&wlan_en_regulator>;
  bus-width = "4";
  pinctrl-names = "default", "sleep";
  pinctrl-0 = <&mmc0_pins_default &wlan_pins_default>;
  pinctrl-1 = <&mmc0_pins_sleep &wlan_pins_sleep>;
  ti,non-removable;
  ti,needs-special-hs-handling;
  cap-power-off-card;
  keep-power-in-suspend;
  max-frequency=<1000000>;
  #address-cells = <1>;
  #size-cells = <0>;

  wlcore: wlcore@0 {
     compatible = "ti,wl1801";
     reg = <2>;
     interrupt-parent = <&gpio2>;
     interrupts = <0 IRQ_TYPE_LEVEL_HIGH>;
  };
};

Additionally, this is the single reference on 'wlan' reported by dmesg:

[    3.603001] wlan_en_regulator: disabling

Thanks for you guidance.

More info:

I've activated debugfs of the kernel, and this is what I've found regarding mmc's:

mmc1 (eMMC) - which is working perfectly:
cat /sys/kernel/debug/mmc1/ios
clock:          52000000 Hz
vdd:            21 (3.3 ~ 3.4 V)
bus mode:       2 (push-pull)
chip select:    0 (don't care)
power mode:     2 (on)
bus width:      3 (8 bits)
timing spec:    1 (mmc high-speed)
signal voltage: 0 (3.30 V)
driver type:    0 (driver type B)

mmc0 (SDIO) - not working - and such bus-width is very strange, isn't?:

cat /sys/kernel/debug/mmc0/ios
clock:          1000000 Hz
vdd:            7 (1.65 - 1.95 V)
bus mode:       2 (push-pull)
chip select:    0 (don't care)
power mode:     2 (on)
bus width:      0 (1 bits)
timing spec:    2 (sd high-speed)
signal voltage: 0 (3.30 V)
driver type:    0 (driver type B)

Hi,
- WLAN_EN is 1.8v IO. Since you mentioned you measured 3.3v, can you pls confirm there is a level shifter to bring it down to 1.8v
- Also check the dma values mentioned for mmc1 to ensure it's correct
- "mmc0: new high speed SDIO card at address 0001" confirms wl8 was powered up and detected ok

Thanks
Saurabh

Hi Saurabh,

Thanks for your reply.

- WLAN_EN: sorry! it is 1.8v in deed - and there is no need for level shifter; my fault. (don't get me wrong... I'm a software guy... ;-)
- DMA values: I've removed my configuration and let the default one for mmc0 from am33xx.dtsi
- wl8 detection: since you have clarified this matter, then I think this is not a hardware problem.

Tested new config; no go yet.

I'm now investigating more possible configuration problems.

If you have any clue...

Thanks,

--Wendell

Wendell,
That's good news ! Good to know wi8 is working on your platform and thank you for posting an update

Best of luck
Saurabh