Hallo,
habe das gleiche Problem. Hast du eine Lösung gefunden? Meine Regel sieht ähnlich aus:
BUS=="usb", ACTION=="add", SYSFS{product}=="AVRISP mkII", GROUP="users", MODE="0666", SYMLINK+="avrdev"
LG Avedo
EDIT:
Here is the output of udevadm info --name=/dev/bus/usb/003/004 --attribute-walk:
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-5':
KERNEL=="3-5"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{bDeviceSubClass}=="00"
ATTR{bDeviceProtocol}=="00"
ATTR{devpath}=="5"
ATTR{idVendor}=="03eb"
ATTR{speed}=="12"
ATTR{bNumInterfaces}==" 1"
ATTR{bConfigurationValue}=="1"
ATTR{bMaxPacketSize0}=="16"
ATTR{busnum}=="3"
ATTR{devnum}=="4"
ATTR{configuration}==""
ATTR{bMaxPower}=="100mA"
ATTR{authorized}=="1"
ATTR{bmAttributes}=="c0"
ATTR{bNumConfigurations}=="1"
ATTR{maxchild}=="0"
ATTR{bcdDevice}=="0200"
ATTR{avoid_reset_quirk}=="0"
ATTR{quirks}=="0x0"
ATTR{serial}=="000200045210"
ATTR{version}==" 1.10"
ATTR{urbnum}=="9"
ATTR{ltm_capable}=="no"
ATTR{manufacturer}=="ATMEL"
ATTR{removable}=="unknown"
ATTR{idProduct}=="2104"
ATTR{bDeviceClass}=="ff"
ATTR{product}=="AVRISP mkII"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb3':
KERNELS=="usb3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="3"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="14"
ATTRS{bcdDevice}=="0319"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:14.0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="80"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.19.2-1-ARCH xhci-hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="xHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:14.0':
KERNELS=="0000:00:14.0"
SUBSYSTEMS=="pci"
DRIVERS=="xhci_hcd"
ATTRS{irq}=="26"
ATTRS{subsystem_vendor}=="0x1462"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0330"
ATTRS{driver_override}=="(null)"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000000f"
ATTRS{device}=="0x8c31"
ATTRS{enable}=="1"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-3"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x7821"
ATTRS{numa_node}=="-1"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
EDIT 2:
The following line solves the permission problem for me:
# Set permissions for the AVRIspMKII programmer granting read- and write-access for every user.
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2104", MODE="0666", SYMLINK+="avrispmkII-%n"
However, it leaves me with a new problem:
avrdude: stk500v2_command(): command failed
avrdude: stk500v2_program_enable(): bad AVRISPmkII connection status: Target not detected
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
Error while burning bootloader.
EDIT 3:
Ok the last error was caused by wrong wiring. Forgot to connect +3.3V to VCC pin. No it works just fine.