I am debugging sample code on the Concerto M3 (nothing loaded on the C28). Stepping through the debugger is painfully slow. For sample programs enet_lwip_m3 and enet_uip_m3, it takes between four and 24 seconds to step from one line to the next. This happens from the very first lines in main() at the start of the debug session. I have eliminated most of the windows in the development environment, leaving only Project Explorer, two source files in the editor, one Console, the Debug window, and the Target Configurations window. enet_uip_m3 comes with a RAM configuration option, but that helps very little -- it still takes close to four seconds to move a step.
Can anyone tell me how I can speed up the debugger?
I could live with four seconds, but the time grows to 10 or even 20 seconds per step.
I am using a recent version of controlSUITE and CCS version 5.1.0.09000. I am using the controlCARD TMDXCNCDH52C1 with the XDS100v2 emulator. The host is a 64 bit Windows 7 computer with a 2.8 GHz Intel Xeon CPU.
Although the xds100v2 emulator is inherently slower than xds510 or xds560 class emulators, I am surprised it is in the range of 10-20 seconds per step. I have run these examples on my Concerto controlcard and single stepping doesn't take more than a second.
It seems like you have already tried some things (like closing out most of the debug views) to improve performance, but this wiki page might also be additionally helpful:http://processors.wiki.ti.com/index.php/XDS100#Q:_How_to_maximize_performance_of_XDS100_under_CCS.3F
Some other general CCS troubleshooting tips to try are to clean out the workspace and delete debug launches and target cache files. Please see the "General IDE" and "Debugger" sections of this page: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS
If possible, it might also be worth trying the same controlcard/emulator on another PC to see if the behavior is different.
If a post answers your question please mark it with the "Verify Answer" button
Search the wikis for common questions: CGT, BIOS, CCSv3, CCSv4Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
My problem turned out to be with a USB hub I was using. As soon as I got rid of the hub, the steps began taking on the order of one second.
Thanks for the update and glad you were able to isolate the cause of the slowdown.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.