• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 317 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSTUDIO: Why switch to Theia framework?

Derek
Mastermind 9802 points
Part Number: CCSTUDIO

Hello,

   I have quite a few MSP430 products that we support, all MSP430F5xx series of processor. I saw that these aren't supported yet in the Theia version, and that's fine. I was wondering why switch to the Theia framework from the Eclipse framework since Eclipse already does so much of the heavy lifting for an IDE. 

I looked through the release notes but I didn't see any mention of the user benefits of Theia vs. Eclipse.

Also, will the new Theia versions support MISRA checking? I looked at 3rd party solutions for MISRA checking and it's surprisingly difficult and/or expensive.

Thanks,

Derek

  • 0
    TI__Guru**** 465171 points

    Hi Derek,

    The next version of Theia (1.3) will have official MSP430 support. 

    Please note that CCS 12.x will be the last CCS version to be based off CCS Eclipse. We are deprecating the CCS Eclipse environment in favor of CCS Theia. The Eclipse framework as a whole is dated and active support by the community is declining. CCS Theia is based off the Theia IDE framework which is in turn based off VS Code. VS Code is a popular environment that is highly extendable with many available extensions. 

    MISRA checking is a feature of the compiler. The same compilers will be available between CCS Eclipse and CCS Theia.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 465171 points

    Just wanted to add that the project formats mostly the same between CCS Eclipse and CCS Theia. What this means is that your CCS Eclipse projects can simply be imported to CCS Theia (assuming any dependencies like device support and compiler are resolved). Same goes with target configuration files, GEL files, and even DSS scripts. This helps alleviate many migration concerns.