• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 1754 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Crash after Terminate Debugging

henning.juerss
Prodigy 40 points

Hello,

i have a problem with Code Composer Studio v5.1.1.00031 runningon a Win7 x64 System:

I´m using an Olimex MSP430 Board (MSP-5438STK) and an MSP430-JTAG-ISO-Adapter from Olimex.

Installation of CCS and JTAG-drivers was fine - no problems.

Build of example-project without errors. When I start "Debug" the project, i get the error-message:

"Error connecting to the target: Could not find device (or device not supported)".

A click on the "retry"-Button and it works - the compiled code is written to the MSP and debugging is possible.

So far, is it possible to work - but when I "Terminate" the Debug-Session, the CCS crashs without any further information.

I think there is a problem between CCS and the JTAG-Adapter, but i don´t know how to fix it.

CCS is new for me, maybe there is a simple checkbox or an option to activate and solve the problem.

Thank you for your help.

  • 0
    TI__Guru**** 481001 points

    Hello,

    Additional logs would help us identify the source of the issue. Please provide the Debug Server Dump Files and Debug Server Log:

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

    Note that the Debug Server Log is not generated by default. You will need to enable it, then reproduce the problem to have a log of the issue.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Hello,

    I´ ve got a message from Olimex support - the problem is the Olimex MSP430-JTAG-ISO driver Version 1.0.4.2.

    With the old "MSP430.dll" of version 1.0.4.1. there is no crash, but thers is still the first error message (1. post) and  i have to click "retry" for programming and debugging. I hope this will be fixed with the next firmware-update (Olimex: April 2012).

    Thank you for help.

  • 0 in reply to henning.juerss
    Prodigy 80 points

    Hi,

    thank you for help. Everything works fine.

    Best regards.

  • 0 in reply to henning.juerss
    Guru 92251 points

    Henning J��r�� said:
    I´ ve got a message from Olimex support - the problem is the Olimex MSP430-JTAG-ISO driver Version 1.0.4.2.

    With the old "MSP430.dll" of version 1.0.4.1. there is no crash, but thers is still the first error message (1. post) and  i have to click "retry" for programming and debugging. I hope this will be fixed with the next firmware-update (Olimex: April 2012).

    Did you receive an updated driver from Olimex support?

    Looking at the olimex website the latest driver available is still Version 1.0.4.2

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Since IAR Kickstart used the Olimex.dll v1.0.4.2 without crashing, I investigated to confirm that the crash with CCS 5.2 was caused by the Olimex.dll. The failure sequence is:

    1) When CCS calls MSP430_SET_SYSTEM_NOTIFY_CALLBACK during starting the debug session, the Olimex.dll creates a thread.

    2) When CCS calls MSP430_EEM_Init during starting the debug session, the Olimex.dll creates another thread.

    3) After CCS calls MSP430_Close when terminating the debugging session, the threads created by the Olimex.dll are still running.

    4) CCS calls FreeLibrary to un-load the Olimex.dll from memory.

    5) After the Olimex.dll has been unloaded, the threads created by the Olimex.dll are still running. The thread which was created by the call to  MSP430_SET_SYSTEM_NOTIFY_CALLBACK then crashes CCS, with an Access violation in what appears to reaching the maximum stack size after infinite recursion.

    i.e. the CCS crash is caused by a thread created by the Olimex.dll still running after the Olimex.dll has been unloaded, presumably the crash happens when the thread accesses memory that has been re-allocated for something else. I will pass this information to Olimex to try and get them to fix it.