NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on The site is now set to read only.

Activating CCSv6

From Texas Instruments Wiki
Jump to: navigation, search


Code Composer Studio v6, like v4 and v5 utilizes software licensing.  You need a license file in order to use CCS.  There are several types of licenses available.  The license file determines which features and capabilities are available in CCS. The details are found in this Licensing_-_CCSv6 page.

This wiki helps you set up a demo or purchased license.  

IMPORTANT UPDATE: Note that full licenses are now available at no cost. See the important update on the Licensing_-_CCSv6 page.

First Time Use

Unlike previous CCS versions, v6 will not prompt you for your license upon first time use. It will automatically start on the free limited license until manually changed or unallowed hardware is used.  

Current License in Use

There are two places you can check your current license stasus.  

In CCSv6, the license type is noted in the bottom right.


The other place is in the license information Help->Code Composer Studio Licencing Information


Adding/Activating a license

You have seen the status tab above. There are two others. 

The manage tab where you can point CCS to a node locked license/view and manage the files used. 


The upgrade tab where you can launch the license setup and activation. 


The first step in activation (either when automatically prompted or else by launching the setup is to choose between a demo license or setting up/activating a purchased license.


Next, you need to select an option. For this wiki, we will select activating a license which provides the next screen.


First time users will need to register! This opens up a browser to create or login to a myti account:


After accepting the myti terms, you must enter your activation ID. This you will have retrieved with your license purchase, likely in an email.


Next, you will need to enter the MAC (eth0) address of the host pc (either for CCS or for the license server)


CCS will list some found addresses, but not the physical eth0 is required


In windows a command prompt to do the command ipconfig/all is also a way to verify


You will once again have to accept the license terms and then will confirm the email for the license generation


Finally the web portion is almost complete and we can chose to download CCS from the link if desired.


Once the email is received and a server setup (see this wiki) in the case of a floating license only, it is back to ccs to indicate where the license file or server is


Glossary of terms  

License File: This is a file that contains the properties of the license under which you are using CCS.  It determines the features that can be used, the product families that CCS can be used with, the length of time that you can use CCS (for evaluation licenses), if there is an object code size limit and the machine that CCS can be run on.  The license file is located on the local workstation when using a node locked license or on a license server when using a floating license.

Activation Code: This is a 32 digit code that is used to register or activate CCS.  This code is entered on the TI software registration site ( as part of the process of generating a license file.

Activate: Used to describe the action that results in the creation of a license file.  In most cases this involves using an activation code on the web to generate a license however in other cases such as when evaluating CCS or using a code size limited verison of CCS you can activate and create a license directly inside CCS.

Register: Used to describe the process where you activate a license on the web.

MAC Address: This is a unique identifier that is present in all network adapters.  For node locked licenses we need to tie them to a particular machine.  We require you to specify a MAC address so that we can identify the machine that CCS is allowed to run on.




Licensing FAQ

License Server Administration

License Server Administration FAQ