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.

TMS320F28386S: How to lock the code

Part Number: TMS320F28386S
Other Parts Discussed in Thread: SYSCONFIG, UNIFLASH

Hello,

I Know this question was asked in the past, and I have read the TMR.

However, the TMR covers all possible options and configurations and is really hard to understand how to do just the basics.

Bottom line, I need to send units to a customer, and I need to prevent the customer from downloading the code from the device.
in the same time, I need to allow the customer to upgrade the software using Uni Flash.

I believe what I am trying to do is what 90% of the users need.

It would be great to get a simple 1 2 3 steps to fallow to get this functionality.

Thanks in advance

  • Nir,

              I presume you want to secure the code in your zone but leave the other zone open for your customer to upgrade the software. Is this correct? Can you please check if this C2000 Academy topic in is easy to understand? We currently do not have a step-by-step document that you are looking for. We are in the process of creating a series of videos that would enable anyone to understand the DCSM module without having to read the entire chapter, but those vidoes are several weeks away. 

  • Hi Nir,

    Like Hareesh said, we are currently in the process of creating videos that will walk users through the basics of DCSM without needing to understand every feature of DCSM.

    As of right now, the easiest way to use DCSM's minimum features is by using SysConfig. We have an app note on using the DCSM tool in SysConfig here:

    https://www.ti.com/lit/an/spracp8a/spracp8a.pdf?ts=1680541284102&ref_url=https%253A%252F%252Fwww.google.com%252F

    There are 3 primary steps to preventing the customer from downloading code while allowing them to program their own code:

    1. Designating the memory regions containing your code as Secured by Zone 1(if no data reads/writes need to be performed in these regions, you can designate them as EXEONLY for maximum protection).

    2. Programming the Zone 1 CSM passwords to something different from the default CSM passwords

    3. Once you've finalized your CSM passwords, enable the permanent PSWDLOCK feature to prevent another user from viewing your programmed passwords in the memory browser.

    Once you have done this, the memory regions designated as Secure can only be read or written to by code running from memory that is also secured by zone 1. Memory designated as EXEONLY block all data read/writes, which offers an additional level of protection.

    All of the above can be easily performed using SysConfig. However if you wish to unlock the secured memory to reprogram your code or view the secure memory regions in the memory browser, UniFlash or the CCS On-Chip Flash tool allow you to easily unlock your device using your chosen CSM passwords.

    Let me know if you have any questions.

    Thank you,

    Luke