This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
Hello, I bought this debug probe to use together Uniflash for programming purposes but I can’t connect through JTAG.
I read previous threads about XDS110 connection problems and I tried with different combinations of XDS110 firmware and Uniflash versione but there’s no water ti make it work.
Suggestions would be appreciated.
Thank you in advance.
Federico
Federico,
What is the error you get when trying to connect the target?
It will be good to go ccs menu View -> Target Configuration. Open target configuration, and run 'Test Connection".
The link below is good reference for debugging JTAG connection issue.
https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html
This is what I get with Uniflash:
And this is what I get with Code Composer Studio v10:
-----[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]
It is a custom board.
But I have the same problem on a custom board mounting TMS320F28035.
Regards,
Federico
Let's use CCS to debug first.
Can you go to Target Configuration, and run the "Test Connections" and send full log?
I also have a LAUNCHXL-F280049C and in this case it works (Uniflash 6.0.0 and Firmware 3.0.0.13)
At least I know that the XDS110 is not defective.
What could be the problem with other 2 devices?
Regards,
Federico
Federico,
Please see if this helps:
https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/917331#pi320995=1
Thanks and regards,
Vamsi
No I didn’t. I’ve bought XDS100v2 and it now works on all the boards I have. I also had connection problems with that probe at the beginning but I fixed by connecting TDIS pin to GND.
I don’t think the problem I’m having with XDS110 depends on that, but it’s worth trying to do same.
As soon as I do this test I’ll let you know.
Closing the thread. Please create new one if still encountering the issue or update here.