Mike, > the current usbblaster driver lists itself as needing libftdi, and it > includes > ftdi headers, but i cant see anywhere in the code where it actually calls any > ftdi functions.
The include probably was a remainder of the usbconn restructuring. It's not required, right. However, usbblaster.c relies on libftdi to talk to the FT245 device. These devices add status bytes in the data stream, so libftdi (and libftd2xx) are required to provide a transparent channel for application code. libftdi/libftd2xx usage is encapsulated in tap/usbconn/libftdi.c and libftd2xx.c. Both abstract the library-specific calls to the usbconn-API. While usbconn/libusb.c exhibits the same interface, it can't talk the FTDI vendor transport protocol. BTW it doesn't implement usbconn_read and usbconn_write functions. > after a simple test build of disabling ftdi i urjtag, > usbblaster still builds & links without warnings/errors (i dont actually have > the cable). so ive gone ahead and committed that. Code will link since usbblaster.c plugs into the usbconn.c API which is always there. But it can't talk to the FT245 device for protocol reasons without libftdi/libftd2xx support. Just checked with a usbblaster clone - it doesn't work in r1804 while it did in r1802. Cheers Arnim ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
