This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Dear TI supporters,
I have tried to test I2C-0 by the following command:
root@am64xx-evm:/# i2cget -y 1 0x40 0 w 0x2741 root@am64xx-evm:/# i2cdetect -l i2c-3 i2c OMAP I2C adapter I2C adapter i2c-1 i2c OMAP I2C adapter I2C adapter i2c-2 i2c OMAP I2C adapter I2C adapter i2c-0 i2c OMAP I2C adapter I2C adapter root@am64xx-evm:/# i2cget -y 0 0x50 0x0 w 0xffff root@am64xx-evm:/# i2cget -y 0 0x51 0x0 w 0xffff root@am64xx-evm:/# i2cset -y 0 0x51 0x0f 0x55aa w root@am64xx-evm:/# i2cget -y 0 0x51 0x0f w 0xffff root@am64xx-evm:/# i2cget -y 1 0x40 0 w 0x2741 root@am64xx-evm:/#
I also tried to read I2C_1_INA226_VDD_CORE_ADD 0x40 that works well.
I didn't know why I couldn't read data from EEPROM on I2C-0
Hello Thinh,
I apologize for the delayed response. It might be another couple of days before I am able to run tests. Could you talk me through what you are trying to do?
Regards,
Nick
Hello Nick,
My application has an EEPROM on I2C0 bus, so I want to test/practice on the EVM kit first.
I used the i2c tools to read data from all internal addresses of EEPROM, the return value always is 0xFF as first my message.
After that I write a small i2c application run on userspace as below:
-open file device.
-set I2C_slave address,
-Read/write SMBUS with word mode.
The return value of Read() still is 0xFFFF.
I don't know why?