Hi all,
This is getting annoying now.
The patched driver which Enrik posted seems to cleanly fix the problem
in the TI driver that USB IDs specified on the module command line do
not work. I am not clear from what Enrik said, whether these are his own
patches, or something he got from Debian. Either way, this is good stuff
that needs to get into the Linux distribution.
Now, new things seem to be breaking. I updated my FC4 and FC5 machines
to the latest kernel RPMS, and it seems something in the core USB serial
handling is broken. The endpoint of the 3410 is 1, and the firmware was
previously being downloaded to endpoint 1. Now both my FC4 and FC5
machines are trying to download to endpoint zero. It seems the
enumeration of the endpoint happens outside the ti_usb_3410_5052 driver,
so I don't think the fault is in that. If I patch the driver to force a
download to endpoint 1, the firmware successfully downloads, but I get a
kernel oops when the device begins normal operation at the end of the
download.
Regards,
Steve
Enrik Berkhan wrote:
Steve Underwood wrote:
Thus looks about right from what I have found so far. However, on
Fedora Core 5 it still doesn't work. I get a failure to download the
firmware.
This works for me, even on FC5 (originally, I've tested on
Debian/testing).
This is my current FC5 setup:
1. add the following line to /etc/modprobe.conf. This ensures that USB
FET support is always enabled when the module is inserted.
# enable TI USB FET430
options ti_usb_3410_5052 vendor_3410=0x0451 product_3410=0xf430
2. add the following to /etc/udev/rules.d/40-mspfet430.rules:
SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{product}=="MSP-FET430UIF
JTAG Tool" \
SYSFS{bNumConfigurations}=="1" \
ENV{MODALIAS}="" RUN+="/sbin/modprobe ti_usb_3410_5052"
SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{product}=="MSP-FET430UIF
JTAG Tool" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"
Additionally, I will attach my patched version of ti_usb_3410_5052.c
(v0.9, from 2.6.17 sources). May be there is a difference ...
Finally, here is the dmesg-report when the USB FET is plugged in:
usb 1-2: new full speed USB device using uhci_hcd and address 8
usb 1-2: configuration #1 chosen from 1 choice
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI
USB 3410 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI
USB 5052 2 port adapter
ti_usb_3410 1-2:1.0: TI USB 3410 1 port adapter converter detected
usb 1-2: reset full speed USB device using uhci_hcd and address 8
usb 1-2: device firmware changed
ti_usb_3410: probe of 1-2:1.0 failed with error -5
usb 1-2: USB disconnect, address 8
usbcore: registered new driver ti_usb_3410
usb 1-2: new full speed USB device using uhci_hcd and address 9
usb 1-2: configuration #1 chosen from 2 choices
ti_usb_3410 1-2:1.0: TI USB 3410 1 port adapter converter detected
ti_usb_3410: probe of 1-2:1.0 failed with error -5
usbcore: registered new driver ti_usb_5052
drivers/usb/serial/ti_usb_3410_5052.c: TI USB 3410/5052 Serial Driver
v0.9
ti_usb_3410 1-2:2.0: TI USB 3410 1 port adapter converter detected
usb 1-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0
Enrik
