Subject: Re: Writing EEPROM on FT232R / FT245R
Marius Kintel wrote:
+ /* These commands were traced while running MProg */
+ ftdi_poll_modem_status(ftdi, &status);
+ ftdi_set_latency_timer(ftdi, 0x77);
ftdi_usb_reset and ftdi_poll_modem_status are unnecessary here
I suspected that, but MProg appears to send them so I was afraid deviating from my traced communication could break smth. Anyway, I'll give it a spin without those calls to verify that it works at least with my setup. I've also built myself an FT245R board now, so I can test with that chip as well.
Nice! Please let me know if I can remove the two other function calls.
Also I did another fix in the eeprom_decode code:
Would be nice if you could verify if the code is still working for you :-)
I just subscribed to this list because I had the same situation as
Marius Kintel did in his original post of the thread started on 25 Feb
2009 -- trouble programming an FT245R with libftdi. My apologies that
this message will likely not be threaded into the original in the archives.
In the email in this thread on 12-Mar-09 from Jim Paris and in the FTDI
datasheet, I see mention of setting the latency timer to 77 (decimal)
milliseconds to program the FT245R. The patch appears to set it to 0x77
I assume the value of 77ms is a minimum and 0x77 seems to work fine too,
but I wanted to point this out in case it matters to anyone.
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
Re: Writing EEPROM on FT232R / FT245R,
Karl Cunningham <=