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 Slow In Launching Target Configuration

Other Parts Discussed in Thread: TMS320C6678

Hi,

I am using a TMS320C6678 eval board with Blackhawk XDS560v2-USB Mezzanine Emulator. Previously I was running CCS V5.1 on a 32-bit Windows XP machine, and launching the target configuration usually take a very short time. However, now that I have ported everything to a 64-bit Windows 7 machine, the time needed to fully launch a target configuration file takes approximately 10minutes. The symptoms that I observed is the progress bar will load smoothly till 99%, and at 99% it will get stucked for about 10minutes before all the cores can be seen on the debug screen. However, the time taken to connect to the cores as well as the time taken to load the program in seems to be normal. Is there any solutions to this or any settings that I might have forgotten to tweak after changing the machine? Will appreciate if someone can help. Thank you!

  • The first time you launch a debug session for a big multicore device like C6678 it can take a few minutes.  This is because CCS has to parse thousands and thousands of registers from some xml files.  However we generate a cache file so that it only happens once.  The fact that everything else is normal makes me think something may be happening to cause the parsing to happen with each launch.  When you launch the debug session and it is stuck what does it say in the progress dialog.  The progress dialog should open up each time you launch the debugger.  If you have minimized it in the past you may need to double click on the little progress bar at the bottom right of your screen to open it.

    If that dialog says it is generating a register database then I would try a couple of things:

    1) delete the launch configuration for your project.  Go to the down arrow beside the bug button and click on "Debug Configurations", you can also go to the Run menu and select the same item.  Then select your debug configuration in the list on the left, it will have the same name as your project.  Then click on the red X at the top to delete it.  CCS will regenerate this the next time you launch.

    2) Shutdown CCS. I would delete the cache files described here: http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#Debugger

    Now start CCS and try launching a debug session.  The first time will be slow.  Once it is launched click on the terminate button in the debug view to kill the debug session.  Then try launching again to see if the speed has improved.

    John