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: Code Composer Directory Structure



Tool/software: Code Composer Studio

Hi,

Is there any documentation that describes the CCS directory structure? In other words, is there a directory that you should run CCS in? I see a .project file, but running CCS in this dir doesn't seem to pick up the project. I tried exporting/importing projects, but it's not clear how CCS expects to see the project data. I'm trying to archive a project, but I'm not able to bring it back into CCS.

thank you.

  • Scott,

    When running CCS it will show the projects that are part of your workspace. A workspace is a folder on your machine (typically in your user folder but can be anywhere). By default Projects are physically inside the workspace folder but this is not required, they can be located anywhere.

    The Project and build handbook here explains in more detail: processors.wiki.ti.com/.../Projects_and_Build_Handbook_for_CCS

    There is a section on importing projects as well.

    There is a video here that covers exporting to an archive file: www.youtube.com/watch
    The topic here has some general info on sharing projects: processors.wiki.ti.com/.../Project_Sharing



    Regards,
    John
  • Hi Scott,

    scott said:
    is there a directory that you should run CCS in?

    Are you referring to the Workspace folder? If so, the only recommendations are that you choose a clean folder outside any project/source repository and that you choose a path with only alphanumeric characters (with the exception of an underscore character, which is fine).

    scott said:
    I see a .project file, but running CCS in this dir doesn't seem to pick up the project.

    You do not want to specify the project folder as your workspace folder. You want them separate initially and then import the project into your workspace.

    scott said:
    I'm trying to archive a project

    How are you doing this? with the "export to archive file" option?

    scott said:
    but I'm not able to bring it back into CCS.

    You can import archived projects with the same "Import CCS Projects" option and using the option "Select archive file"

    Hope this helps

    ki

  • Hi All,
    Thanks for the replies. I watched the video and looked briefly at some of the docs. I hope I don't have to read the entire build doc just to do this, that would take weeks.

    The way that I exported the project was exactly as described in the video: File->Export->General, etc into a .zip file. I did the following steps:
    1. Start CCS in a workspace called OldWorkSpace.
    2. File->Export->General->Archive to test.zip.
    1. Exit CCS.
    2. mkdir NewWorkSpace.
    3. Start a new CCS session, running now in NewWorkSpace.
    4. File->Import->General->Archive File. In the form, I fill in:
    From Archive File -> Browse -> test.zip
    Into Folder -> Browse -> Select a Folder to Import Into -> ??

    here I get lost. There's no way to browse for a folder that I created before I started CCS, nor will it create one for me (It says "Desitination Project Does Not Exist"). Howefver, It does have a "RemoteSystemsTempFiles" as a default so I just went with that. I can see that it unzipped my test.zip in this RemoteSystemsTempFiles. OK, if that's what it wants. So then I view the Project Explorer but it does not see it. So then I tried a few exit/restarts with no luck. I just end up creating a new project then manually moving all my source code over.

    confused...
  • scott said:
    The way that I exported the project was exactly as described in the video: File->Export->General, etc into a .zip file.

    What version of CCS are you using? The project export feature has a known bug for linked file projects:

    http://processors.wiki.ti.com/index.php/Project_Sharing#Known_Issues

    The bug affects all CCSv5 and CCSv6 versions. It should be resolved in v7, but it hasn't been confirmed yet.


    Thanks

    ki

  • Well, I found a workaround is just to unzip it in Windows then import the CCS project instead of importing an archive.