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/TMS320F28335: Protections against reverse engineering of the *obj files compiled through CCS

Part Number: TMS320F28335

Tool/software: Code Composer Studio

How can we make sure to protect the *obj files compiled through CCS against reverse engineering?

We need to provide our control libraries to another company in order to integrate it in its control hardware (TMS320F28335) and we want to make sure about the protection of our IPs. Could you kindly provide information about the protections and/or certifications that could be relevant for this topic?

  • Unfortunately, there are no compiler toolchain options or features which are directly aimed at protecting intellectual property (IP).  While I cannot offer any guarantee, here are two suggestions which help.

    Do not supply debug information.  This is information (line numbers, types, etc) the compiler adds by default which is used by the debugger (CCS) in order to step through the code, display variables, etc.  There are two methods to consider.  One is to build with --symdebug:none.  This option is documented in the C28x compiler manual.  Avoid using this option until the final release build, because it makes it next to impossible for anyone, even you, to debug the code.  The other method is to use the strip utility strip2000 after the build.  This utility is documented in the C28x assembly tools manual.

    If this custom library contains functions or variables that are not part of the public API, then consider using code obfuscation tools to obscure the names of those entities.  An internet search on that term yields some links that appear useful.

    Thanks and regards,

    -George