请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。
器件型号：AM6422 Thread 中讨论的其他器件：WL1837
工具与软件：
您好！
我们目前使用 AM64-SK 开发板的评估板原理、并生产出我们自己的硬件、包括 WL18MODGI 模块。 对于部分功能、我们完全按照评估板的示例进行操作、但有时在上电"wlcore：收到错误软件看门狗中断！"后会出现 WIFI 模块。 开始恢复"。 我们在硬件上还具有使用 USB 接口的4G 模块。 此时4G 模块工作正常。 我 在 e2e.ti.com/.../ 5499812上看到了有关此问题的链接？tisearch=e2 e-sitesearch&keymatch=SW%20watchdog%20interrupt%20received%21%20%22%20%09%09%20%20%20%20%20%22starting%20recovery#5499812、我在内容中看到可能有其他 RF 源会影响 WiFi 模块正常工作、从而导致 WiFi 模块无法正常工作。 这是真的吗？ 如何应对这种情况？ 或者、如果4G 模块发出的信号在使用过程中影响了 WiFi 模块、如何将 WiFi 模块的工作频段设置为固定？ 以下是发生这种情况时的打印信息。
root@am64xx-evm:~# [ 40.287068] wlcore: ERROR SW watchdog interrupt received! starting recovery. [ 40.294231] ------------[ cut here ]------------ [ 40.298891] WARNING: CPU: 1 PID: 548 at drivers/net/wireless/ti/wlcore/main.c:803 wl12xx_queue_recovery_work+0x8c/0x98 [wlcore] [ 40.310343] Modules linked in: iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_tables x_tables qmi_wwan_q qmi_wwan cdc_wdm option cdc_ether usb_wwan usbnet usbserial wl18xx wlcore mac80211 xhci_plat_hcd xhci_hcd cfg80211 cdns3 udc_core rfkill libarc4 roles usbcore usb_common rpmsg_char irq_pruss_intc icssg_prueth crct10dif_ce wlcore_sdio pru_rproc icss_iep ti_k3_r5_remoteproc cdns3_ti virtio_rpmsg_bus rti_wdt ti_k3_m4_remoteproc sa2ul sha512_generic authenc pruss optee_rng rng_core sch_fq_codel cryptodev(O) ipv6 [ 40.359331] CPU: 1 PID: 548 Comm: irq/365-wl18xx Tainted: G O 5.10.168-g2c23e6c538 #1 [ 40.368442] Hardware name: Texas Instruments AM642 EVM (DT) [ 40.374002] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 40.380018] pc : wl12xx_queue_recovery_work+0x8c/0x98 [wlcore] [ 40.385858] lr : wlcore_irq+0x168/0x2c8 [wlcore] [ 40.390462] sp : ffff800012003d30 [ 40.393765] x29: ffff800012003d30 x28: ffff8000100bb000 [ 40.399069] x27: ffff000000343900 x26: ffff000000343900 [ 40.404373] x25: 0000000000000001 x24: ffff000000343900 [ 40.409675] x23: ffff8000100bb718 x22: ffff000006cf2188 [ 40.414977] x21: ffff000006cf1f60 x20: ffff000006cf1f80 [ 40.420280] x19: ffff000006cf1f00 x18: 0000000000000010 [ 40.425583] x17: 0000000000000000 x16: 0000000000000000 [ 40.430886] x15: ffff000000343e50 x14: 00000000000001bb [ 40.436189] x13: ffff000000343e50 x12: 00000000ffffffea [ 40.441492] x11: ffff8000111a0770 x10: ffff800011188730 [ 40.446795] x9 : ffff800011188788 x8 : 0000000000017fe8 [ 40.452097] x7 : c0000000ffffefff x6 : 000000095f78728e [ 40.457400] x5 : ffff00000503ad48 x4 : ffff800012653830 [ 40.462703] x3 : ffff0000016cb140 x2 : 0000000000000000 [ 40.468005] x1 : ffff000006cf1f00 x0 : 0000000000000015 [ 40.473308] Call trace: [ 40.475769] wl12xx_queue_recovery_work+0x8c/0x98 [wlcore] [ 40.481264] wlcore_irq+0x168/0x2c8 [wlcore] [ 40.485530] irq_thread_fn+0x2c/0xb0 [ 40.489096] irq_thread+0x164/0x2e0 [ 40.492577] kthread+0x140/0x160 [ 40.495798] ret_from_fork+0x10/0x30 [ 40.499363] ---[ end trace 10fe934b5547482b ]--- [ 41.028256] wlcore: WARNING ELP wakeup timeout! [ 41.032848] wlcore: down [ 41.035394] wlcore: down [ 41.039144] ieee80211 phy0: Hardware restart was requested [ 41.339419] wlcore: using inverted interrupt logic: 2 [ 41.398049] wlcore: PHY firmware version: Rev 8.2.0.0.245 [ 41.550627] wlcore: firmware booted (Rev 8.9.0.0.86)
