You are not logged in.

#1 2014-01-10 18:52:57

dk23
Member
Registered: 2014-01-10
Posts: 2

modprobe ftdi_sio errors

I have a usb device with  FTDI vid of 0x0403 and pid of 0x9e50 that is not in ftdi_sio.ko .
with kernel 3.10.10 I was able to use modprobe and /dev/ttyUSB0 was created when the device was plugged in.

# modprobe -v ftdi-sio vendor=0x0403 product=0x9e50

However under kernel 3.12.6 I get the following errors with modprobe:

[  146.583270] usbcore: registered new interface driver usbserial
[  146.583307] usbcore: registered new interface driver usbserial_generic
[  146.583335] usbserial: USB Serial support registered for generic
[  146.590245] ftdi_sio: unknown parameter 'vendor' ignored                                     
[  146.590254] ftdi_sio: unknown parameter 'product' ignored
[  146.590460] usbcore: registered new interface driver ftdi_sio
[  146.590561] usbserial: USB Serial support registered for FTDI USB Serial Device

when I plug the device in /dev/ttyUSB0 in not created


any insight?

Thank You
dk23

Offline

#2 2014-01-29 23:26:41

fahadsadah
Member
Registered: 2014-01-29
Posts: 1

Re: modprobe ftdi_sio errors

From kernel 3.12, the ftdi-sio module no longer accepts the "vendor" and "product" parameters (commit link). I think it was assumed that this was a debugging feature that should not be used by end users, and so the change was not at all publicised.

The new way to add a new VID/PID pair for the ftdi-sio driver is to write them both, one after the other, to /sys/bus/usb-serial/drivers/ftdi_sio/new_id:

# modprobe ftdi-sio
# echo 0403 9e50 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id

Last edited by fahadsadah (2014-01-29 23:26:52)

Offline

#3 2014-05-21 18:24:21

fulminictus
Member
Registered: 2014-05-21
Posts: 1

Re: modprobe ftdi_sio errors

I have built a FTDI 2232H based JTAG adapter too (yet another one :-).
One MPSSE is used for JTAG and the other one for USB_Serial.
Since Linux 3.12, I'm no longer able to use the vendor and product arguments.

Unfortunately, the solution described above does not work for me either.
The device is detected as USB device, but no /dev/ttyUSB0 entry is created.
If I create the device node manually via mknod, they transport no data.

When connecting the device to USB, syslog says:

==> /var/log/syslog <==
May 21 20:14:08 hlb21 kernel: [ 2611.788147] usb 1-1.3: New USB device found, idVendor=0403, idProduct=bafa
May 21 20:14:08 hlb21 kernel: [ 2611.788154] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 21 20:14:08 hlb21 kernel: [ 2611.788158] usb 1-1.3: Product: OpenGLink_r11
May 21 20:14:08 hlb21 kernel: [ 2611.788161] usb 1-1.3: Manufacturer: FHM
May 21 20:14:08 hlb21 kernel: [ 2611.788165] usb 1-1.3: SerialNumber: 12WP4Q5E
May 21 20:19:57 hlb21 mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
May 21 20:19:57 hlb21 mtp-probe: bus: 1, device: 14 was not an MTP device

I also created a udev rule in /etc/udev/rules.d/45-openglink-permissions.rules:

SUBSYSTEMS=="usb-serial", DRIVERS=="ftdi_sio", SYMLINK+="ttyUSB_FTDI"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bafa", MODE="0664", GROUP="dialout", DRIVERS=="ftdi_sio", NAME="ttyWSN"
ATTR{idVendor}=="15ba", ATTR{idProduct}=="0004", GROUP="dialout", MODE="0660" # Olimex Ltd. OpenOCD JTAG TINY
ATTR{idVendor}=="15ba", ATTR{idProduct}=="002b", GROUP="dialout", MODE="0660" # Olimex Ltd. OpenOCD ARM_USB_OCD_H

When I blank the FTDI EEPROM via MProg, then both USB-Serial converters are detected and /dev/ttyUSB* get created automatically.


Ideas?

Offline

Board footer

Powered by FluxBB