• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 369 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 12.5.0.00007 becoming slower/less responsive during debug sessions

citizen
Expert 2830 points

Hi,

I would like to know if this behavior is normal during CCS 12.5.0.00007 debug sessions ? I start the session using a BH XDS560v2 emulator and the initial configuration then loading of the .out file is lightning fast (using 34MHz JTAG clock).

As settle into debugging the current application which requires regular RESTARTs and/or LOADs of recompiled source code, I'm noticing during debug sessions the restart, and reset to the c_int() entry point and main() seem to take longer and longer, with the lower right REMOTE SYSTEM EXPLORER Operation progress bar churning away more and more each time, before getting to the entry point and finding main() to restart the code execution ?!? Just now as I did a recompile and restart the RSE operation progress bar seemed to churn a way for a good 15 - 20 seconds and this goes on and on to the point of having to quit the debug session and restart CCS12, then open another debug session etc. This seems to get back the initial responsiveness, but then gradually I'm back to waiting on the churning progress bar, like its must be doing some stuff in the background ... Also I notice my RTOS ROV doesn't reset to start defaults until all the churning stops and the debugger reaches main(). This also is taking longer and longer with ongoing debug activity, restart, recompile reload, break views etc.

What could be the cause of this ? Is my PC just not up to it ? It might be old by modern standards but it's a 4-core i5 Intel device that was considered very fast back in the days ...

Any suggestions ?

Regards, MM

  • 0
    TI__Guru**** 449991 points

    Hello,

    citizen said:
    operation progress bar seemed to churn a way for a good 15 - 20 seconds and this goes on and on to the point of having to quit the debug session and restart CCS12, then open another debug session etc. This seems to get back the initial responsiveness, but then gradually I'm back to waiting on the churning progress bar, like its must be doing some stuff in the background ...

    I assume you mean the little CCS progress bar in the lower right corner of the CCS IDE. If there are many background operations running, it can certainly slow down CCS in general. One thing that can slow down CCS a lot is the indexer. If you have many projects open in the workspace (especially if they are large projects), the constant scanning of the indexer can greatly impact performance. 

    See slide 32: https://dev.ti.com/tirex/explore/node?node=A__AP3OHQvHbqav9piQQX3FIQ__ccs_devtools__FUz-xrs__LATEST

    You can try turning it off.

    Another suggestion is try cleaning your workspace: https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_troubleshooting.html#clean-the-workspace-or-try-using-a-new-one

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2830 points

    Thanks for the info. I wasn't aware of that.

    I have only one project open in the one workspace that I choose at CCS12.5 start-up. The project has about 30 .c files and another 30 .h files etc.

    It looks like I can right click on the project and rebuild or freshen up the files ... I'll see if that does anything.

    For this not to be an issue with CCS12.5, what would a PC build CPU/RAM/Drive config look like for optimal use with CCS12 ? Just curious ...

    Thanks and Regards, MM

  • +1 in reply to citizen
    TI__Guru**** 449991 points
    citizen said:
    I have only one project open in the one workspace that I choose at CCS12.5 start-up. The project has about 30 .c files and another 30 .h files etc.

    That is not too bad. It really shouldn't be an issue.

    citizen said:
    It looks like I can right click on the project and rebuild or freshen up the files ... I'll see if that does anything.

    That would force the index to run to rebuild the index from scratch. But the indexer running itself is the issue in regards to slow performance. I would try disabling it completely.

    citizen said:
    For this not to be an issue with CCS12.5, what would a PC build CPU/RAM/Drive config look like for optimal use with CCS12 ? Just curious ...

    a 4-core i5 should be fine as long as you have at least 8GB RAM and an SSD (though a HDD should really be fine too as long as you PC is not trying to run a bunch of other things in the background).