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.

Trouble with CCS 5 on Linux

Other Parts Discussed in Thread: CCSTUDIO

I am trying to get CCS 5 running under Linux (currently using slackware 14.1)  I have it all installed.  I am tring one of the example programs.

when I go to debug it, I get the following error 

Error connecting to the target:
(Error -151 @ 0x0)
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.
(Emulation package 5.1.232.0)

when I run the utility as suggested I get the following output

Scanning for XDS100 emulators...

VID/PID    Type            Serial #    Description
0403/a6d0  XDS100v1/v2     SD5505      Texas Instruments Inc.XDS100 Ver 1.

(I did have to do a chmod +s on the file so I could run it as a standard user)

I have tried running ccstudio as root (just to test things out) and it did work, but I would rather not have to run it as root.  Is there any way I can make this work running as a standard user?  I have already tried to chmod +s the ccstudio bin just to test but that cause an issue where ccstudio would not even load till I chmod -s on ccstudio.

Edit: continuing to play with it, I have found that if I run it via sudo it works also.  Not sure I want to add the users all to sudo.  but I am looking at that as an option.

Any help would be appreciated.

Final: edit, I found a acceptable work around for me, I downloaded gksudo compiled and installed it, I now wrape the launching of CCS5 in that, I just have to type my user password in each time i want to run it, but it appears to work now.  But I would like other options that might be more correct then the solution I came up just now.

  • Good to hear you found a workaround.

    Michael OConnor said:
     But I would like other options that might be more correct then the solution I came up just now.

    If you don't install under root, you need to run the install_drivers.sh script after installation as mentioned here:

    http://processors.wiki.ti.com/index.php/Linux_Host_Support#Installation_Instructions

    Did you do that and it still failed?

    Thanks

    ki

  • I did run that command, and it did not work last night  but going off of that I tried something else.  The true answer kind of is related but not exactly that (so I am going ot just mark yours as the answer) I had to force a restart of udeve

    root@home:/etc/rc.d# ./rc.udev restart
    Restarting udevd is STRONGLY discouraged and not supported.
    If you are sure you want to do this, use 'force-restart' instead.
    root@home:/etc/rc.d# ./rc.udev force-restart
    Restarting udevd
    root@home:/etc/rc.d# 

    is what finnally did it