TMS320F28388D: TMDXCNCD28388 with docking station and XDS110 programmer/debugger

Hi Bob,

2.2K ohms or smaller resistor should be sufficient. 

Please refer to the earlier E2E posts. 

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1174451/tmdsemu110-u-xds110-fails-after-some-time-when-debugging-f280025/4420340?tisearch=e2e-sitesearch&keymatch=XDS110%2520trstn%2520resistor#4420340

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/628509/ccs-tmdsemu110-u-xds110-not-working-but-my-xds100v2-works-fine/2333828#2333828

Let me know if this doesnt resolve your concern.

Best,

Uttam

Yes, I tried that.  No luck.  

I should note that many of the comments say '2.2kohm or smaller' and then indicate that 10kohm worked better.  I would say that 10kohm is larger than 2.2kohm.  Perhaps I am missing something here.

Bob,

1. Can you check whether were you able to use XDS100 on control card and  connect to CCS?

2. When you mention not working do you mean JTAG connection is the issue? or something else? if possible please share the error you are seeing on the CCS.

Best,

Uttam

The XDS100 on the control card works fine.  With a scope I can see the TDI signal and the TCLK signal but nothing on TDO or TMS when I use the XDS110.  The error is as follows:

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
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.

Hi Bob,

I verified with XDS110 it works fine to me. Can you share the snipshot of the setup and scope obervations. 

Best,

Uttam

I found a work around for the time being.  Switched to an XDS100.  It's possible that my XDS110 is simply damaged in some way and will never work.

might be because of damaged XDS110as you mentioned.

Get back to us if you need anything else