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

[Francisco E. <pac...@gm...>]

 Thank you, Timr,

<timr <at> probo.com> writes:

> On Mon, Apr 27, 2009 at 01:03:31AM +0200, Francisco Escarpa wrote:
> > 
> > I', trying to interface with an astronomic camera (still image, long
> > exposure) based on Micron MT9M001 and cypress cy7c68013, on Opensuse
> > 11.1(X86-64)
> > 
> > 
> Did you actually buy this as a finished product?  If so, this manufacturer 
> is deserving of a lawsuit.
> > ...
> >   iManufacturer           1 Cypress
> >   iProduct                2 EZ-USB FX2
> >   iSerial                 0
> 
> 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?

> >..
> >         wMaxPacketSize     0x0040  1x 64 bytes
> 
> That's invalid.  A bulk endpoint in a high-speed device MUST have a 
> max packet size of 512.  There is no other choice.
> 
>..
> >         wMaxPacketSize     0x0400  1x 1024 bytes
> 
> This ALSO is invalid.  You can't use 64, and you can't use 1024.  The 
> ONLY valid choice for a bulk endpoint is 512.  The 64-byte endpoint 
> might be made to work, but 1024 certainly cannot.
> 
> Also, there are no alternate settings in these descriptors.  If there are
> supposed to be alternate settings, then my guess is that your firmware
> load did not work.

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?

Thanks in advance,


Paco.