Enrik Berkhan wrote:
Steve,
Steve Underwood wrote:
If anyone can twell me how to configure this, they get hero status. :-)
When I put the following rule in some file under /etc/udev/rules.d, the
driver gets loaded. As I didn't fix the id-on-command-line issue, I
haven't tested if it really works with firmware loading etc.
BUS=="usb" ACTION=="add" SYSFS{product}=="MSP-FET430UIF JTAG Tool"
SYSFS{bNumEndpoints}=="01" RUN+="/sbin/modprobe ti_usb_3410_5052 vendor_3410=0x451 product_3410=0xF430"
This rule certainly gets things started. When I plug in the FET tool the
driver is loaded, but then I get "ti_download_firmware - error
downloading firmware". The older rule create two phases - a boot load
phase, and a running phase. I guess something like this is needed in the
rules here to get the device up and running. Lots of USB devices need
this kind of download operation. I found a couple of examples of
downloading from a firmware file, but the TUSB3410 driver has the
firmware inside it. I am still not clear how this works.
Thanks to all the people who responding to my request. The responses
have certainly cut my learning time. I suspect when I properly
understand how this new udev scheme works it will look a lot cleaner
than the old hotplug scheme.
Regards,
Steve
