• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1654 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.

CCS/CC1350: Configuring and using RTSC in CCS 7.1

David Bartle
Intellectual 585 points
Part Number: CC1350

Tool/software: Code Composer Studio

I'm new to TI uControllers and CCS - my installation of CCS allows me to build and run the example projects however I can't figure out how to use RTSC in configuring a new project of modifying an old one. The "RTSC Tools" menu selection appears in project menu, however the "platform package" isn't configured and it's not clear what I need to choose. Any pointers to documentation or tutorials would be greatly appreciated.

  • 0
    TI__Guru* 96960 points
    Hi David,

    You can convert a non-RTSC project to be a RTSC project, but there are several steps. We recommend you import a simple template project that is RTSC based and for your desired device. Then move your application code into it.

    Note: once a project is tagged as a RTSC project, it cannot be converted back to non-RTSC.

    Todd
  • 0 in reply to ToddMullanix
    Intellectual 585 points

    Thanks for the information on RTSC project configuration.  Before I proceed further, is RTSC the right approach for product configuration? It's not clear if TI is encouraging its use as I have discovered the example projects I have tested for the CC1350 LaunchPad appear to NOT be RTSC based. And CCSV7 doesn't include "Empty RTSC Project" in it's new project choices. If RTSC isn't used, instructions for manually editing the appropriate config file would be helpful as well.

    I did some digging around on how to create and build an empty RTSC project. I found some references to how to create an RTSC project by adding an RTSC  configuration file to a new empty project. I followed the instructions for an earlier version of CCS but alas my project has build errors related to failure to find an "xdc.services.global.XDEException" file. I thought I had installed all the necessary components in CCS.

    Advice on the preferred project creation (RTSC or not) configuration would be helpful. And if RTSC is the preferred approach, pointers to detailed instructions/documentation would be appreciated. 

  • 0 in reply to David Bartle
    TI__Guru* 96960 points
    Hi David,

    First a little background. For the CC13xx and CC26xx a decision was made several years ago to require applications to be TI-RTOS based (I won't go into the details). The TI-RTOS kernel (with a few hard-coded configuration settings) was generated and placed in the ROM to help minimize footprint impacts. Therefore all the examples in the SimpleLink CC13x0 SDK are TI-RTOS based.

    The TI-RTOS kernel requires a configuration file (aka .cfg file). This is a JavaScript like file that allows configuring the kernel to meet your application needs. The .cfg file is used in a pre-build step to generate source files (and headers) and a linker file that is used in building the application.

    Historically, the .cfg file was included in the project (or the application project for CC26xx devices that have a stack project and application project). With the SimpleLink SDKs this is still possible, but you can have it as a separate project called the kernel configuration file. There is a "release" and "debug" kernel configuration available in the SDK and you can modify or make more (please refer to the SimpleLink User Guide for more details). All the driver and all (I believe) of the EasyLink examples use this separate project approach. The kernel examples still use the .cfg file in the project approach.

    If the project has a .cfg file, it is a RTSC project. So for the EasyLink and Driver examples, the application project is not a RTSC project, but is dependent on a kernel configuration project (which is a RTSC project).

    For the foreseeable future, the TI-RTOS kernel project will always be a RTSC project. We don't have any concrete plans to change this (but we are always looking for ways to make it easy for the user that does not break compatibility).

    Having the .cfg in the application project allows for better fine-tuning of the application. Having the application project depend on a kernel project allows for a more standardized kernel (which works well when there are many people working on a product or several products that want to share the same configuration).

    I personally prefer having the application depend on a kernel project. So I would start with maybe the simplest EasyLink or 15.4 example and use that as the template. You'll get all the RTSC and stack settings you'll need.

    Fyi...for the MSP432 and CC32xx SimpleLink MCU devices we also support FreeRTOS, but there is no current plan to support this on the CC13xx/CC26xx devices. We are actively looking at supporting a no-RTOS solution for the CC13xx/CC26xx devices. You'll still get the functional TI Drivers (e.g UART, I2C) and power management that you get with the RTOS based solution. These obviously would not be RTSC projects.

    Hope that helps and does not just confuse things:)
    Todd