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 Cloud 'Build' runs very slow just of late

Greetings.  I have had such good luck with CCS Cloud, being able to develop from two locations, via the internet.

But as of a couple days ago, when I do a 'Build', it takes up to 15 minutes as it slowly prints out all the comments and warning messages.

It happens from home and from work, so it appears to be downstream of my pc hardware.  

But just in case, I checked my TI Cloud Agent anyway and it seems fine.

I really miss it, hope someone can help troubleshoot.

Best Regards,

-John F

  • Hi John,
    Yes I've noticed this too. We are looking into this.

    Thanks
    ki
  • If it is any clue, it appears that during a Build, a new remark is printed out every six seconds, synchronized to the 'green slider' busy indicator you see if you hit 'Debug'. Since I have a lot of remarks, it takes a long time. Also, I cannot cannot cancel or exit during this long period. The Build does finally finish, but is many times slower than before.

    Hope this helps ki!
    -John F
  • My TI CCS Cloud for MSP430 using the launchpad continues to be very slow, porting out remarks at a 6 second interval, causing an uninterruptible wait of 5-10 minutes for each new build or debug.  Please let me know if this is the new normal, possibly a way of weaning users off this free service.  Otherwise, if it is fixable, please let me know ASAP.

    Some of the remarks are helpful tips, but I do not want to implement the programming suggestions just yet, and so the 6-second remark interval is long for my programs.

    One of the remarks that repeats many times, taking up several minutes of the build time, is apparently related to my use of my inlcude math.h functions.

    "@ccs/tools/compiler/msp430_15.12.3.LTS/include/_defs.h", line 203 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive 

    Again,

    Please let me know if this gets fixed.

    Best Regards,

    -John F

  • Hi John,
    A fix for this issue (tracking ID: TICLD-1714) has been implemented and the should be applied to the Cloud tools sometime this week (tentativeliy Wednesday for now)

    Thanks
    ki
  • Yes ki, it is fixed, seems like within the last hour!

    Thank you very much, I love it!

    -John F