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 6.0.1 metadata directory location

I created a project in the below directory using CCS 6.0.1 

C:\Users\usd00000\Documents\###_MyPoj1_InstaSpin_###\MyPoj1_28027_Code\MyProj1_IS_FOC_28027_V0_0\MyPrij1_CCS_Project 

But for some reason the metadata directory was created in 

C:\Users\usd00000\Documents\.metadata

 

Now when I try to create a new project in the below directory 

C:\Users\usd00000\Documents\###TI_HVKIT_InstaSpin_###\HVKIT_28027_Code 

CCS still brings up the MyPrij1_CCS_Project instead of allowing me to create a new project.

 

The “C:\Users\usd00000\Documents\###TI_HVKIT_InstaSpin_###\HVKIT_28027_Code” is a new directory with no files in it yet.

I select this directory from the Workspace launcher, but it still brings up the MyPrij1_CCS_Project instead of a blank project.

 

How do I create a new project without bringing up the old project? I would prefer my metadata directory to have been created in the below directory. 

C:\Users\usd00000\Documents\###_MyPoj1_InstaSpin_###\MyPoj1_28027_Code\MyProj1_IS_FOC_28027_V0_0\ 

How can I fix this without messing with the original project? Can O move is metadata directory? 

Any advice or explanation of how to control the location of the metadata directory would be helpful.

  • Gary H said:
    Any advice or explanation of how to control the location of the metadata directory would be helpful.

    The metadata directory is in the workspace folder, which is the location you are prompted to select when CCS starts up. The project location can be either within the workspace folder (this is the default) or can be specified to be elsewhere (by unchecking the "Use default location" checkbox). 

    There is some background on CCS Workspaces and Projects in this wiki article that might be helpful:
    http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Workspaces

    Gary H said:
    How do I create a new project without bringing up the old project?

    I am not quite sure what you mean here. Could you provide an example? When you open up a workspace, all projects present in that workspace will be shown in the CCS Project Explorer view. But you can still create new projects or import existing ones into that workspace.

  • Thanks Asrti,

    The wiki helped alot.

    I notice different behavior with CCS 6 than with CCS 5. It seems with CCS6 even if I choose the below directory for my workspace
    C:\Users\usd00000\Documents\###_MyPoj1_InstaSpin_###\MyPoj1_28027_Code\MyProj1_IS_FOC_28027_V0_0\MyPrij1_CCS_Project

    The metadata directory is created in the below directory by CCS 6.
    C:\Users\usd00000\Documents\.metadata

    Even if I create a new directory as below
    C:\Users\usd00000\Documents\###TI_HVKIT_InstaSpin_###\HVKIT_28027_Code

    When I choose it as my new workspace, CCS 6 keeps using "C:\Users\usd00000\Documents\.metadata" as the workspace.
    I would expect the metadata directory to be created in the directory I choose.
    Its almost as if CCS6 cannot go but so many directories deep. Or maybe I am misunderstanding something.
  • Gary H said:
    I notice different behavior with CCS 6 than with CCS 5. It seems with CCS6 even if I choose the below directory for my workspace
    C:\Users\usd00000\Documents\###_MyPoj1_InstaSpin_###\MyPoj1_28027_Code\MyProj1_IS_FOC_28027_V0_0\MyPrij1_CCS_Project

    The metadata directory is created in the below directory by CCS 6.
    C:\Users\usd00000\Documents\.metadata

    The issue seems to be with the "#" characters in the path. I was able to reproduce the behavior, and I see the same thing for both CCSv5.5 and CCSv6. There are definitely some known issues with Eclipse and CCS handling special characters in file paths. Sorry, but the suggestion here would be to change the workspace path to something without special characters.

  • Thanks for the answer. This is good to know.