GSG:CCSv5.0 Running for the first time

IMPORTANT! This Getting Started Guide was designed to be used only with Code Composer Studio 5.0.x and pre-releases of 5.1.x.
Running Code Composer Studio for the first time

---

Defining the workspace directory

The first thing CCSv5 asks is to define a workspace - a directory that holds all elements (projects, links to projects, possibly source code) used in the development.

• Differently than CCSv4, by default the workspace is created under the C:\Users\<user> or C:\Documents and Settings\<user> directory, but its location is arbitrary.
• Every time CCSv5 is executed it will ask for the workspace directory. If you plan to use just a single directory for all your projects, just check the option Use this as the default and do not ask again. The workspace can always be changed later from inside CCSv5.

Fig. 1: selecting the workspace location

Choosing the license

You need a license to use CCS for JTAG debugging. If you are just doing Linux Application Debug then no license is needed.

CCSv5 on Windows will give you the option to generate a 30 day eval license. On Linux you can use this link to create an eval license. If you already have a CCSv4 license you can use this with CCSv5.0.x.

The welcome screen

After the license process is finished, CCS will show the Welcome Screen and be ready to use.

Fig. 2: Welcome to Code Composer Studio v5!

What's next?

Now that you have finished the license activation of Code Composer Studio v5, please continue on to the Working with CCS section of the CCSv5 Getting Started Guide.

---