4.1. Get Started View

First time users of Code Composer Studio™ should start with the aptly named Get Started view. The Get Started view is the first screen that is visible when Code Composer Studio is launched for the first time. The view can also be explicitly opened via the Help → Get Started menu item.

The purpose of the Get Started view is to provide fast access to common actions and tasks, especially those that are relevant when first starting to use Code Composer Studio. This includes browsing examples and documentation, importing example projects, changing the IDE theme, and so forth:

image0

If you have a valid TI kit (such as a LaunchPad Development Kit) connected to your computer, the Getting Started view may be able to autodetect it. If autodetect is successful, it will be displayed under the Get started section of the view along with other relevant links for the target. If no target is autodetect, one can be manually selected by using the dropdown menu under the Get started section. Text can also be manually entered in the associated field to filter the options in the dropdown list.

4.2. Resource Explorer

The Resource Explorer helps you find all the latest examples, libraries, demo applications, data sheets, and more for your chosen platform.

Hint

The Code Composer Studio Academy is available from Resource Explorer. Explore the Code Composer Studio Academy for additional resources on Code Composer Studio.

The Resource Explorer can be opened by selecting Browse Software and examples under Start exploring in the Getting Started view or from the View → Open Resource Explorer menu item.

image1

Filtering by device, or by TI LaunchPad Kit, the interface enables you to filter the content to only what is relevant to your chosen platform.

Use the Select Board or Device filter field to search and select the device or TI LaunchPad Kit that you are using. For example, if you are using the LP-MSPM0L1306, you can starting typing "L1306" in the search field to filter the list to easily find your LaunchPad:

image2

If you have a valid TI kit (such as a LaunchPad Development Kit) connected to your computer, Resource Explorer may be able to autodetect it. If autodetect is successful, you can select the USE MY BOARD option to specify your kit:

image3

Once your device or TI LaunchPad Kit is selected, the filter will be applied and only content relevant to your selection will be displayed. You can now browse through the displayed content to learn more about your device, board, relevant tools, and available software packages. Note the additional filters to display examples based on RTOS and compiler type.

image4

The best way to get going with software development on your target is to start with some existing examples for your target. Many examples are included with the software package with supports your device, and many of these software packages are accessible right from Resource Explorer.

Note

Not all devices are supported via Resource Explorer.

4.3. Importing a Code Composer Studio Project

Code Composer Studio projects must be imported into the current Code Composer Studio workspace before they can be used. The most convenient way to import example Code Composer Studio projects is from Resource Explorer, as mentioned in some of the sections above.

The project can also be manually imported using the Import Projects wizard:

  1. Go to menu File → Import Project(s).
  2. Next to Search directory, click Browse and browse to the location of a project or project spec.
  3. Select the desired project(s) from the list of Discovered projects.
_images/ccs_doc_proj-gsg07.png

An alternative way to import a project is to drag it from the system file explorer and drop it directly into the Code Composer Studio Explorer. Once the project has been imported into the workspace, it will be visible in the Explorer.

Warning

Importing a project of the same name as one that already exists in the workspace is not allowed.

Note

Code Composer Studio can import projects that are created with Code Composer Studio versions 4.x and greater. However, bear in mind that the greater the variance in Code Composer Studio version used to create the project vs. the version used to import the project, the more error-prone the import process could be.

If a project created with an older version of Code Composer Studio is imported into the workspace of a newer Code Composer Studio version, the project may be migrated to support the newer version of Code Composer Studio. This may prevent the project from being imported or opened again with the older Code Composer Studio version. This is more likely for major Code Composer Studio revision number differences while minor revision number differences are typically not impacted.

The same rule can also apply when a project created with a newer version of Code Composer Studio is imported into an older version of Code Composer Studio. Code Composer Studio projects are typically not backward compatible in cases with major revision number differences. If you want to use a newer Code Composer Studio project with an older Code Composer Studio version, it is recommended to create a new project in the older Code Composer Studio version and copy over the source files and settings.

For more information on importing Code Composer Studio projects, please refer to the relevant section in the Projects and Build chapter.

4.4. Creating a New Code Composer Studio Project

Creating a new Code Composer Studio project purely from "scratch" is typically not recommended. Instead, it is strongly recommended to start with an existing SDK example. There is often a very minimal SDK example which ofter serves as a template for users wishing to start from "scratch".

  1. Go to menu File → Create New Project... or open the Getting Started view and select the Select the Create a new project in Code Composer Studio option under the Start developing section of the Getting Started view. This will open the Project Wizard.
  2. In Project Wizard, specify the board or device under under Select a board or device. Once a board or device is specified, a list of available projects appear.
  3. (Optional) Use the Filters and Categories fields to filter the list of available projects.
  4. Select the desired project to import. Most SDKs provide some sort of empty type example which serves as a basic template for new projects.
  5. (Optional) Under Configure selected project
  • Use the Project Name field to change the project name from the default.
  • Use the compiler and kernel fields below the project list to specify the compiler type and kernel to use. Note that not all projects have multiple options for these fields.
  1. Press Create to import the example project into the Code Composer Studio Explorer

image9

Warning

The Project Wizard is based off of Resource Explorer and will allow a user to select from a rich variety of device specific templates from an available on-line SDK for the device in Resource Explorer. Internet access is required for full access to all the templates/examples. If internet access is not available, then the user will only have the option to select simple non-SDK based projects such a skeleton “empty” or basic “hello world” projects. These templates are often incomplete and require additional work to have a complete working project.

4.5. Building and Debugging Your Project

Once your project has been created/imported and any necessary manual changes completed, the project can then be compiled and loaded to the target for execution/debug. There is one easy option to do all this - by selecting the project in the Explorer view and selecting Debug Project in the context menu (or select Run → Debug Project in the top menu bar). This option will automatically do all the below steps by default:

  • Save source files (if necessary).
  • Build the project (incrementally).
  • Start the debugger (Code Composer Studio will switch from the Explorer to the Debug view in the Side Bar).
  • Connect Code Composer Studio to the target.
  • Load (flash) the program on the target.
  • Run to main.

image11