• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 646 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.

CC3220SF-LAUNCHXL: XDS 110 USB Debug Probe Failure

Himanshu Batra
Prodigy 120 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: TMDSEMU110-U

We are using XDS 110 for programming CC3220MODASF in our production line. But we are facing the issue that all of are XDS110 stop working one after the other. Four programmers have gone faulty. What could be the issue of failure?

If the schematic for XDS110 is available kindly share it as early as possible so that we can analyse the failure.

  • 0
    Guru 79905 points

    Hi,

    Design files for CC3220SF-LAUNCHXL are available at product page. Design files for TMDSEMU110-U need to be provided by TI, if are publicly available.

    BTW ... it will be good to know what are symptoms of non functional XDS-110.

    Jan

  • 0 in reply to Jan D
    TI__Guru* 91206 points
    Dear Himanshu -
    in addition to the symptom(s) - it would also be quite helpful to know how you are connecting to the PC and then also to the MOD.
    as much information as possible would be great. (Pictures, wiring diagram)
  • 0 in reply to Josh Wyatt
    TI__Guru**** 171044 points
    Himanshu,

    In addition to Josh's requested details, the most common cause of premature failure for Debug Probes is the presence of ground loops between the host PC, the target board and the outlet ground pins of the two supplies (the PC and the board). The second most probable cause are high voltage transients, which can be coming from the outlet or from the board itself (in case of motor drive or inverters). Obviously that any mistake in the wiring/PCB connections will stress the Debug Probe as well.

    Ground loops can be detected by a multimeter with low input impedance (LowZ or Zlow, depending on the manufacturer) and transients can be detected by a fast oscilloscope or data acquisition unit (sometimes a multimeter with a fast peak detect can also catch these). In addition to the Launchpad schematics, you can also reference the document below with routing guidelines for Debug Probe connections.
    software-dl.ti.com/.../emu_xds_target_connection_guide.html

    At last, would you mind sending the serial number of the failed probes?

    Regards,
    Rafael