Re: [Ftdi-usb-sio-devel] FT232BM with different bcdDevice

[<am...@sy...>]

I played a little around with the Mprog utility from ftdi and discovered
that a ft232bm with an empty eeprom has the bcdDevice 0x400. As soon as
something (also the defaults) gets programmed in the eeprom with mprog the
bcdDevice changes to 0x200.

> I have a bunch of FT232BL here which is the lead free versions of the
> FT232BM. They have a
> different bcdDevice version then the kernel driver expects:
>
> ftdi_determine_type: bcdDevice = 0x200, bNumInterfaces = 1
>
> With that Version they are detected as FT8U232AM which does not work. When
> I force them to be
> detected as FT232BM they work fine.
> So now I'm not sure how to change the detection routine, without breaking
> detection for the
> other chips.
> This would work:
>
> --- ftdi_sio.c.orig	2008-08-14 10:18:40.000000000 +0200
> +++ ftdi_sio.c	2008-08-14 10:21:16.000000000 +0200
> @@ -825,6 +825,9 @@
>  			dbg("%s: something fishy - bcdDevice too low for multi interface
> device",
>  				__FUNCTION__);
>  		}
> +	} else if (version == 0x200) {
> +		// Assume its an FT232BL (lead free version of FT232BM)
> +		priv->chip_type = FT232BM;
>  	} else if (version < 0x200) {
>  		/* Old device.  Assume its the original SIO. */
>  		priv->chip_type = SIO;
>
> But since I did not found a list of all bcdDevice for all ftdi chips, I
> don't know if there is
> a FT8U232AM with the same bcdDevice and I need to make a complete
> different detection.
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>