WL1835MOD: WL1835MOD

Soumya

Prodigy 655 points

Part Number: WL1835MOD
Other Parts Discussed in Thread: WL1835, WL1271, TPS65218, AM3352

Hi,

Can you please help to answer the below inquiry from my customer?

We're using chip wl1835 + FW 8.9.0.0.78.

We just found that every once in a while we can get the following error messages from the Wi-Fi driver.

We don't know if it's normal, or we didn't configure the chip properly or there are any hardware issues. Can you please give us some advice?

[97417.622337] CPU: 0 PID: 104 Comm: irq/60-wl18xx Tainted: G W O 4.14.54-yocto-standard #1
[97417.631851] Hardware name: Generic AM33XX (Flattened Device Tree)
[97417.638335] [<c0110c38>] (unwind_backtrace) from [<c010cca4>] (show_stack+0x10/0x14)
[97417.646516] [<c010cca4>] (show_stack) from [<c085e7e4>] (dump_stack+0xb0/0xe8)
[97417.654148] [<c085e7e4>] (dump_stack) from [<c0137a6c>] (__warn+0xd8/0x104)
[97417.661509] [<c0137a6c>] (__warn) from [<c0137b44>] (warn_slowpath_null+0x20/0x28)
[97417.669515] [<c0137b44>] (warn_slowpath_null) from [<bf09e290>] (wl12xx_sdio_raw_write+0xa4/0x130 [wlcore_sdio])
[97417.680604] [<bf09e290>] (wl12xx_sdio_raw_write [wlcore_sdio]) from [<bf286b10>] (wl1271_ps_elp_wakeup+0xe8/0x1dc [wlcore])
[97417.692708] [<bf286b10>] (wl1271_ps_elp_wakeup [wlcore]) from [<bf2793c0>] (wlcore_irq_locked+0x44/0x6ac [wlcore])
[97417.703974] [<bf2793c0>] (wlcore_irq_locked [wlcore]) from [<bf279ca8>] (wlcore_irq+0xd4/0x17c [wlcore])
[97417.714165] [<bf279ca8>] (wlcore_irq [wlcore]) from [<c01a826c>] (irq_thread_fn+0x1c/0x54)
[97417.722894] [<c01a826c>] (irq_thread_fn) from [<c01a8538>] (irq_thread+0x130/0x204)
[97417.730987] [<c01a8538>] (irq_thread) from [<c015c88c>] (kthread+0x138/0x150)
[97417.738532] [<c015c88c>] (kthread) from [<c0107ff4>] (ret_from_fork+0x14/0x20)
[97417.746501] ---[ end trace 162d5686ec39dabd ]---
[97417.751409] wl1271_sdio mmc1:0001:2: sdio write failed (-110)
[97417.757671] ------------[ cut here ]------------
[97417.762952] WARNING: CPU: 0 PID: 104 at /usr/src/kernel/drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x54/0x5c [wlcore]
[97417.777395] Modules linked in: ctr ccm arc4 wl18xx wlcore mac80211 cfg80211 omap_rng rng_core wlcore_sdio tps65218_pwrbutton at24 rtc_omap cpufreq_dt thermal_sys hwmon omap_wdt motor_ctrl(O) ledtrig_timer leds_rgb_gpios(O) led_class gpio_keys flow_pulse(O) evdev autofs4
[97417.803474] CPU: 0 PID: 104 Comm: irq/60-wl18xx Tainted: G W O 4.14.54-yocto-standard #1
[97417.812994] Hardware name: Generic AM33XX (Flattened Device Tree)
[97417.819448] [<c0110c38>] (unwind_backtrace) from [<c010cca4>] (show_stack+0x10/0x14)
[97417.827622] [<c010cca4>] (show_stack) from [<c085e7e4>] (dump_stack+0xb0/0xe8)
[97417.835244] [<c085e7e4>] (dump_stack) from [<c0137a6c>] (__warn+0xd8/0x104)
[97417.842599] [<c0137a6c>] (__warn) from [<c0137b44>] (warn_slowpath_null+0x20/0x28)
[97417.850791] [<c0137b44>] (warn_slowpath_null) from [<bf279a7c>] (wl12xx_queue_recovery_work.part.10+0x54/0x5c [wlcore])
[97417.862534] [<bf279a7c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf286b34>] (wl1271_ps_elp_wakeup+0x10c/0x1dc [wlcore])
[97417.875455] [<bf286b34>] (wl1271_ps_elp_wakeup [wlcore]) from [<bf2793c0>] (wlcore_irq_locked+0x44/0x6ac [wlcore])
[97417.886720] [<bf2793c0>] (wlcore_irq_locked [wlcore]) from [<bf279ca8>] (wlcore_irq+0xd4/0x17c [wlcore])
[97417.896908] [<bf279ca8>] (wlcore_irq [wlcore]) from [<c01a826c>] (irq_thread_fn+0x1c/0x54)
[97417.905632] [<c01a826c>] (irq_thread_fn) from [<c01a8538>] (irq_thread+0x130/0x204)
[97417.913719] [<c01a8538>] (irq_thread) from [<c015c88c>] (kthread+0x138/0x150)
[97417.921262] [<c015c88c>] (kthread) from [<c0107ff4>] (ret_from_fork+0x14/0x20)
[97417.929110] ---[ end trace 162d5686ec39dabe ]---
[97417.944374] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.78
[97417.951878] wlcore: down
[97418.013859] ieee80211 phy0: Hardware restart was requested
[97418.583895] wlcore: PHY firmware version: Rev 8.2.0.0.242
[97418.651759] wlcore: firmware booted (Rev 8.9.0.0.78)
[97418.717718] wlcore: Association completed.
[97457.968681] wlan0: deauthenticating from b0:be:76:ad:84:9e by local choice (Reason: 3=DEAUTH_LEAVING)
[97460.965265] wlan0: authenticate with b0:be:76:ad:84:9e
[97460.992854] wlan0: send auth to b0:be:76:ad:84:9e (try 1/3)
[97461.147532] wlan0: authenticated
[97461.162665] wlan0: associate with b0:be:76:ad:84:9e (try 1/3)
[97461.186411] wlan0: RX AssocResp from b0:be:76:ad:84:9e (capab=0x1031 status=0 aid=1)

over 6 years ago

0 Hari Nagalla over 6 years ago

TI__Mastermind 27080 points

Which host processor is being used and what is the SDIO/eMMC clock speed?

Thanks

0 user3811532 over 6 years ago in reply to Hari Nagalla

Prodigy 30 points

Hi Hari,

We're using AM3352.

SDIO/eMMC clock speed is listed below (from .dts):

&mmc3 {
	dmas = <&edma_xbar 12 0 1
		&edma_xbar 13 0 2>;
	dma-names = "tx", "rx";
	status = "okay";
	vmmc-supply = <&wlan_en_reg>;
	bus-width = <4>;
	non-removable;
	cap-power-off-card;
	ti,needs-special-hs-handling;
	keep-power-in-suspend;
	pinctrl-names = "default";
	pinctrl-0 = <&mmc3_pins &wl18xx_pins>;
	max-frequency = <30000000>;

	#address-cells = <1>;
	#size-cells = <0>;
	wlcore: wlcore@2 {
		compatible = "ti,wl1835";
		reg = <2>;
		interrupt-parent = <&gpio0>;
		interrupts = <27 IRQ_TYPE_EDGE_RISING>;
	};
};

And the clock speed of eMMC is:

cat /sys/kernel/debug/mmc0/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)

Thanks

0 S over 6 years ago in reply to user3811532

TI__Mastermind 35795 points

Hi ,
- can you update to latest fwr 8.9.0.0.79 and re-test ? git.ti.com/.../wl18xx_fw
- can you reduce SDIO to 5 MHz for testing

Saurabh

0 Daniel Urbano over 6 years ago in reply to S

Prodigy 10 points

Hi Saurabh,

Is there anything in the change log from .78 to .79 that is relevant to the sdio write failure?

0 S over 6 years ago in reply to Daniel Urbano

TI__Mastermind 35795 points

Hi Daniel ,
SDIO write failures could be due to multiple reasons - did you re-test with reduced SDIO clk frequency ? It's always a good idea to test with latest fwr.

Saurabh

Wi-Fi

Wi-Fi forum

WL1835MOD: WL1835MOD