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.

SIMPLELINK-SDK-WIFI-PLUGIN: CC26x2 network terminal projectspec incorrect path



I'm trying to import the network terminal project from the simplelink wifi plugin v 4.20 and just wanted to mention that the .projectspec calls out an incorrect path for the TI-RTOS build:

It looks like the correct path is:


Can we get this updated?


  • Oh just kidding, this plugin expects the 4.20 sdk release which has a different directory structure. Will the plugin be updated at some point to the new SDK?

  • Hi,

    The WiFi plugin was verified against v3_40_00_xx of the MSP432P4 SDK and v4_20_00_xx of the MSP432E4, CC26X2R1, and CC32XX SDKs. So you might have issues using latest base SDK.

    To my knowledge, there are no plans to update these to be compatible with new base SDKs but let me check internally.



  • Hi Shlomi,

    Thanks for confirming. It's fine if the sdk compatibility doesn't get updated immediately, but the projectspec file should really call out the sdk required then, since right now it uses the system default location using the COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR variable which always points to the latestsdk.

    From the projectspec file:

    <import spec="${COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR}/kernel/tirtos/builds/CC26X2R1_LAUNCHXL/release/ccs/tirtos_builds_CC26X2R1_LAUNCHXL_release_ccs.projectspec"/>

    This will cause users with the latest 5.xx SDKs to fail on the import step due to the directory structure change described above.


  • well, it is a little more complicated than it looks.

    It is not just the base SDK directory since the internal structuring in the SDK has also changed.

    For example, for the kernel it goes to /kernel/tirtos/builds/MSP_EXP432P401R/... but this one doesn't exist even if you modify the base SDK directory. Same applies also to other locations in the projectspec.

    So it is either to modify the projectspec entirely with hard coded path or leave it as-is with a bolded message on the RN itself describing what base SDK is compatible with the plugin (as of today).



  • Yes, what I'm saying is that it should be hardcoded to a specific version if this is what's required to import successfully.

    I don't think customers should have to modify .projectspec files regardless of which SDK versions they have installed. This should be something that we should figure out internally to make the experience easy. As an FAE I've already spent over an hour trying to get this project to import and build do you really think customers would have that patience even if we note it in the release notes?


  • I will look into it internally and see what we can do and who own it.



  • Hi,

    Currently, we don’t have plans to make a new release of the plug-in in the near future, but we will take the feedback.

    We will also get in touch with you offline.