Hi Robin,
See doc/EEPROM-structure, and git commit a45ea32b4ffd. I believe the
existing code intentionally goes against what AN_121 describes, as
written in that doc.
Either way, the _230X is decribed in its datasheet sa having an
identical EEPROM structure as the _R, so any patch that treats them
differently is probably not correct.
Jim
Robin Haberkorn wrote:
> Hello,
>
> I'm working on the libftdi Git head.
> I found that ftdi_eeprom_build's user area size check for type R
> chips is too restrictive. See the patch attached and
> http://www.ftdichip.com/Support/Documents/AppNotes/AN_121_FTDI_Device_EEPROM_User_Area_Usage.pdf
>
> Best regards,
> Robin
>
>
> --
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
> To unsubscribe send a mail to
> libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
> commit 41cbc9f98f242e273fa48c8043f3089f298f2fd5
> Author: Robin Haberkorn <haberkorn@xxxxxxxxxxxx>
> Date: Thu Jan 8 22:37:25 2015 +0100
>
> fixed EEPROM user-area space checks for FT232R and FT245R chips in
> ftdi_eeprom_build()
>
> according to FTDI Application Note 121 ("Accessing the EEPROM User Area
> Of FTDI
> Devices"), the FT232R and FT245R chips have a total 48 words (96 bytes) of
> user area space available for descriptive strings.
>
> diff --git a/src/ftdi.c b/src/ftdi.c
> index 47e6959..ea487d0 100644
> --- a/src/ftdi.c
> +++ b/src/ftdi.c
> @@ -2604,6 +2604,8 @@ int ftdi_eeprom_build(struct ftdi_context *ftdi)
> user_area_size = 90; // two extra config bytes and 4 bytes
> PnP stuff
> break;
> case TYPE_R:
> + user_area_size = 96;
> + break;
> case TYPE_230X:
> user_area_size = 88; // four extra config bytes + 4 bytes
> PnP stuff
> break;
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
