CCS V6 Terminate Debug hangs

Hi Barry,

Try running the same project from a new workspace.

Regards,

Gautam

I created a new workspace, imported a copy of the original project, cleaned and built the project.

Launched the debugger, all ran fine.

Terminated the debug session and it froze again - so no difference in operation with new workspace.

Barry Andrews said:

Terminated the debug session and it froze again - so no difference in operation with new workspace.

Seems strange, Barry! Generally this works... but there are some strange cases. Do you've any other CCS version (v5.5) to test similar behavior? Also, here's a similar post:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/291218.aspx

Regards,

Gautam

Hi Barry,

the way I see it there are two options.   The first is to clear ccs and install the latest as a full fresh installation.

The second would be to send us any logs that might help us diagnose things and suggest any possible alternatives.

The update log would help along with any .dmp files or hs_err logs generated on the crash.  This wiki will help you find those.

http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

Best Regards,
Lisa

I did a complete uninstall of existing CCS application.

Downloaded the latest CCS V6 install from TI (took ages as web site wasn't responding properly to login, kept timing out).

Installed the latest version which then asked for some updates, installed these as well

Ran the new installation with my existing workspace.

Same problem, clicking the terminate button from debug wound up with the spinning circle of death.

Ending the task with task manager results in a ccstudio.exe still running as background process (So full PC restart is required to run again).

Screen capture of hang below, I tried pause, resume, reset from debugger, all worked - just the terminate which hangs.

Log files attached

1777.ti_trace_log_8132014_3560.zip

0410.com.ti.logs.zip

Some further information for you.

The hangup seems to be related to the Stellaris FTDI driver.

I uninstalled my ICDI com port (including drivers).

Downloaded the latest drivers from the TI website http://www.ti.com/tool/lm_ftdi_driver

Installed these drivers and still get the hangup of the application.

However if I then pull the USB cable from the BD-ICDI-C PCB the program correctly returns to the Edit mode.

When I look at the USB device through Device Manager it says

Driver provider: FTDI

Driver Date: 22/10/2009

Driver Version 2.6.0.0

Details tab says

Stellaris ICDI COM Port

Some further information to hopefully help identify the issue.

I have another PCB with FTDI chip FT230XS plugged into my PC, this has FTDI driver version 2.0.10.0 which is latest for 64bit windows.  If this device is plugged into the PC and I have a terminal program using it when I launch the debugger onto the development board CCS indicates that it cannot connect to the target device.  If it is just plugged into the PC but not in use the Debug interface will connect to the target.

Simply stopping the use of the other FTDI port (close terminal proram but leave USB plugged in) allows CCS to connect to the target and flash the firmware.

At any stage after the connection is established I can reconnect my terminal application to the other FTDI port and all runs fine.

The hangup of CCS coming out of Debug back to edit mode occurs regardless of if the other FTDI USB device is plugged into my PC or not.

Unplugging the BD-ICDI-C board reliably restores the CCS to edit mode and stops the hangup.

Definite issue with CCS connecting to the BD-ICDI-C when any other FTDI USB port is in use on the same PC.

Will come up with unable to find target.

My PC has 4 port USB to serial device which has FTDI driver as well as single USB to serial FTDI device (FT230XS).

If I use any of these and then try to connect to the debug target CCS says it cannot find the target.

As long as none are in use I can connect.

I also tried unplugging all other FTDI devices completely, I can connect to the target device, load and run the target device but still hangs when trying to terminate the debug session. The terminate of debug session was previously working till I changed to CCS 6.01.

Hi Barry,

unfortunately I am not sure what can be done here.  I have seen with some devices going through a hub etc causes the device not to work.  

Regarding the crash, I am going to see if I can forward this to the appropriate people here.

Best regards,

Lisa

Barry,

Could you please attach a debugserver log (explanation is here: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS).  You previously attached workspace and trace logs, but neither of those help with debugging this specific issue.

Second, could you see if there's a hang_*.dmp file generated?  Click on Help->CCS Support->Debug Server Dump File->View.  If so, please attach that.

In the meantime, you can work around this by not explicitly terminating, but just clicking on "CCS Edit" in the upper right corner.  Once you make changes and re-build, you should be prompted to reload the newly build .out file.  You can select yes and then click on "CCS Debug" in the upper right corner to switch back.

Darian

Hang Files as requested

7725.Hang files.zip

Enabling the debug server caused it to hang before code was even written to my module, closing the application then subsequently failed.

3580.Debug Server Log File.zip

I am going to have to reboot the PC and attempt again.

Please note that I am direct onto on of the PC USB ports, not via any sort of external hub.

All the other com ports are also direct onto their own motherboard USB ports.

Clean reboot of PC - Enabled the logging loaded the file to the device, ran in debug, terminated Debug and program hung up, removed the ICDI USB cable, application restored, shut down application.

Log File

7713.Debug server log 2.zip

Hang File

7367.hang_27_4c2a892f-9c62-4ee7-81cc-745031a4c110.zip

Just a note regards suggested work around.

This doesn't stop the hangup occuring, simply delays it until I either attempt a new debug session or try to close the application.

Only reliable workaround I have is to let it hang and then pull the USB cable and then plug the USB cable back in.

I still get the hangup but the application isn't frozen and I can close it without having to restart my PC.

Barry,

I was suggesting the workaround as a way of continuing to compile/reload code without encountering the hang.  I realize it just delays it...

I've opened SDSCM00050744 to track this and notified the responsible engineer.

Darian

Any update on how this is progressing?

Zackary Long said:

I am having this exact same issue with the cc3200-Launchpad and CCSv6. The Code Composer Studio hangs forever until i disconnect the USB from the board and plug back in. Is there a solution for this ?

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/446680#pi316318=2 suggests keeping a terminal program connected to the FTDI emulator UART connection prevents CCS hanging.

For me the only solution was a clean install of CCSV6.

It may well be that drivers were the issue but I did try installing drivers multiple times with no change in my issues.

However a complete new download and install of CCSV6 did the trick.

If anyone is experiencing the hang when terminating an ICDI session, I would suggest updating TI Emulators to the latest release (6.0.14.5).  Several hang on disconnect issues have been addressed since the time of the original posting of this thread.  You can update TI Emulators from the Help->Check for Updates menu.  To see which version of TI Emulators is installed select Help->About Code Composer Studio->Installation Details.  If you have a version less than 6.0.14.5 and Check for Updates shows that nothing needs to be updated, you can download the standalone installer here: http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package. If you are using the standalone installer, point the install location to your ccsv5/ccsv6 directory.

Let me know if this does not fix the issue.

Thanks,

Mark

Hi all,

I had a similar type of problem, only mine started happening after I upgraded from version 6.0.1.00040 to version 6.1.1.00022. On my CCS, launching the debugger would work as usual up until it was about to un-gray the Run, Stop, Pause, etc. buttons in the Debugging Perspective, but it never would. The status of the debugger would be locked at 100% of the way of launching the debugger. I waited as much as 30 minutes one day and it was still sitting at 100% with all grayed out buttons. 

Other people's suggestion of making a new workspace and importing the project into that one worked wonders for me. Several of my other projects had this same debugger locking up issue, but some didn't. This makes me wonder if it has something to do with the version of Code Composer the project was originally created on. 

This is yet another troubleshooting step for me with CCS. I always remember to try things like this when solving weird Code Composer/Debugger problems: Restarting the workspace, Restarting your computer, making sure Java is up to date on your computer, doing a Clean instead of Build, and now also re-creating the workspace and importing the project. Learning these have saved me a lot of troubleshooting time.

Best of luck to everyone with this problem,

Hello Darian, 

I did try the move to edit and rebuild. Didn't work. Rebuild didn't cause the session to terminate and trying to go back to debugging wouldn't work either by switching tabs or by trying to start a session. The old debug session would take a long time to die..then the new session would not start i.e no stop or run icon

I now seem to get around it most times by terminating then powering off and detaching the EDK after each debug session. I believe that this disables (automatically removes) the FTDI drivers and that this might be where the problem lies? Still have problems at times but they are less likely than before.

I'm going to be too busy for the rest of the week, but I will try to get a log file over the weekend or next week.