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.

TMS320F280049: How to zip some function into a DLL file and link to the CCS project?

Part Number: TMS320F280049

For secure, part of my code cannot be seen by others when delivering the project.

So can I zip some code and generate some dll files with Visual Studio, then link to the CCS project?

  • You can create and deliver static library .lib and in the final project, just link the library

  • Further information about creating a static library and protecting your code is in this forum post.

    Thanks and regards,

    -George

  • George,

    Thanks, very useful.

    And I wonder what the difference is for code running between executing  the code sentence by sentence and executing the lib file.

    For the lib, is there more function jump, lower efficiency, or something else? what is the difference and how can i evaluate it?

    Thanks

  • I'm not sure I understand your question.  Here is what I think you mean to ask:  While debugging the final system under control of CCS, the user can single step through functions that come from source files that are directly part of the project.  Single step means executing one C statement at a time.  What about functions that come from libraries?  Can you single step through those functions?

    The answer is yes, but only with moderate difficulty.  If the source code to the library is available, it is possible to configure CCS to know the location of that source code, which makes it possible to single step through it.  

    If the source code to the library is not available, or CCS is not configured to know the location of that source code, then it is not possible to single step through those functions.  It is possible to step one assembly instruction at a time.  But that is rarely useful.

    Thanks and regards,

    -George