DART-MX8M I2C: Difference between revisions

From Variscite Wiki
No edit summary
No edit summary
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- Set release according to "release" parameter in URL and use RELEASE_SUMO_V1.0_DART-MX8M as default
<!-- Set release according to "release" parameter in URL and use RELEASE_SUMO_V1.0_DART-MX8M as default
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release|RELEASE_SUMO_V1.0_DART-MX8M}}}} <!--
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_SUMO_V1.0_DART-MX8M}}}} <!--
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
--> {{PageHeader|{{#var:HARDWARE_NAME}} I2C}} {{DocImage|category1=Yocto|category2=Android}}[[Category:DART-MX8M]][[Category:DART-MX8M-MINI]][[Category:Debian]] __toc__
--> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
--> {{PageHeader|{{#var:HARDWARE_NAME}} I2C}} {{DocImage|category1=Yocto|category2=Android}}[[Category:Debian]][[Category:{{#var:HARDWARE_NAME}}]]__toc__


= Available I2C buses =
= Available I2C buses =
Line 265: Line 266:
i2cdump - dump the content of an I2C device <br>
i2cdump - dump the content of an I2C device <br>
i2cset  - write a single character to an I2C device<br>
i2cset  - write a single character to an I2C device<br>
i2cget - read a single character to an I2C device.<br>
i2cget - read a single character to an I2C device<br>
<br>
<br>
In addition follow 'C' code example as describe in the linux kernel documentation : https://www.kernel.org/doc/Documentation/i2c/dev-interface
In addition follow 'C' code example as describe in the linux kernel documentation : https://www.kernel.org/doc/Documentation/i2c/dev-interface
Line 291: Line 292:
I2C-2 0x60 - i.MX8M SoC voltage regulator on SOM
I2C-2 0x60 - i.MX8M SoC voltage regulator on SOM


I2C-3 0x20 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x21 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x3c – MIPI-CSI camera on expansion board
I2C-3 0x3c – MIPI-CSI camera on expansion board
</pre>
</pre>
Line 309: Line 312:


I2C-2 0x1a - Audio codec on SOM
I2C-2 0x1a - Audio codec on SOM
I2C-3 0x20 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x21 - TCA6408 GPIO expander on carrier board V2 only
</pre>
</pre>


Line 362: Line 368:
I2C-1 0x68 – RTC on carrier board
I2C-1 0x68 – RTC on carrier board


I2C-3 0x20 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x21 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x3c - MIPI-CSI camera on expansion board
I2C-3 0x3c - MIPI-CSI camera on expansion board
</pre>
</pre>
Line 372: Line 380:
I2C-0 0x53 - EEPROM on SOM. Don't modify!
I2C-0 0x53 - EEPROM on SOM. Don't modify!


I2C-1 0x20 - PCA9534 GPIO expander on carrier board
I2C-2 0x20 - PCA9534 GPIO expander on carrier board
I2C-1 0x3c – MIPI-CSI camera on expansion board
I2C-2 0x3c – MIPI-CSI camera on expansion board
I2C-1 0x3d – USB Type C controller on carrier board
I2C-2 0x3d – USB Type C controller on carrier board


I2C-2 0x1a - Audio codec on SOM
I2C-3 0x38 – Capacitive touch controller on kit display
I2C-2 0x38 – Capacitive touch controller on kit display
I2C-3 0x54 - EEPROM on carrier board
I2C-2 0x54 - EEPROM on carrier board
I2C-3 0x55 - EEPROM on carrier board
I2C-2 0x55 - EEPROM on carrier board
I2C-3 0x68 – RTC on carrier board
I2C-2 0x68 – RTC on carrier board
</pre>
</pre>
|}} }} }} }}
|}} }} }} }}

Revision as of 19:44, 29 January 2022

DART-MX8M 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
crw------- 1 root root 89, 3 Jul  4 09:09 /dev/i2c-3

System class:

# ls /sys/class/i2c-dev/
i2c-0  i2c-1  i2c-2  i2c-3

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:          -- -- -- -- -- UU -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- 52 53 -- -- -- -- -- -- -- -- -- -- -- -- 
60: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- UU -- -- -- UU UU -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- 54 55 -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

Scan bus 3:

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

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.

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: Do not write to Variscite's on-SOM EEPROM or you will damage the SOM!

Variscite devices:

I2C-0 0x08 – PMIC on SOM
I2C-0 0x1a - Audio codec on SOM
I2C-0 0x2c - MIPI-LVDS bridge on SOM
I2C-0 0x52 - EEPROM on SOM. Don't modify!
I2C-0 0x53 - EEPROM on SOM. Don't modify!
I2C-0 0x60 - i.MX8M ARM voltage regulator on SOM

I2C-1 0x38 – Capacitive touch controller on kit display
I2C-1 0x3c – MIPI-CSI camera on expansion board
I2C-1 0x3d – USB Type C controller on carrier board
I2C-1 0x54 - EEPROM on carrier board
I2C-1 0x55 - EEPROM on carrier board
I2C-1 0x68 – RTC on carrier board

I2C-2 0x60 - i.MX8M SoC voltage regulator on SOM

I2C-3 0x20 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x21 - TCA6408 GPIO expander on carrier board V2 only
I2C-3 0x3c – MIPI-CSI camera on expansion board