• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 509 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

RTOS/SIMPLELINK-CC13X0-SDK: RTOS/SIMPLELINK-CC13X0-SDK

Peter Kostadinov
Prodigy 230 points
Part Number: SIMPLELINK-CC13X0-SDK

Tool/software: TI-RTOS

Hello,

I was unable to find detailed information about differences between usage of SIMPLELINK-CC13X0-SDK and stand alone TI-RTOS.

Can you please give me a link to such document.

Best Regards,

Peter

  • 0
    TI__Guru**** 317180 points
    It's a significant difference. When we started to provide a TI-RTOS solution for CC13x0 the TI-RTOS solution was standalone. But a bit over a year ago we started to provide SDKs that contains a TI-ROS version. In other words the last standalone version is rather old and to get the latest and greatest you should use the SDKs.

    The SDKs also contains a lot of up to date documentation, the 15.4 stack and Simplelink academy that is a very useful learning tool.
  • 0 in reply to TER
    Expert 1455 points
    I also had this question. The multitude of similarly labelled options is confusing. Can the older options be removed? Also, For clarity, when configuring a new project, we should be using "SimpleLink CC13X0 SDK" and not "TI-RTOS for CC13xx and CC26XX" or "TI-RTOS for SimpleLink Wireless MCUs", correct?

    Thank you,

    Michael
  • 0 in reply to Michael Cress
    TI__Guru**** 317180 points
    Steps has been done to make it clear that the SDK should be used. Now the old TI-RTOS versions are a bit hidden and are only there if someone that started development early and need to re-download.
  • 0 in reply to TER
    Expert 1455 points
    These versions all appear to have parity to me within the IDE. Perhaps it is because I have installed them inadvertently. But if so, this is me being proactive in installing/updating software through the CCS App Center which didn't notify me that I was installing a deprecated API.

    As a brand new user to this platform, I would like to see this situation improved in the next CCS release because the multitude of options for installing SDKs, libraries, and current/out-of-date documentation (via instructions disseminated through the TI website, forums, and CCS itself) makes for a very steep learning curve.
  • 0 in reply to Michael Cress
    TI__Guru**** 317180 points
    If you find something on the TI web that you think could be improved, is misleading etc, send us a description of what the issue is and a link to the page you are referring to.

    The most up to date documentation is in the SDK: dev.ti.com/.../

    A post on E2E will always be a time snap shot meaning that the information is (hopefully) correct at the time of writing. On the CC13x0 platform we do a lot of development meaning that in the time span of a couple of years a lot has changed, bugs has been found and fixed, more efficient ways to do things has been found etc meaning that some care has to be taken to use information relevant for your usage.