• State
  • Locked Locked
  • Replies 17 replies
  • Subscribers 53 subscribers
  • Views 2169 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CC430F5147: Building the SW through the IDE is sometimes very slow

Wouter Cappelle
Intellectual 315 points
Part Number: CC430F5147

Tool/software: Code Composer Studio

I've set up a multi-configuration project where I build from 1 source tree multiple targets. The problem however is that the builds are incredible slow from time to time on all of the configurations.

When I press the build icon, I get the popup saying "Building project...", and the gmake command it issued. Then the UI freezes for a long timeout, and occasionally de-freezes, shows one line of console output, and freezes again for a timeout, and then another compilation of 1 file, and so on untill the build finishes after like 20-30 minutes (normal time is like 30 seconds). Doing the build on the commandline (even when the UI is frozen) tells me the build has already succeeded ages ago. Somehow eclipse is freezing in processing the build output, but I cannot find back where.

Unfortunately, this problem is like 90% of the time there. It can be there at startup of CCS, and once it's there, I can try to restart CCS, and sometimes it gives the normal build times.

I never have problems when I build my project headless in eclipse.

I'm using Linux Ubuntu 16.04LTS with CCS version 7.0.0.00042 - Eclipse CDT: 9.0.1.201607151550

My build has been extended with extra makefiles for pre-build targets & post build images, but these are not the problem (already tried disabling them, without success)

  • 0
    TI__Guru**** 173310 points

    There have been some reports of slowdowns attributed to the Eclipse indexer in CCS. Please take a look at this post. 

    Try disabling the indexer to see if that improves the build time. If it does, it might be a good idea to try CCS 8.1 since it contains a fix for at least one bug that was identified as contributing to the slowdown. All of the details are in the thread linked above.

    Let us know how that goes.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Since I haven’t heard back from you, I’m assuming you were able to resolve or move past this issue. If not, please feel free to post a reply with an update below. Thanks!
  • 0 in reply to AartiG
    Intellectual 315 points

    I tried to disable the indexer in the past, and that didn't resolve my issues. I didn't yet do the migration to CCS 8.1, but will try to do so in a short term. I will come back to you if it solves the issue

  • 0 in reply to AartiG
    Intellectual 315 points

    I retried with a fresh installation of CCS v8.1, and similar issue is being seen. Not sure it could be important, but I've installed the previous compilers I'm using with CCSv7 as well:

    0 ✓ 15:55:34-wouter@TLV-THC-WC:/opt/ti/ccsv8$ ll ccsv8/tools/compiler/
total 36
drwxrwxr-x 9 wouter wouter 4096 jul  3 15:56 ./
drwxrwxr-x 4 wouter wouter 4096 jul  3 15:51 ../
drwxrwxr-x 3 wouter wouter 4096 jul  3 15:53 dmed/
drwxr-xr-x 9 wouter wouter 4096 mei  6 14:17 msp430-gcc-7.3.1.24_linux64/
drwxrwxr-x 6 wouter wouter 4096 apr 23 16:21 ti-cgt-msp430_16.9.0.LTS/
drwxrwxr-x 6 wouter wouter 4096 jul  3 15:51 ti-cgt-msp430_18.1.2.LTS/
drwxr-xr-x 6 wouter wouter 4096 jul 14  2016 ti-cgt-msp430_4.4.5/
drwxrwxr-x 6 wouter wouter 4096 nov 15  2016 ti-cgt-msp430_4.4.7/
drwxrwxr-x 6 wouter wouter 4096 dec 20  2016 ti-cgt-msp430_4.4.8/

    I'm using ti-cgt-msp430_16.9.0.LTS compiler for my builds (but again, the builds are not the problem, it seems still the UI).

  • 0 in reply to Wouter Cappelle
    TI__Guru**** 159725 points

    If the slow down is not happening in the headless build but is in the UI it really smells like the indexer.    However what you described would indicate that is not happening.  You mentioned that it will build a file, pause, build another file, pause...  That likely is not the indexer then.  When we do a build we spawn another process and call make. The index updating would happen before the call to make and not in-between individual files being built.  i.e. it is not like the UI is building each file individually, instead it is generating a makefile and calling make.

    One thing to check would be the parallel build settings.  Maybe something is going on there as it seems like make itself is getting stuck.

    Parallel build should be on by default.  You could try disabling it.  The option to disable it is here.  You can uncheck the box "enable parallel build"

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 315 points

    Hi John, 

    Thanks for your input.I will try this right away after my holidays. I'll keep you posted

  • 0 in reply to Wouter Cappelle
    TI__Guru**** 159725 points
    IF this does not work feel free to reject the suggested answer and we can keep looking at it.
  • 0 in reply to JohnS
    Intellectual 315 points
    I've tried it with disabling the parallel jobs, but nothing changed. Also, if I execute the gmake command manually on a console (/opt/ti/ccsv7/utils/bin/gmake -k -j 8 all -O), it always builds fast. It seems that it has nothing to do with the Makefiles, but with the editor. Also the build in the editor has been done like a normal build time (I can see that through the object files in the build folder). It's just the UI that takes ages to process/show the console output.

    I also have checked already the providers for "Preprocessor include Paths, Macros etc.", but there is no output parser active for the console output. This should mean that eclipse should not parse the output, and cannot block on that part.
  • 0 in reply to Wouter Cappelle
    TI__Guru**** 173310 points

    Wouter,

    This may be a shot in the dark, but could you do a test of disabling the RSE UI as per this post to see if that makes any difference at all?

  • 0 in reply to AartiG
    Intellectual 315 points
    I've checked the option, but it seems that the RSE UI was already disabled
  • 0 in reply to Wouter Cappelle
    TI__Guru**** 173310 points
    One more thing to try - could you try disconnecting your PC from the internet before initiating the build and see if that changes the build time?
    Sorry about having you test out various suggestions, but we have not seen this issue locally so it is hard to nail down the root cause.
  • 0 in reply to AartiG
    Intellectual 315 points

    No problem, i'm already happy someone it trying to help me on this :-). I've tried with disconnecting myself from the network to build, but that didn't change the behavior.

    I could also create you a reproduction package, with code tree, but I don't know how this works with NDA's with our company.

  • 0 in reply to Wouter Cappelle
    TI__Guru**** 173310 points
    If you are able to share a project that would be great. We can check if the behavior is reproducible at our end.
    If you hover over my ID in this page, you should be able to start a private conversation with me and attach the project zip file there.
  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Wouter,

    Do you happen to have TrendMicro anti-virus running on your machine? If so, could you check using the Task Manager if any of its processes are running during the slow CCS builds?
  • 0 in reply to AartiG
    Intellectual 315 points

    I'm running linux (Ubuntu 16.04) as OS, without any anti-virus tools

  • 0 in reply to Wouter Cappelle
    TI__Guru**** 173310 points

    Could you try the steps mentioned in this forum post and let us know if that makes any difference at all?

    Also just wanted to double-check if you are still using CCS 8.1 and not 7.0.0 that you originally started with.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Hi Wouter,

    Just wanted to check if you had a chance to try out the suggestion in my previous post (replacing the cache file attached to the referenced forum post) and/or if there was any new update.