Part Number: CCSTUDIO
Tool/software: Code Composer Studio
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.
In reply to Fred Assadi:
Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.
Having CCS problems? Check out the CCS Troubleshooting Guide
Looking for CCS Training? Check out the CCS Training Site
Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal
In reply to Ki-Soo Lee:
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 AssadiI 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 AssadiBut 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
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.