TMS320F28027: TMS320F28027

Nistha,
Thanks for reaching out to the TI E2E forums. From the error message I think this is showing a connection issue as part of the flashing process.

I'd like to break the two steps from one another, connecting to the device first, then erasing.
Inside CCS can you right click on the target .ccxml file and "launch selected config". Once this is done, right click on the C28x CPU then select connect target.

Let me know if you are able to get this far in the process and we can debug from there.

Best,
Matthew

Actually we i short the capacitor near XRSn i got JTAG integrity test passsed .

I suspect that the device is executing from a secure region of memory when you are trying to connect, based on you last post.  I would recommend changing the boot mode to Wait Boot Mode.  I've copied a screen shot from the DS on how to do this.  You'll need to power cycle the device after setting these. This should allow CCS to connect(I would still recommend the same procedure as I mentioned before).

Once you are connected, you can use the flash tools to erase the device.  If that gives an error let me know.

Best,

Matthew

it gives same error as before.

Yes it indicated it may be locked and showing error --1135. if the  device is get locked so how can i unlocked it. i doesnt unerstand how its get locked i am debugging the code after some changes when i again try to flash i get this error can you tell me why this isue occur.

JTag connection is succedded if i short the capacitor which connected to XRSn pin but when i am not short that capacitor jtag integrity test is also get failed as i report you above but in both condition i am not able to flash as well as erase the device.

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 9.3.0.00032)
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 9.3.0.00032)
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:283]
at C28x_Mode() [f28027.gel:80]
at OnTargetConnect()

Regards

Nistha

Nistha,

Part of the issue is that all the automatic features of CCS when clicking the "debug" button like auto code load, run to main, etc all give errors when CCS can't complete some or all of them.

I'd like to avoid using the debug button to initiate the CCS session while we root cause this. 

The reason holding XRSn low will allow the connection is that the device will be inside of the Boot ROM, which is unsecure, and not cause an immediate termination of the JTAG connection like executing from secure memory would do.

After you connect to the device manually, I'd like to open a memory browser and point it to 0x3F7FF8.  You'll want to look at the 8 16-bit words starting at this address.  If these are all 0x0000, then the device is locked.  This can happen if the device is being programmed and it is interrupted(power loss, clock loss, XRSn asserted)

If this is the case, there is no way to recover the device if the password is unknown, and the F28027 will need to be replaced.

Let me know if this is what you see at the password addresses above.

Best,

Matthew

0x3F7FF8  is 00 so where the device password is givencan you suggest me where password is given so i can unlock the device.

Regards

Nistha

Nistha,

If this location is reading back all 0x0000, it means the device is locked.  From what you are describing it was locked un-intentionally, as I mentioned in the previous post.  If this is the case, and the password is unknown, then the device will need to be replaced with a new F28027 which is unlocked.

Best,

Mathew