i see in the archives that someone else was having trouble with interface A on a 4232. i'm using a mini-module. using the example bitbang_ft2232.c (substituting 6011 for 6001 for the device id), and also using a copy i've been modifying for my purposes, which only opens one interface, i can get success on interface B, but not on interface A.
at first i thought it was simply a bug in the interface and index initialization for interface A, since ftdi_set_interface() clearly handles it quite differently, but gdb says things are set up properly by the time the bulk write is attempted. here's output from bitbang_ft2232.c: $ sudo ./bitbang_ft2232 ftdi open succeeded(channel 1): 0 enabling bitbang mode(channel 1) ftdi open succeeded(channel 2): 0 enabling bitbang mode (channel 2) startloop porta: 00: 0x01 porta: 00: 0x02 write failed on channel 1 for 0x2, error -110 (usb bulk write failed) portb: 00: 0x01 portb: 00: 0x02 porta: 01: 0x01 write failed on channel 1 for 0x1, error -110 (usb bulk write failed) porta: 01: 0x02 write failed on channel 1 for 0x2, error -110 (usb bulk write failed) portb: 01: 0x01 portb: 01: 0x02 porta: 02: 0x01 write failed on channel 1 for 0x1, error -110 (usb bulk write failed) porta: 02: 0x02 write failed on channel 1 for 0x2, error -110 (usb bulk write failed) portb: 02: 0x01 portb: 02: 0x02 porta: 03: 0x01 write failed on channel 1 for 0x1, error -110 (usb bulk write failed) porta: 03: 0x02 write failed on channel 1 for 0x2, error -110 (usb bulk write failed) portb: 03: 0x01 portb: 03: 0x02 (i'm running the 0.16 release, which i see is mostly identical to current git.) anyone taken a look at this? i only need one interface, so i'll just use interface B for now... paul =--------------------- paul fox, [email protected] (arlington, ma, where it's 57.4 degrees) -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
