CCS/TMS320F28335: Trouble connecting to custom board with CCS via XDS560

David Marty

Part Number: TMS320F28335

Tool/software: Code Composer Studio

Hi!

CCS being connected to a custom board via XDS560, if I modifiy the binary (building my project), CCS flash the DSP with the new binary.

But I have modified the binary via the file explorer (via SVN in fact), CCS have tried to flash the DSP but it fails. And I'm not able to re-connect to the target. CCS give this error : "C28xx: Error connecting to the target: (Error -233 @ 0x0) The JTAG IR and DR scan-paths cannot circulate bits, they may be broken. An attempt to scan the JTAG scan-path has failed. The target's JTAG scan-path appears to be broken with a stuck-at-ones or stuck-at-zero fault. (Emulation package 6.0.14.5)".

But no action on the hardware have been made on the custom board or in the XDS560 connection before and after the problem occur.

I'm running Code Composer Studio 5.5 and the JTAG emulator is an Spectrum Digital XDS560v2 STM.

Thanks for your help

over 8 years ago

0 desouza over 8 years ago

TI__Guru**** 171309 points

Hi,

Please check the error in section 5.13 of the wiki page below.
processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

Given you mentioned that a previous flash operation failed and no hardware was changed, that matches with what I have seen in the past when code running on the target either disables JTAG (which I don't think it is a capability of F28x devices) or it happens to continuously reset the device, thus causing errors on the JTAG interface.

In order to take control back, you could try to mass erase the flash contents via CCS - for details, check the page below:
processors.wiki.ti.com/.../Flash_Programming_F28x

Hope this helps,
Rafael

0 David Marty over 8 years ago in reply to desouza

Intellectual 655 points

Hi,

Thanks for your answer

I have read the wiki page "Debugging JTAG Connectivity Problems" and I have tried this :

with an another XDS560, the same : connection failed
with an other CCS installation on an other computer, the same : connection failed
with an other custom board, connection succeed and flash the device is possible

It isn't possible to make a "mass erase" if I'm not able to connect CCS to the device.

The same problem have occured in 2 custom boards.

Without solutions, we will try to replace the device in this 2 boards.

Regards

David

0 desouza over 8 years ago in reply to David Marty

TI__Guru**** 171309 points

David,

>>It isn't possible to make a "mass erase" if I'm not able to connect CCS to the device.
Sorry, I think I got confused with other devices that allow this.

One thing that I just recalled doing to try and connect to misbehaving devices/firmware was to hold the device in reset by external means (jumper, switch, etc.), launch the debugger manually but only releasing the reset immediately after connecting to the core. This sometimes allowed the JTAG debugger to halt the device before it reached the problematic code - not very scientific but by chance I was able to connect.

The procedure to do that is shown at the page below: hold the reset and release it immediately after step 4:
processors.wiki.ti.com/.../GSG:Connecting_to_slave_cores_in_SoC_devices_v5

Hope this helps,
Rafael

0 David Marty over 8 years ago in reply to desouza

Intellectual 655 points

Hi,

desouza said:
One thing that I just recalled doing to try and connect to misbehaving devices/firmware was to hold the device in reset by external means (jumper, switch, etc.), launch the debugger manually but only releasing the reset immediately after connecting to the core. This sometimes allowed the JTAG debugger to halt the device before it reached the problematic code - not very scientific but by chance I was able to connect.

I have tried your solution without succeed.

The DSP seems to be held in reset even if the XRS signal is at 3.3V.

Regards

David

0 David Marty over 8 years ago in reply to David Marty

Intellectual 655 points

Hi,

The DSP seems to be held in reset even if the XRS signal is at 3.3V.

I have made a mistake, like you can see in the attached screen shot, XRS is driven every 4.5ms.

We have encountered the same problem on 3 boards now.

We are able to connect the XDS560 when the DSP is booting in a mode other than "Jump to Flash". The "secure zone" aren't accessible. It seems that the flash programming failed during the erase process and the CSM is permanently locked.

What we have to do to prevent this failure ?

This occurs 3 times in differents environments.

Why the flash programming failed ?

XRS.tif

XRS periode.tif

Regards

David

C2000™︎ microcontrollers

C2000 microcontrollers forum

CCS/TMS320F28335: Trouble connecting to custom board with CCS via XDS560