About problem of Rrk3399's I2C being not able to driven up

wizama

Hi,
I have got the same problem (same error message), but on I2C4.
When you say "It might be the hardware broken" : does Firefly change the board ? It's a brand new one received one week ago !!!

wizama

Hi penguin,
Thank you for your message.

I have got 3 boards AIO-3399C, and the issue only concerns one of them.
All three run the same customized firmware which is compiled from the sources with only the LVDS screen resolution modified in the DTS and the boot animation updated with customized logo. No changes have been made about I2C configuration.
On the I2C4 port, a NFC reader is connected, but is never detected whereas it is on the 2 other boards.

Here is the log I got from debug serial port on launch :

1. [    1.878134] rk3x-i2c ff3d0000.i2c: Initialized RK3xxx I2C bus at ffffff800994a000

Copy the code

which suppose it seems to correctly initialized;
however, when i run "i2cdetect -y 4" command as root, it runs very slow, and for each tested address, I have the following in the logs :

1. [  288.691942] rk3x-i2c ff3d0000.i2c: timeout, ipd: 0x00, state: 1

Copy the code

SDA is 3V and SCL is 0V, but should be 3V also

On the 2 other boards, this command is fast and displays for each address if a device is connected or not.

Any idea ?