MacOS X CCSv6 Beta

From Texas Instruments Wiki
Jump to: navigation, search


This page contains information regarding Code Composer Studio v6.1.1 Beta2 running on MacOS X. It includes general information as well as known issues.


  • The Beta installer does not detect if a version of CCS is already installed in the location you have selected. Thus please take care to not choose a location that already has a CCS installation. Or delete the previous version before installing a newer beta version.
  • The installation instructions (Step 6 in README_FIRST.txt) asks to run in <Install-Folder>/ccsv6/install_scripts, but there is no such folder. This step is actually not required but the README and installer haven't been updated to reflect that.

Projects and Build

  • Avoid project names that have spaces in them, especially for RTSC projects. Also avoid installing RTSC tools (TI-RTOS, SYS/BIOS etc.) in directories that have spaces in the directory name. This is a known issue with RTSC and is not specific to MacOS.


  • C I/O does not work on ARM based devices due to a known issue with conditional breakpoints.
  • Breakpoints do not work on ICDI JTAG debuggers.

MSP-FET Probes

With El Capitan OS (10.11 release) and CCS 6.1.1 Beta2, there may be issues connecting to the target with MSP-FET probes. If you hit connection issues, please try updating the MSP430 Emulators pack (menu Help->Check for Updates, and select the MSP430 Emulators update) to version OR download and install CCS 6.1.2 Beta3.

XDS Probes

With El Capitan OS (10.11 release) and CCS 6.1.1 Beta2, there may be issues connecting to the target with XDS probes. If you hit connection issues, please try updating the TI emulation pack (menu Help->Check for Updates, and select the TI Emulation update) to version OR download and install CCS 6.1.2 Beta3.

Working with TI software packages

  • MSPWare is currently not available in CCS App Center, but can be downloaded and installed separately from There is a MacOS specific installer available there.
  • Other packages (TivaWare, Controlsuite, BLE Stack etc.) do not have Mac installers. You can install the software on Windows and copy the contents over to Mac.
  • After the software packages are installed, Resource Explorer can be configured to discover them. Go to the Resource Explorer home, click on Configure Resource Explorer to discover examples, documentation and generates a resource package. Click on Add, and browse to the location of the package.


  • There is an incompatibility between MSPWare version and CCS 6.1.1 that does not allow creating one-click projects using Resource Explorer. The error generated is: CreateProcess error=267, The directory name is invalid.
    The issue happens on Windows and MacOS. Please see this thread.

This is fixed in newer versions of MSPWare.

Bluetooth Low Energy Software Stack (BLE-STACK)

There is no MacOS installer available for the BLE-Stack, however it can be installed on Windows and then copied over to the Mac. The CCS projects in BLE-Stack can also be imported and built on MacOS after editing some variables that have hard-coded paths. Please follow the steps below:

  • BLE-STACK-2-1:
  1. Copy the Simplelink BLE-Stack software (the entire simplelink folder) from Windows to Mac.
    Note: as will be clear below, it will simplify the process if the BLE projects of interest are compiled at least once in Windows before copying the BLE-stack.
  2. Install TI-RTOS by copying software over from Windows to Mac
    Note: TI-RTOS can be installed from CCS App Center, however only the latest version is available there. Specifically, the latest version available through App Center does not build with this version of BLE-Stack, hence the need for version The BLE-Stack installer for Windows will install TI-RTOS 2.13.00,06.
  3. If TI-RTOS was copied over to a folder other than /Applications/ti, then have CCS detect it by adding its path to Product Discovery path (under menu Code Composer Studio->Preferences->Code Composer Studio->RTSC->Products)
  4. Import the desired CCS project
  5. Go to Project Properties->General->RTSC tab and ensure that TI-RTOS for Simplelink Wireless MCUs is selected
  6. Go to Project Properties->Build->Variables tab. Click on Show System Variables to view all variables. Edit the variables CC26XXWARE (needed for both 'App' and 'Stack' examples) and TI_RTOS_DRIVERS_BASE (needed for 'App' examples) to point to their location on the Mac system (make sure the c:/ prefix is removed)
  7. Build project
    Note: Before building, the right library files must be copied to the project folder. In Windows this is handled automatically as a pre-build step, but this will not run on Mac. The simplest way to do this is to compile the respective projects in either IAR or CCS on Windows and then copy the *.a files to the right location in the Mac file system. If the projects were compiled in Windows before the stack was copied to the Mac, no actions are required. The library files are found here (for SimpleBLEPeripheral in BLE 2.1.1): C:\ti\simplelink\ble_cc26xx_2_01_01_44627\Projects\ble\SimpleBLEPeripheral\CC26xx\IAR\Lib
  8. NOTE: For the 'Stack' examples, the Boundary tool is called as a post-build step (Under 'Project Properties->Build->Steps'). The Boundary tool is used to adjust the Stack flash / RAM boundary to the optimal value. These errors typically occur when the Stack configuration is modified such that RAM/Flash usage has changed. This tool is only available for Windows, hence this post-build step will fail. While the error message for this failure does not impact the build, this step can be removed to avoid the error.