• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 1066 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: A bunch of monkeys hammering on a keyboard with bananas could write a better environment than CCS

lemmiwinks
Expert 1060 points

Tool/software: Code Composer Studio

Why does every release of CCS get slower and more buggy than the previous? It's to the point that I spend more time waiting for things to happen than actually writing code. Even though I've turned off "Automatically Update the Index" the C/C++ indexer runs every time I save a file which, of course, causes a huge delay when building the project.

Typical workflow:
Click "Build Project"
Wait 30 seconds while CCS does nothing. Project tree rearranges itself a couple times for some reason.
Eventually the project will start building. Sometimes, for no explicable reason it will rebuild all the libraries too.
Wait several minutes for various things to apparently happen in the background I guess because there's no output to the console.

Want to have a really fun day? Try graphing something. Apparently taking N points of data from a start address and plotting that to a window is too complicated even though every other dev. environment has been doing it for decades. And don't even get me started on the auto-scale behavior...

Sound harsh? It's deserved...

  • 0
    TI__Guru**** 464411 points
    Hello,
    Sorry for all the pains you are experiencing with CCS. Eclipse CDT Indexer issues have been a major issue recently for multiple users and we are currently investigating.

    There are a few tips in the below link that may help a bit... but frankly, it is likely just small band-aids on a gaping wound.
    blogs.itemis.com/.../improving-eclipse-cdt-indexer-performance

    We hope to get a better handle of the issue and address this ASAP.

    ki
  • 0 in reply to Ki
    TI__Guru**** 464411 points
    Could you try completely disabling the indexer? This help us to confirm that your slowdown issue is directly related to the indexer. For more information on how to do it, see:
    e2e.ti.com/.../2361142

    If this does not help at all, then it is unrelated to the indexer. In this case, please open the Progress view ( View -> Other -> General -> Progress) and provide some screenshots of the messages in there during the various delays.

    Thanks
    ki
  • 0 in reply to Ki
    Expert 1060 points
    Disabling the indexer definitely improves things.

    Now about those graphs...

    Seriously though, the work we do often requires visualization of waveforms. The graphing stuff simply doesn't work reliably. Too often the graphs don't update and the auto-scaling usually just doesn't work.
  • 0 in reply to lemmiwinks
    TI__Guru**** 464411 points

    lemmiwinks said:
    Disabling the indexer definitely improves things.

    Thanks for trying it out. 

    Yep, we have issues with the indexer. We are looking though the known issues with the CDT indexer to see if they have already been reported to the Eclipse community and if there is any work to improve.

    If I may ask you a favor, would you mind enabling the indexer again and then following the steps to generate a thread stack dump file as mentioned in the below thread:

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/659011

    This would help us a lot in our analysis.

    lemmiwinks said:
    Seriously though, the work we do often requires visualization of waveforms. The graphing stuff simply doesn't work reliably. Too often the graphs don't update and the auto-scaling usually just doesn't work.

    Unfortunately due to limited resourcing, there are several known issues with the graphs that are still outstanding (especially auto-scaling). If you can provide a bit more details on what the exact issues are, I can try to dig up those issues and prioritize them to get addressed. If you can provide a simple reproducible test case (executable to run and the graph parameters), that would be very helpful

    Thanks

    ki

  • 0
    Guru 18595 points
    Is there any update on this?
    Not giving feedback about the obtained answers and proposals is probably not the best way to improve things.
  • 0 in reply to kazola
    TI__Guru**** 162305 points

    kazola said:
    Is there any update on this?
    Not giving feedback about the obtained answers and proposals is probably not the best way to improve things.

    Ki's last post had a request for more information and a test case so that he could help pursue this.

    "If you can provide a bit more details on what the exact issues are, I can try to dig up those issues and prioritize them to get addressed. If you can provide a simple reproducible test case (executable to run and the graph parameters), that would be very helpful"

  • 0 in reply to JohnS
    TI__Guru**** 162305 points
    I am going to close off this thread. Unfortunately there is nothing more we can do without the requested information. I understand that you are frustrated and need to vent, having tools issues impact your ability to do work is not desirable. If at some point in the future you wish to pursue the graph issues further please feel free to start a new thread and we can pick this up.

    Regards,
    John