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/MSP432E411Y: XDCTools still used in TI-RTOS examples of MSP432?

Part Number: MSP432E411Y

Tool/software: TI-RTOS

Dear TI-Experts,

I'm just comparing Tiva C and SimpleLink for a new project.

After looking at many TI-RTOS examples for the MSP432 processor family I could only very rarely see a .cfg file (which configures XDC as far as I know). (Only exception so far: uart_logging)

Is it possible to use TI-RTOS without the XDC/RTSC environment? (Or is it somehow hidden?)

All Tiva C / TI-RTOS examples I inspected use a .cfg file. Why don't the SimpleLink / TI-RTOS examples? Is TI leaving the XDC approach?

Is Tiva C development ongoing or did TI completely switch to SimpleLink? (In other words: is it wise to base a new project on Tiva C?)

Another concern: Why do all MSP432 TI-RTOS examples reserve half the processor memory as heap in the *.cmd file. Is there a rationale?

Why didn't the Tiva C / TI-RTOS examples?

Please help me in finding the right decision!

  • In the SimpleLink SDK, the .cfg file is contained in the associated TI-RTOS project.
    For new projects, I would recommend using the MSP432E4 unless the feature set requires you to use the TivaC devices . Using the MSP432E4 allows you to operate within the SimpleLink SDK, which greatly simplifies porting (or writing new) code to other devices in the family. For example, building a WiFi-Ethernet gateway using the MSP432E4 and a CC32xx device is much easier since Plugins which support various stacks are readily available.
    As for the heap allocation, I don't believe there was any specific rationale, other than perhaps to allow for the configuration to cover a wide range of possible examples that might be created, without having a separate config for each example.

    -Bob L.
  • Hi Bob,

    thank you for your response. But there are still things unclear to me:

    You wrote "In the SimpleLink SDK, the .cfg file is contained in the associated TI-RTOS project."
    Let's take the example "adcbufcontinuous_MSP_EXP432E401Y_tirtos_ccs". I cannot find a *.cfg file after importing the project into CCS. Even CCS does not identify it as an RTSC project and no xdc header files are included. Could you point to the .cfg file location? (It doen't look like a duck, it doesn't swim like a duck - is it really a duck ;-) ??)

    What do you mean with "unless the feature set requires you to use the TivaC devices"? Are there any limitations in the SimpleLink software package compared to TivaC, or are you only referring to hardware?
  • Hi Bob,
    the first question is resolved: It is a duck. There is a referenced project in project properties -> CCS Build -> Dependencies. This project "tirtos_builds_MSP_EXP432E401Y_release_ccs" contains the *.cfg file as you explained.
    (I should have read the "SimpleLink MCU SDK User's Guide" to the ending.)

    Could you please answer the second question?
  • Not sure how you're counting. are you referring to the "Why don't the SimpleLink / TI-RTOS examples? Is TI leaving the XDC approach?"
    The answer to that is "no", not leaving the XDC approach. It's just a different way of organizing the files.
    -Bob L.
  • Hi Bob,
    sorry for being too unspecific. I was referring to my post on Jun 12, 2018 7:46 PM, question: "What do you mean with "unless the feature set requires you to use the TivaC devices"? Are there any limitations in the SimpleLink software package compared to TivaC, or are you only referring to hardware?"
  • Ahh yes. My turn to apologize for being too unspecific :)
    This is a hardware-only comment. If you're using only USB and not Ethernet, then I would steer you towards the TM4C123. If you ARE using Ethernet on a new project, and have the possible future need for wireless in your system, then I would recommend the SimpleLink MSP432E4.
    -Bob L.

  • PS- I'm marking some of my prior responses as "resolved" to identify each as a partial answer for future readers of the posts. If these cover all your questions, please mark them as "this solved my issue". Thanks.
    -Bob L.

**Attention** This is a public forum