TIDM-02006: Program link problem

Part Number: TIDM-02006

Hi Team,

I found that many of our motor control SDK programs are in the form of links. What should I do if I want to create a different test version? Is there any easy way? (Because the file is in the form of link, no matter what the modification is, it will be saved, and the re-imported project is also the changed file)

Thanks

Jenson

  • You can pretty easily edit the .projectspec for the example projects to tell CCS to copy the files into the workspace instead of linking them. Find the .projectspec for the project you want to change (like in \solutions\tidm_02006_multi_axis_drive\[device]\ccs\sensored_foc), make a back up of it just in case, open it up in a text editor, and search and replace 'action="link"' with 'action="copy"'

    Whitney

  • I would recommend only doing this for code though. .libs are usually better left as links.

    Whitney

  • Hi Whitney,

    I am currently encountering a new problem. I have changed all the reference designs to the copy method, and then modified the program. I want to send the project to the customer.


    But I found that even if all the text is changed to the form of copy, there will be files with links (for example, some header files, they are stored in the libraries of the SDK). How should I do?

    Then I found out that even if I all use the copy form, and then package the project and send it to the customer, they still have some errors. I want to know what you would do in this situation? Regarding the project in the SDK, if you modify it, how would your recommendation be sent to the customer?

    Thanks

    Jenson

  • Hi Jenson,

    Wanted to let you know that Whitney is currently out of the office and will return by next Monday the 4th of October.  You should expect a reply by that time.

    Best.

    Krishna

  • Hi Krishna,

    OK,should I open a new theme to ask this questtion?The customer needs this soon.

    Thanks.

    Jenson

  • Hi Jenson, 

    You don't have to...I can try to help you here.  When you are working with a projectspec, it best to fully make the required modifications yourself and get it working fully.  If you are being thorough, it could be tedious.  As an initial step, I suggest you make the recommended updates incrementally and test if your last change worked.  For each test, I suggest you open the projectspec in a new workspace just to be sure there is no residual stuff from the previous attempt.  If you are already making the updates in the manner being described here, please explain what you are seeing. 

    Thanks,

    Krishna 

  • Hi Jenson,

    Since header files are found by adding them to the compiler #include search path they are not linked or copied in to the project by the projectspec as you've seen. You would have to copy all of the include path directories into your project and then update the #include search path in the compiler options to point to the copies within the project.

    Does the customer at least have the MotorControl SDK installed? Could you set up your search paths to be relative to a single project path variable to the SDK root so that they only update they need to make in the project to get it to build is to update that path variable to their own SDK installation?

    Whitney