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: Problem View is not displayed even when selected from the menu



Tool/software: Code Composer Studio

I installed the latest 7.1 Code Composer as we are migrating from version 6.0.0 after 3 years of good work with the old version. Time to catch up now that things are slow.

I used an existing project which got updated to the newer format for projects. When I built the project there were errors (no surprise there), but the window pane for Problems and also Advice are not displayed. Going to View->Problems and View->Advice do not show either pane as I had in my original project. I deleted CCS V7.1 since it had errors of some sort and was suspect. I opened the failing project back in v6.0.0 and the Problems view still does not show up. I did a Winmerge on the .metadata directory from a working 6.0.0 workspace and my 7.1 modified workspace. There are massive differences in some files and it is not obvious what might be causing the issue.

It looks like workbench.xmi might be the source of the issue.

Any pointers on how to get Eclipse to display the ProblemsView pane? Also ideas why it is happening?

Thanks.

  • I think I found a work around. It is pretty stupid you have to do this, but it seems to work:

    Go to Window->New Window. It will pop up a completely new set of window panes that includes what you want. Then you just close the old one that has deleted all of your stuff.

    BTW, I discovered that closing things like the editor window and the console makes them go away forever in that original window. Very weird operation.
  • Raymond Mack said:
    I used an existing project which got updated to the newer format for projects.

    It sounds like you opened a CCS 6.0 workspace in CCS 7.1. Is that so?

    Using the same workspace across different versions of CCS is generally not recommended. This is mainly because the underlying Eclipse does not support this very well. The recommendation, for each new release of CCS, is to start up a new workspace and import existing projects into the new workspace. Could you check if opening a new workspace with CCSv7 and importing your project into it opens/preserves all the views?

  • Aarti:

    You are correct that I just opened a CCSv6.0 workspace in the new CCSv7.1

    Thanks. That does, indeed, hold a key to the problem. Perhaps that could go in release notes and/or a getting started document. Let's assume it is an issue only when going from one major version of Code Composer rather than minor versions. It could be a heading in the Getting Started (and I actually read those!) under "Migrating Projects Between Major Versions".

    I have stumbled across another major change between version 6 and version 7: The RTOS has changed significantly for the drivers (packages/ti/drivers) functionality from 2_00 to 2_16. We are going to have to stumble through migrating our internal version of EK_TM4C1294XL.c into the new RTOS driver paradigm. If there is a set of instructions on migration, I haven't found it. There is mention that it changed, but not any suggestions on how to manage the changes.

    I would even go so far as to suggest that the change from 2_00 to 2_15 was really a major version change and should have started with 3_00 instead of 2_15.

    Thanks again for all the superb support that TI gives for its processors.

    Ray