root/i2c-tools/trunk/tools/i2cdump.8

Revision 5236, 3.3 KB (checked in by khali, 4 years ago)

List the optional command line parameters in a consistent way.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1.TH I2CDUMP 8 "May 2008"
2.SH NAME
3i2cdump \- examine I2C registers
4
5.SH SYNOPSIS
6.B i2cdump
7.RB [ -f ]
8.RB [ "-r first-last" ]
9.RB [ -y ]
10.I i2cbus
11.I address
12.RI [ "mode " [ "bank " [ bankreg ]]]
13.br
14.B i2cdump
15.B -V
16
17.SH DESCRIPTION
18i2cdump is a small helper program to examine registers
19visible through the I2C bus.
20
21.SH OPTIONS
22.TP
23.B -V
24Display the version and exit.
25.TP
26.B -f
27Force access to the device even if it is already busy. By default, i2cdump
28will refuse to access a device which is already under the control of a
29kernel driver. Using this flag is dangerous, it can seriously confuse the
30kernel driver in question. It can also cause i2cdump to return invalid
31results. So use at your own risk and only if you know what you're doing.
32.TP
33.B -r first-last
34Limit the range of registers being accessed. This option is only available
35with modes \fBb\fP, \fBw\fP, \fBc\fP and \fBW\fP. For mode \fBW\fP,
36\fBfirst\fR must be even and \fBlast\fR must be odd.
37.TP
38.B -y
39Disable interactive mode. By default, i2cdump will wait for a confirmation
40from the user before messing with the I2C bus. When this flag is used, it
41will perform the operation directly. This is mainly meant to be used in
42scripts.
43.PP
44At least two options must be provided to i2cdump. \fIi2cbus\fR indicates the
45number or name of the I2C bus to be scanned. This number should correspond to one
46of the busses listed by \fIi2cdetect -l\fR. \fIaddress\fR indicates the
47address to be scanned on that bus, and is an integer between 0x03 and 0x77.
48.PP
49The \fImode\fR parameter, if specified, is one of the letters \fBb\fP, \fBw\fP,
50\fBs\fP, or \fBi\fP, corresponding to a read size of a single byte, a 16-bit
51word, an SMBus block, an I2C block, respectively. The \fBc\fP mode is a
52little different, it reads all bytes consecutively, and is useful for chips that
53have an address auto-increment feature, such as EEPROMs. The \fBW\fP mode is
54also special, it is similar to \fBw\fP except that a read command will only
55be issued on even register addresses; this is again mainly useful for EEPROMs.
56.PP
57A \fBp\fP can also be appended to the \fImode\fR parameter (except for
58\fBi\fP and \fBW\fP) to enable PEC. If the \fImode\fR parameter is omitted,
59i2cdump defaults to byte access without PEC.
60.PP
61The \fIbank\fR and \fIbankreg\fR parameters are useful on the W83781D and
62similar chips (at the time of writing, all Winbond and Asus chips).
63\fIbank\fR is an integer between 0 and 7, and \fIbankreg\fR is an integer
64between 0x00 and 0xFF (default value: 0x4E). The W83781D data sheet has more
65information on bank selection.
66
67.SH WARNING
68i2cdump can be dangerous if used improperly. Most notably, the \fBc\fP mode
69starts with WRITING a byte to the chip. On most chips it will be stored in the
70address pointer register, which is OK, but some chips with a single register
71or no (visible) register at all will most likely see this as a real WRITE,
72resulting in possible misbehavior or corruption. Do not use i2cdump
73on random addresses. Anyway, it is of little use unless you have good
74knowledge of the chip you're working with and an idea of what you are looking
75for.
76
77.SH SEE ALSO
78i2cset(8), i2cdetect(8), isadump(8)
79
80.SH AUTHOR
81Frodo Looijaard, Mark D. Studebaker and Jean Delvare
82
83This manual page was originally written by David Z Maze <dmaze@debian.org> for
84the Debian GNU/Linux system.
Note: See TracBrowser for help on using the browser.