Enrik Berkhan wrote:
Steve Underwood wrote:

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.

My rule would be for phase one (SYSFS{bNumEndpoints}=="01", the device
with loaded firmware would have two endpoints).

Nonsense, its bNumConfigurations, of course.

Now I have the following working ruleset:

SUBSYSTEM=="usb_device" ACTION=="add" SYSFS{product}=="MSP-FET430UIF JTAG Tool" 
\
  SYSFS{bNumConfigurations}=="1" \
  RUN+="/sbin/modprobe ti_usb_3410_5052 vendor_3410=0x%s{idVendor} 
product_3410=0x%s{idProduct}"

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'"

Enrik

Reply via email to