Part Number:TMS320F28375S
Tool/software: Code Composer Studio
Hi,
I have launchpad-28375D and I tested my code on this launchpad.
After I got a custom board of TMS320F28375S.
Unfortunately, I don't have standalone XDS debugger yet.
So, I tried to use on-board XDS110 debugger on lauchpad-F280049 .
launchpad-F280049 provides the XDS110 port for external board.
XDS110 support cJTAG 2 pin mode,, TMS and TCK, as I know.
I set the target configuration like this.
I connected the TMS and TCK two signal to my custom board, ground as well.
And I push the test connection button.
test is failed.
Two signal are enough for XDS110? My custom board's JTAG has TMS,TCK,TDO,TDI,JRST signals, but I connected two XDS110 debug signals.
I tested the clock 100kHz, but fail.
What seems be the problem?
Thanks in advanced
BR
Paul
-----[Print the reset-command hardware log-file]-----------------------------
The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).
-----[An error has occurred and this utility has aborted]--------------------
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.
[End: Texas Instruments XDS110 USB Debug Probe_0]