I tried both of these with no luck (if it's QHY5 based, these seemed like a reasonable choice)
(only one at a time)
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="29a2", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="29a2", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME}"

dmesg output was
[50756.552342] usb 1-1.4.1: new high-speed USB device number 13 using dwc_otg
[50756.682735] usb 1-1.4.1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[50756.683109] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=296d
[50756.683121] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[50756.683129] usb 1-1.4.1: Product: QHY5-CMOS
[50756.683138] usb 1-1.4.1: Manufacturer: QHY_CAMS
[50756.684148]usb 1-1.4.1: device descriptor read/64, error -110

I do a bit of hardware development, so I took a look at the camera PCBs to see if the IC markings would offer any suggestions, they had all had their markings sanded off. The camera still works with the windows drivers, so nothing has caused permanent damage. I might take a look at the windows driver to see if I can figure out what's going on.

Read More...