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.

CCS5.2.1.00018_linux and ubuntu 12.04 LTS 64bits : XDS560 emu not recognized ...

Other Parts Discussed in Thread: CCSTUDIO

Hi All,

Here's an interesting case I'm phasing :

The situation:

  • Ubuntu 12.04LTS 64 bits is freshly installed on a new PC.
  • Installed 32bit application libraries with   sudo apt-get install ia32-libs
  • Installed libjpeg library with                              sudo apt-get install libjpeg62:i386
  • CCS5.2.1.00018 for linux installed OK and has a full License
  • C6678 EVM with native XDS100 is coming up fine.

The Issue

  • the same EVM 6678 as above, either now connected with its XDS560v2 Mezzanine emulator or an external Blackhawk BH-USB-560M emulator is not coming up at emulator launch time (see below traces).

What can cause such behaviour ? we replicated the issue on two different Computers, each time the same issue, as if the XDS560 is not recognized.

Any comments welcome.

Cheers.


[Start] (this is with the mezzanine xds560v2)

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/3205019477/0/0/BrdDat/testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560v2u.out'.
E_RPCENV_IO_ERROR(-6) No connection: open failed: code 19
Download failed for file /opt/ti/ccsv5/ccs_base/common/uscif/./././././xds560v2.out

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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the named emulator via USCIF ECOM has failed.

[End]

[Start] (this is with an external Blackhawk BH-USB-560M)

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/3205019477/0/0/BrdDat/testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560usbm.out'.
E_RPCENV_IO_ERROR(-6) No connection: Emulator open error
Failed to open i/o connection (bh560usbm:0)

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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the named emulator via USCIF ECOM has failed.

[End]

  • One quick thing to try is to check the udev rules file for the blackhawk drivers.http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/81/5277.71_2D00_bh_2D00_permissions.rules

    I know this was fixed but maybe it is still there in 5.2.1.  

    You could try updating the rules file and then rerunning the driver install script (remember to run the script as sudo).

    John

  • I've proceed with the install script again. Execution went OK. But CCS still claims for the same error when launching the XDS560 Mez .

    //PM

  • What do you see when you run lsusb?  There should be an item listed for "Electronic Warfare Assoc."

    I will download and install 5.2.1.  I suspect that it is going to work for me though since the drivers are already installed.  Maybe I will try to uninstall them first.

  • I found a 5.2.1 install on this machine.  I get the same error as you when running as user.  When I run as sudo I can test connection fine.  This is the same problem someone else was seeing and that updated rules file fixed it.  I am going to try that now.

    John

  • Ok.  I got it working.  I knew this had been fixed ;)

    Check for updates and install the latest Blackhawk package.  I also installed the latest TI emulation package but you shouldn't need that.

    This will prompt you to restart CCS.

    During the installation the blackhawk installer will detect that you are running in user mode and remind you to run the driver install script (shows you where) when done.  This is because that permissions file has changed and you need to update the drivers.

    Once the install is done close CCS and run the script.  Also unplug your emulator's usb cable and plug it back in.  I had to unplug the emulator and plug it back in otherwise the changes did not take effect.

    Launch CCS

    You can now connect

    John

  • Hi John,

    It answers partially the question since I can launch the XDS560Mez now on C6678 EVM, but only as root. For this I had to enable the root account on Ubuntu for having a full "su" profile (done via 'sudo passwd' and then entering the choosen root pw).

    If I launch the ccstudio under /opt/ti/ccsv5/eclipse from the command line with the command sudo ./ccstudio , it keeps failing and not connecting. But if I change profile to SuperUser : su, and then as 'root @ user ...'  I launch from the command line ./ccstudio, then the setup works OK.

    So I still have the issue of getting this also working as 'user'

    Also, wrt your earlier post, I also get the usb ID 0b1e:0009 when I connect my XDS560 mez .

    Cheers,

  • I am able to run as user.

    I did a fresh install as user

    Ran the driver install script as sudo

    Ran CCS as user and updated the Blackhawk package

    Ran the driver install script as sudo

    Unplugged and replugged by emulator

    Ran CCS as user

    I am able to use the Mezz card

    Since you are installed on /opt I am guessing that your initial install was as sudo so you would need to run CCS as sudo in order to be able to update the software.

  • Yes, I did the full install as sudo . I'll now verify again the full procedure as 'user' for CCS5.2.1.00018.

    Thanks , this helps definitivelly.

    Cheers,

     

  • Hi John,

    some updates:

    After reinstalling the CCS5.2.100018 as 'user' (following a meticulous deinstall of the former setup), I am still at a similar point. I can access the BH560 Mez when I launch the CCS from the command line with SUDO, but definitivaly not with my use profile. I verified the same when launching the 'dbgjtag' command the command line . It gives a positive diagnostic when I'm using sudo, but not when I ran it as user.

    So the questions is linked to the binding of 'rights'. Former install was done as root (using sudo), is was removed for the OS according to the unsinstall scripts. New install is made as 'user', but the queries to the USB device in Linux must have root rights. Is there any call stack out of CCS that I can review to see which file still having 'root' rights blocks the connection to the driver when launched form user ?

    The only diff between your install and mine is that I didn't reinstall the ubuntu OS fresh. Did anything survive during the clean out ?

    I as said earlier in the post , this issue is resolved in CCS5.3, but I have to stay with the CCS5.2.1 for still some times...  

    Cheers,

  • Just to confirm.  After installing CCSv5.2.1 as user did you Update the Blackhawk package via update manager and then run the driver install script again (as sudo)?

    John

  • Ok, I have the explanation : I had actually another issue with the update manager which proceeded with rolling over the listed sites but actually downloaded nothing. First I enabled the ErrorLog window to see every log for the tool, then saw that I got messages about malformed packects from SOCKS ans HTTPS.... I then verified my Preferences settings for the Network Connections and observed that during the installation the CCS captured the proxy entries form my system settings, and that the "Active Provider" was turned to "Native". Those settings do appear in Dark Shadow in the Proxy entry list. I then changed the Active Provider to Manual and only stuffed the HTTP proxy with my proxy host, leaving the HTTPS and SOCKS empty, see picture below.

    From that stage I was able to correctly download the BlackHawk updates from the web repository and proceed the same way as listed by you earlier in this msg thread.

    Now I have full access to my XDS560Mezz .

    Thanks for your support .