Michel Catudal wrote: > Dirk Behme a écrit : > >> Now that I'm able to easily build with libftdi and libftd2xx, I tried >> libftd2xx (libftd2xx0.4.16.tar.gz), too. >> >> While libftdi works fine, with libftd2xx I get: >> >> -- cut -- >> ... >> Debug: 58 3 ft2232.c:1412 ft2232_init_ftd2xx(): 'ft2232' interface >> using FTD2XX with 'flyswatter' layout (0403:6010) >> Error: 59 4 ft2232.c:1455 ft2232_init_ftd2xx(): unable to open ftdi >> device: 2 >> Error: 60 11 ft2232.c:1470 ft2232_init_ftd2xx(): ListDevices: 0 >> -- cut -- >> >> Any idea what might be wrong here? Just in case somebody has a better >> idea than "use open source an no binary driver" ;) >> >> Thanks >> >> Dirk >> >> P.S.: This is with recent SVN 1293. >> >> Working libftdi output: >> >> Debug: 58 3 ft2232.c:1537 ft2232_init_libftdi(): 'ft2232' interface >> using libftdi with 'flyswatter' layout (0403:6010) >> Debug: 59 23 ft2232.c:1579 ft2232_init_libftdi(): current latency >> timer: 2 >> Debug: 60 24 ft2232.c:1981 flyswatter_init(): 80 18 fb >> Debug: 61 25 ft2232.c:2004 flyswatter_init(): 82 08 0c >> Debug: 62 26 ft2232.c:259 ft2232_speed(): 86 01 00 >> Debug: 63 30 openocd.c:158 handle_init_command(): jtag interface init >> complete >> >> > > I get similar results with Olimex Tiny dongle if I run openocd from > user. I have to either run sudo, root or make a chmod a+s on openocd.
Running it as root does the trick. chmod a+s didn't help. I wonder why open source libftdi is able to do the job, but libftd2xx needs to do some root stuff. Anyway, thanks Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
