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.

CC3135: Application issues of chips

Part Number: CC3135
Other Parts Discussed in Thread: SIMPLELINK-SDK-WIFI-PLUGIN,

1. Last time there was an issue with CC3135 not being able to connect to the AP. On the E2E forum, it was suggested that we switch to an SDK. The local TI FAE suggested that I use SIMPLELINK-SDK-WIFI-PLUGIN as the basis for development, and which SDK would be more suitable.
2. After the development of the driver was completed, testing revealed that there were some APs that could not be connected, as well as other issues. How to solve it. SIMPLELINK-SDK-WIFI-PLUGIN has long stopped updating (I checked and the last update was on January 31, 2019). Whether to use SimpleLink CC32xx SDK is the best choice
3. I downloaded the SimpleLink CC32xx SDK, but when I flipped through the release notes, I didn't see CC3135 in the supported components section.
 
I would like you to confirm again whether the subsequent development of CC3135 should shift to the SimpleLink CC32xx SDK? My concern is that the official RN did not mention support for CC3135. If any bugs are found in CC3135 using the SimpleLink CC32xx SDK in the future, can TI provide us with patches and support based on the SimpleLink CC32xx SDK?

  • Hi,

    SIMPLELINK-SDK-WIFI-PLUGIN is indeed the basis for development but the cadence of releasing updates has been stopped few years back.

    Since the NWP is identical, the host driver is also identical. So you can just use the servicepack and host driver from CC32xx SDK.

    As such, bugs that are found in NWP/PHY or in the host driver, are automatically fixed and updated on the CC32xx SDK so you should be safe here.

    As for the Wi-Fi connection issues, I suggest you open a thread to discuss (unless you already did).

    Regards,

    Shlomi