10.1. Installation¶
10.1.1. General Tips for Installing Code Composer Studio™¶
- Clean out all prior failed or incomplete installations (by deleting the install directory) before attempting a new one to the same directory. In Windows, use Shift+Del and in Linux and MacOS use
rm -Rfon the install directory. - If you plan to install two versions side-by-side, always use different workspaces. Sharing a workspace between two versions may cause severe impact in project building and debugging.
- Disable anti-virus (certain anti-virus software is known to cause problems). If it cannot be disabled, try the off-line installer instead of web installer.
- It is recommend to have a username that does not have any non-alphanumeric characters, and that you are installing Code Composer Studio to a directory that does not have any non-alphanumeric characters.
10.2. General IDE¶
10.2.1. Delete Workspace Cache¶
Code Composer Studio caches various workspace information in a separate folder located in the user's home directory. The contents of this folder can get corrupted over time, causing various instability and strange behavior with the IDE. Clearing this cache can help resolve these issues.
This folder is located in:
- WIndows:
[USER HOME]\AppData\Local\Texas Instruments\CCS\.ccs-server\workspaces - Linux:
[USER HOME]/.config/Texas Instruments/CCS/.ccs-server
Note
Deleting this cache will restore the IDE back to the original default state.
10.3. Resource Explorer¶
10.3.1. Check your Internet Connection¶
A poor internet connection may cause Resource Explorer to timeout when attempting to sync with the server. Try again when you have more bandwidth available.
10.3.2. Check the Proxy Setting¶
If Resource Explorer is unable to connect to the internet it may be an issue with the proxy settings. Check that your system proxy settings and environment variables are set correctly:
- Open the General Settings in Code Composer Studio (File → Preferences → General Settings)
- Type "proxy" in the search box
- Set the proxy url under Http: Proxy
- Restart Code Composer Studio
10.3.3. No Content Displayed¶
There are some known issues with Resource Explorer inside the Code Composer Studio IDE not being able to display certain content properly or at all. The root cause is often not Resource Explorer itself but the internal web browser that is used by the IDE. If this happens, navigate to the relevant node in the left panel and then choose the option to Open in System Browser. This will open the page outside of the IDE in your default system web browser.
In some cases, an additional message will appear explicitly mentioning that the content must be opened in an external browser (such as above), while in other cases it will simply display invalid content. Regardless, the Open in System Browser button should be available in the upper right corner if the correct node is selected.
10.4. Projects¶
10.4.1. Unable to Build or Debug Projects¶
If the option to build or debug a project is unavailable, try restarting Code Composer Studio.
10.5. Debug¶
10.5.1. Delete the Launch Configuration¶
Invalid information in the launch.json file can cause issues with the debug session. Clearing the contents of this file (or deleting it completely) can help resolve these issues.
10.5.2. Delete Debug Cache Files¶
Code Composer Studio caches various debug information in a folder located in the user's home directory. The contents of this folder can get corrupted over time, causing various instability and strange behavior with the debugger. Clearing this cache can help resolve these issues.
This folder is located in:
- WIndows:
[USER HOME]\AppData\Local\Texas Instruments\CCS\[CCS INSTALL FOLDER NAME] - Linux:
[USER HOME]/.config/Local/Texas Instruments/CCS/[CCS INSTALL FOLDER NAME]
10.5.3. JTAG Connectivity Issues¶
If an error happened during the process of launching the debugger or any JTAG specific issues, see: Debugging JTAG Connectivity Problems.
Warning
If running Code Composer Studio on a Linux host, please make sure the driver install script is run as superuser using sudo after installation. See: Post Installation Step
10.5.4. Data Verification Issues¶
If a data verification error occurs when loading a program, see: Troubleshooting Code Composer Studio - Data Verification Errors.
10.5.5. Unable to Enable Trace¶
If the options to enable trace are unavailable, check the status of the Trace Server in the Trace view. It may be offline. If so, please restart Code Composer Studio.
10.5.6. CPU Reset is not resetting all cores in the group¶
There is a known issue where a CPU reset is not being applied to all members of the group despite the Enable Cross Triggering and Synchronous Execution button being enabled. This will get addressed in a future release. A workaround is to use the default keyboard short to execute the default reset (CTRL+SHIFT+R) or use the Reset button in the Toolbar.
10.6. Getting Support¶
If the troubleshooting tips mentioned above do not help resolve the issue, please check the Support dialog under Help → Support for a link to the support forum and access to diagnostic logs.
