Nuno Lucas wrote:
> I just started toying with a FTDI USB-Key on Linux, using libftdi and the
> ftdi_eepropm utility. The kernel says it's an FT232RL chip on "dmesg".
>
> Well, as a noob on this things, I tried to just replace the vendor,
> product and serial strings, and had half success at that. The success was
> that the write worked, but on the other hand it seems my settings broke
> the chip and it can't be writen any more (although it works ok reading).
What version of libftdi are you using? Versions prior to 0.16 have a
bug where the latency timer isn't set properly for writing to EEPROM.
In my experience, not setting this timer means that EEPROM writes
sometimes work on the first time, but subsequent attempts fail.
Erasing the EEPROM never works on the FT232R.
> It seems I wrote the eeprom for a "self powered" device instead of "bus
> powered" one and the MaxPacketSize for the Input EP was zeroed.
Neither of those should be a problem. Writing the EEPROM uses
endpoint 0x80, not 0x81.
-jim
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
