MX8 I2C: Difference between revisions
From Variscite Wiki
(Created page with "<!-- Set release according to "release" parameter in URL and use RELEASE_SUMO_V1.0_VAR-SOM-MX8X as default --> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- --> {{#lst...") |
No edit summary |
||
| Line 2: | Line 2: | ||
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | --> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | ||
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_SUMO_V1.0_VAR-SOM-MX8X}}}} <!-- | --> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_SUMO_V1.0_VAR-SOM-MX8X}}}} <!-- | ||
--> {{PageHeader|{{#var:HARDWARE_NAME}} I2C}} {{DocImage|category1=Yocto|category2= | --> {{PageHeader|{{#var:HARDWARE_NAME}} I2C}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME}}}} __toc__ | ||
= Available I2C buses = | = Available I2C buses = | ||
Revision as of 16:20, 2 September 2019
VAR-SOM-MX8X I2C
Available I2C buses
List I2C available devices:
# ls -l /dev/i2c-* crw------- 1 root root 89, 0 Jul 4 09:09 /dev/i2c-0 crw------- 1 root root 89, 1 Jul 4 09:09 /dev/i2c-1 crw------- 1 root root 89, 2 Jul 4 09:09 /dev/i2c-2
System class:
# ls /sys/class/i2c-dev/ i2c-0 i2c-1 i2c-2
I2C devices per bus
Scan bus 0:
# i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- 52 53 -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Scan bus 1:
# i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Scan bus 2:
# i2cdetect -y -r 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- 54 55 -- -- -- -- -- -- -- -- -- --
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 on-SOM EEPROM, or you will damage the SOM!
When the device is marked with "UU" it means that a driver is using it.
When the device is marked with numbers it means that no driver is using it.
Variscite devices:
I2C-0 0x1a - Audio codec on SOM I2C-0 0x52 - EEPROM on SOM. Don't modify! I2C-0 0x53 - EEPROM on SOM. Don't modify! I2C-1 0x20 – GPIO expander on carrier board I2C-1 0x3c – MIPI-CSI camera on expansion board I2C-1 0x3d – USB Type C controller on carrier board I2C-2 0x38 – Capacitive touch controller on carrier board I2C-2 0x54 - EEPROM on carrier board I2C-2 0x55 - EEPROM on carrier board I2C-2 0x68 – RTC on carrier board