SLAU664B February   2016  – August 2017

 

  1.   MSP430FR2311 LaunchPad™ Development Kit (MSP‑EXP430FR2311)
    1.     Trademarks
    2. 1 Getting Started
      1. 1.1 Introduction
      2. 1.2 Key Features
      3. 1.3 What's Included
        1. 1.3.1 Kit Contents
        2. 1.3.2 Software Examples
      4. 1.4 First Steps: Out-of-Box Experience
        1. 1.4.1 Connecting to the Computer
        2. 1.4.2 Running the Out-of-Box Demo
      5. 1.5 Next Steps: Looking Into the Provided Code
    3. 2 Hardware
      1. 2.1 Block Diagram
      2. 2.2 Hardware Features
        1. 2.2.1 MSP430FR2311 MCU
        2. 2.2.2 eZ-FET Onboard Emulator With EnergyTrace™ Software
        3. 2.2.3 Emulator Connection: Isolation Jumper Block
        4. 2.2.4 Application (or "Backchannel") UART
        5. 2.2.5 Special Features
          1. 2.2.5.1 Smart Analog Combo (SAC)
      3. 2.3 Power
        1. 2.3.1 eZ-FET USB Power
        2. 2.3.2 BoosterPack Plug-In-Module and External Power Supply
      4. 2.4 Measure MSP430 MCU Current Draw
      5. 2.5 Clocking
      6. 2.6 Using the eZ-FET Emulator With a Different Target
      7. 2.7 BoosterPack Plug-in Module Pinout
      8. 2.8 Design Files
        1. 2.8.1 Hardware
        2. 2.8.2 Software
      9. 2.9 Hardware Change log
    4. 3 Software Examples
      1. 3.1 Out-of-Box Software Example
        1. 3.1.1 Source File Structure
        2. 3.1.2 Power Measurement
      2. 3.2 Blink LED Example
        1. 3.2.1 Source File Structure
      3. 3.3 Software I2C Example
        1. 3.3.1 Source File Structure
    5. 4 Resources
      1. 4.1 Integrated Development Environments
        1. 4.1.1 TI Cloud Development Tools
          1. 4.1.1.1 TI Resource Explorer Cloud
          2. 4.1.1.2 Code Composer Studio Cloud
        2. 4.1.2 Code Composer Studio IDE
        3. 4.1.3 IAR Embedded Workbench for Texas Instruments MSP430
        4. 4.1.4 Energia
      2. 4.2 LaunchPad Websites
      3. 4.3 MSPWare Software and TI Resource Explorer
      4. 4.4 FRAM Utilities
      5. 4.5 MSP430FR2311MCU
        1. 4.5.1 Device Documentation
        2. 4.5.2 MSP430FR2311 MCU Code Examples
        3. 4.5.3 MSP430 MCU Application Notes and TI Designs
      6. 4.6 Community Resources
        1. 4.6.1 TI E2E Online Community
        2. 4.6.2 Community-at-Large
    6. 5 FAQ
    7. 6 Schematics
  2.   Revision History

4.1.2 Code Composer Studio IDE

Code Composer Studio Desktop is a professional integrated development environment that supports TI's microcontroller and embedded processors portfolio. Code Composer Studio IDE comprises a suite of tools used to develop and debug embedded applications. It includes an optimizing C/C++ compiler, source code editor, project build environment, debugger, profiler, and many other features.

Learn more about CCS IDE and download it at www.ti.com/tool/ccstudio.

CCS v6.1 or higher is required. When CCS has been launched, and a workspace directory chosen, use Project>Import Existing CCS Eclipse Project. Direct it to the desired demo's project directory that contains main.c (see Figure 12).

fig12_Project_Import.jpgFigure 12. Directing the Project>Import Function to the Demo Project

Selecting the \CCS subdirectory also works. The CCS-specific files are located there.

When you click OK, Code Composer Studio should recognize the project and allow you to import it. The indication that Code Composer Studio has found it is that the project appears in the box shown in Figure 13, and it has a checkmark to the left of it.

fig13_CCS_Found_Project.jpgFigure 13. When CCS Has Found the Project

Sometimes Code Composer Studio IDE finds the project but does not show a checkmark; this might mean that your workspace already has a project by that name. You can resolve this by renaming or deleting that project. (Even if you do not see it in the Code Composer Studio IDE workspace, be sure to check the workspace directory on the file system.)