Re: [Libusb-devel] Problem with libusb_0.7, cypress fx2LP and linux

[Tim R. <ti...@pr...>]

Francisco Escarpa wrote:
> <timr <at> probo.com> writes:
>   
>> 0547/1002 is the VID/PID exposed by an unconfigured FX2.  It is a number
>> that belongs to Cypress.  Manufacturers are SPECIFICALLY PROHIBITED by
>> the Cypress license to release products that use this number.  They are 
>> supposed to change it to their own ID numbers.  It's not hard to do.
>>     
>
> The vid/pid exposed when the camera is first plugged is 1618/0901 (QHY) or other
> for different resellers (Orion, Luna ...)
> Cypress vid/pid appears AFTER renumeration and firmware load. Maybe this
> confuses UHCI driver?
>   

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.

> Calling to vendor_requests I got correct answers, and I got the same results
> with different fx2 firmware loaders (cycfx2prog-0.41, fx2_programmer). Could be
> the misdefinition of maxpacket the final cause of the problem?, or must be a
> general firmware failure?
>   

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?

-- 
Tim Roberts, ti...@pr...
Providenza & Boekelheide, Inc.