• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 670 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.

CODECOMPOSER: Testing connection in code composer has blown XDS110 probe

Mike Henry
Prodigy 70 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: TM4C1294NCPDT

I have just bought two XDS110 Debug Probes

Before moving to Code Composer 11 I decided to make sure my code was running in Code Composer 6.

Both devices were detected in 11.

When I setup the debug target configuration as a XDS110, I previously used a XDS510 and then tested the connection the probes disconnected and never came back.

Both probes are now not recognised in device manager and Code Composer 6 or 11

Running "xdsdfu -e" returns with both devices not found.

When plugged in the D1 LED is lit but no USB connection.

Did testing the connection blow both devices !!

  • +1
    Prodigy 70 points

    Managed to sort it, had to go through the recovery process ie

    Connect the JTAG TDO pin of the XDS110 TM4C1294NCPDT device (pin 97 of the 128-pin package device) to ground. and reflash the firmware.

    Looks like Code Composer 6 had corrupted the firmware.

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#troubleshooting

  • 0 in reply to Mike Henry
    TI__Guru**** 473001 points

    Hi Mike, 

    Glad to hear you sorted it out. Sorry to hear that you had to go through the hassle though.

    What was the exact sequence of steps when the failure occured? Based on your initial post, I am assuming:

    1) received new XDS110 probes

    2) tested with CCS 11 (it worked). Do you know if CCS 11 auto-update the firmware during the test?

    3) tested with CCS 6 and it failed with apparent corrupted firmware.

    Is the above correct?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    Hi Ki,

    That was basically what happened.

    Worked find in CCS 11, didn't notice any firmware update happening.

    Loaded CCS 6 and changed the debugger in the Project General Properties from XDS510 to XDS110

    I then went to the Target Configuration and setup the new debugger and deleted the old one.

    Then hit the "Test Connection" button

    It failed at that point and the debugger disappeared from the Windows device manager and it never came back

    Even after power cycling and reinserting the USB connector.

    Mike

  • 0 in reply to Mike Henry
    TI__Guru**** 473001 points

    Thanks Mike.

    Still not sure how the corruption happened. I go between CCS versions all the time and never experienced this. But it is something we will need to keep an eye on.

    ki