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.

Workspace crash?

Guru 15580 points


I appear to have had a workspace or project crash while using ccsv4.2.0.10012. Each time I open ccs in my desired workspace, I get the following error window:

Then if I click on my specific  project, I get the following:

Is the project file corrupt? Is the workspace file corrupt? Can I reconstruct them without starting over?

Thx

MikeH

 

 

  • MikeH,

    Please check the post below:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/63650.aspx

    I recall having this issue a while ago and did the exact same procedure listed there to find the project that was causing this. Although an inconvenience, rebuilding the project fixed the whole thing.

    Hope this helps,

    Rafael

  • Rafael,

    I tried to rebuild the offending project but am getting errors ("Could not find filexyzcfg"). During the attempt to build, the clean command is looking for the wrong file to delete (one of my BIOS cfg files). Is there something that I can delete to allow a totally new build/clean? Before this started happening I had switched projects, during which a ccs crash occured. I am gussing that one of the project files is from the other project. What can I safely earas (.cdtbuild?)?

    Thx,

    MikeH

  • JohnS.....can you take a look at this? I'm dead in the water.......

    Thx

    MIkeH

  • Did you try cleaning out your workspace or starting CCS with the -clean option?

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

    ki

  • MikeH,

    Sorry, what I meant by "Rebuild" was to recreate the project from scratch... A simple rebuild does not help...

    In my case I couldn't simply restore the project by deleting specific files - unfortunately I had to recreate everything from scratch.

    The file <.cdtbuild> contains the build options for the files used in the project, therefore it is highly dependent on the project. If you have just a few common options it shouldn't be a big deal recreating the project - if each file has its own set of options then the work will be a lot larger.

    Regards,

    Rafael

     

     

     

  • Ki,

    I was able to create a new workspace and import the appropriate projects, including the corrupted one.

    Thanks!

    MikeH

     

  • Rafael,

    Thanks for the input. Ki's solution seemed to have worked with minimal effot (ie re-creating the project).

    thx

    MikeH

     

  • Dear Fellow Forummers....:)

    I thought it my civic duty to let you all know that the "cleaning" of you workspace can do WONDERS for the stability of CCS! For months I have been fighting frustrating, unexplained instabilities and crashes while debugging my code. I have spent many hours cursing the constantly spinning cursor, waiting for my project to miraculously come back to life, only to resort to killing the session the hard way and starting over.

    Now, today, Ki has suggested the simple (and probably well-know to all but me) strategy of cleaning the workspace by deleting the .metadata file. IT HAS HELPED THE STABILITY OF MY DEBUG SESSIONS TRMENDOUSLY!

    Here's what I did:

    1. With CCS not running, open the project file with Windows Explorer.

    2. Navigate to your workspace folder.

    3. Rename the ".metadata" for to "metadata.old" just in case you need to recover.

    4. Start CCS and open your desired workspace. There will be no projects in it.....don't panic.

    5. Enter Project->Import Existing CCS Project-> Select Search Directory.

    6. Navigate to your workspace folder and hit OK.

    7. Now all of your existing projects in the workspace will appear as selections in the "Discovered Projects" window.

    8. Make sure all of them are checked, then hit Finish.

    Now all of your existing projects have been reloaded into your exisiting workspace, but with a clean workspace. If you want to keep your old "preferences" (not sure what they are) you can first export the preferences file, then re-import it, per the wiki that Ki references above.

    I hope you guys find this as valuable as I have. Frustration level and blood pressure have both dropped dramatically!!

    Thx,

    MikeH

     

     

  • Just to add to Mike's post. 

    .metadata folder is used by views and features to store data that needs to be restored when a debug session or CCS is restarted. Thus .metadata folder contains user changes that are made through Windows->Preferences. It also stores opened windows, their state and debugger options. Changes made to target configuration files (i.e. .ccxml) are stored in a separate location and are not affected by deleting .metadata folder. 

    If you experience similar issues to what Mike described above i.e. re-creating a workspace fixes stability, crashes and responsiveness issues, then please start a conversation with me. I'd like to get more information on your scenario to see if we can figure out what might be causing these issues. 

     

    Thank, 

    Martin