VAR-SOM-AM43 I2C: Difference between revisions

From Variscite Wiki
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{PageHeader|VAR-SOM-AM43 - I2C}} {{DocImage|category1=VAR-SOM-AM43|category2=Yocto}} __toc__
= Available I2C buses =
= Available I2C buses =
List I2C available devices:
List I2C available devices:
Line 45: Line 46:


= Variscite's system integrated I2C devices =
= Variscite's system integrated I2C devices =
{{note|Note:Don't manipulate Variscite's on-SOM EEPROM, or you will damage the SOM!|info}}
{{note|Note:Don't manipulate Variscite's on-SOM devices, or you will damage the SOM!|info}}
When the device is marked with "UU" it says a driver is using it.
When the device is marked with "UU" it says a driver is using it.
<br/>Driver with numbers are available.
<br/>Driver with numbers are available.
<br/>Variscite devices:
<br/>Variscite devices:
<br/>I2C-0 0x3C CAMERA
<br/>I2C-0 0x1B On SOM Audio Codec - do not alter
<br/>I2C-0 0x24 On SOM PMIC - do not alter
<br/>I2C-0 0x50 On-SOM EEPROM - do not alter
<br/>I2C-0 0x51 On-SOM EEPROM - do not alter
<br/>
<br/>
<br/>I2C-1 0x37 HDMI
<br/>I2C-1 0x38 Capacitive touch panel
<br/>I2C-1 0x49 HDMI
<br/>I2C-1 0x68 RTC
<br/>I2C-1 0x59 HDMI
<br/>I2C-1 0x50
<br/>I2C-1 0x56 On-SOM EEPROM - do not alter
<br/>I2C-1 0x57 On-SOM EEPROM - do not alter

Latest revision as of 13:20, 24 December 2015

VAR-SOM-AM43 - I2C

Available I2C buses

List I2C available devices:

root@varsomam43:~# ls -l /dev/i2c-*
crw-------    1 root     root       89,   0 Dec 24 13:50 /dev/i2c-0
crw-------    1 root     root       89,   1 Dec 24 13:50 /dev/i2c-1

I2C devices per bus

Scan bus 0:

root@varsomam43:~# i2cdetect -y -r 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 51 -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --                      

Scan bus 1:

root@varsomam43:~# i2cdetect -y -r 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --                    

Reading / Writing from an I2C device

Variscite includes I2CTools as a part of the default file system build. examples of optional commands:
i2cdump - dump the content of an I2C device
i2cset - write a single character to an I2C device
i2cget - read a single character to an I2C device.

In addition, follow 'C' code example as describe in the linux kernel documentation : https://www.kernel.org/doc/Documentation/i2c/dev-interface

Variscite's system integrated I2C devices

Note:Don't manipulate Variscite's on-SOM devices, or you will damage the SOM!

When the device is marked with "UU" it says a driver is using it.
Driver with numbers are available.
Variscite devices:
I2C-0 0x1B On SOM Audio Codec - do not alter
I2C-0 0x24 On SOM PMIC - do not alter
I2C-0 0x50 On-SOM EEPROM - do not alter
I2C-0 0x51 On-SOM EEPROM - do not alter

I2C-1 0x38 Capacitive touch panel
I2C-1 0x68 RTC