This page shows the basic usage of the I2C bus.
the following examples are using an external GPIO expander.
i2cdetect is used to identify available I2C devices on a given I2C bus. An overview of the available I2C busses can be achieved by using i2cdetect -l
--: No device found
21: There is a device on address 0x21
UU: A Linux driver is currently using this device
Syntax: i2cdetect [options] <busNr>
The ì2cdump operation is good tool to see the content of a given I2C device to get a better overview of the stored data in its registers.
Syntax: i2cdump [options] <busNr> <deviceAddress>
i2cget is used for reading a byte value from a given device I2C register address.
Syntax: i2cget [options] <busNr> <deviceAddress> <register> <address>
i2cset is used for writing a byte value to a given device I2C register address.
Syntax: i2cset [options] <busNr> <deviceAddress> <register> <address> <value>
This guide provides the basic usage of I2C devices that are often used on our Carrierboards.
| Version | Changes |
|---|---|
Disclaimer PDF export Auvidea can take no responsibility for the accuracy or completeness of any information presented in an exported PDF document as the export feature is developed, managed and maintained by GitBook. Those export mechanisms are subject to change without interaction by Auvidea. Please note that Auvidea includes this version table to identify the document and reference changes.
I2C (Inter-Integrated Circuit) is a two wire communication protocol that is used to read and write data to peripherals devices form one master system (In our case the Jetson Module). It is commonly used in embedded hardware due to its simplicity & low power communication between components.
This protocol is used on our hardware for several devices such as:
Camera sensors
Temperature sensors
IMU's
GPIO Port extender
and so on...
1.0
Internal release
1.1
Publication