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.

Protecting code for a C5515

Other Parts Discussed in Thread: TMS320C5515

Hi Guys,

I am embarking on developing a system for sale using a C5515 platform with included software/algorithms that we want to protect. I'm aware there are a number of threads already covering this but I have a couple of questions I couldn't get information on...

First of all, is there a special part number for the TMS320C5515 required for an encrypted boot image?

Secondly - when using an encrypted boot image, say for the end user to flash onto an SD card and the bootloader has set everything up, can the then unencrypted program code be read from the device using JTAG?

I've seen mention of devices with disabled JTAG so I believe this is the purpose of that feature, but I wanted to be sure. I guess it's a shame the JTAG can't be disabled in software as a switch in the encrypted boot image (or is that actually possible?)...

Also, in the UK, who do I need to contact with respect to getting hold of the encrypted image tool? Does this tool use a private TI key or do I have to choose one for myself?

I see that you can choose for the firmware to be binded to a particular device on first boot - is it possible to script the compilation of code passing a particular device ID or some other serial number into a memory location so that code will only boot on a particular device prior to distribution (i.e. device locked, 'licenced', firmware)?

Many thanks to anyone who can help me with these queries!

  • There is not plan to offer a secured part of C5515 and any tool for such matter.

    Regards.

  • Ok,

    After some more reading I did see that the TMS320C5515/14/05/04 Bootloader supports both encrypted and unencrypted boot images.

    What about the rest of my query?

    Best regards

  • Program code can be red via JTAG. JTAG can be disabled during production testing, not by software. The encryption tool is controlled by the US Export Compliance. Customer please send the following information to TI directly for approval and recording. Please email to Artem Aginskiy @ aaginskiy@ti.com

    • Name:
    • E-Mail:
    • Company:
    • Address:
    • Application:
    • Is application military related?
    • Tel.:

    A development key same for all customers is provide for evaluation/development purpose. Currently, a secure version of C5535 can be avaliable with specific term of engagement. Customer can work with Artem for details.

    Regards.