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.

CCS/CC1310: Skipped download, terminate red but resume grayed after doing "debug as CCS Session"

Part Number: CC1310
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software: Code Composer Studio

I copied my source files from a local git repo on one computer to another as I've done twice a day for a week or two, with workspaces on the two systems that link over to local git repos. I did a "clean project" and "build project" to inform the second computer's session that the files may have changed and then a "debug as CCS debug session" for the umpteenth time. Almost immediately the red square "terminate" icon appeared but the "resume" arrow did not appear in green and no download/flash to the target had taken place. 

I've now torn files out of the repo and stripped it down to nothing (deleting the project with prejudice[i.e. yes, zap the linked-to files 'cause i've got a copy of them], then reverting to old .cproject, .ccsproject, .project files, removing the .launches and Debug directory,  re-importing the CCS project from the fully scrubed local repo, stopping/restarting CCS every step of the way, all multiple times. I don't seem to be able to find the right size boot to kick CCS with to get it back into a state that will allow me to normally build/download/debug my program.  My active build configuration hasn't changed: still "debug" as it had been. EnergyTrace auto-launch is not enabled.  System is fully patched Ubuntu 18.04   4.15.0-43-generic kernel  system PC has I7-8700K/16GB RAM/Toshiba M.2 SSD. CCS version: 8.1.0.00011 }

Should I really consider expunging CCS from my computer, reinstalling it, reinstalling Simplelink 2.20 and the XDC tools, reloading/building an RTOS example and then re-importing my fully scrubbed repo as the next hail mary pass to overcome this situation? This is a bit of a silly question because unless one of you dedicated souls is at the ready on a Sunday with very fast fingers I'll have tried this while waiting to hear from you ("for next time, or the sake of others",  except I'm H O S E D today with two of the four hours I could afford for this specific piece of work already poured down the drain and the completely tear down/restart will fill in the other hours).

Could there be a simple solution, like deleting magic file xyz/abc/pdq from within the ti install or workspace file tree that would give me relief? 

And  what I'm really eager to know is what, exactly, would cause the download/flash to be skipped and the terminate icon to be enabled but not the resume icon? What does a "debug session" mean without the resume icon enabled? 

  • Hi Pete,

    Before doing any thing drastic, can you provide a screenshot of the entire CCS IDE when you see this issue? Make sure the Debug view is visible. 

    Pete Soper said:
    And  what I'm really eager to know is what, exactly, would cause the download/flash to be skipped and the terminate icon to be enabled but not the resume icon?

    It could be that the build failed but CCS decided to launch a debug session for the project anyway, and Debug context is not properly selected. A screenshot can help me validate this.

    Thanks

    ki

  • Sorry, it's history. Running on 8.3/Simplelink 2.30 now, but if I see it again I'll send a screen shot. (The builds were working perfectly)

    But what about my question? What is the utility of offering to halt a program that hasn't been started and cannot be started? What does this state even mean?
  • Pete Soper said:
    What is the utility of offering to halt a program that hasn't been started and cannot be started? What does this state even mean?

    You would only have the option to suspend/halt if the CPU is detected in running state. Otherwise it should be greyed out.