• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 282 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28035: software programmed issue

Yale Li 李耀先
Expert 4660 points

Part Number: TMS320F28035

Hi Team,

Here's an issue from the customer may need your help:

After the program is encrypted, it cannot work after programmed into the device. It works fine without encryption.

encrypted location: PWL4/PWL5/PWL6/PWL7

--

Thanks & Regards

Yale

  • 0
    TI__Guru* 95315 points

    Yale,

              “Securing” the device with passwords is not the same as “encrypting” the device. These are two completely different things. I presume the customer is only securing the device with passwords and that no encryption of the code is done. I think what you are trying to say is that the code in Flash works fine as long as passwords are not programmed but the code doesn’t work once the passwords are programmed, is this correct? Please clarify “it cannot work”. Exactly what is not working? 

    1. Are you trying in standalone mode or with the JTAG+CCS connected?
    2. If you program a simple GPIO toggling code in flash, does it work on a secure device? 

    Presence or absence of passwords should have no bearing on code execution in a standalone device.

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 4660 points

    Hi Hareesh,

    Thanks for your correct! My fault. It should be "Securing".

    Hareesh Janakiraman said:
    I think what you are trying to say is that the code in Flash works fine as long as passwords are not programmed but the code doesn’t work once the passwords are programmed, is this correct?

    Yes.

    1. It cannot work in standalone mode, but can work with the JTAG+CCS connected.
    2. No, the customer cannot observe the toggle signal during the port pin.

    --

    Thanks & Regards

    Yale

  • 0 in reply to Yale Li 李耀先
    TI__Mastermind 28580 points

    Hi Yale,

    Has the customer verified that their boot mode select pins (GPIO34 and GPIO37) are both pulled high? It's possible these pins are configured to be in wait boot mode (GPIO34=0,GPIO37=1), which would cause the device to loop within the BOOTROM until a JTAG probe is connected. Wait boot mode is discussed in section 2.2 of the TRM.