• State Resolved
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 56 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

CODECOMPOSER: CCS20.1: CCS Server failing to initialize

Markus Großer
Prodigy 105 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: TMS320F28386D

Tool/software:

This is an issue that has, in various forms, repeatedly plagued me with various versions of CCS Theia (knowing fully well that it was still semi-experimental software), but still persists with CCS 20.1.

I am using an ostensibly rather simple file-based workspace, with three folders that are adjacent to the projectname.theia-workspace file. Each folder contains one CCS project (CPU1, CPU2, CM; the three cores on a TMS320F28386D). This setup was last working with CCS Theia 1.4.0.

Before the below steps, both cache directories listed on the CCS troubleshooting page (%LOCALAPPDATA%\Texas Instruments\CCS\.ccs-server\workspaces\22def2ca02b59dc614d7e2fb59ea9423 and %LOCALAPPDATA%\Texas Instruments\CCS\ccs2010) had been deleted.

With CCS 20.1, opening the workspace will have an endlessly loading "Code Composer Studio - Initializing" notification in the bottom right. Additionally, none of the projects in the folders are recognised as such (as evidenced by the lack of project-related options in the right-click menu). The general log file in %LOCALAPPDATA%\Texas Instruments\CCS\.ccs-server\workspaces\22def2ca02b59dc614d7e2fb59ea9423 repeatedly contains the following error:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
!SESSION 2025-03-10 14:05:05.937 -----------------------------------------------
eclipse.buildId=unknown
java.version=17.0.2
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -application com.ti.ccs.server.start -pluginCustomization C:\ti\ccs2010\ccs\eclipse\ccs.preferences.ini -ccs.socketPath \\.\pipe\22def2ca02b59dc614d7e2fb59ea9423.sock -ccs.workspaceFolderPaths e:\Git\projectname\Firmware\CPU1;e:\Git\projectname\Firmware\CPU2;e:\Git\projectname\Firmware\CM -ccs.defaultImportDestinationPath c:\Users\m.grosser\workspace_ccstheia -ccs.buildSecurityPolicy level:desktop
Command-line arguments: -os win32 -ws win32 -arch x86_64 -application com.ti.ccs.server.start -pluginCustomization C:\ti\ccs2010\ccs\eclipse\ccs.preferences.ini -data C:\Users\m.grosser\AppData\Local\Texas Instruments\CCS\.ccs-server\workspaces\22def2ca02b59dc614d7e2fb59ea9423 -ccs.socketPath \\.\pipe\22def2ca02b59dc614d7e2fb59ea9423.sock -ccs.workspaceFolderPaths e:\Git\projectname\Firmware\CPU1;e:\Git\projectname\Firmware\CPU2;e:\Git\projectname\Firmware\CM -ccs.defaultImportDestinationPath c:\Users\m.grosser\workspace_ccstheia -ccs.buildSecurityPolicy level:desktop
This is a continuation of log file C:\Users\m.grosser\AppData\Local\Texas Instruments\CCS\.ccs-server\workspaces\22def2ca02b59dc614d7e2fb59ea9423\.metadata\.bak_1.log
Created Time: 2025-03-10 14:18:45.603
!ENTRY org.eclipse.core.jobs 4 2 2025-03-10 14:18:45.603
!MESSAGE An internal error occurred during: "Sending build events with disabled autobuild".
!STACK 0
java.lang.StackOverflowError
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:142)
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:203)
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:142)
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:203)
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:128)
at org.eclipse.core.internal.dtree.AbstractDataTreeNode.assembleWith(AbstractDataTreeNode.java:203)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The same issue 

Going back to CCS Theia 1.4.0 has not worked out as planned either -- after various attempts, the projects get recognised as such, but the StackOverflowErrors still appear whenever trying to build the project, without anything actually happening.

Details about the projects (including .project/.cproject/.ccsproject files) can be shared in private if required.