• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 84 subscribers
  • Views 4627 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.

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

TobyM
Genius 5200 points
Other Parts Discussed in Thread: UNIFLASH

I seem to have somehow locked my F28027 on the LaunchPad-XL.

Everything worked fine yesterday (and the last few weeks!) until I came in this morning and powered on and attempted to load the device (no code changes) which resulted in the following error messages:

C28xx: GEL Output: 
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx: GEL Output: 
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.
C28xx: File Loader: Memory write failed: Unknown error
C28xx: GEL: File: C:\ProjectName\Debug\ProjectName.out: Load failed.

And as far as I can tell the memory at the CSM locations (0x3f7ff8) is all zeros. 

I have tried using Uniflash to unlock or erase the device with no success and now attempting to load results in the following error (although I have power cycled the device several times to try to reset):

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.407.3)

I note that there are a number of other threads from the last few years regarding such problems with some threads mentioning that TI are actively looking into what causes this to randomly occur and possible solutions.

Where any causes or solutions ever found??

I will probably replace the device on the board now, but if no cause or workaround is identified how can I be sure this wont cause problems with devices in production?

Thanks, T

  • 0
    Guru 192875 points

    Hi Toby,

    Toby Mole said:
    Everything worked fine yesterday (and the last few weeks!) until I came in this morning and powered on and attempted to load the device (no code changes)

    Did you by any chance try configuring the CSM passwords? or power reset during erase? or any unusual instance last night?

    Did you also try the launchpad on any other PC/USB port?

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Genius 5200 points

    Hi Gautam,

    Nope, no reset during erase of anything unusual. The CSM passwords have never been set on this so should have been all FF's.
    I tried the launchpad on different USB ports/hub but not another PC. I've swapped the device out at this point and the new one is working well.

    I could place the old one on a spare ControlStick if further tests might prove useful?

  • 0 in reply to TobyM
    TI__Mastermind 32995 points
    Have you gotten this to work properly with another controlStick?
  • 0 in reply to Sal Pezzino
    Genius 5200 points

    Hi Sal

    I popped this on a ControlSTICK this morning. When attempting to load a program to it I get error -1135 if I hit retry it gives -1015, then -1015, then -1135 again and finally fails. 

    The device is connected directly to a USB socket (several different sockets tried and I've restarted the PC since the last time I tried it). I have not ever attempted to set CSM passwords on the device, nor have there been any abnormal shutdowns while debugging.

    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.407.6) 
C28xx: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request.  Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.407.6) 
C28xx: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request.  Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.407.6) 
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.407.6) 
C28xx: Trouble Halting Target CPU: (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.407.6) 
C28xx: Error: (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.407.6) 
C28xx: Unable to determine target status after 20 attempts
C28xx: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx: GEL: Error while executing OnTargetConnect(): Could not read register ST1: target is not connected
	at (ST1&~(0x0100)) [f28027.gel:272]
	at C28x_Mode() [f28027.gel:80]
	at OnTargetConnect()

    T

  • 0 in reply to TobyM
    TI__Mastermind 32995 points

    Is it possible that a switch on the board was changed? Is there a JTAG enable switch?

    I am asking another engineer to help with this.

    sal

  • 0 in reply to Sal Pezzino
    Genius 5200 points
    Sal,

    Switches have not been changed, I have a replacement device on the original LanchPAD and it is working fine without any other modifications. The ControlSTICK I have placed the suspect device on has no switches, but does have R9 removed from previous use - though IIRC this should not affect the JTAG operation.

    Thanks, T
  • 0 in reply to TobyM
    TI__Guru 57255 points

    Hi Toby,

    I apologize for the trouble here.

    As you've read and mentioned, the most likely root cause is that reset occurred while the flash was being programmed (or something similar to this).  From what we've seen power is the most often cause.  Long unshielded USB cables, use of USB hubs,etc all decrease the ability to regulate the voltage at the target (and also add delay in the communication).  The setup can certainly be part of the issue.

    As a note, working with these boards internally, my group runs into very few of these type problems. 

    In the past, we have looked through the CCS programming flow to see if there's anything marginal.  We haven't found much when we do this, but it's also very difficult to find anything without a reproduce-able setup.

    If you find that the issue comes up again, especially during production programming, please let us know.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Genius 5200 points

    Brett,

    Thanks for the info, T

  • 0 in reply to Brett Larimore
    Prodigy 10 points
    Is there any way to normally write the code once again without replacing the IC? I have already replaced the IC twice and the problem crops up every time after a few successful writes.