From d832ee135d927d367dc52e390109591e7d64ef31 Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Tue, 20 Apr 2004 19:34:10 +0000 Subject: [PATCH] More detail on how i2cdump can write to a chip. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2462 7894878c-1315-0410-8ee3-d5d059ff63e0 --- prog/dump/i2cdump.8 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/prog/dump/i2cdump.8 b/prog/dump/i2cdump.8 index 4cc08121..60a1a22b 100644 --- a/prog/dump/i2cdump.8 +++ b/prog/dump/i2cdump.8 @@ -33,8 +33,11 @@ between 0x00 and 0xFF (default value: 0x4E). The W83781D data sheet has more information on bank selection. .SH WARNING -i2cdump can be dangerous if used improperly. On some chips that do not support -read data commands, i2cdump can actually WRITE to the chip. Do not use i2cdump +i2cdump can be dangerous if used improperly. Most notably, the \fBc\fP 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 general knowledge about hardware monitoring chips internals.