• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 220 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F280041: Invalid Project Description during project import

Bruce Nielsen
Prodigy 170 points
Part Number: TMS320F280041
Other Parts Discussed in Thread: C2000WARE

Hello,

I am trying to import a project into CCS.  I got a Invalid Project Description during the initial attempt to import.  With a bit of research it seemed that this error was caused by the original project being in the same directory as the workspace prior to import.  I fixed this by using two separate directories for original project files (which was part of a git respository) and the workspace.  This allowed the import to work and allow the changes to the files to be made to the original location so I could commit and push easily.  A couple of questions:

A. If I wanted project and workspace to be in the same directory while also maintaining connection to the original git remote.

B. With the separate project and workspace location are there any files in the workspace that are needed to make the project build, debug, and run?  Or is that ALL contained within the project files including links to C2000Ware, etc?  Trying to understand if there are files in the workspace that should also be being retained for historical reasons?

  • 0
    TI__Mastermind 30825 points

    Hi, 

    When you import the project to workspace, there is an option to "Copy projects into workspace" . If you disable that the project will not be copied into the workspace and retained in the original directory.  If you do any changes also, it will be done in the original project and not in the workspace. 

    To do this, you can add the following line in the projectspec file   "      location="." " under the project option.

    There are no files within workspace that need to be retained . You should be able to recreate everything from the original project.

    Best Regards

    Siddharth

  • 0
    Prodigy 170 points

    Siddharth,

    Thanks.  A couple more questions:

    A. You mention modifying the projectspec to add the line.  Why would I need to do this?  It seems based on your your first paragraph if I don't copy the files the import function should direct the project to work in the original location or am I missing something?  What happens if I don't add this line to the projectspec?

    B.  Where is this project spec located?  I originally started with an Instaspin project that's now been heavily modified.  But when I view the .ccs file in my project it still points to the old Instaspin project spec file.  I would have assume a copy would have been made and kept current with the modifications I've made to the project.

    C.  How do I change the project name or maybe more importantly the generated output file names?  I'm still using the original names from the Instaspin lab and its probably time to update project name and file names accordingly to reflect the new applications intent.

    Thanks - Bruce

  • +1 in reply to Bruce Nielsen
    TI__Mastermind 30825 points

    Bruce, 

    Wasn't aware that you were using a CCS Project and not a projectspec. My response was relevant if you were using projectspec . 

    You can refer the following link https://software-dl.ti.com/ccs/esd/documents/ccs_projectspecs.html

    C. To change the project name , you will have to edit the ".project" file and specify the name in the <name> tag of this file.  To change the output file name. you will have to edit the ".cproject" , search for "name="Specify output file name (--output_file, -o)" string and change its value. You can change the output file name also using the CCS GUI. Select the project , right click and then select Properties. Select the "basic options" under the C2000 linker and then specify the output file name . See the attached snapshot.

    Best Regards

    Siddharth