We are using WL1807MOD Wifi module in our device and a third-party Wifi stack. Our application is such that three SSIDs can be configured in it. The device will automatically search for next SSID if the previous one is not available. We observed an odd behaviour in it. The scenario is such that, the device is connected to a mobile hotspot. Once the mobile hotspot goes out of range ,the device disconnects and later when the hotspot is back in range, the device wont connect to it (i.e if device comes in range after 3 or more hours). 'SCAN FAILED' or 'HW_COMMAND_TIMEOUT_ERROR' is observed. It wont connect to other configured SSIDs also. Same error comes when trying to connect. Once the device is rebooted, the issue gets resolved.
TI logs are attached. line 55650 onwards below; there is a waning first "Resumed client in thepast". Then line 55662 has an assert that we would like TI to help figuring out the reason. We are currently using Rev 8.9.0.0.79 . Any hints from TI would be great.
55650 1 0 2023-12-19 13:10:27.367 0 0
tx_watchdog.c:744 1 TxWatchdog_Resume Resumed client in the
past: Frame inQ TSF : 3111411097, Free TSF : 3111414941, resumeFrameTSF:
1337943396, suspendDuration:2521499595
80ff3b140100995d74b99d6c74b96465bf4fcb074b96
55651 1 0 2023-12-19 13:10:27.367 0 0
asu.c:2092 1 ASU_ResumeRole NOTIFY RESUME2SCHED: at
TSF=0xB9746CF9,ROLE_STA [role Id(16msb):plan_uid(16lsb)]=0x0000005b is RESUMED.
first+last index=0x00000002 800311461000f96c74b9005b02
55652 1 0 2023-12-19 13:10:27.367 0 0
tx_watchdog.c:209 1 TxWatchdog_DebugPrintWatchdogInfo TX
Watchdog started roles BM : 0x1, tx starts=17051415,tx stops=17051415
803c8d14010001172f0401172f0401
55653 1 0 2023-12-19 13:10:27.367 0 0
tx_descriptor_queue.c:612 1 tx_desc_q_PrintValidDesc 1-of-2:
tdq 13 has a valid queue type=Q_TYPE_NON_QOS, start tsf=0xB9745C52, len=30
8030172a01000d08525c74b91e
55654 1 0 2023-12-19 13:10:27.367 0 0
tx_descriptor_queue.c:618 1 tx_desc_q_PrintValidDesc 2-of-2:
tdq 13 state=TX_TRANSMITTED,frame type=0xb0 8000292a01000d12b0
55655 1 0 2023-12-19 13:10:27.367 0 0
tx_descriptor_queue.c:612 1 tx_desc_q_PrintValidDesc 1-of-2:
tdq 42 has a valid queue type=Q_TYPE_NON_QOS, start tsf=0x00000000, len=10
8000172a01002a08000a
55656 1 0 2023-12-19 13:10:27.367 0 0
tx_descriptor_queue.c:618 1 tx_desc_q_PrintValidDesc 2-of-2:
tdq 42 state=TX_TRANSMITTED,frame type=0xf3 8000292a01002a12f3
55657 1 0 2023-12-19 13:10:27.367 0 0
event_mbox.c:129 1 Service_SetEventMbox At Tsf=0xB9746F28, set
Event MAX_TX_FAILURE_EVENT_ID, EventData (Byte1)= 2
800749610100286f74b9001002
55658 1 0 2023-12-19 13:10:27.367 0 0
event_mbox.c:351 1 __SWI_Entry_EventMBox Event Vector=0x1000
(buffer=1) 8001ff600100001001
55659 1 0 2023-12-19 13:10:27.383 0 0
tx_watchdog.c:434 1 TxWatchdog_MainCall TX Watchdog occurred on
client TX_WATCHDOG_FRAME_IN_QUEUE, passedTime : 1773472128, minTime : 3000000
802cd91501000f8009b569c0c62d
55660 1 0 2023-12-19 13:10:27.383 0 0
tx_watchdog.c:435 1 TxWatchdog_MainCall TX Watchdog occurred
client last TSF : 0x4FBF6564, Current TSF : 0xB9746EE4
800fdf1501006465bf4fe46e74b9
55661 1 0 2023-12-19 13:10:27.383 0 0
irq_18xx.c:981 1 handlerDebugMon ASSERT ERROR at address 115de
8002fb850100de1501
55662 1 0 2023-12-19 13:10:27.383 0 0
tx_watchdog.c:436 1 TxWatchdog_MainCall ASSERT ERROR 0
8000de150100
55663 1 0 2023-12-19 13:10:27.383 0 0
release.c:46 1 PrintRevision Firmware Revision (FRev) Rev 8.9.0.0.79
8000e9d30100
