• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 84 subscribers
  • Views 885 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.

CCS/LAUNCHXL-F28069M: Exporting InstaSpin Labs as Shareable Entities

Kyle Bartholomew
Prodigy 30 points

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: MOTORWARE

Tool/software: Code Composer Studio

I'm using the InstaSpin lab 5a as the base of my project, and I would like to export all the files that it uses into a folder. I would like to separate it out, so that I can track my code with Git and share it as an open source project. There are no code files in the project folder and everything is dispersed throughout a web of folders in Motorware. I think it would be nearly impossible to identify each file and put it in a separate folder by hand.

This shouldn't affect the question much, but I'm doing development with a Launchpad-F28069M and the Boosterpack-drv8305.

If this is the wrong way of going about it, please suggest a better way to keep track of the code. But I think separating it out is the best option, because there are a lot of files that need to be modified for each specific application, like adding sci bus functionality.

My version of CCS is 7.1.0.00016

  • 0
    TI__Genius 17370 points
    Hello,
    I am writing to let you know that a C2000 team member has been assigned to this post and should be answering shortly.

    Regards
    Baskaran
  • 0 in reply to Baskaran Chidambaram
    TI__Genius 17175 points
    You could do something like create a new CCS project and import the necessary .c source files using the "Copy into Workspace" option, which will create a second copy in the project folder you are working from. Additionally, you'll need to make sure you add the include paths in the CCS project properties. You could take the time to copy the .h headers from the modules/drivers folders in Motorware into the CCS project folder in your Windows file explorer. If you manually copy over the header files into this project, and add the source files using the copy into workspace import option, that should pretty much cover all the files for a Motorware lab. Add in the linker command file and InstaSPIN libraries, you should have a completely movable directory/project, given you've set up all the dependencies to be linked correctly.

    Sean