• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1897 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 v5.3 debug problem

Charles Jackel
Expert 1345 points
Other Parts Discussed in Thread: ENERGIA

I am running Code Composer v5.3 with the Delfino F28335 Experimenter's Kit with the XDS100v1 USB Emulator.

After being able to build and debug a project a few times today without issue, I have not been able to get an active green resume arrow

following debug. The debug process finishes, but the resume arrow does not become active.

I suspect corrupted drivers. Is there something to check without re-installing code composer? I already checked the target configuration file and that is okay.

The Experimenter's Kit works on a different PC with the same version of Code Composer.

Any suggestions?

  • 0
    TI__Guru**** 173310 points

    Charles Jackel said:
    I have not been able to get an active green resume arrow following debug. The debug process finishes, but the resume arrow does not become active.

    I am assuming you mean that the program gets correctly loaded to target, but that the green resume button is grayed out, is that correct? Is the code running in that case? Are you able to halt the program and then resume running? Does the code actually function correctly?

    My first suggestion would be to try deleting the debug launch configuration and target cache files are documented in this wiki page.

  • 0 in reply to AartiG
    Expert 1345 points

    AartiG said:
    I am assuming you mean that the program gets correctly loaded to target, but that the green resume button is grayed out, is that correct? Is the code running in that case? Are you able to halt the program and then resume running? Does the code actually function correctly?

    The program takes a long time to correctly load to the target, but it does. The green resume button is grayed out but the code does not seem to be running. The halt button (red button) is also grayed out. The code functioned correctly before this problem started. I had this issue back in February (see my post) with a totally different project. I was able to fix it by removing the project from the workspace and importing it back into the workspace. 

    Since my original post yesterday, I did a clean install of code composer v5.3 and removed garbage files, etc. I placed my project in a new workspace and it debugs correctly with active green and red buttons, but the program seems to be stopped like an invisible breakpoint somewhere in the code. Not sure if this is my code or my experimenter's kit issue. The debugging is still slow compared to a couple of weeks ago. Is it possible to fry the flash memory? I was testing my ADC module and applied 0 to 3 volts to A3 and A2 on the board without buffering the input signal. I did not short anything or apply too much voltage, but I thought this might be the source of the slow debugging process.

  • 0 in reply to Charles Jackel
    Expert 1345 points

    I have a TI example project working okay now. It debugged at normal speed and it works. I am

    able to apply a buffered 0 to +3V signal to A2 and A3 with correct readings.

    I am still interested in the graying out green and red button issue, however.

  • 0 in reply to Charles Jackel
    TI__Guru**** 173310 points

    I'm glad to hear that things are back to working well with normal debug speeds.

    I can't be certain what caused the graying out of the debug buttons earlier, but the deletion of debug launch configuration and cache files may have helped. I realize you didn't have a chance to try that since you had already reinstalled CCS, but if you happen to run into the issue again, please give that a try to see if it helps.

  • 0 in reply to AartiG
    Prodigy 40 points

    I got the exactly the same problem as  met.  I use CCS v 6.1.0.

    Change the workspace location solved my issue.

    [Edit - 29 Mar 2015]  I got this issue when importing a new Energia project which had the same name as an exist project.  An error message displayed. Then I can not debug on source code (but disasembly can).