TMS320F28P559SJ-Q1: Getting connection error : controller has detected a dead JTAG clock with Blackhawk XDS560 v2 system trace emulator

Hello,

The message indicates the emulator completely lost the device (dead JTAG clock and target power loss) - in other words, a catastrophic failure from an emulator standpoint.

Do you tie the TCK pin to the RTCK pin? Please compare your JTAG header to the datasheet's recommendations:

Can you check your target configuration file (.ccxml) and see if you have the JTAG TCLK option set to Automatic instead of Adaptive? 

Best,
Matt

"Do you tie the TCK pin to the RTCK pin?"

Yes.

Here is my targets device JTAG pinout


I have tried both methods by setting JTAG TCLK frequency automatic and adaptive.

And I m using JTAG(2x10 2.54mm) to SWD(2x5 1.27mm) cable adaptor which is connected between blackhawk XDS560 v2 system trace emulator and target device

Hello,

Can you check the XRSn signal to confirm the device is properly coming out of reset?

It is also important to have a pull-up on TMS so the JTAG state machine can be properly held in reset during normal operation. nRESET can be left NC since the device can be reset through a JTAG scan sequence. 

Best,
Matt

I have checked both pin signals TMS and XRSn they are found high (3.3V).

Hello,

Thank you for confirming that. Can you also check TCK? 

Vikas Bankar said:

When I use the On-Chip Debugger (LAUNCHXL-F280049C), the code runs properly without any errors, and the device unlocks successfully.

When you're using the LaunchPad's debugger, how are you connecting the JTAG signals to the device? Are you using the same JTAG to SWD Serial adapter?

Which pin converter are you using from the BH XDS560v2 (14-pin TI, 20-pin ARM, 20-pin TI, etc.)?

Best,
Matt

My TCK is also 3.3V

Matt Kukucka said:

When you're using the LaunchPad's debugger, how are you connecting the JTAG signals to the device? Are you using the same JTAG to SWD Serial adapter?

There is no use of TAG to SWD Serial adapter, actually direct connection between LaunchPad's debugger and target and I'm using 20-pin TI pin converter in Blackhawk.

Hello,

Vikas Bankar said:

My TCK is also 3.3V

Just to confirm, when you state that the signal is high, that means that the signal isn't switching between 0 and 3.3V? 

Vikas Bankar said:

I'm using 20-pin TI pin converter in Blackhawk.

I don't think your JTAG to SWD adapter matches the TI 20-pin pinout, it looks like it's intended for the ARM 20-pin pinout: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#pinout

Best,
Matt

Matt Kukucka said:

Just to confirm, when you state that the signal is high, that means that the signal isn't switching between 0 and 3.3V? 

Yes, that pin stays at 3.3V

Matt Kukucka said:

it looks like it's intended for the ARM 20-pin pinout

I think yes it is for ARM 20-pin.

Can you please suggest any converter for the same? 

Now I have made below connections with TI 14 pin and my target and getting below error against proper connections, any other connection required?

Hello 

Thank you for your help.

Sometimes I'm able to connect with my target but most of times getting below message

Hello,

This error is usually reported when the JTAG signals are not connected correctly, though the error can also be caused by poor signal quality. Please ensure that the connections are proper between the debug probe and the target.

How are you connecting the debugger to the target header? Are you using an adapter?

Best,
Matt

Matt Kukucka said:

How are you connecting the debugger to the target header? Are you using an adapter?

No, I have made a circuit on general purpose board and tested with the target, sometimes it works ok but most of the time above message is found.

Hello,

If you don't have the recommended pull ups, especially on TMS, then the JTAG connection can be unstable. Please also verify that TCK is looped back to RTCK and that EMU0/EMU1 are pulled high to 3v3. 

Best,
Matt

Hi,

I have made connection as per fig.7-26.Connecting to the 14-Pin JTAG Header and checked well.

Hello,

What is the distance between the header and the target? Is it within 6 inches?

Best,
Matt

Yes, It is withing 6 inches. 

Hello,

Are the pull-ups matching datasheet specifications? Can you try putting the device in WAIT boot before connecting?

Best,
Matt