Texas Instruments today announced the release of Code Composer Studio version 5.1 with Linux support. This comes after the Limited Release of v5.0 which was  a preliminary release to fill some existing development tool gaps, such as Linux Application Debug and Linux host support. The objectives of the Code Composer Studio v5 program is to bring CCS to the latest version of Eclipse with no modifications (‘Stock Eclipse’). This will allow customers to integrate a wider range of 3rd party plugins (as compared to CCSv4.x) and will also allow upgrades of open source components of CCS. To get the full rundown of features in the new CCS, look up this presentation.

Unfortunately there is no Linux support for the MSP430 and Stellaris controllers.

Key Changes and Limitations

  1. Using “stock” Eclipse and CDT.  What this means is that we are no longer branching the Eclipse and CDT source code.  This means that CCS will now keep pace with the latest Eclipse and CDT releases so that you will be able to take advantage of any fixes and improvements made.  TI will also be contributing fixes and enhancements back to the open source community.  The Eclipse and CDT update sites will automatically be checked for updates.  This will greatly improve compatibility with other Eclipse plug-ins.
  2. No more “active project”.  The concept of an active project was something that TI had added in its code branch and we have not been able to get it back into the open source code.  Instead of an active project in CCSv5 you have a “selected” project context.  i.e. whatever project(s) is selected in the project view will be the one that build and other actions are applied to.
  3. Drag and drop support.  You can now drag text around within editor windows as well as from the editor to the watch window.
  4. OS application debug support.  This is a benefit of being based on stock Eclipse.  The application (run-mode) debuggers for many popular OSs are based on Eclipse.  So you can now integrate Application level debug for OSs such as Linux, Android, OSE, Neutrino and Nucleus just to name a few.
  5. Multiple instances of views not supported in 5.0 (will be present in CCSv5.1). In CCSv4 you can open up multiple expression views or memory views or disassembly views… This was a TI custom feature that we implemented which is not present in stock Eclipse as this time and thus is not present in current builds of CCSv5. Note that if you want to view things side be side, it is still possible via Eclipse’s feature to launch unlimited workbenches (Window->New Window).  So for example, to view two memory windows side by side, you can simply select Window->New Window command to launch a new workbench. Then you can simplify the new view, by closing all unnecessary views and leaving only the memory window open. We consider this to be an acceptable workaround for most users.
  6. Real Time Access not tested: Up until now, we have not tested any real time target access features. This may or may not work. Users who rely on this feature heavily,  my not want to upgrade to CCSv5 LR.
  7. Linux host support: CCSv5 supports both Windows and Linux PCs.
  8. Command Lined Project Create/Import/Build: Command line to invoke commands is different CCSv4 commands were invoked by executing java with a specific .jar in CCSv5 eclipsec.exe is used. CCSv4 “jre\bin\java -jar startup.jar restOfCommand” ; CCSv5 requries “eclipsec -nosplash restOfCommand”


Links:
CCSv5 Getting Started Guide: a more comprehensive Getting Started Guide.
CCSv5 Fundamentals Workshop: Introductory hands-on training for CCSv5.1 using an MSP430 LaunchPad