|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
I2CDUMP(8) I2CDUMP(8)
NAME
i2cdump - examine I2C registers
SYNOPSIS
i2cdump [-y] i2cbus address [mode] [bank [bankreg]]
i2cdump -V
DESCRIPTION
i2cdump is a small helper program to examine registers visible through
the I2C bus.
OPTIONS
-V Display the version and exit.
-y Disable interactive mode. By default, i2cdump 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.
At least two options must be provided to i2cdump. i2cbus indicates the
number of the I2C bus to be scanned. This number should correspond to
one of the busses listed by i2cdetect -l. address indicates the address
to be scanned on that bus, and is an integer between 0x00 and 0x7F.
The mode parameter, if specified, is one of the letters b, w, s, or i,
corresponding to a read size of a single byte, a 16-bit word, an SMBus
block, an I2C block, respectively. The c mode is a little different, it
reads all bytes consecutively, and is useful for chips that have an
address auto-increment feature, such as EEPROMs. The W mode is also
special, it is similar to w except that a read command will only be
issued on even register addresses; this is again mainly useful for EEP-
ROMs.
A p can also be appended to the mode parameter (except for i and W) to
enable PEC. If the mode parameter is omitted, i2cdump defaults to byte
access without PEC.
The bank and bankreg parameters are useful on the W83781D and similar
chips (at the time of writing, all Winbond and Asus chips). bank is an
integer between 0 and 7, and bankreg is an integer between 0x00 and
0xFF (default value: 0x4E). The W83781D data sheet has more information
on bank selection.
WARNING
i2cdump can be dangerous if used improperly. Most notably, the c mode
starts with WRITING a byte to the chip. On most chips it will be stored
in the address pointer register, which is OK, but some chips with a
single register or no (visible) register at all will most likely see
this as a real WRITE, resulting in possible misbehavior or corruption.
Do not use i2cdump on random addresses. Anyway, it is of little use
unless you have an idea of what you are looking for and have some gen-
eral knowledge about hardware monitoring chips internals.
CONFORMING TO
lm_sensors-2.x
SEE ALSO
i2cset(8), i2cdetect(8), isadump(8)
AUTHOR
Frodo Looijaard, Mark D. Studebaker, and the lm_sensors group
http://www.lm-sensors.org/ This manual page was originally written by
David Z Maze <dmaze@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.
April 2006 I2CDUMP(8)
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Sat Sep 8 16:40:23 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
svn man page (6164 hits)
(FreeBSD 6.2)
sqlite3 man page (5598 hits)
(openSUSE 10.2)
adv_cap_autoneg man page (5045 hits)
(Solaris 10 11_06)
CPAN man page (4791 hits)
(Suse Linux 10.1)
ssh man page (4439 hits)
(Suse Linux 10.1)
ssh-socks5-proxy-connect man page (3525 hits)
(Solaris 10 11_06)
signal man page (3395 hits)
(Suse Linux 10.1)
netcat man page (3383 hits)
(Suse Linux 10.1)
pprosetup man page (2889 hits)
(Solaris 10 11_06)
startproc man page (2739 hits)
(Suse Linux 10.1)
|
Man Pages 
