Hello,
On Friday, 22. May 2009 00:56:50 Karl Cunningham wrote:
> We're setting up a programming station for FT245RL chips using libftdi
> 0.15 in Ubuntu. When we program chips using libftdi the first two bytes
> of the eeprom are being programmed with 0's. The problem is that chips
> programmed this way aren't recognized by Mprog or the Windows driver.
>
> When a fresh chip is read using libftdi, the first two bytes appear to
> be set to 0x01 and 0x40, respectively. After programming with Mprog,
> they are 0x09 and 0x40.
I have an old version of the eeprom documentation which mentions
the first two bytes as "configuration value" with 0x00 0x00.
No further explanation is given.
Another document for the FT2232 mentions something like this,
I guess the values are the same for the FT234RL type chips:
Bit 2,1,0 - '000' = A part is UART RS232
- '001' = A part is 245 fifo mode
- '010' = A part is 245 fifo mode CPU target
- '100' = A part is fast serial
Bit 3 - '1'= Load VCP drivers for A
Bit 4 - '1'= High Drive Current on Port A
Bit 5 -
Bit 6 -
Bit 7 -
Bit 10,9,8 - '000' = B part is UART RS232
- '001' = B part is 245 fifo Mode
- '010' = B part is 245 fifo Mode CPU target
- '100' = B part is Fast Serial
Bit 11 - '1'= Load VCP drivers for B
Bit 12 - '1'= High Drive Current on Port B
Bit 13 -
Bit 14 -
Bit 15 -
The values for the FT2232 seem to correspond to the values DJ Delorie
found while reverse engineering the 2232 eeprom bits.
Maybe this helps someone to cook up a patch.
Cheers,
Thomas
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
