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.
- If possible, disable anti-virus/security software (certain such software are known to cause problems).
- It is recommended 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 user information in separate folders 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.
Warning
Deleting this cache will restore the IDE back to the original default state. Any custom user settings will be lost.
10.2.2. Multi-Root Workspace Issues¶
There are several known issues with Multi-Root Workspace environments. It can cause issues with launch configurations and corrupt the *.theia-workspace file. These issues are addressed in Code Composer Studio v20.0.2 and greater. If you are using an older version, it is strongly recommended to update to a version with the fix. Any existing *.theia-workspace files created with an earlier version should be deleted.
10.2.3. Unable to Connect to the Internet¶
If Code Composer Studio is running on a network that requires a proxy server to access the internet, it may be required to set the proxy settings for Code Composer Studio. This can be done from the General Settings:
An alternative to the above is to set the http_proxy and/or https_proxy system environment variables instead. Code Composer Studio will use the value of those variables if one is not set in the General Settings.
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 proxy settings in Code Composer Studio and for the system.
10.3.3. No Content Displayed¶
There is a known limitation 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.3.4. Video Playback Error¶
There is a known limitation with Resource Explorer inside the Code Composer Studio IDE not being able to playback certain video formats. This is common with many videos from the TI video library
The root cause and workaround is the same as mentioned in the "No Content Displayed" FAQ above.
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. Unable to Launch Debug Session when using Multi-Root Workspaces¶
10.5.2. 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.3. Delete Debug Cache Files¶
Code Composer Studio caches various user information in separate folders 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.
Warning
Deleting this cache will restore the IDE back to the original default state. Any custom user settings will be lost.
10.5.4. JTAG Connectivity Issues¶
If an error occurs 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.5. Data Verification Issues¶
If a data verification error occurs when loading a program, see: Troubleshooting Code Composer Studio - Data Verification Errors.
10.5.6. 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.7. 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 Toggle Group Operations button being enabled. This will be addressed in a future release. A workaround is to use the default keyboard shortcut (CTRL+SHIFT+R) to execute the default reset, 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.
