>> 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.
>>
>> [...]
>>
>> Anyone know if/how I could fix this?
>> As I have a second device it's not that important the first one is
recovered,
>> but I would like to know if I can recover from a second bad try.
Well, your FTDI chip probably still works. You could replace the EEPROM;
they're cheap (about a dollar).
While taking the EEPROM off and recovering its contents is possible, if
you're able to take it off, externally programming it is really not worth
the trouble. I have no idea if there's a way to recover it without pulling
it off the board, but that WOULD be worth the trouble...
>> I tried the MProg program on windows to re-program the device but as soon
as the
>> FTDI windows drivers load the system reboots.
In other words, the "official" FTDI drivers are broken. I'm not terribly
surprised.
One thing that I doubt will work, but is worth a try (if you can't solder):
try putting libusb-win32 on there and compiling your libftdi code for
windows...see if maybe windows will let you write to it. It may be that one
OS detects a broken descriptor and picks sane values, while the other
doesn't. If there's a way (DMM) you can verify whether or not the device is
getting power, you can know if the OS corrected the power issue, anyway.
Maybe not the max packet size problem, but I don't know what 0 does.
Michael
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
