Thanks for the tip, Dominic. I almost have it working.
I found this page helpful.
http://www.reactivated.net/writing_udev … erminology
The thread you sent me to had the rules file named “45-ft2232.rules”. Just a heads up that that file name might not work depending what is in the later scanned files, ie those starting with a number greater than 45. In my case the general rules file for my system started with 50 and it reassigned the permissions for USB devices.
So, I renamed my file to be 55-myusb.rules and it goes as follows:
#OLIMEX Debugger
SYSFS{idProduct}==“0003”, SYSFS{idVendor}==“15ba”, MODE=“777”, OWNER=“me”, GROUP=“users”
#PL2303 USB SERIAL DEVICES
SYSFS{idProduct}==“2303”, SYSFS{idVendor}==“067b”, MODE=“664”, OWNER=“me”, GROUP=“users”
It seems to have worked, because a) the permissions work for ttyUSB* devices now, which is a great thing in itself and b) I have this in /dev/
crwxrwxrwx 1 me users 442, 2054 Jan 18 11:52 /dev/usbdev2.7_ep00
crwxrwxrwx 1 me users 442, 2054 Jan 18 11:52 /dev/usbdev2.7_ep02
crwxrwxrwx 1 me users 442, 2054 Jan 18 11:52 /dev/usbdev2.7_ep04
crwxrwxrwx 1 me users 442, 2054 Jan 18 11:52 /dev/usbdev2.7_ep81
crwxrwxrwx 1 me users 442, 2054 Jan 18 11:52 /dev/usbdev2.7_ep83
And yet, I get this when I try to run openocd:
$ openocd -d3
Info: openocd.c:84 main(): Open On-Chip Debugger (2006-11-22 14:00 CEST)
Debug: jtag.c:1217 jtag_init():
Debug: ft2232.c:1244 ft2232_init(): ‘ft2232’ interface using FTD2XX with ‘olimex-jtag’ layout
Error: ft2232.c:1286 ft2232_init(): unable to open ftdi device: 2
If I run as root, it works fine. Is there something else I need to set other than the USB port permissions ?
/usr/lib
ls -l libftd*
lrwxrwxrwx 1 root root 34 Jan 16 15:08 libftd2xx.so.0 → /usr/local/lib/libftd2x
/usr/local/lib
ls -l libftd*
lrwxrwxrwx 1 root root 19 Jan 16 14:52 libftd2xx.so → libftd2xx.so.0.4.13
-rwxr-xr-x 1 root root 319466 Jan 16 14:52 libftd2xx.so.0.4.13
What am I missing ?