• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 283 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.

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

Mark Feller
Expert 1220 points

Part Number: TMS320F28384D

I am working with a custom board using F28384D.

I imported the Motor Control SDK Universal Control Lab project, and adapted it so that it runs with the custom board.

After importing the original Universal Motor Control Lab project on my development PC, most of the files are links to files in the Motor Control SDK.  I need to modify some of these files to support the custom hardware.  There is no option to create local copies of these files within the project versus using the files in the SDK.  

I need to give the project to another user.

If I export my project as an Archive File, and select the option to "Resolve and export linked resources", those files from the SDK folder are copied into the exported project.

When I import the project on another PC (that already has the Motor SDK installed, but I'm not sure if this makes a difference), the project has "local copies" of the modified files.  However, when trying to build, it still goes out to the Motor Control SDK for some things, and produces errors because it is looking at the original/unmodified versions of files in the SDK, instead of the modified local copy of the file that was imported.  As an example, hal.h.  

I guess on the import PC, I could start to change include directories and files to get things pointed at the local copy instead of the SDK.  However, this breaks sync/settings with the original project on the export PC.

My question: Is there a "best practices" or recommended procedure for how to create a Motor Control SDK project, modify it to support custom hardware (which seems to mean modifying files within the SDK folder), and exporting the project to another PC, so that the other PC can build and run with ideally no changes needed to the imported project?

(A related comment: modifying files in the SDK versus local copies creates complications for version control of software.  Some project files are in the project directory.  Some changes are in the SDK directory.  I will create a separate ticket to ask about this.  But in general, import/export and version control are a couple of areas where the otherwise-good Motor Control SDK can use some improvement)

Thanks!

--Mark

  • 0
    Expert 1220 points

    Part Number: TMS320F28384D

    I am working with a custom board using F28384D.

    I imported the Motor Control SDK Universal Control Lab project, and adapted it so that it runs with the custom board.

    After importing the original Universal Motor Control Lab project on my development PC, most of the files are links to files in the Motor Control SDK.  I need to modify some of these files to support the custom hardware.  There is no option to create local copies of these files within the project versus using the files in the SDK.  

    I need to give the project to another user.

    If I export my project as an Archive File, and select the option to "Resolve and export linked resources", those files from the SDK folder are copied into the exported project.

    When I import the project on another PC (that already has the Motor SDK installed, but I'm not sure if this makes a difference), the project has "local copies" of the modified files.  However, when trying to build, it still goes out to the Motor Control SDK for some things, and produces errors because it is looking at the original/unmodified versions of files in the SDK, instead of the modified local copy of the file that was imported.  As an example, hal.h.  

    I guess on the import PC, I could start to change include directories and files to get things pointed at the local copy instead of the SDK.  However, this breaks sync/settings with the original project on the export PC.

    My question: Is there a "best practices" or recommended procedure for how to create a Motor Control SDK project, modify it to support custom hardware (which seems to mean modifying files within the SDK folder), and exporting the project to another PC, so that the other PC can build and run with ideally no changes needed to the imported project?

    (A related comment: modifying files in the SDK versus local copies creates complications for version control of software.  Some project files are in the project directory.  Some changes are in the SDK directory.  I will create a separate ticket to ask about this.  But in general, import/export and version control are a couple of areas where the otherwise-good Motor Control SDK can use some improvement)

    Thanks!

    --Mark

  • 0 in reply to Mark Feller
    TI__Guru** 117160 points

    Seems like there is no a best way to export the project includes all of the source and header files used in the project. You have to share the whole motor control SDK folder and cleanup the files are not used in the project in Motor control SDK., that could be a easy and simple way.