LP-MSPM0G3507: Code composer Studio no longer reporting errors

Ken Ayre

Part Number: LP-MSPM0G3507
Other Parts Discussed in Thread: CCSTUDIO

Tool/software:

Was running CCS 20.3, now running 20.3.1.5_1.9.1

using ticlang C compiler with FreeRTos

I have a large body of code which run's through the build process and finishes with "gmake: Target 'all' not remade because of errors.", but no errors are identified. The build issues were becoming more frequent, with errors being flagged in the Output window, but no tagging within the actual files or workspace explorer window. Then on Friday, the build process just stopped- it always hung.

Looking through other e2e posts, I read deleting cache from {home}/ti/ might help. It did not. Also, deleting the contents of the \Debug folder did not help.

Reading bug report EXT_EP_12940, i updated to 20.3.1 (bug report says fixed in 20.4. After new install, we can run through the build process again, but still the build states there are errors, but does not identify where the problem(s) are.

I noticed changes occurred in the files .cproject and .ccsproject during Azure Pull requests. I wonder what differences across the design team could be throwing a wrench in the works.

Help about

@ccs/ccstudio 20.3.0
@ccs/ccstudio-debug 20.3.0
@ccs/ccstudio-getting-started 20.3.0
@ccs/ccstudio-guicomposer 20.3.0
@ccs/ccstudio-plugin 20.3.0
@ccs/ccstudio-project 20.3.0
@ccs/ccstudio-support 20.3.0
@ccs/ccstudio-trace-config 20.3.0
@ccs/ccstudio-trace-viewer 20.3.0
@ccs/ccstudio-updater 20.3.0
@theia/ai-anthropic 1.58.4
@theia/ai-chat 1.58.4
@theia/ai-chat-ui 1.58.4
@theia/ai-code-completion 1.58.4
@theia/ai-core 1.58.4
@theia/ai-history 1.58.4
@theia/ai-huggingface 1.58.4
@theia/ai-llamafile 1.58.4
@theia/ai-mcp 1.58.4
@theia/ai-ollama 1.58.4
@theia/ai-openai 1.58.4
@theia/ai-scanoss 1.58.4
@theia/ai-terminal 1.58.4
@theia/ai-workspace-agent 1.58.4
@theia/bulk-edit 1.58.4
@theia/callhierarchy 1.58.4
@theia/collaboration 1.58.4
@theia/console 1.58.4
@theia/core 1.58.4
@theia/debug 1.58.4
@theia/dev-container 1.58.4
@theia/editor 1.58.4
@theia/editor-preview 1.58.4
@theia/electron 1.58.4
@theia/external-terminal 1.58.4
@theia/file-search 1.58.4
@theia/filesystem 1.58.4
@theia/keymaps 1.58.4
@theia/markers 1.58.4
@theia/messages 1.58.4
@theia/metrics 1.58.4
@theia/mini-browser 1.58.4
@theia/monaco 1.58.4
@theia/navigator 1.58.4
@theia/notebook 1.58.4
@theia/outline-view 1.58.4
@theia/output 1.58.4
@theia/plugin-dev 1.58.4
@theia/plugin-ext 1.58.4
@theia/plugin-ext-headless 1.58.4
@theia/plugin-ext-vscode 1.58.4
@theia/preferences 1.58.4
@theia/preview 1.58.4
@theia/process 1.58.4
@theia/property-view 1.58.4
@theia/remote 1.58.4
@theia/scanoss 1.58.4
@theia/scm 1.58.4
@theia/scm-extra 1.58.4
@theia/search-in-workspace 1.58.4
@theia/secondary-window 1.58.4
@theia/task 1.58.4
@theia/terminal 1.58.4
@theia/test 1.58.4
@theia/timeline 1.58.4
@theia/toolbar 1.58.4
@theia/typehierarchy 1.58.4
@theia/userstorage 1.58.4
@theia/variable-resolver 1.58.4
@theia/vsx-registry 1.58.4
@theia/workspace 1.58.4

9 months ago

0 Ki 9 months ago

TI__Guru**** 484151 points

Hello,

Can you provide a small test case? Ideally a simple project with a limited number of source files. Your issue sounds a bit different from EXT_EP_12940.

Thanks

0 Ken Ayre 9 months ago in reply to Ki

Prodigy 120 points

Correct, I had (2) things.... the non-report is separate from EXT_EP_12940; re-install (w/ 20.3.1) allowed for build to complete.

As far as test case- I honestly wouldn't know where to start backing this project out; over 33 files representing 4 months of work across the team.

0 Ki 9 months ago in reply to Ken Ayre

TI__Guru**** 484151 points

Perhaps just the files that generate the build errors? What are the exact errors in the output window?

0 Ken Ayre 9 months ago in reply to Ki

Prodigy 120 points

That is the topic of this ticket.... there are no errors in the output window, nor in the workspace explorer. Only a message that build fail due to errors.

0 Ki 9 months ago in reply to Ken Ayre

TI__Guru**** 484151 points

Can you build from the command-line like I did in the below thread and see if there is more output there?

RE: CODECOMPOSER: CODECOMPOSER: 20.3.0 Hangs on build doesn't display compiler errors.

0 Ken Ayre 9 months ago in reply to Ki

Prodigy 120 points

OK, so the command line (which is completely foreign to me) works correctly. I guess it's in the IDE?

The reported error "read-only variable is not assignable...."

It appears 11 more times than it should, but please don't shoot me- I'm the hardware guy.

0 Ken Ayre 9 months ago in reply to Ken Ayre

Prodigy 120 points

I'd like to add, the highlighting in the Workspace explorer window stopped long before the non-reporting in the output window.

0 Ki 9 months ago in reply to Ken Ayre

TI__Guru**** 484151 points

Ken Ayre said:
OK, so the command line (which is completely foreign to me) works correctly. I guess it's in the IDE?

Thanks. It could be related to EXT_EP_12940 then.

Not sure if you have CCS 20.2.0 on the same machine. If so, can you try it there?

0 Ken Ayre 9 months ago in reply to Ki

Prodigy 120 points

If it is available on-line, I can roll back. This is a new laptop as of 2 weeks ago so 20.3.0 was my starting point.

0 Ki 9 months ago in reply to Ken Ayre

TI__Guru**** 484151 points

Ki said:
Thanks. It could be related to EXT_EP_12940 then.

Thanks to your screenshot, I can see the error message. I then added some code to a example project I have that would generate the same error. I was able to reproduce the error. And I also confirmed there is no issue with CCS 20.2.0.

0 Ken Ayre 9 months ago in reply to Ki

Prodigy 120 points

Yes, the issue resolved in 20.2.0.12, including issues with tagging files and errors in the workspace explorer pane.

Looking forward to the fixed release!

Thank you very much!

Ken \ Sielox

0 Mykhaylo Lodygin 8 months ago in reply to Ki

Intellectual 300 points

hello Ki, could you update on the issue? have same on 20.3.1.5__1.9.1

0 Ken Ayre 8 months ago in reply to Mykhaylo Lodygin

Prodigy 120 points

Hi, I have not updated CCS after rolling back to 20.2.0.12 so I don't know if the issue has been resolved in later releases. I was hoping this thread might have triggered a notification when the issue was confirmed resolved. Until then, I won't bring my department forward.

0 Ki 8 months ago in reply to Ken Ayre

TI__Guru**** 484151 points

The issue will be fixed in the upcoming CCS 20.4.0.

CCS 20.3.1 was a very targeted release, addressing only very specific issues. EXT_EP_12940 is not part of CCS 20.3.1

Code Composer Studio™︎

Code Composer Studio forum

LP-MSPM0G3507: Code composer Studio no longer reporting errors