CCS/BEAGLEBN: Beaglebone White XDS100v2 connection problem

Markus Mayer53

Part Number: BEAGLEBN

Tool/software: Code Composer Studio

I have an old Beaglebone 'white', labelled Rev. A3 that I want to use to go through the PRU labs.

Luckily the Beaglebone has an integrated XDS100v2, as required for the PRU labs. But unfortunately on Linux the connection check fails:

sudo ./ccsv8/ccs_base/common/uscif/dbgjtag -f ~/.ti/ti/1/0/BrdDat/testBoard.dat -rv -o -F inform,logfile=yes -S pathlength -S integrity

-----[Print the board config pathname(s)]------------------------------------

/home/me/.ti/ti/1/0/BrdDat/testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioserdesusbv3.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 be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

(the shell command "sudo ...dbgjtag..." is what 'Verifiy' in CCS runs, as far as I can tell - and this is easier to run than the GUI so I just run the shell command.)

I tried the same thing on Windows and the verification is successful!

The VID:PID is 0403:a6d0 (Future Technology Devices International, Ltd Texas Instruments XDS100v2 JTAG / BeagleBone A3).

On Windows I can't install the PRU compiler, so I'm stuck with Linux. (And Linux is preferrable because the AM33x Linux SDK is only available on Linux - but that's for later.)

Any advice on how to sort this out would be very welcome!

over 7 years ago

0 desouza over 7 years ago

TI__Guru**** 171519 points

Hi,

At around the time that revision A5 was out, there was a change to the FTDI VID/PID of the BeagleBone White board that turned it incompatible with newer releases of CCS. This is described at:

http://processors.wiki.ti.com/index.php/FAQ_-_CCSv5#Q:_I_can.27t_connect_to_my_BeagleBone_in_CCSv5._What_is_happening.3F

After the change, your lsusb should show the VID/PID as below:

user@host:~$ lsusb -d 0403:6010
Bus 003 Device 012: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC

And have one ttyUSB port:

user@host:~$ ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Jul 16 09:51 /dev/ttyUSB0

In addition to that, can you make sure you ran the install_scripts.sh after you installed CCS? This will help with non-root access to the debug probe. Also, if you want user access to its serial port, make sure your user is part of the dialout group (this was a change that happened somewhat recently on Ubuntu).

Hope this helps,

Rafael

Just for reference, a more detailed listing would be:

user@host:~$ lsusb -vd 0403:6010
Bus 003 Device 012: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6010 FT2232C Dual USB-UART/FIFO IC
bcdDevice 7.00
iManufacturer 1 FTDI
iProduct 2 BeagleBone/XDS100V2
iSerial 3 TI2ABMTG
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 55
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 BeagleBone/XDS100V2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 BeagleBone/XDS100V2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Code Composer Studio™︎

Code Composer Studio forum

CCS/BEAGLEBN: Beaglebone White XDS100v2 connection problem