2004-09-22 20:37:06 +00:00
|
|
|
.TH I2CDETECT 8 "September 2004"
|
2004-03-22 19:53:44 +00:00
|
|
|
.SH NAME
|
2004-07-24 19:00:21 +00:00
|
|
|
i2cdetect \- detect I2C chips
|
2004-03-22 19:53:44 +00:00
|
|
|
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.B i2cdetect
|
2004-09-22 20:37:06 +00:00
|
|
|
.RI [ -y ]
|
|
|
|
|
.RI [ -a ]
|
2004-04-21 20:58:05 +00:00
|
|
|
.RI [ -q | -r ]
|
2004-03-22 19:53:44 +00:00
|
|
|
.I i2cbus
|
|
|
|
|
.br
|
|
|
|
|
.B i2cdetect
|
2004-09-22 20:37:06 +00:00
|
|
|
.I -V
|
|
|
|
|
.br
|
|
|
|
|
.B i2cdetect
|
2004-03-22 19:53:44 +00:00
|
|
|
.I -l
|
|
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
2004-07-24 19:00:21 +00:00
|
|
|
i2cdetect is a userspace program to scan an I2C bus for devices. It
|
2004-03-22 19:53:44 +00:00
|
|
|
outputs a table with the list of detected devices on the specified bus.
|
2004-07-24 19:00:21 +00:00
|
|
|
\fIi2cbus\fR indicates the number of the I2C bus to be scanned, and
|
2004-03-22 19:53:44 +00:00
|
|
|
should correspond to one of the busses listed by \fIi2cdetect -l\fR.
|
|
|
|
|
|
|
|
|
|
.SH WARNING
|
2004-07-24 19:00:21 +00:00
|
|
|
This program can confuse your I2C bus, cause data loss and worse!
|
2004-03-22 19:53:44 +00:00
|
|
|
|
|
|
|
|
.SH OPTIONS
|
|
|
|
|
.TP
|
2004-09-22 20:37:06 +00:00
|
|
|
.B "\-y"
|
|
|
|
|
Disable interactive mode. By default, i2cdetect will wait for a confirmation
|
|
|
|
|
from the user before messing with the I2C bus. When this flag is used, it
|
|
|
|
|
will perform the operation directly. This is mainly meant to be used in
|
|
|
|
|
scripts.
|
|
|
|
|
.TP
|
|
|
|
|
.B "\-a"
|
2004-03-22 19:53:44 +00:00
|
|
|
Force scanning of non-regular addresses. Not recommended.
|
|
|
|
|
.TP
|
2004-04-21 20:58:05 +00:00
|
|
|
.B "\-q"
|
|
|
|
|
Use SMBus "quick write" commands for probing (by default, the command
|
|
|
|
|
used is the one believed to be the safest for each address).
|
|
|
|
|
Not recommended. This is known to corrupt the Atmel AT24RF08 EEPROM
|
|
|
|
|
found on many IBM Thinkpad laptops.
|
|
|
|
|
.TP
|
|
|
|
|
.B "\-r"
|
|
|
|
|
Use SMBus "read byte" commands for probing (by default, the command
|
|
|
|
|
used is the one believed to be the safest for each address).
|
|
|
|
|
Not recommended. This is known to lock SMBus on various write-only
|
|
|
|
|
chips (most notably clock chips at address 0x69).
|
|
|
|
|
.TP
|
2004-09-22 20:37:06 +00:00
|
|
|
.B "\-V"
|
|
|
|
|
Display the version and exit.
|
|
|
|
|
.TP
|
2004-03-22 19:53:44 +00:00
|
|
|
.B "\-l"
|
|
|
|
|
Output a list of installed busses.
|
|
|
|
|
|
|
|
|
|
.SH CONFORMING TO
|
|
|
|
|
lm_sensors-2.x
|
|
|
|
|
|
|
|
|
|
.SH SEE ALSO
|
|
|
|
|
i2cdump(8), sensors-detect(8)
|
|
|
|
|
|
|
|
|
|
.SH AUTHOR
|
2004-04-20 01:25:22 +00:00
|
|
|
Frodo Looijaard, Mark D. Studebaker, and the lm_sensors group
|
|
|
|
|
http://www.lm-sensors.nu/
|
2004-03-22 19:53:44 +00:00
|
|
|
This manual page was written by Aurelien Jarno <aurel32@debian.org>, for
|
|
|
|
|
the Debian GNU/Linux system. It was then reviewed by the lm_sensors team and
|
|
|
|
|
is now part of the lm_sensors source distribution.
|
