libftdi Archives

Subject: Re: First byte of LT245R eeprom

From: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Fri, 1 Feb 2013 11:04:21 +0100
>>>>> "Karl" == Karl Cunningham <karlc@xxxxxxxxxx> writes:

    Karl> I am starting to use libftdi1 v1.0 in Ubuntu 12.04.  First, thanks
    Karl> to all who made this possible.

    Karl> We have been using an FT245R for several years, programming them
    Karl> with libftdi v0.16 with an older Ubuntu system. After programming
    Karl> one with libftdi1 v1.0, we can't communicate with it.

    Karl> I traced the problem to a difference in what is programmed into
    Karl> the first byte of the eeprom. v1.0 is programming that byte as
    Karl> 0x00. Version 0.16 originally did that too, but I had modified it
    Karl> to program with 0x09 to match what MProg was doing. This made the
    Karl> chip work for us.

    Karl> Are these bits are associated with enabling VCP? We don't use VCP,
    Karl> so that might account for the difference. I can't see how to
    Karl> program this byte to 0x09 in libftdi1 v1.0, short of modifying
    Karl> ftdi.c. Is there a way already there?

I think bit 3 of Eeprom byte 0 is not yet documented in libftdi. If you have
access to mprog, experiment a little to find out it's meaning and document
and in lin libftdi.

Thanks
-- 
Uwe Bonnes                bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread