The problem is the device is recognised by RPi and lists correctly from dmesg
Code: Select all
usb 1-1.2.3: new full speed USB device number 5 using dwc_otg usb 1-1.2.3: New USB device found, idVendor=0403, idProduct=6001 usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.2.3: Product: USB <-> Serial usb 1-1.2.3: Manufacturer: FTDI usbcore: registered new interface driver usbserial USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usbserial: USB Serial Driver core USB Serial support registered for FTDI USB Serial Device ftdi_sio 1-1.2.3:1.0: FTDI USB Serial Device converter detected usb 1-1.2.3: Detected FT232BM usb 1-1.2.3: Number of endpoints 2 usb 1-1.2.3: Endpoint 1 MaxPacketSize 64 usb 1-1.2.3: Endpoint 2 MaxPacketSize 64 usb 1-1.2.3: Setting MaxPacketSize 64 usb 1-1.2.3: FTDI USB Serial Device converter now attached to ttyUSB0 usbcore: registered new interface driver ftdi_sio ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
I do not know what the problem is, the FTDI driver has been part of the kernel for some time, the avenue I am pursuing now is that the driver is not ARM compatible, the FTDI web site doesn't list an ARM linux driver (cant say if that's even relevant).
There is this http://www.ftdichip.com/Support/Documen ... ndroid.pdf regarding cross compiling to ARM (for Android).
So my train of thought is that the current driver is not ARM compatible and requires compiling for ARM, with all that entails and the pitfalls associated.
However I may be barking up completely the wrong tree so any more experienced kernel/driver peeps with a thought?