• Locked Locked
  • Replies 4 replies
  • Subscribers 56 subscribers
  • Views 7569 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Problems detecting XDS100v2 under Linux with CCSv6

Steven Hansen
Intellectual 591 points

Hello,

I have an XDS100v2 USB emulator that I have successfully used to debug and program F28335 devices using CCSv5 under Windows. However, I have attempted to migrate to Linux and I cannot get the XDS100 drivers to detect the USB emulator.

Here is the relevant info:

Computer:

Ubuntu 14.04, CCS v6.0.0.00190

XDS100v2 info:

Bus 002 Device 005: ID 0403:a6d0 Future Technology Devices International, Ltd Texas Instruments XDS100v2 JTAG / BeagleBone A3

Here are the last several lines of output from CCS when I use the "Test Connection" button:

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioserdesusb.so'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may one or more of: invalid emulator serial number,
blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the emulator can be located.

[End: Texas Instruments XDS100v2 USB Emulator_0]

Here is the output of the xds100serial utility:

Scanning for XDS100 emulators...

No XDS100 emulators were found on the system.

 


Also, for what it's worth /dev/ttyUSB0 does get populated when the XDS100v2 emulator is connected to the computer, so the FTDI driver must be loading. Also, I have tried to re-run /ti/ccsv6/install_scripts/install_drivers.sh and it seems to succeed, but CCS still cannot detect the XDS100v2.

Any suggestions?

  • TI__Guru**** 168297 points

    Hi,

    It seems this thread fell under the radar. Are you still having this issue?

    I was able to run my XDS100/F28335 controlCARD on Ubuntu 14.04/64 bits and I got no problems.

    A few details: did you install CCS as sudo or as user? If as user, you must run the install_script.sh as superuser (the installer mentions this). This script will install the XDS100 drivers and allow access to them for all users.

    The issue above would also be evidenced if you are able to connect when starting CCS as superuser (and not as user).

    Is /dev/ttyUSB1 also available together with /dev/ttyUSB0? This happens with my XDS100 and it is due to the fact that the FTDI device has two serial connections. If you only see one serial USB port, it is possible something else may be connected and (maybe) conflicting with your XDS100.

    I would also double-check if the udev rules are properly installed. Check if the file /etc/udev/rules.d/71-ti-permissions.rules exists and its contents are somewhat similar to what is shown in the screenshot below:

    Apart from this I am unsure what else may be happening.

    Hope this helps,

    Rafael

  • in reply to desouza
    Intellectual 591 points

    Rafael,

    Sorry for the late reply. I ended up going back to Windows for now, as I couldn't get the XDS100 driver to work under Ubuntu. When I plug in the XDS100, I only see one device populated (/dev/ttyUSB0).

    I did check the udev rules and they are installed properly, and everything was installed with superuser privileges.

    If I get another opportunity I will try to figure out why the USB driver isn't loading properly, as I would prefer to use Ubuntu.

  • in reply to desouza
    TI__Intellectual 760 points

    I also have this problem. lsusb shows two devices belong to the Beaglebone

    Bus 003 Device 024: ID 0451:6141 Texas Instruments, Inc.

    Bus 003 Device 023: ID 0403:a6d0 Future Technology Devices International, Ltd Texas Instruments XDS100v2 JTAG / BeagleBone A3

    xds100serial shows:

    ./xds100serial

    Scanning for XDS100 emulators...

    VID/PID    Type            Serial #    Description

    0403/a6d0  XDS100v1/v2     ?           BeagleBon

    I only see /dev/ttyUSB0 in the device list.  dmesg shows this when I plug the beaglebone in:

    [85898.547003] usb 3-4: new high-speed USB device number 28 using xhci_hcd

    [85898.563095] usb 3-4: New USB device found, idVendor=0424, idProduct=2412

    [85898.563100] usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0

    [85898.563366] hub 3-4:1.0: USB hub found

    [85898.563393] hub 3-4:1.0: 2 ports detected

    [85898.834872] usb 3-4.1: new high-speed USB device number 29 using xhci_hcd

    [85898.853382] usb 3-4.1: New USB device found, idVendor=0403, idProduct=a6d0

    [85898.853387] usb 3-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

    [85898.853390] usb 3-4.1: Product: BeagleBone

    [85898.853392] usb 3-4.1: Manufacturer: FTDI

    [85898.854882] usb 3-4.1: Ignoring serial port reserved for JTAG

    [85898.856175] ftdi_sio 3-4.1:1.1: FTDI USB Serial Device converter detected

    [85898.856212] usb 3-4.1: Detected FT2232H

    [85898.856215] usb 3-4.1: Number of endpoints 2

    [85898.856217] usb 3-4.1: Endpoint 1 MaxPacketSize 512

    [85898.856220] usb 3-4.1: Endpoint 2 MaxPacketSize 512

    [85898.856222] usb 3-4.1: Setting MaxPacketSize 512

    [85898.856397] usb 3-4.1: FTDI USB Serial Device converter now attached to ttyUSB0

    [85901.789483] usb 3-4.2: new full-speed USB device number 30 using xhci_hcd

    [85901.805942] usb 3-4.2: not running at top speed; connect to a high speed hub

    [85901.806818] usb 3-4.2: New USB device found, idVendor=0451, idProduct=6141

    [85901.806823] usb 3-4.2: New USB device strings: Mfr=33, Product=37, SerialNumber=0

    [85901.806827] usb 3-4.2: Product: SUBARCTIC

    [85901.806829] usb 3-4.2: Manufacturer: Texas Instruments

    [85901.849462] rndis_host 3-4.2:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-4.2, RNDIS device, 9a:1f:85:1c:3d:0e

    The message "Ignoring serial port reserved for JTAG" probably explains why I see only one ttyUSB0 in the device list.

    I tried running CCS as super user as well, but it didn't fix the problem.

    Any other suggestion?

    Thanks

  • in reply to desouza
    Prodigy 10 points

    Thanks desouza. I had similar problems with the C2000 Launchpad and CCSv6 running on Linux Mint 13. However, running the command ti/ccsv6/install_scripts/install_drivers.sh as sudo and rebooting the computer resolved the issue. Now the debugger works as expected. Thank you very much for your tips!