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.

Code Composer v5.3 bugs report

Other Parts Discussed in Thread: CCSTUDIO

I have been pesting against CCS since day one. Here is why.
These comments all apply two v5.3 under Win7.  v5.2 was behaving quite the same though.
Everytime a debug session is mentioned, it is on a F28335 DSP.

Hope this report will help you improve your tool...

--- PROCESS

ccstudio.exe often stays in memory after exiting the application. It happens at least 1 time out of 4. I noticed is it is NOT related to the way CCS closes (crash or clean exit).

There must be a lot of memory leaks in there too. From time to time (say, at least once a day), I can spot ccstudio.exe at more than 1GB of memory usage. I think it happens only if I have started a few debug sessions that display graphs. It may give you a clue...
When it happens, a clean exit never leads to the proper killing of the process. I need to manually kill it. Please notice that I have two collegues experiencing that problem with the same version under Win7 also.


--- STARTUP

No matter if CCS closes cleanly or not, there is popup saying that it did not close properly.


-- HANG
Every now and then, when a debug session is underway, CCS simply hangs. We have been experiencing that since day 1 on CCS 5.2 and 5.3 .
Yesterday, using Win7 ressource monitor "analyze wait chain" tool revealed two threads waiting for Network I/O operation completion. I was not connected to any network. Half the time, I am connected to a network but do experience hangs. I did not check the wait chain in that situation. I will, as soon as I can. Most probably the next time I use CCS, unfortunately...


--- GRAPH TOOL

The graph tool is very useful. That is, when it works.

Sometimes, from one debug session to another, the menu entrie in "Tool-Graph" ar all greyed out. Usually, stopping the debug session and starting it again brings back the entries. It happened twice over 2 months where for about 2 days, entries where grayed out exactly one time out of two debug sessions. Then is started working "well" again.
Restarting code composer does not appear to help in reducing the occurence of that problem.

Also, I have now reached a point with one setup where I can't graph more than one Single Time curve (did not try other graphs) . The window to select graph properties blinks with no result on the first OK button click. The second click closes the window but does not bring a new graph. Restarting CCS AND my computer did not help. Moreover, the graph window sometimes duplicate 5 times some of its toolbar icons. Clicking on it hangs CCS (waiting for network I/o, see above). I may get you a snapshot if you want.


Enjoy...

  • Looks like serious bugs to me...

    TI team, do you need any more details to works on these?  Any comments?

    If I am doing something wrong, please help me out!

  • Hey Fred, another user here. I have been using CCS on two PCs: WinXP and Win7(64-bit) for over a year now, about every other day, keeping up with updates. I have seen it crash a handful of times, but pretty uncommon for me. The graphing issue however has been a thorn in my side for the past year. I really wish this one could be resolved. I think it was supposed to be addressed in 5.2.1, and then 5.3 but I still see it. There is a work-around for it however, which is only slightly annoying. Once you reach a state when you can no longer open up graphs, start a new workspace (type in a new folder name when you first start CCS). You will have to re-load your project, create a target configuration and enter all your watch variables again. Takes about 20 minutes for me. I have had to do this about 7 times in the past year. So, a fresh project will last me about 6-8 weeks before graphing issues pop up again.

  • Thanks Ken!  I appreciate your tip on graphs.  I'll give it a try; that's far less worse than reinstalling CCS!