• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 383 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.

XDS200 update

HS FAE Germany
Mastermind 32220 points
Part Number: XDS110ISO-EVM
Other Parts Discussed in Thread: TMS320F28027

Tool/software:

Hi,
customer wants to do an firmware update of their XDS200 but got following message:

Regards, Holger

  • 0
    TI__Guru**** 162305 points

    Holger,

    Is the XDS200 not working?

    The message looks like it updated it ok.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Mastermind 32220 points

    Hi John,
    yes, the XDS200 is not working under CCS.

    When the JTAG is connected to the laptop, one yellow LED lights up. When he tries to connect to the target, the second yellow LED briefly turns on for a second, and then both LEDs turn off and getting the following error:

    This error is generated by TI's USCIF driver or utilities.
    The value is '-183' (0xffffff49).
    The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
    The explanation is:
    The controller has detected a cable break far-from itself.
    The user must connect the cable/pod to the target.

    Could this indicate a fault with the programmer, or is there something I might be doing incorrectly? I also tried different cables. Same for a 2nd XDS200.

    In Code Composer Studio (CCS), he has selected the programmer type as "Texas Instruments XDS2xx USB Debug Probe." The target they are using is the TMS320F28027.

    Regards, Holger

  • 0 in reply to HS FAE Germany
    TI__Guru**** 162305 points

    Holger,

    That error message typically means that the debugger is not receiving anything back on TDO.  There is more information at the link below:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

    Is this a custom board?  Has any debug probe been able to successfully connect to it?

    Regards,

    John