libftdi Archives

Subject: Re: SOLVED: Release 0.15 and the ft2232 data loss.

From: George Boudreau <george.boudreau@xxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 23 Mar 2009 13:05:30 -0400


On Mon, Mar 23, 2009 at 12:20 PM, Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> wrote:
On Monday, 23. March 2009 16:55:47 David Challis wrote:
> The line in the patch:
>
>       else if (dev->descriptor.bcdDevice == 0x800)
>               ftdi->type = TYPE_2232H;
>
> for the FT2232H should be:
>
>       else if (dev->descriptor.bcdDevice == 0x700)
>               ftdi->type = TYPE_2232H;

Ah ok. I did this by looking at the output provided from George Boudreau.
 
It seems my FT2232H mini/mod may be defective. Although the silkscreen says FT2232H and the ftdi chip reads FT2232HQ  note the output. It reads as a 'Quad RS232' and enumerates 4 USB ports.  When I explored this chip module on a windows machine I received the same results, 4 USB ports. 

This output may be appropriate for a FT4232H device but not a FT2232H


If I understood Uwe Bonnes correctly, this could read:

if (dev->descriptor.bcdDevice == 0x700 || dev->descriptor.bcdDevice == 0x800)

Right?


> With your patch applied, my proposed new ftdi_read_data() is:

Please resend as a patch, the line endings got mangled.
Also this will make review of the changes easier. Thanks.

Thomas


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx




libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx


Current Thread