en:i2c
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:i2c [2014/12/21 10:12] – fluktuacia | en:i2c [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 38: | Line 38: | ||
===== Convertors to connect I²C to PC ===== | ===== Convertors to connect I²C to PC ===== | ||
- | Although I²C is quite popular bus suitable to connect different sensors over short distances, it is not usually found and readily available on regular computers | + | Although I²C is quite popular bus suitable to connect different sensors over short distances, it is not usually found and readily available on regular computers. (([[http:// |
==== USB interface ==== | ==== USB interface ==== | ||
Line 53: | Line 53: | ||
==== USB HID ==== | ==== USB HID ==== | ||
- | For connections without the need for drivers designed for specific hardware [[http:// | + | For connections without the need for drivers designed for specific hardware [[http:// |
Line 62: | Line 62: | ||
==== Ethernet to I²C ==== | ==== Ethernet to I²C ==== | ||
- | This type of convertor can be constructed using [[cs: | + | This type of convertor can be constructed using [[en: |
===== I²C implementation in Linux systems ===== | ===== I²C implementation in Linux systems ===== | ||
Line 88: | Line 88: | ||
i2c-6 i2c | i2c-6 i2c | ||
- | Using // | + | Using // |
kaklik@radio-arm-0: | kaklik@radio-arm-0: | ||
Line 102: | Line 102: | ||
kaklik@radio-arm-0: | kaklik@radio-arm-0: | ||
- | The output above shows, that apart from system device with 0x10 address, there are to additional devices connected to the bus: 0x1e ([[cs: | + | The output above shows, that apart from system device with 0x10 address, there are to additional devices connected to the bus: 0x1e ([[en: |
==== Communication with I²C devices ==== | ==== Communication with I²C devices ==== | ||
Line 127: | Line 127: | ||
Reading from I²CHub is atypical as well, because the data registry is not addressed: | Reading from I²CHub is atypical as well, because the data registry is not addressed: | ||
- | | + | $ sudo i2cget -y 1 0x70 |
0xff | 0xff | ||
+ | ==== Use of Linux kernel drivers ==== | ||
+ | |||
+ | Some I²C devices have their drivers directly in the linux kernel allowing an access directly through file system. It applies to following MLAB modules: | ||
+ | |||
+ | * [[en: | ||
+ | * [[en: | ||
+ | * [[en: | ||
+ | |||
+ | Due to the fact that, in principle, I²C is not a [[http:// | ||
+ | |||
+ | echo driver' | ||
+ | |||
+ | Linux kernel will take control of I²C device - such state can be seen in i2cdetect list labeled as UU. Details concerning the initialisation can be further found in [[http:// | ||
===== Other operating systems ===== | ===== Other operating systems ===== | ||
Line 137: | Line 150: | ||
===== Related sites ===== | ===== Related sites ===== | ||
- | * [[cs:usbi2c]] | + | * [[en:usbi2c]] |
- | * [[cs: | + | * [[en: |
- | * [[cs: | + | * [[en: |
- | * [[cs: | + | * [[en: |
- | * [[cs: | + | * [[en: |
- | * [[cs: | + | * [[en: |
- | * [[cs:i2chub]] | + | * [[en:i2chub]] |
- | * [[cs:pymlab]] | + | * [[en:pymlab]] |
en/i2c.1419156763.txt.gz · Last modified: 2014/12/21 10:12 (external edit)