• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 81 subscribers
  • Views 1816 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28027: UniFlash lock of TMS320F28027 not reversable operation: Device made unprogrammable for ever

Vlad Pavlovic
Intellectual 690 points
Part Number: TMS320F28027
Other Parts Discussed in Thread: UNIFLASH,

Hi,

I used UniFlash to try to lock TMS320F28027.

The procedure resulted with some error that I do not remember.

After that, I was not able to unlock the TMS with the same lock key.

Also, I was not able to use the TMS at all, so I have to go through the trouble of replacing it with the new device.

Since I am required to lock the device, please, let me know what is the step by step procedure to successfully lock and unlock TMS320F28027 device by using UniFlash tool.

regards,

Vlad

  • 0
    TI__Guru** 109165 points

    Hi,

    Can you please let us know how did you try to program the device earlier which locked the device permanently? Please note that the flash operations should never get interrupted else such condition could happen.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 690 points
    Hi,

    I did not interrupt programming of FLASH.

    Here is what I did step by step:
    1. Double click on UniFlash tool to open it.
    2. Click on C2000 on Choose Your Device
    3. Click on TMS320F28027 within the menu with devices
    4. In 2, Choose Your Connection: Texas Instruments XDS100v2 USB Debug Probe
    5. Clicked on START
    6. Went to Settings & Utilities
    7. Scrolled down to Security where the keys are
    8. Clicked on Key 0 and typed in 1234
    9. Clicked LOCK. Got the following: Texas Instrumends XDS100v2 YSB Debug Probe/C28X:
    Can't Run Target CPU: (Error -1156 @ 0x3FF7BF) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 6.0.628.3)
    10. I have choosen yes, and the device was irrecoverable after that.

    So what is the cause of the problem and how to resolve it?

    regards,
    Vlad
  • 0 in reply to Vlad Pavlovic
    Intellectual 690 points

    I tried it again, and instead of LOCK step clicked PASSWORD< and the result is the same. So, I have to unsolder yet another chip and put the new one in. This is not a hobby project, this has to go into production, and the DSP has to be locked.

    I tried it further to unlock it and got the following: "

    Texas Instruments XDS100v2 USB Debug Probe/C28xx

    Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.628.3)"
    Now, I am stuck without development board, and without solution for manufacturing locking.
  • 0 in reply to Vlad Pavlovic
    TI__Guru** 109165 points

    Hi,

    If flash operation is not interrupted then I don't think device is permanently locked. Once you lock the device, you may not be able to connect to it via JTAG and unless you connect it you can not run the unlock sequence. To enable JTAG connection, you need to use the "wait" boot mode. See following note in BOOT ROM document.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 690 points

    My question is what is the proper step by step procedure to lock TMS320F28027 device using UniFlash?

    I gave you my procedure, and went into trouble to brick another board of mine, and to resolder the chip again.

    Based on your last comment, I have one more question: How to set "wait" mode using UniFlash tool for TMS320F28027 step by step procedure?

  • 0 in reply to Vlad Pavlovic
    TI__Guru** 109165 points
    I do not see anything wrong in the steps you are following. Please note that once you LOCK the device with password, there are some restriction on data accesses (secure memory vs non-secure memory) and if there are violations then device may not work as expected. In my last post I did highlight the wait boot setting. You need to pull GPIO34 '0' and then power-up the board to go into "wait" boot.

    Vivek Singh
  • 0 in reply to Vlad Pavlovic
    Intellectual 690 points
    If my steps are OK, the only part of the system that remain under the question is the JTAG pod that I am using for programming and locking, which is Blackhawk XDS100v2. I will look into what are the alternatives to it, and will raise another question about it if needed. I will close this question, thanks for your help.
  • 0 in reply to Vlad Pavlovic
    TI__Guru** 109165 points
    Along with emulator, we also need to make sure the software is written in such a way that there is no access to secure data from code running from non-secure memories else it'll not work. Also we need to make sure device is not locked permanently and for that we need to connect the CCS using "wait" boot and check some status bits.

    Vivek Singh
  • 0 in reply to Vivek Singh
    TI__Guru** 109165 points
    Closing thread based on last post from customer.