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-CC13X2-26X2-SDK: SDK update/name change + Resource explorer links missing

Part Number: SIMPLELINK-CC13X2-26X2-SDK
Other Parts Discussed in Thread: CC1352R

Hello,

So I was using Simplelink CC13x2-CC26x2 SDK v5.20.00.52 in my application with CC1352R devices, and now that the SDK has updated to a new name "Simplelink CC13XX-CC26XX" a lot of things have changed.

First of all I can no longer find the older version "Simplelink CC13x2-CC26x2" on the resource explorer page, so many of the simplelink academy links that I had, have stopped working, and I can't find that information anywhere. Sure I have newer updated versions of it with the new SDK but I have saved links with shortcuts to different topics that no longer work and I have no way of know what they were.. This is a massive drawback and disapointment, all my knowledge base summary with useful links is useless now with broken links. Can't the older version of the SDK continue to exist in resource explorer for legacy sake? Or at least is there somewhere else I can find it?

Second, because of this, I can no longer import demos/examples from the old SDK, again I can use the new SDK ones, but sometimes some drivers have changes and there are situations where it is useful to grab an example from a specific SDK version, and now, since it was simply removed from resource explorer, I can't find a way to import older examples anymore. An example would be anything with UART driver vs the UART2 driver. I have code that no longer runs correctly. Any solution on how to import examples from the old Simplelink CC13x2-CC26x2 SDK?

Third, since some things have changed in the SDKs, my application no longer compiles with the new SDK, besides driver issues like the UART one, some other things have changed as well. I'm using TI15.4 stack, already highly modified for my use case, and when copying the application code to a new example imported for the new SDK, it just breaks on dozens of issues. Is there a  a migration guide for TI15.4 stack from the old Simplelink CC13x2-CC26x2 to the new one Simplelink CC13xx-CC26xx? What else has changed in TI15.4 stack examples?

I appreciate the help, since this new SDK update was not just a normal update, given that you guys deleted the old one... 

Thanks,

  • Hey JD,

    Thanks for letting us know. Let me follow up with the appropriate team to figure this out. You make excellent points. I do want to say that SDK 5.20 is soon to be ~1 year old so I definitely recommend updating to the latest SDK if it's feasible for you.

    Is there a  a migration guide for TI15.4 stack from the old Simplelink CC13x2-CC26x2 to the new one Simplelink CC13xx-CC26xx? What else has changed in TI15.4 stack examples?

    I will loop an expert who can answer your questions with regards to porting 15.4 to the latest SDK.

  • Hi,

    If you are using Code composer Studio, you can import examples from any SDK version by doing the following (instead of using resource explorer):

    1. Project (in the menubar) -> Import CCS Projects...
    2. In the window import the example project you want to import by browsing to the directory of the example you want to import in the SDK you want to import it from.

    You can find migration guides here: https://dev.ti.com/tirex/explore/node?node=AJfRVHzN2M6THppeeBnGiA__BSEc4rl__LATEST, but I do not think these guides will solve all of your problems. What are the exact issues you are seeing?

    Thanks,
    Nikolaj

  • Hi Nikolaj, 

    Thanks for reaching out.

    Regarding importing projects from the SDK folder itself, I tried that, but it doesn't import all needed files, I guess it doens't link all the necessary files distributed through different folders, so it imports an incomplete project and fails to compile obviously.

    Now, the other issue, I've been through those migration guides but they are not that helpful in actually migrating an existing application from an older SDK to the new one. I actually didn't find them helpful at all. They mention a few changes in some libs or in SDK folder structure but explain nothing for someone who already has an existing application from an old SDK. In my case I have an application using TI15.4 Stack (2 projects): 1 based of collector example and another based on the sensor example from SDK 5.20. So my application code in both of them has been adapted to my app, files like collector.c, sensor.c, csf.c, ssf.c, cllc.c, among others have been modified by me. Now in the new SDK, the same examples have the same files but they have been modified by TI. My question is how can I "merge" my modifications with the modifications from the new SDK? Since my app is based of sensor and collector example from SDK 5.20, what do I need to add/change in my files (and which files have changed since SDK 5.20 to SDK 6.10) in order to be compatible with the new SDK. This information would be a much helpful migration guide than the ones you guys provide.

    Thanks,

    JD

  • Hi JD,

    Importing projects from the SDK itself will work (if done correctly). What issue are you seeing?

    I understand your frustration regarding the lack of migration guide. The merging steps are highly dependent on the application, and the merging steps would be difficult to describe in a generic migration guide. So we do not have a migration guide of the type you are requesting.

    We recommend importing the examples from the new SDK and reapply the modifications you have made in your application. I would recommend using a comparison tool, that will let you easily apply your changes to the new example.

    I do not expect that you will encounter many "merge conflicts", but if you do, please let us know, and we can help you sort it out for specific conflicts.

    Regards,
    Nikolaj

  • Hi Nikolaj,

    You're right, the importing worked, I guess I wasn't exactly in the correct folder when I was trying before. I can't seem to replicate the problem now, but the issue was like I said, the project structure was imported but some files were missing. Anyway, I'm glad it works now though, that's one issue out of the way.

    Now for the migration, that's what I've already been doing, using a diff tool, file on file, redoing all modifications. I was hoping there would be a guide explaining what files have changed in the new SDK, and which lines were added or removed, so I didn't have to find out by myself, I'm afraid I can miss something.. At least saying files A, B C have changed would already be useful.

    By the way, is there a recommended way by TI to write your application code using these examples in a way that avoids this issue in the future? What file structure would you recommend? Should I avoid editing the existing files entirely?

    Thanks

    JD

  • Hi JD,

    We don't have an official list of files changed, but you can use the diff tool to compare the differences between the out of the box examples of the two SDKs.
    I have tried to do that myself, and according to my analysis the following files has been changed (if you ignore the files where the only change is the copyright information at the top of the file)

    sensor:

    • cui.c
    • cui.h
    • jdllc.h
    • sensor.c
    • smsgs.h
    • ssf.c
    • main.c
    • sensor.syscfg
    • linker command file (*.cmd)
    • project settings

    collector:

    • cllc.c
    • cllc.h
    • collector.c
    • collector.h
    • csf.c
    • csf.h
    • smsgs.h
    • cui.c
    • cui.h
    • main.c
    • collector.syscfg
    • linker command file (*.cmd)
    • project settings

    The only recommendations for how to structure the application code that I am aware of at the moment is what you find here: https://dev.ti.com/tirex/explore/node?node=AGQDX07KBijdMR-Z7mbDSA__BSEc4rl__LATEST

    Regards,
    Nikolaj

  • Thanks for confirming the file change.

  • Hey JD,

    As a follow-up on your first points: the change was mainly done to avoid confusion for new and existing customers to find the latest SDK content.

    We have some planned optimizations to TIREX that will eventually address the issues you've brought up. We appreciate your patience during this transition time.

  • Thanks, I understand the need for the change, but it's bad that old links get broken and entire sections of TIREX just disappear, that's never a good thing to do for legacy reasons. I'm glad to hear you are addressing these issues.