• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 241 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC3300: Android support and AOSP integration status for TI CC3300 Wi-Fi module

Taraprasad Shadangi
Prodigy 20 points

Part Number: CC3300

Hi Team,

I’m evaluating the TI CC3300MODENIAMOZR Wi-Fi module for an embedded Android project (i.MX8M Mini platform) and would like to understand the level of Android support compared to typical Android Wi-Fi chipsets (Qualcomm/Broadcom).

I’ve seen Linux support for the CC33xx family, but I’m specifically interested in Android compatibility.

Questions:

  1. Android support status

    • Is the CC3300 officially supported on Android (AOSP)?

    • Are there reference Android BSPs or integrations available?

  2. Driver architecture

    • Are the Linux drivers compatible with Android kernels directly, or are Android-specific modifications required?

    • Is the solution based on mac80211/nl80211 (standard cfg80211 stack)?

  3. Android Wi-Fi stack compatibility

    • Does the module work with the standard Android Wi-Fi framework (wpa_supplicant / hostapd)?

    • Any limitations related to:

      • Wi-Fi Direct

      • SoftAP

      • Concurrent STA/AP modes

  4. Firmware and calibration

    • Is firmware loading handled via standard Linux mechanisms?

    • Any special considerations for Android boot flow?

  5. Documentation

    • Are there any Android-specific integration guides or application notes?

Appreciate any guidance from TI engineers or developers who have worked with CC33xx on Android.

Thanks!

  • 0
    TI__Mastermind 36650 points

    Hello Taraprasad,

    I'll write generally about cc3300 with android compatibility in the hopes that it will answer multiple of your questions.

    Because Android uses linux, we generally get Android support for free. So we have integrated cc33xx into the AM62 Android SDK as well, and we do it see it functional. For a reference, you can see here: https://www.ti.com/tool/download/PROCESSOR-SDK-ANDROID-AM62X/11.00.00 

    I noticed you didn't mention which Android/kernel version you are using, but I assume it will not be kernel 6.1. So our process for using cc33xx drivers in kernels outside of 6.1 is to first patch the 6.1 kernel, and then apply a forward or backport patch based on the respective kernel as listed here: https://github.com/TexasInstruments-Sandbox/cc33xx-linux-mpu-ports/  

    CC33xx linux drivers do use the mac80211 and cfg80211 stacks. We cover this some in our Linux documentation: https://dev.ti.com/tirex/explore/content/CC33XX_LINUX_MPU_1_00_00_09__all/docs/linux/html/linux/intro-linux.html#cc33xx-linux-driver-architecture 

    Taraprasad Shadangi said:

    Any limitations related to:

    • Wi-Fi Direct

    Our current limitation is the Wi-Fi direct. We do not have this feature available today, but it is planned to come later this year. However, no issues with concurrent softAP/STA modes.

    Outside of patching the kernel, there is nothing really specific to Android. Just make sure to also install the firmware binaries into /lib/firmware/ti-connectivity/. Again, you can refer to the am62 android BSP I linked above.

  • 0 in reply to Sabeeh Khan1
    Prodigy 20 points

    Hi Sabeeh,

    Thanks for the earlier clarification around CC33xx Android compatibility. I’d like to dive deeper specifically into Wi-Fi Direct (P2P) support, as this feature is important for our evaluation.

    I understand that Wi-Fi Direct is currently not available but planned. I have a few follow-up questions to better understand feasibility and timelines:

    1. Feature roadmap

    • Is Wi-Fi Direct expected via a firmware update, driver update, or both?

    • Is there an estimated timeline for availability?

    • Will it be supported across the full CC33xx family (including CC3300 modules)?

    2. Android compatibility

    • Once available, is Wi-Fi Direct expected to work with the standard Android Wi-Fi P2P framework (wpa_supplicant + nl80211)?

    • Will any Android framework changes be required, or will it remain within kernel/firmware scope?

    3. Driver architecture

    • Since CC33xx uses mac80211/cfg80211, will Wi-Fi Direct be implemented using standard P2P interfaces in cfg80211?

    4. Concurrency behavior

    • Will Wi-Fi Direct support concurrent operation with:

      • STA mode

      • SoftAP mode

    Any details on roadmap, architecture, or early access availability would be very helpful for planning purposes.

    Thanks for your support.

  • 0 in reply to Taraprasad Shadangi
    TI__Mastermind 36650 points

    Hi Taraprasad,

    The Wi-Fi direct feature is still under definition so I can't confirm on the concurrent operations. Likely it will be one of the available roles, but we can only support two roles at at time. So that means you can have P2P active with STA or SoftAP, not all three roles at the same time.

    Taraprasad Shadangi said:
    Since CC33xx uses mac80211/cfg80211, will Wi-Fi Direct be implemented using standard P2P interfaces in cfg80211?

    Yes. We will not stray away from mac80211 compatibility.

    Taraprasad Shadangi said:
    Is Wi-Fi Direct expected via a firmware update, driver update, or both?

    We release all CC33xx related software in terms of the cc33xx SDK: https://www.ti.com/tool/download/CC33XX-LINUX-MPU

    Which will contain a driver and associated firmware. Certainly firmware will be updated but it's very likely that driver will also be updated.

    Taraprasad Shadangi said:
    Is there an estimated timeline for availability?

    Again, we're still in the planning phases of this but we are estimating some time in H2 of this year.

    Taraprasad Shadangi said:
    Will any Android framework changes be required, or will it remain within kernel/firmware scope?

    Kernel/driver/firmware scope. Should not break android compatibility and maintain operation with wpa-supplicant.