• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 403 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CCS/PROCESSOR-SDK-AM335X: Output windows SOMETIMES wraps text.

CCSTUDIO: CCS Crash - Again

Christopher Weber
Genius 4995 points

Part Number: CCSTUDIO

This is to Ki... if he sees it.

Still intermittent crashing on CCS 10.1

And my shortcut starts CCS clean EVERY time.

I have no idea WHAT is it failing at.  Or what it is corrupting in my workspace.  But since it's all not documented, and horrible looking XML, I fear what it might do and me not be able to repair it.

  • 0
    TI__Guru**** 482311 points

    Hello,

    What is the full path mentioned in that first error message: "Could not write workspace metadata 'C:/source/Digit...."? I assume a file of some sort. Could you provide that file?

    Thanks

    ki

  • 0 in reply to Ki
    Genius 4995 points

    Ki,

    I have no idea.  The full path is very long, and goes into the workspace folders...  (I naturally redacted it from a world wide forum)

    I guess I should mention, this is on exit.  But I think I mentioned that in the past.

    C:\source\...\projects\.jxbrowser-data\
C:\source\...\projects\.metadata\
C:\source\...\projects\.tempFiles\

    And a whole bunch of subfolders inside them.

    I figured you guys would know what your IDE is writing to.

    It does it every few days.  When it's in the mood... I assume in a bad mood.  I have no idea why, or what it's writing.  But next time I see it, I'll expand the dialog and try to see if there is a file name at the end of that long path.

  • 0 in reply to Ki
    Genius 4995 points

    Ki,

    Here it is again.

  • 0 in reply to Ki
    Genius 4995 points

    Ki,

    And again, 20 minutes later...

  • 0 in reply to Christopher Weber
    TI__Guru**** 482311 points

    Thanks. They always seem to occur in the same directory (though the name of the *.tree file varies). It is still unknown why invalid data is attempted to be written to the workspace folder. That is the million dollar question which I had an answer for. There isn't a whole lot of info out there on what these files are used for. I'll keep digging...

  • 0 in reply to Ki
    Genius 4995 points

    And now they are occurring in a different workspace. On a different PC.

    I have a collection of (non-employer) projects for other purposes, and they are all TIVA devices.  These aren't the Sitara devices I've been using.

    Many times, I load and run the app, debug it, reset it, rebuild, rerun, etc...  When I exit CCS, the error appears again. Same folder location, another "tree" file  (but I didn't check the actual filename - they aren't very intuitive).

    Also CCS 10.1

    It scares me because I've had projects get corrupted by unknown causes, and I end up having to recreate it from scratch.  Having to do that to a large project would be a setback of days.

    It hasn't happened yet, but I fear that it might. I have no idea how the CCS workspace functions, and can't rebuild it from corrupted files if I need to.

  • 0 in reply to Christopher Weber
    TI__Guru**** 482311 points

    the /.metadata/.plugins/org.eclipse.core.resources/.root/*.tree files are some type of eclipse storage metadata for the workspace. It is a bit of a mystery what exactly they are used for but the errors are clearly related to some sort of workspace metadata corruption and not related to any type of project corruption. Why this is happening I do not know. These workspace metadata corruption issues tend to be pretty specific to a user's environment. A common suggestion for Eclipse based environments when this happens is to delete the whole .metadata folder. But you can just try deleting the specific *.tree file instead. I wish I had more useful information to share but unfortunately I am quite unsure exactly what is happening myself.