Difference between revisions of "How to use EEPROM"
From IGEP - ISEE Wiki
m (→IGEP PARIS Expansion) |
m (→IGEP BERLIN Expansion) |
||
Line 24: | Line 24: | ||
==IGEP BERLIN Expansion== | ==IGEP BERLIN Expansion== | ||
+ | <section begin=berlin /> | ||
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2: | For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2: | ||
<pre>i2cset -f -y 3 0x51 0x10 0x22 | <pre>i2cset -f -y 3 0x51 0x10 0x22 | ||
i2cget -f -y 3 0x51 0x10</pre> | i2cget -f -y 3 0x51 0x10</pre> | ||
+ | <section end=berlin /> | ||
= Know more= | = Know more= |
Revision as of 16:23, 5 September 2012
Contents
Overview
The IGEP expansion boards (except IGEP New York) provides an AT24C01B serial EEPROM memory which is connected to the OMAP via I2C (register 50).
Play with EEPROM memory
Use i2c-tools to manage it:
i2cget <bus> <chip> <register> i2cset <bus> <chip> <register> <value>
IGEPv2 Expansion
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2:
i2cset -f -y 2 0x50 0x10 0x22 i2cget -f -y 2 0x50 0x10
IGEP PARIS Expansion
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2:
i2cset -f -y 3 0x51 0x10 0x22 i2cget -f -y 3 0x51 0x10
IGEP BERLIN Expansion
For example, the following writes the value 0x22 to register 0x10 of device 0x50 on i2c bus 2:
i2cset -f -y 3 0x51 0x10 0x22 i2cget -f -y 3 0x51 0x10
Know more
See also: i2dump(8), i2cget(8) and i2cset(8) man page