CC3301: the firmware not responding to commands by multiple connections to the AP.(R5 version)

yuan yang

Part Number: CC3301

Tool/software:

After the cc3301 successfully connects to the AP, restarting the cc3301 and attempting to reconnect to the AP results in the first connection attempt failing, while the second connection attempt succeeds.

The reason for the first connection failure is that the AP sends a disassociation packet, which happens very quickly, but we do not receive any related events and have to wait until the connection times out.

The second connection may also fail, as the firmware no longer responds to commands issued by the driver, the firmware logs no longer show any prints, while under normal circumstances, the firmware logs would continuously display prints. This error occurs with a high probability.

so, My issue is:

1. Why doesn't the driver receive the disassociation event in a timely manner?

2. Why does such a connection operation cause the firmware to stop working?

2 months ago

0 AB 2 months ago

TI__Mastermind 21105 points

Hello,

Can we please get some wireshark captures, and firmware logs?

In order to capture Firmware logs you need to download the simplelink WiFi toolbox https://www.ti.com/tool/SIMPLELINK-WIFI-TOOLBOX

Follow the Logger instructions on the application and provide us with the data collected.

Thanks,

0 yuan yang 2 months ago in reply to AB

Prodigy 120 points

Hi AB

Here is log, connect failed, and receive event HINT_FW_DOWNLOAD_ERROR,

wifi connect test101 abcdef1234 -r
ssid: test101, len 7
key: abcdef1234, len 10, index 0
bssid:
0000 00 00 00 00 00 00
security: -1, wepauthtype: -1
chanspec 0
0000 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
0010 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
scan_security: 0, scan_encryption: 0

[WLAN EVENT] Device disconnected from the AP, ReasonCode: 1
Easycam network link is off!!
Do reconnect...
clean prev pmk
libwifi_connect
scan 4 find ssid test101 (len 7)
security type: WPA3

[WLAN EVENT] Device disconnected from the AP, ReasonCode: 200
connect to test101, sectype: 12
Get unexpected event: HINT_FW_DOWNLOAD_ERROR
connect timeout
connect to test101, sectype: 12
wlan_connect faild, return 1078428372
can not find test101
scan test101 failed
WIFI Connect 0th Retry Fail.
[ERROR]: Wifi Connect Fail!!

0 Shlomi Itzhak 2 months ago in reply to yuan yang

TI__Guru 60995 points

Hi,

The link is broken. Can you please provide the FW log?

Shlomi

0 yuan yang 2 months ago in reply to Shlomi Itzhak

Prodigy 120 points

It seems can't upload file here, only can paste picture.

0 Shlomi Itzhak 2 months ago in reply to yuan yang

TI__Guru 60995 points

Hi,

Don't you have the Insert->image/video/file?

Shlomi

0 yuan yang 2 months ago in reply to Shlomi Itzhak

Prodigy 120 points

Here is the file you want.

multiconnect.7z.log

0 Shlomi Itzhak 2 months ago in reply to yuan yang

TI__Guru 60995 points

Hi,

The log is not using the correct parser so the interesting packets are not decodable.

If you are using R5, the firmware version is 1.7.0.185. You need to use the logger.bin file from the R5 itself (under cc33xx_mcu_package_R5\tools\wifi_fw).

What logger.bin are you using?

Shlomi