• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1067 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: XDS110 not working properly

Amtech
Genius 4585 points
Other Parts Discussed in Thread: UNIFLASH, TMS320F28375D

Tool/software: Code Composer Studio

Hello,

We were using XDS100V2 for TMS320F28375D previously. We have upgraded to XDS110 and found lot of problems in connecting and downloading firmware. As we unboxed and connected XDS110 to uniflash, the firmware of device automatically updated. Then i tried to download firmware with latest version of uniflash but again i failed to download. I found on the TI forum that pull down resistor on nTRST pin should be changed to 10K for XDS110. I did the same and the firmware downloaded successfully for few instance. Than again the problem arises and this time it occurrence is uncertain. Sometimes when i connect JTAG it works smoothly and sometimes it didnt work. I again searched on TI forum and found that it goes to DFU mode and changing USB port will work fine. I did the same again the uncertainty is there. Sometime is shows as device in "low power mode" and after sometime is gives error like "Unable to access device registers". With the same port and cable, at some instance the device work properly and after sometime it didnt work. I need proper solution for this now as my board is reached at production level. Waiting for your solution. I have attached screenshot.

  • 0
    TI__Guru**** 171309 points
    Hi,

    It seems you followed the correct pattern to solve the issues between the XDS110 and the F28035 board by changing the pull down TRST resistor. However, the subsequent diagnostics are very random and make me very suspicious of problems of electrical or physical nature - things such as flaky USB or debug cables and connections, for example. These would trigger errors 1135, 1044, 2131, 1155 and others.

    Apart from that, I really can't tell much else other than verify the checklist shown in the reference below:
    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

    I will think about additional scenarios and report back if I find anything relevant.

    Hope this helps,
    Rafael