On 10/27/2011 01:58 AM, Uwe Bonnes wrote:
"Karl" == Karl Cunningham<karlc@xxxxxxxxxx> writes:
Karl> Compiled and installed lubftdi-1.0 from
Karl> git://developer.intra2net.com/libftdi
git remote -v
origin git://developer.intra2net.com/libftdi (fetch)
origin git://developer.intra2net.com/libftdi (push)
git branch -r
origin/HEAD -> origin/master
origin/autoconf-removal
origin/eeprom-new
origin/get-library-version
origin/libftdi-0.x
origin/master
origin/new-baudrate-code
git checkout origin/eeprom-new -b eeprom-new
...
Karl> Any ideas?
Most work has been done on the ftdi-1.0 branch. Probably Thomas is waiting
on feedback before merging the ftdi_eeprom branch
While ./ftdi_eeprom/ftdi_eeprom is run time configurable, examples/eeprom is
only
compile time configurable, beside an eventual serial number, but may be
worth a look too.
Thanks for the reply. examples/eeprom built without any problem, and
does successfully erase the eeprom.
I have appended the tool based on examples/eeprom ( or
probably vice-versa) that I use to configure local devices. You can easily
add your device. Probably your device has a misconfigured EEPROM now. The
first thing to do is to erase the eeprom. This will not erase the serial
number.
I'm unclear where to find the tool you mention, based on examples/eeprom
(or vise-versa).
$ git branch -r
origin/HEAD -> origin/master
origin/libftdi-0.x
origin/master
Since we have two pids and different model strings to program, we'd
prefer something more flexible than example/eeprom.
Thanks for your help.
Karl Cunningham
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
| 