Re: Problem in sending I2C message from SMBus Intel's controller to a slave device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean,

Do you mean the list in:

-----Original Message----- From: Jean Delvare
Sent: Wednesday, July 30, 2014 9:48 PM
To: Zvi Vered
Cc: lm-sensors@xxxxxxxxxxxxxx
Subject: Re: Problem in sending I2C message from SMBus Intel's controller to a slave device

Hi Zvi,

On Wed, 30 Jul 2014 20:59:15 +0300, Zvi Vered wrote:
From an Intel’s ATOM I want to send an I2C message from SMBus controller to
a TI’s microcontroller configured as an I2C slave.

I used the following code:

handle = fopen (“/dev/i2c-14”,O_RDWR); //open SMBUs controller

ioctl (handle, I2C_SLAVE, 0x43);  //set I2C slave destination address

i2c_smbus_write_block_data (handle, 0x00, 16, buffer); //send 16 bytes
message, command = 0x00

The message I want to send is: 0xAD, 0x2D, 0xFE, 0xCA, ..... 0x00  (16
bytes)

I’m using I2C sniffer to see what I sent and what I see is:

0x00, 0x10, 0xAD, 0x2D, 0xFE, 0xCA, .....

It seems the register (command) and length are also sent.

The MCU expect pure data without the 2 bytes: 0x00, 0x10

The above code runs under vanilla linux 3.2.48

Can you help ?

This is unrelated to hardware monitoring and thus off-topic on the
lm-sensors list. Please ask on the linux-i2c list, Cc me.

--
Jean Delvare
SUSE L3 Support

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux