• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 273 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/TM4C1294NCPDT: Confusing error message from CCS 10 under Linux when CCS used a FT2232H USB to Dual Serial RS232 Converter rather than an XDS100v2

Chester Gillon
Guru 92251 points
Part Number: TM4C1294NCPDT

Tool/software: Code Composer Studio

Having plugged a single XDS100v2 into a Unbuntu computer running CCS 10.0, created a target configuration file for a XDS100v2 with the default of "Only one XDS100 installed". When went to start a debug session got the following error:

The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

After being unable to find any problem with the connection between the XDS100v2 and the target, realised that xds100serial was reporting two emulators found:

$ /home/mr_halfword/ti/ccs1000/ccs/ccs_base/common/uscif/xds100serial
Scanning for XDS100 emulators...

VID/PID    Type            Serial #    Description
0403/6010  generic FT2232  FTVIZUNN    FT2232H device 
0403/a6d0  XDS100v1/v2     TIVIRUHI    Texas Instruments Inc.XDS100 Ver 2.

The first "emulator" is actually a FT2232H USB to Dual Serial RS232 Converter, rather than an emulator. Having seen the above changed the target configuration to specify "Select by serial number" and entered the serial number of the actual XDS100v2 emulator, and was then able to start a debug session.

If the target configuration is "Only one XDS100 installed" but CCS detects more than one (potential) emulator could CCS provide a suitable warning, rather than just trying to use the first "emulator" detected, to alert the user?

  • 0
    TI__Guru**** 171104 points

    Chester,

    I hope all is well with you and your family in these crazy times... 

    Chester Gillon said:
    If the target configuration is "Only one XDS100 installed" but CCS detects more than one (potential) emulator could CCS provide a suitable warning, rather than just trying to use the first "emulator" detected, to alert the user?

    This is a good suggestion for the XDS100 class of Debug Probes. This is already implemented for the XDS110 and hopefully can be extended without a major infrastructure overhaul. There are already several enhancement reports covering several methods to ease the life of multiple Debug Probes connected but I will file one specific for this.

    The TL;DR version of why the XDS100 utility may erroneously acknowledge some third party FTDI-based adapters is due to the fact that, when BeagleBone White board was released, it required the TI XDS100v2 device drivers installed on the system even if the developer only needed to use the RS232 port for basic board operation. By revision A4~A5, the VID/PID was changed to the standard FTDI and the differentiation was made at a higher level on the CCS tool itself.  

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 171104 points

    Chester,

    I just filed the enhancement report EXT_EP-9777. Please check its status in the link SIR in my signature below.

    Regards,

    Rafael