• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 233 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:

TMS320F28384D: How to export / import Motor Control SDK projects for a *custom board* to another PC?

TMS320F28384D: Strategy for version control of modifications to Universal Motor Control Lab project

Mark Feller
Expert 1220 points
Part Number: TMS320F28384D


If I modify the Universal Motor Control Lab project to run on custom HW, I end up with some setting and files in the project directory.  But most of the source code in the project are linked to files in the SDK installation directory, and to support new hardware, I need to modify those files.  So I end up with two places where modifications are done: the project directory and the SDK installation directory.  For version control of the changes needed to support the custom HW, I need to work with both directories.


Question here:  Is there a better way to do this, or are there "best practices" / procedure that I should consider?

Thanks!

-Mark

  • 0
    TI__Guru** 116090 points

    You may try to use the Pre-defined symbols to support different boards and versions as shown in the Universal Lab supporting different kits. 

  • 0 in reply to Yanming Luo
    Expert 1220 points

    That's where I started, copying an existing board configuration to a new one.  But I did this within the same files, so that all modifications are to files that are located in the SDK directory.  The project settings, etc. are in the Workspace directory.  In this way, the whole project is divided into two different directories, which makes these a little more complicated when trying to implement version control to track my changes.  

  • 0 in reply to Mark Feller
    TI__Guru 54195 points

    Are you able to create your workspace within the SDK installation directory? You could even create a workspace in the SDK installation, import the Universal Lab projectspec into it to generate the project, delete the workspace files but leave the newly created project, and then import that project into a workspace in your preferred workspace location (making sure not to check that "copy into workspace" box when you import it).

    The other option would be to try to copy all of the linked files and dependencies into the workspace. You can edit the universal_motorcontrol_lab.projectspec file to change the file action field from "link" to "copy," but this only will copy the files and folders listed. It still won't get all of the .h files on the #include path though, so you'd still have to manually copy those.

    Whitney

  • 0 in reply to Whitney Dewey
    TI__Guru** 116090 points

    We haven’t heard from you for a week, so we are assuming you were able to resolve your issue. Please let me know if you have any questions. We would like to close this thread if no any further questions. Thanks!