• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3167 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.

CCS/CCSTUDIO: No consoles to display at this time

Fred Assadi
Intellectual 330 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hi everyone,

I'm using CCS 6.1.3 build to run a C/C++ project on a TIVA MCU. Yesterday for some unknown reason my display console stopped working. I now get a message when trying to open a console (from View::console menu) that appears for less than a second that states "No consoles to display at this time". At the beginning of the project run time, I can see that the console screen appears several times for about 100 mSec each but with no text on it and then it closes again. I can still run, and put break points on the project, but don't see anything on the console anymore.

Note that this appears to be a project based problem and not a CCS wide problem because when I run another project with the same CCS the console works normally.

Below is the screen shot of the failing console:

Following old advice from other Eclipse users I've tried to solve this problem by deleting my .metadata directory or changing the project's "Debug Configurations:Common" setting to allocate a console, or try to create a new console. Nothing has worked so far.

Any help is appreciated.

Fred

  • 0
    Intellectual 330 points
    I think that I might have found a solution for this: If you delete the work space (not the repository location), and recreate a new work space then import the source code form the repository location, the console seems to come back.
    Wish I knew what I did to cause this, or how to fix it. But at least there's a way to recover from it.
    Hope that this helps others,
    Fred
  • 0 in reply to Fred Assadi
    TI__Guru**** 420630 points
    Hi Fred,
    Thanks for the update. You mentioned you tried deleting the .metadata directory in your workspace folder, but that failed to help. Deleting the metadata location should have a similar effect as deleting the workspace. Did you also try importing the code from the repo location when you did that but it failed to resolve the problem?

    thanks
    ki
  • 0 in reply to Ki
    Intellectual 330 points

    Hi Ki,

    I quit and restarted the CCS app after the deleting the metadata directory. But I don't think that I re-imported the project files since they were already there.

    So that could be the difference in that in a new workspace one has to re-import the project.

    But if you have to re-import the project, you might as well just delete the original workspace and start clean. Is there any reason to keep the old workspace?

    Fred

  • 0 in reply to Fred Assadi
    TI__Guru**** 420630 points

    Fred Assadi said:
    I quit and restarted the CCS app after the deleting the metadata directory. But I don't think that I re-imported the project files since they were already there.

    The project folders may be physically there in the workspace folder, but the association to the workspace would be lost since that information is stored in the .metadata folder. Hence you would need to reimport the projects to create the association again.

    Fred Assadi said:
    But if you have to re-import the project, you might as well just delete the original workspace and start clean. Is there any reason to keep the old workspace?

    Only if you have project folders inside the workspace folder. That way you don't lose those projects if you delete the whole workspace folder or have to copy them somewhere else first before deleting it.

    Thanks for the feedback

    ki