|
From: Francisco E. <pac...@gm...> - 2009-04-28 19:07:10
|
Tim Roberts <timr <at> probo.com> writes: > > Francisco Escarpa wrote: > > <timr <at> probo.com> writes: > > No, this is the same method used by all virtually FX2 devices. Is this > firmware that YOU wrote, or that they supplied? If you wrote it, you > should change the VID/PID to one of your own, instead of using the > Cypress numbers. Those numbers are known to be one of the Cypress > samples, and it's quite possible that your udev is set up to load a > standard Cypress driver for them. The firmware came from the maker of the camera. I created the following udev rule to activate the camera: # Reglas para arrancar y cargar el firmware de la cámara # QHY5 o equivalente (OrionStarshoot Guider ...) # Paco Escarpa, 25 de febrero de 2008 # Camera inserted. # Vendorid & Prodid: Orion Starshoot SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1608", ATTR{idProduct}=="0901", RUN="/sbin/fxload -t fx2 -D $ENV{DEVNAME} -I /lib/firmware/QHY5.hex" # This is the ID presented once the firmware has been loaded. # idVendor and idProduct match Cypress FX2 USB chips. SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0547", ATTR{idProduct}=="1002", ENV{DEVICE}!="", SYMLINK+="qhy5", MODE="0666" > Vendor requests use the control pipe. They always work, even if no > interface is claimed. The packet sizes are clearly wrong, and it's > quite possible that's causing your final problem. However, if the > software expects to select a different alternate setting, then your > firmware isn't going to work. Are you sure the firmware you have is > supposed to work with the software you are using? Is it possible the > software is supposed to work with the camera as it is first plugged in? It's supposed to work, must be the same included in the .sys file on windows. XP (no Vista), as the maker sent to me. As far I can see from your comments, should be better to write a new one from scratch :-) |