This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] WL1835MOD:WiFi被阻止

Guru**** 2551370 points


请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1098271/wl1835mod-blocked-wifi

部件号:WL1835MOD

大家好,

这是该 员额的延续。  

我们测试了以下建议:

1.您能否确认wlan_EN在cmd 'ifconfig wlan0 down '后被取消断言,并在cmd 'ifconfig wlan0 up '后重新断言?  

  是的,使用`ifconfig wlan0 down`时,wlan_EN被取消断言,使用`ifconfig wlan0 up`时重新断言。  当WiFi正常工作时,此功能有效。

2.  您是否可以降低DTS文件中的SDIO最大clk频率( Ex 5 MHz)并重新测试

  时钟频率已更改为建议值。

3.  请使用最新固件: https://git.ti.com/cgit/wilink8-wlan/wl18xx_fw/log/

   使用最新固件(8.9 .0.0 .88时)。

WiFi被阻止时,我们仍然遇到相同的问题,重新启动WiFi 的唯一方法 是重新启动整个设备(关闭/打开电源),这样WiFi才能正常工作。  我们希望就如何解决这个问题提出更多的建议。  附件是所用的WIFI.DTS以及一些错误日志。

&am33xx_pinmux {
	pinctrl-names = "default";

	/* WIFI */
	mmc3_pins: mmc3_pins {
		pinctrl-single,pins = <
			AM33XX_IOPAD(0x88c, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (V12) gpmc_clk.mmc2_clk [MMC2_CLK] */
			AM33XX_IOPAD(0x888, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (T13) gpmc_csn3.mmc2_cmd [MMC2_CMD] */
			AM33XX_IOPAD(0x830, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (T12) gpmc_ad12.mmc2_dat0 [MMC2_DAT0] */
			AM33XX_IOPAD(0x834, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (R12) gpmc_ad13.mmc2_dat1 [MMC2_DAT1] */
			AM33XX_IOPAD(0x838, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (V13) gpmc_ad14.mmc2_dat2 [MMC2_DAT2] */
			AM33XX_IOPAD(0x83c, PIN_INPUT_PULLUP | MUX_MODE3) 	/* (U13) gpmc_ad15.mmc2_dat3 [MMC2_DAT3] */
		>;
	};
	
	mmc3_pins_sleep: mmc3_pins_sleep {
		pinctrl-single,pins = <
			AM33XX_IOPAD(0x88c, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (V12) gpmc_clk.mmc3_clk */
			AM33XX_IOPAD(0x888, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (T13) gpmc_csn3.mmc3_cmd */
			AM33XX_IOPAD(0x830, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (T12) gpmc_ad12.mmc3_dat0 */
			AM33XX_IOPAD(0x834, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (R12) gpmc_ad13.mmc3_dat1 */
			AM33XX_IOPAD(0x838, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (V13) gpmc_ad14.mmc3_dat2 */
			AM33XX_IOPAD(0x83c, PIN_INPUT_PULLDOWN | MUX_MODE7) /* (U13) gpmc_ad15.mmc3_dat3 */
		>;
	};

	wlan_pins_default: wlan_pins_default {
		pinctrl-single,pins = <
			AM33XX_IOPAD(0x9a4, PIN_OUTPUT_PULLDOWN | MUX_MODE7) 	/* (C13) mcasp0_fsr.gpio3[19] [WLAN_EN] */
			AM33XX_IOPAD(0x9ac, PIN_INPUT_PULLUP | MUX_MODE7) 		/* (A14) mcasp0_ahclkx.gpio3[21] [WL_IRQ] */  
			AM33XX_IOPAD(0x8c8, PIN_OUTPUT_PULLDOWN | MUX_MODE7) 	/* (U3) lcd_data10.gpio2[16] [WL_PWR_CTRL] */			
			/*AM33XX_IOPAD(0x890, PIN_OUTPUT_PULLDOWN | MUX_MODE7) 	/* P8.07, Audio_sync */        
		>;
	};

   	wlan_pins_sleep: wlan_pins_sleep {
		pinctrl-single,pins = <
			AM33XX_IOPAD(0x9a4, PIN_OUTPUT_PULLDOWN | MUX_MODE7) 	/* (C13) mcasp0_fsr.gpio3[19] [WLAN_EN] */
			AM33XX_IOPAD(0x9ac, PIN_INPUT_PULLUP  | MUX_MODE7) 		/* (A14) mcasp0_ahclkx.gpio3[21] [WL_IRQ] */ 
			AM33XX_IOPAD(0x8c8, PIN_OUTPUT_PULLUP | MUX_MODE7) 		/* (U3) lcd_data10.gpio2[16] [WL_PWR_CTRL] */
			/*AM33XX_IOPAD(0x890, PIN_OUTPUT_PULLDOWN | MUX_MODE7) 	/* P8.07, Audio_sync */        
		>;
	};	
};

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

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

May 01 18:14:02  kernel[211]: [169924.106724] WARNING: CPU: 0 PID: 190 at drivers/net/wireless/ti/wlcore/sdio.c:131 wl12xx_sdio_raw_write+0xf4/0x154 [wlcore_sdio]
May 01 18:14:02  kernel[211]: [169924.118490] Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc option usb_wwan usbserial aes_arm_bs crypto_simd cryptd aes_arm aes_generic ccm iptable_filter xt_MASQUERADE xt_nat xt_tcpudp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_tables x_tables ds2482 wire wl18xx wlcore mac80211 sha256_generic libsha256 sha256_arm usb_f_ecm pru_rproc irq_pruss_intc cfg80211 libarc4 musb_dsps musb_hdrc usbcore phy_am335x phy_generic phy_am335x_control ti_am335x_adc snd_soc_wilink8_bt snd_soc_simple_card snd_soc_simple_card_utils pruss omap_aes_driver crypto_engine omap_crypto libaes pm33xx omap_sham ti_emif_sram c_can_platform c_can can_dev snd_soc_davinci_mcasp snd_soc_ti_udma snd_soc_ti_edma snd_soc_ti_sdma st_lsm6dsx_spi snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore st_lsm6dsx wlcore_sdio rtc_omap omap_wdt wkup_m3_ipc wkup_m3_rproc musb_am335x ti_am335x_tscadc at24 sch_fq_codel g_ether usb_f_rndis u_ether libcomposite udc_core
May 01 18:14:02  kernel[211]: [169924.212281] CPU: 0 PID: 190 Comm: irq/73-wl18xx Not tainted 5.4.20-g738552d0b0 #1
May 01 18:14:02  kernel[211]: [169924.248832] [<c0128eb4>] (warn_slowpath_fmt) from [<bf06f2dc>] (wl12xx_sdio_raw_write+0xf4/0x154 [wlcore_sdio])
May 01 18:14:02  kernel[211]: [169924.259334] [<bf06f2dc>] (wl12xx_sdio_raw_write [wlcore_sdio]) from [<bf31d8a8>] (wlcore_runtime_resume+0x10c/0x278 [wlcore])
May 01 18:14:02  kernel[211]: [169924.270967] [<bf31d8a8>] (wlcore_runtime_resume [wlcore]) from [<c051c9e8>] (__rpm_callback+0x11c/0x188)
May 01 18:14:02  kernel[211]: [169924.304467] [<c051c7d0>] (__pm_runtime_resume) from [<bf31aa1c>] (wlcore_irq_locked+0x54/0x73c [wlcore])
May 01 18:14:02  kernel[211]: [169924.314265] [<bf31aa1c>] (wlcore_irq_locked [wlcore]) from [<bf31dc1c>] (wlcore_irq+0xc0/0x230 [wlcore])
May 01 18:14:02  kernel[211]: [169924.323996] [<bf31dc1c>] (wlcore_irq [wlcore]) from [<c016c69c>] (irq_thread_fn+0x1c/0x78)
May 01 18:14:02  kernel[211]: [169924.388297] wl1271_sdio mmc2:0001:2: sdio write failed (-110)
May 01 18:14:02  kernel[211]: [169924.406470] wlcore: WARNING Enable for recovery failed
May 01 18:14:02  kernel[211]: [169924.411792] wlcore: down
May 01 18:14:03  kernel: wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:03  kernel[211]: [169925.240141] wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:03  kernel: wlcore: ERROR reg domain conf error
May 01 18:14:03  kernel[211]: [169925.269613] wlcore: ERROR reg domain conf error
May 01 18:14:04  kernel: wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:04  kernel[211]: [169926.070096] wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:04  kernel: wlcore: ERROR reg domain conf error
May 01 18:14:04  kernel[211]: [169926.103345] wlcore: ERROR reg domain conf error
May 01 18:14:05  kernel: wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:05  kernel[211]: [169926.914377] wlcore: PHY firmware version: Rev 8.2.0.0.245
May 01 18:14:05  kernel: wlcore: ERROR reg domain conf error
May 01 18:14:05  kernel: wlcore: ERROR firmware boot failed despite 3 retries
May 01 18:14:05  kernel[211]: [169926.950297] wlcore: ERROR reg domain conf error
May 01 18:14:05  kernel[211]: [169926.955713] wlcore: ERROR firmware boot failed despite 3 retries


谢谢!

耶稣普利多

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好,耶稣,

    我已将此主题分配给主题专家,并将很快为您提供答案。

    巴西,

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    如果重新启动时一切正常,则可能是硬件问题。 最常见的情况是,SDIO线路上可能缺少上拉。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好,Sabeeh,  

    感谢您的回复,目前我们在所有SDIO线路上都有上拉菜单,但WL_SDIO_CLK除外。  该线路是否需要上拉?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    Jesus,我建议您提交硬件审查请求。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    嘿,耶稣,

    CLK线不需要脉冲。

    如Sabeeh所建议,您可以在此处请求设计审核-> https://www.ti.com/tool/WILINK-DESIGN-REVIEWS

    谢谢!

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    谢谢您,Seong, 我们将继续进行设计审核。

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    耶稣,

    已注意到。 审核请求后,我们将在5个工作日内提供反馈。

    谢谢,此致,