IP protection C2000

Hi Scott,

There are three parts -

trial period so that the software no longer functions after a certain date and having  a password requirement to run the software

I think this is more about how the SW is developed and implemented so that it can not be executed without password.

the most important thing is to make sure that the software cannot be reverse engineered from compiled code on the microcontroller

C2000 devices have security feature to prevent this from happening. I assume you are looking at general solution at this point and would use any device which has this feature but if you have some specific C2000 device in mind, please let us know.

Further complicating matters, there will be counterparty software on the same microcontroller

We do have device which provide dual-zone security feature which can be used for this. Please refer "Dual Code Security Module (DCSM)" section of F28377S device TRM for more detail about this.

Regards,

Vivek Singh

Scott,

To add onto what Vivek stated:

Yes, protecting a base code and from another developer that adds a SW layer on top is precisely the purpose of the DCSM. For Piccolo class devices with Dual Code Security, you can look at the F2805x and F2807x devices, and for the Delfino class devices we have the F2837xS and F2837xD devices.

Additionally, our other C2000 devices have single code security (CSM). The difference is that the 3rd party has the opportunity to also secure their code to the world in the DCSM devices, due to the fact that there are two secure areas (zones). Whereas once you use up the single secure area of the CSM, additional SW must be left unsecured. So, if there is no requirement that the 3rd party also has the option to protect their code (IP), then you can use pretty much any C2000 device.

For the trial period, there are no specific HW hooks that protect the timers. So, you may have to get creative with SW checks, but you can program a password into the Flash and protect it similar to the code you are protecting. Your code will be able to read it, but someone else on a debugger or another parties code outside of your code should not.

Regards,
Dave Foley