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.

DebugLib.dll causing CCS crashing

Other Parts Discussed in Thread: CCSTUDIO

Hi, I've recently acquired a Stellaris LaunchPad for my uni group project. I couldn't enjoy it though because loading the microcontroller with sample programs causes CSS to crash. It happened on three separate machines, all running Windows 7 64 bit. Crash report suggests it's the DebugLib.dll that's causing it to crash.

I'm not sure if this problem was raised here before, but my searches through the forum for that library related problems did not provide any useful information.

I'm quite new to this so please tell me what other info should I provide to help you help me resolve that issue :)

  • Hi Kacper,

    is this reproducable?  Ie is there a program or window or situation that seems to trigger this?  Do you see this with every project/workspace?  Have you tried a fresh workspace?  What exactly do you experience and what steps do you take?  Ie what exactly do you term "crash" and at what point?

    Could you please send any error files or dump files generated?

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

    Best Regards,
    Lisa

  • Hi Lisa,

    yes, I just did a clean installation of CCS and done exactly the same what caused the IDE to crash last time. Basically what I did was:

    1. Follow the instructions for installation from here http://processors.wiki.ti.com/index.php/Stellaris_LM4F120_LaunchPad_Blink_the_RGB

    2. Connect the Stellaris LM4F120 with the USB cable, to the debug port on the micro, set the two way switch to "DEBUG". Now the micro is running the last program it was programmed with, for me it's some LED blinking program. Start the CSS, go to Project Explorer

    3. Try some example programs - I've rebuilt "project0" then pressed "debug Project0" (the bug icon on the toolbar)

    4. This goes smoothly, although the microcontroller stops the last program it was running. I have to disconnect and reconnect it to the PC, ONLY THEN it starts running Project0. The "Console" window shows me "CORTEX_M4_0: Error: Timed out while waiting for target powerup/polling a hardware resource." of course.

    5. Close the debug, go back to Project Explorer

    6. This time I try "blinky" and I follow the exact same procedure -> rebuild -> debug "blinky"

    7. I get a warning "You are required to terminate existing debug session to perform the current action. Do you want to continue." Press Yes.

    8. CCS goes to debug but I get a message "ccstudio,exe has stopped working" and I can only close the program.

    Here's Windows Error log for that http://pastebin.com/iAuShbT0

    edit: I've read the troubleshooting and found the diagnostic tool, how/where should I send it? which files do you require?

  • Hi Kacper,

    thanks for the logs, we are going to have a look and I will post feedback as soon as I have some.

    In the mean time there are a few comments in your steps that also seem to indicate note quite the typical debug proceedure.  

    4. This goes smoothly, although the microcontroller stops the last program it was running.

    What do you mean here?  What do you see/experience?

    I have to disconnect and reconnect it to the PC, ONLY THEN it starts running Project0. The "Console" window shows me "CORTEX_M4_0: Error: Timed out while waiting for target powerup/polling a hardware resource." of course.

    Does this mean you are unplugging and plugging the the target when in a  debug session? This is not at all recommened.  There are other ways to reset or restart or reload a target right from within a debug session.

    5. Close the debug, go back to Project Explorer

    How do you close the debug?  The message below indicates the debug session may not have be exited in a proper/normal way for whatever reason.

     "You are required to terminate existing debug session to perform the current action. Do you want to continue." Press Yes.

    Best Regards,
    Lisa

  • Hi Kacper,

    please send the debug servers logs (or any .dmp and errors logs) either attached here or to us offline.  You can do this via a friend/conversation request.   You will notice my user id is a link.

    Best Regards,
    Lisa

  • "4. This goes smoothly, although the microcontroller stops the last program it was running.

    What do you mean here?  What do you see/experience?"

    For example - if it was running project0 before starting debug the LED would stop at the last colour it was showing, and stay like that until I flip a switch. (the Debug/Device switch on the board)

    "Does this mean you are unplugging and plugging the the target when in a  debug session? This is not at all recommened.  There are other ways to reset or restart or reload a target right from within a debug session."

    Can you enlighten me? Reset switch doesn't work in this situation, before microcontroller starts the program I currently wish to debug I have to flip Debug/Device switch, or dis and re-connect the USB cable.

    "5. Close the debug, go back to Project Explorer

    How do you close the debug?  The message below indicates the debug session may not have be exited in a proper/normal way for whatever reason."

    In the right, upper corner of the screen, just below the Minimize/Maximize/Close controls of the window, there is a CCS Debug button while debuging, I right-click on it and select Close from that menu. I assumed that when IDE prompts me later to close the debug session it gets closed properly anyway.

    Here's the "Eclipse log" http://pastebin.com/vJfAqVcK

    And attached is a Debug Server Dump file.


    DebugServer20121207154237.zip
  • Hi Kacper,

    a couple things.  Do you know/can you try to see if you can generate an ds logs (debug server)?  For now what we see is that it appears a thread was started by debuglib.dll to do something, however the dll was unloaded before the thread started.

    A ds log would possibly tell us more. 

    Best Regards,
    Lisa

  • Ok, firstly I found out my "method" was at fault - I have missed the tool set that shows up when in debug view - Resume, Suspend, Terminate and all the rest, that's why I was switching the microcontroller on and off to see program running. So the problem was all because of my lack of experience.

    Secondly - I have recreated the "crash" and recorded the log using debug server as you asked, so if you could still analyse it, and perhaps stop it from crashing when someone as inexperienced as I tries to do the same. 

    Sorry to cause you trouble, I obviously should have studied how CCS work and the microcontroller more before attempting to use it.

    log.rar
  • Hi Kacper,

    very glad to hear you managed to find out what the issue was.   Thanks for the update and log.

    All the best with development.

    Best Regards,
    Lisa