Tutorial: setting up CCS v4 for MSP430 Launchpad

Raj inform us that he recently finished writing a step-by-step guide for setting up the Code Composer Studio v4 build and debug environment for TI MSP430 Launchpad. You can read Raj’s tutorial at Embedded lab.

Via the contact form.

Join the Conversation


  1. These IDE/compiler programmers need to learn to make their installations independent of other IDE’s that may already exist on the system (including previous versions of their own). As it is today, installing the likes of CCS on a system often breaks other IDEs that coexist unless the user performs major surgery on the environment settings. An alternative of-course (sometimes) is to use virtual machines, but they have steep resource requirements and are often troublesome when it comes to I/O.

  2. You should always consider setting up an IDE inside a VM, especially if you’re using it in a commercial environment, or if the IDE has some sort of mechanism to stop arbitrary installations.

    If you have to maintain code a year or two down the line when you’ve changed your PC, changed the engineer maintaining the project, or the IDE version has changed and you cannot use your old code under the new version without considerable work, you will be very glad of the ability to run it ‘just as it was’ without archiving the whole PC.

    I would go so far as to say it is commercially negligent to do anything else. Some vendors do not support this type of operation. You should consider whether they are appropriate for purchase – you will spend considerably more on maintenance on most projects than on the initial development and economic support for it is crucial.

Leave a comment

Leave a Reply to brentbxr Cancel reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.