• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 461 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.

Original question:

CCS 6.1.2.00014 under Linux unable to connect to a XDS100v2 with a blank serial number

CCS/TMDSICE3359: CCS 8.2.0.00007 under Linux unable to connect to a XDS100v2 with a blank serial number

Chester Gillon
Guru 92251 points
Part Number: TMDSICE3359


Tool/software: Code Composer Studio

With CCS 8.2.0.00007 under Linux (Ubuntu 18.04.1 LTS) was unable to use a XDS100v2 with a blank serial number, in that:

a. Attempting to start a debug session or perform a test connection failed with a 'SC_ERR_FTDI_OPEN'.

b. xds100serial reported 'No XDS100 emulators were found on the system'

Whereas CCS 8.2.0.00007 under Windows 10 PRO was able to use the XDS100v2 with a blank serial number:

a. Could start a debug session.

b. xds100serial reported the XDS100v2 and showed a blank serial number.

Once ft_prog was used under Windows to program an automatically generated serial number, the XDS100v2 was then usable with CCS under Linux.

Just reporting this again as in the original thread there was no bug report number listed.

  • 0
    TI__Guru**** 171309 points
    Chester,

    I recall having conversations with folks at the time and the bug was never filed. This is mainly due to the fact that we have been adding the serial number to pretty much all development kits for a long time.

    In Linux we are relying on the open source libftdi for XDS100v2, thus a repair could be possible but its priority will be quite reduced.

    The obvious workaround in this case is to simply add a serial number via the FTProg SW.

    At any rate I filed the bug number DBGTRC-4541.

    Please apologize for the inconvenience.

    Rafael