• State
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 48 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM620-Q1: CC3301 Wi-Fi STA and AP Disconnect/Reconnect Issue During Long-Duration Testing

Navami GS
Prodigy 110 points

Part Number: AM620-Q1
Other Parts Discussed in Thread: CC3301

We are using a custom AM62xx-based board with the CC3301 wireless module. The Wi-Fi interface is configured over SDIO, and both Station (STA) and Access Point (AP) modes are enabled and working correctly. BLE is configured over UART and is also functioning as expected.

However, we have observed an issue during long-duration testing. After approximately one hour of continuous operation, the Wi-Fi driver starts reporting the logs shown below.

At the same time, we observe that both the Wi-Fi STA and AP interfaces get disconnected and then reconnect automatically.

Could you please help us understand what could be causing this behavior after prolonged operation? Is this related to a CC3301 firmware/driver issue, SDIO communication, or any Wi-Fi configuration/timeout?

Please find the relevant logs below for reference.

[23009.665791] wlan0: disconnect from AP d8:44:89:d5:0a:8c for new auth to a8:6e:84:cb:27:b4
[23009.721517] wlan0: authenticate with a8:6e:84:cb:27:b4 (local address=34:68:b5:88:3e:6f)
[23009.730369] wlan0: send auth to a8:6e:84:cb:27:b4 (try 1/3)
[23009.858896] wlan0: send auth to a8:6e:84:cb:27:b4 (try 2/3)
[23009.873622] wlan0: authenticated
[23009.882835] wlan0: associate with a8:6e:84:cb:27:b4 (try 1/3)
[23009.962409] wlan0: RX AssocResp from a8:6e:84:cb:27:b4 (capab=0x1431 status=0 aid=1)
[23009.983722] cc33xx: HE Disabled
[23009.989990] wlan0: associated
[23010.083693] cc33xx: Association complete.
[23013.669499] wlan0: disconnect from AP a8:6e:84:cb:27:b4 for new auth to d8:44:89:d5:0a:8c
[23013.749485] wlan0: authenticate with d8:44:89:d5:0a:8c (local address=34:68:b5:88:3e:6f)
[23013.758899] wlan0: send auth to d8:44:89:d5:0a:8c (try 1/3)
[23013.874890] wlan0: send auth to d8:44:89:d5:0a:8c (try 2/3)
[23013.923379] wlan0: authenticated
[23013.938849] wlan0: associate with d8:44:89:d5:0a:8c (try 1/3)
[23013.956666] wlan0: RX AssocResp from d8:44:89:d5:0a:8c (capab=0x1431 status=0 aid=4)
[23013.972800] cc33xx: HE Disabled
[23013.979264] wlan0: associated
[23014.050833] cc33xx: Association complete.
[23024.758331] wlan0: disconnect from AP d8:44:89:d5:0a:8c for new auth to a8:6e:84:cb:27:b4
[23024.817969] wlan0: authenticate with a8:6e:84:cb:27:b4 (local address=34:68:b5:88:3e:6f)
[23024.827251] wlan0: send auth to a8:6e:84:cb:27:b4 (try 1/3)
[23024.974849] wlan0: send auth to a8:6e:84:cb:27:b4 (try 2/3)
[23024.996840] wlan0: authenticated
[23025.002848] wlan0: associate with a8:6e:84:cb:27:b4 (try 1/3)
[23025.015697] wlan0: RX AssocResp from a8:6e:84:cb:27:b4 (capab=0x1431 status=0 aid=1)
[23025.033128] cc33xx: HE Disabled
[23025.039113] wlan0: associated
[23025.111573] cc33xx: Association complete.
[23028.796387] wlan0: disconnect from AP a8:6e:84:cb:27:b4 for new auth to d8:44:89:d5:0a:8c
[23028.882707] wlan0: authenticate with d8:44:89:d5:0a:8c (local address=34:68:b5:88:3e:6f)
[23028.901228] wlan0: send auth to d8:44:89:d5:0a:8c (try 1/3)
[23029.014854] wlan0: send auth to d8:44:89:d5:0a:8c (try 2/3)
[23029.029583] wlan0: authenticated
[23029.042870] wlan0: associate with d8:44:89:d5:0a:8c (try 1/3)
[23029.154832] wlan0: associate with d8:44:89:d5:0a:8c (try 2/3)
[23029.195624] wlan0: RX AssocResp from d8:44:89:d5:0a:8c (capab=0x1431 status=0 aid=4)
[23029.218554] cc33xx: HE Disabled
[23029.225066] wlan0: associated
[23029.302316] cc33xx: Association complete.
[23040.164823] wlan0: disconnect from AP d8:44:89:d5:0a:8c for new auth to a8:6e:84:cb:27:b4
[23040.210771] wlan0: authenticate with a8:6e:84:cb:27:b4 (local address=34:68:b5:88:3e:6f)
[23040.219790] wlan0: send auth to a8:6e:84:cb:27:b4 (try 1/3)
[23040.234593] wlan0: authenticated
[23040.242827] wlan0: associate with a8:6e:84:cb:27:b4 (try 1/3)
[23040.255175] wlan0: RX AssocResp from a8:6e:84:cb:27:b4 (capab=0x1431 status=0 aid=4)
[23040.272132] cc33xx: HE Disabled
[23040.279521] wlan0: associated
[23040.316127] cc33xx: Association complete.
[23050.934653] wlan0: disconnect from AP a8:6e:84:cb:27:b4 for new auth to d8:44:89:d5:0a:8c
[23051.160374] wlan0: authenticate with d8:44:89:d5:0a:8c (local address=34:68:b5:88:3e:6f)
[23051.180986] wlan0: send auth to d8:44:89:d5:0a:8c (try 1/3)
[23051.299036] wlan0: send auth to d8:44:89:d5:0a:8c (try 2/3)
[23051.313812] wlan0: authenticated
[23051.322889] wlan0: associate with d8:44:89:d5:0a:8c (try 1/3)
[23051.367388] wlan0: RX AssocResp from d8:44:89:d5:0a:8c (capab=0x1431 status=0 aid=4)
[23051.386373] cc33xx: HE Disabled
[23051.391868] wlan0: associated

  • 0
    Prodigy 110 points

    Hi Team,

    Any help regarding this issue is appreciated.

    Thanks

    Navami

  • 0 in reply to Navami GS
    TI__Guru* 86085 points

    Hello Navami

    This E2E fell through the cracks. I have assigned it another colleague to look. However to save time, I am also pasting responses from our AI assistant on E2E, that may help both you and my colleague who can take a deeper look. 

    Form your logs there is a  clear pattern here: your device is repeatedly roaming between two APs (MAC addresses d8:44:89:d5:0a:8c and a8:6e:84:cb:27:b4) in a cyclical pattern, with disconnects occurring roughly every 4–11 seconds after the initial hour of operation.

    The logs themselves show successful authentication and association each time, so the disconnects aren't due to authentication failures. This pattern strongly suggests a roaming or AP selection issue rather than a basic connectivity problem.

    To help narrow down the root cause, I have a few clarifying questions:

    1. Are both APs part of the same network (same SSID)? If so, are they configured with identical or similar signal strengths in your test environment? The repeated switching between the two suggests the driver may be making poor roaming decisions based on signal quality or other metrics.

    2. Is the CC3301 firmware and Wi-Fi driver up to date? Roaming behavior, especially after extended operation, can be affected by firmware bugs or driver-side state management issues. What firmware version are you running on the CC3301?

    3. Are you running both STA and AP modes simultaneously on the same wlan0 interface, or are they on separate interfaces? If they're on the same interface, mode switching could be triggering the roaming loops. If they're separate, this helps isolate whether the issue is specific to one mode.

    4. Have you observed any SDIO communication errors or retries in the kernel logs (look for mmc or sdio related messages)? SDIO instability under sustained load could cause the driver to lose sync with the module, leading to unexpected roaming behavior.

    5. Is there any BLE activity happening during these roaming cycles? Since you have BLE over UART running concurrently, coexistence handling in the firmware could be interfering with Wi-Fi stability.

    Once I understand these details better, I can point you toward specific configuration tuning, firmware updates, or known workarounds for the CC3301 on AM62xx platforms.

  • 0 in reply to Mukul Bhatnagar
    Prodigy 110 points


    Hi Mukul Bhatnagar,

    Thanks for your reply.

    1. Are both APs part of the same network (same SSID)? - 

        STA Mode: The CC33xx connects to my main external router network.
        AP Mode: The CC33xx simultaneously hosts its own local hotspot network.

     "ap": {
                "enable": 1,
                "ip_addr": "192.168.10.1",
                "password": "12345678",
                "security": 1,
                "ssid": "DMS_AELP_WIFI_DEV_0000001_V1R0"
            },
            "enable": 1,
            "mac_addr": "FF:FF:FF:FF:FF:FF",
            "sta": {
                "broadcast": 0,
                "enable": 1,
                "ip_addr": "192.168.1.10",
                "mode": 1,
                "password": "$P0rtMan@$2047",
                "security": 1,
                "ssid": "Rtpl"
            },

    2. Is the CC3301 firmware and Wi-Fi driver up to date? - yes its latest

    3. Are you running both STA and AP modes simultaneously on the same wlan0- Sta in wlan0 and Ap in wlan1

    4. Have you observed any SDIO communication errors or retries in the kernel logs - NO

    5. Is there any BLE activity happening during these roaming cycles? BLE is enabled but we are not doing any activities like scanning or advertising or any communication. just enabled

    Thanks