Beaglebone "STOP MODE" (Jtag) debugging with CCS

GoogleGroups
1

I can’t connect to the JTAG USB emulator of my beaglebone Rev4.
Here is the message when testing connection:

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

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

/home/user/.TI/1548333067/0/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 ‘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]

Notice that my beaglebone is correctly started with the BSP and the two FTD1 port are visible as ttyUSB0 and ttyUSB1 and i use ttyUSB1 for the terminal emulation on the board.

Notice also that i’m running ubuntu 11.04 in a virtual box on MacOSx.

Last notice the result of the required test command:
sudo ./xds100serial
Scanning for XDS100 emulators…

VID/PID Type Serial # Description
0403/a6d0 XDS100v1/v2 ? BeagleBon

Any help welcome

2

I encountered the same problem. The solution is cleverly hidden in the “README_FIRST.txt” file which is part of the original CCS install files.

In “README_FIRST.txt”, after it provides the steps for installing CCS, it mentions that the emulation (e.g. JTAG adapter) drivers won’t install properly if the user didn’t (or doesn’t want to) run the setup as root.

It then points the user to an install script created by the installer under /ccv5/install_scripts/ that must be run as root for the drivers to work.

There are also similar instructions written here:

http://processors.wiki.ti.com/index.php/Code_Composer_Studio_v5_Users_Guide#Installing_Emulator_Support