You have chosen to WRITE to this eeprom. If you have a more elegant solution, I will be glad to hear about it. Is it a bug in the driver, or in the application level ?Īnyway, I find a solution, I simply reposition the eeprom read-pointer until it succeded. This is well documented in the datasheet ( ) as Acknowledge (ACK) Polling The program provided by lmsensor seems to be bugged, basically when it write to the eeprom, we must way until the content has been written before continuing. If you are using a 24C16 the file should be 2048 bytes length. The program should work out of the box, and the content of the eeprom must be save into data. Read 16 bytes from eeprom at 0x57, offset 000000f0 Read 16 bytes from eeprom at 0x50, offset 00000000 You can also add the line i2c-dev to the /dev/modules file Detecting the i2cdetect -y -a 0Ġ0: -ġ0: -Ģ0: -ģ0: -Ĥ0: -ĥ0: 50 51 52 53 54 55 56 57 -Ħ0: -ħ0: -įor testing the reading I am using a test program from i2ctools It will probably work with smaller one, and bigger with code changes ( page size, and page number ) Connect the deviceĮasy, just connect the 3,3v, the gnd, the SCL and the SDA pins. Let’s try to connect a i2c eeprom to the raspberry, since it is the only i2c device that I have in my drawer. Now it is time to test if the i2c bus and the driver is working. If you followed my previous blog entry, you have a nice raspberry pi system with support for i2c.

Raspberry pi 8192cu driver