This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TMS320F28335: Huge slowdown when compiling programs for all developers

Part Number: TMS320F28335

Tool/software: Code Composer Studio

On Tuesday the 17th of April all developers on my team experienced a huge slowdown when compiling a program in CCS.

The compile time went from ~30 seconds for the entire program, to 10-20 minutes for a rebuild of the program. The compilie process seems to compile one file, then hang for ~20-30 seconds, then compile a new file.

This is common for all projects on all computers, both running Windows 7 and Windows 10. We are currently using Version: 6.1.3.00033 of CCS, but we downloaded and tried compiling the projects on CCS8.0.0.00016_win32 with the same problem..

We are behind pretty strict firewall, but I've configured the proxies in Preferences/General/Networks connections  for HTTP, HTTPS to our companies proxies, but that didn't help.

I've tried adding the workspace folder, /ti/ folder where everything from TI is installed and specific folders /ti/ccsv6/utils/bin, /ti/ccsv6/compilier/our_compiler/bin, /ti/ccsv6 to exclusion from our anti virus. if there are any specific folders I have missed, please let me know.

The only workaround we have found that works is to disconnect both from the Internet. Then the programs compiles as they used to.

From a couple of older threads, I've found that CCS tries to connect to the some specific sites during compile.

e2e.ti.com/.../552459

e2e.ti.com/.../559315

Disabling the  TI error parsers is not an option, as having the warning and errors appear in the Problems window is pretty useful (they appear even though Internet is disabled)

Is there another workaround to speed up the compile time?

  • Vegard,

    Based on your description it seems that your team encountered this issue on a specific day last month. Has the issue happened again since then? 

    It would be interesting to know if disabling the TI error parser makes a difference even though it may not be a feasible workaround. If you encounter this issue again (or are seeing it on an intermittent basis) could you please do a test of disabling the error parser the next time you hit the slow-down? Also could you try out the suggestion in this post about disabling updates?

  • Vegard,

    I wanted to follow up and see if you'd had a chance to try out the suggestions in my previous post and provide the requested details. If not, we will close out this thread for now and can always reopen it when you have additional details. Thanks!