Re: Reading/Writing FT4232 EEPROM

[Ori Idan <ori@xxxxxxxxxxxxxxxxx>]

On Sun, Jun 23, 2013 at 6:47 PM, Anders Larsen <al@xxxxxxxxxxx> wrote:

Hi,

On 2013-06-23 08:23, Ori Idan wrote:

On Fri, Jun 21, 2013 at 5:31 PM, Anders Larsen <al@xxxxxxxxxxx> wrote:

> with an erased EEPROM the FTDI chip falls back to the default
> vendor:product (which is 0403:6011)

Assuming my EEPROM is erased, I tried doing flash-eeprom.
The result was even stranger:
Unable to find FTDI devices under given vendor/product id: 0x403/0x6011
Error code: -4 (usb_open() failed)

this is indeed strange; that particular error message comes from ftdi_usb_open_desc_index() in ftdi.c when your device was found by libusb_get_device_list() but couldn't be opened by libusb_open() immediately thereafter.

Assuming you didn't forget 'sudo' it looks like a problem with libusb, outside the scope of libftdi.

Thank you, it seems the problem was sudo.

Now when I write I get:

FTDI eeprom generator v0.17

(c) Intra2net AG and the libftdi developers <opensource@xxxxxxxxxxxxx>

FTDI read eeprom: 0

EEPROM size: -1

Used eeprom space: 230 bytes

FTDI write eeprom: 0

Writing to file: eeprom.new

FTDI close: 0

When I read I get:

 FTDI eeprom generator v0.17

(c) Intra2net AG and the libftdi developers <opensource@xxxxxxxxxxxxx>

FTDI read eeprom: 0

EEPROM size: 256

FTDI close: 0

That seems fine to me.

However after write I see no change in lsusb, I assume the serial number should be changed, but I see no change so I have no idea if it did write or not.

-- 

Ori Idan

Cheers
Anders

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

---

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