• State
  • Replies 5 replies
  • Subscribers 85 subscribers
  • Views 74 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

F28027 Device Calibration not complete, check if device is unlocked and recalibrate

TMS320F28031:C28xx Target Connection Failure: Error -1015 / Error -1137 / Flash Unlock Failed

e t
Prodigy 10 points
Part Number: TMS320F28031
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello,
I'm currently working with a TMS320F28031 device and encountering persistent issues with JTAG connection and flash programming. I would appreciate any guidance or suggestions.

Setup

  • Device: TMS320F28031
  • IDE & Debug Probes:
    • Code Composer Studio v8 with Blackhawk USB200
    • Code Composer Studio v20 with XDS110
  • Flash Tools: UniFlash

Errors Encountered

・CCS v20 + XDS110

GEL: Error while executing OnTargetConnect(): Could not read register ST1: target is not connected

Error -1015 @ 0x0: Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable.

・CCS v8 + Blackhawk USB200

Error -1137: Device held in reset

・UniFlash+ XDS110
[ERROR] C28xx: Flash Programmer: Error unlocking flash memory. Device is still locked [ERROR] C28xx: Error connecting to the target: (Error -1015 @ 0x0) [INFO] C28xx: GEL Output: Device Calibration not complete, check if device is unlocked and recalibrate.

 What I've Tried

  • "Test Connection" passes on both CCS versions and both probes
  • Lowered TCLK settings → no improvement
  • Attempted full sector erase via UniFlash → failed

Additional Notes

  • The last program flashed to the device no longer runs.
  • That program did not configure or set any CSM passwords.
  • The issue may have originated from an interrupted flash operation during bootloader development.

Questions

  1. Is this behavior consistent with a device locked via CSM?
  2. Are there recommended steps to force unlock or connect?
  3. Is there any chance UniFlash could still erase sectors if the device is partially locked?

  • 0
    TI__Mastermind 27110 points

    Hi,

    I don't this issue is caused by CSM directly, however I believe it is typical behavior for a power loss during programming to cause a device to be permanently bricked. Reassigning this thread to our flash expert to confirm.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 10 points

    I appreciate your continued support.

  • 0 in reply to e t
    TI__Guru* 80080 points

    I would try Wait Boot mode, this will keep the device outside of the CSM protected region, so that JTAG connection will be allowed:

    You can then inspect the CSM password locations to see if the device is locked(a simple read of those locations should unlock the device, and you will see all 0xFFFF).  

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Prodigy 10 points

    When I try to "Connect Target", the device always enters HALTED state.
    I attempted to erase or unlock the device from the CCS Properties menu, but it only shows unknown error.

    In the password location, I see 00written.
    Does this mean the device has been locked?

    I was able to connect via JTAG in Wait Boot mode, but I would like to know if there is a way to completely erase or reset the Flash by switching to some kind of emulation boot mode or another method.

    Could someone please provide the correct procedure to fully reset the Flash in this situation?

    Any guidance on how to confirm and recover from this state would be appreciated.

    Thank you.

  • 0 in reply to e t
    TI__Guru* 80080 points

    Since you are seeing all 0x0000 in the password locations, this means that the device has a password programmed to it and is locked.  As you mentioned in your original post, if the flash operation was interrupted previously it can result in a non 0xFFFF value in the CSM password locations, which will (and likely has) locked the device.

    Since the CSM password is un-known, there is no way to recover the device, or get it back to a default state.  The only solution/path forward will be to replace the MCU.

    Best,

    Matthew