libftdi Archives

Subject: Re: EEPROM handling work

From: DJ Delorie <dj@xxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Wed, 15 Sep 2010 12:56:05 -0400
> Daring now to give my code a try?

When I get time, sure.  My tool can backup and restore eeproms anyway
(based on my last attempt to do eeprom editing, which didn't go so well :)

Hmmm... I'll try it on my ft2232h board, it has a blank external
eeprom anyway.

But the tool I ended up writing is a tweaker - it always reads the
eeprom *anyway*, lets you tweak the values, then puts it back in:

  $ ./eeprom -cbus2 io
  1 device connected
  Dev  0: Filename "103", Manf "FTDI", Desc "FT232R USB UART", Ser# "A600dOgq"
  writing out new EEProm...

I've not yet had the need to write out a whole new eeprom from
scratch, so why is that the default use model?  I would think we'd
want to encourage people to do a read/modify/write cycle instead, for
chips with built-in eeproms like the 232R.

libftdi - see for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread