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.

Why is CCSv4.2 GUI so slow?

Hi,

New to CCSv4.2. If I click on a file in the C Projects window, it takes 20 seconds to open.

If I click on an error in the Problems window, it takes 5 seconds to go to the error in the source file. 

Doing just about anything in the GUI, like scrolling in a window or highlighting text, has a few seconds of delay.

It wasn't like this before. Any ideas about what is causing this?

Thanks,

Steve

  • Hi Steve,

    steve gallagher said:
    It wasn't like this before. Any ideas about what is causing this?

    I assume your mean that it used to behave faster and now it appears to behave more sluggishly. There could be several factors. Having many projects open in the workspace, or a few very large projects, can cause CCS to slow down as the C/C++ indexer begins to consume more system resources. Also sometimes the cached files in the workspace folder can get corrupted over time and starting with a clean new workspace folder can help.During debugging, having many various debugging views open can impact performance as CCS need to do many reads to the target and if you have a slow emulator like an XDS100, it can cause CCS to behave sluggishly.

    ki

  • So I killed CCS and restarted and it got rid of the problem.

    I'd still like to know what caused it or if anyone else has seen this.

    I'll probably go back to CCS3.3 since my schedule won't allow for the learning curve required for 4.2.

    Thanks,

    Steve

  • steve gallagher said:
    I'll probably go back to CCS3.3 since my schedule won't allow for the learning curve required for 4.2.

    Ok. Next time you want to try to move on from 3.3, I'd go straight to v5.1. One of the goals of v5 was to make it a little bit more easier to use than v4.

    Thanks

    ki

  • >>  ... if you have a slow emulator like an XDS100, it can cause CCS to behave sluggishly.

    I didn't even have the eval board powered up, so I hope it wasn't that.

    I got the xds100 with the eval board, but I have an xds510 usb that I was using with the F2812. The connector on the eval board is keyed to accept the xds510. Will it work with the C6748 eval board?

    Thanks,

    Steve


  • steve gallagher said:
    I didn't even have the eval board powered up, so I hope it wasn't that.

    If you were not even in a debug session, then your emulator would not be a bottleneck. Emulator performance would only impact performance related to host<->target communication.

    steve gallagher said:
    I got the xds100 with the eval board, but I have an xds510 usb that I was using with the F2812. The connector on the eval board is keyed to accept the xds510. Will it work with the C6748 eval board?

    It will work. The only thing to keep in mind is that if you are using the free bundled license, it will not work with an external XDS510 USB. You will need a full license (or the time based eval license). The free bundled license is only good for XDS100 and integrated on-board emulation.

    Thanks

    ki