Luckfox Forums

Hi, first post here.

I'm trying to read a BME680 sensor, I connected to i2c1 (on i2c1_SDA_M1 pin 11 and i2c_SCL_M1 pin 17). I activated i2c1 and build and flashed the image, now I can see the device when doing a ls /dev/i2c1 but probing with "i2cdetect -y 1" gives me this:

[root@luckfox root]# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: [ 76.992974] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 77.202986] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 77.412971] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 77.622974] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 77.832976] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 78.042972] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 78.252980] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 78.462979] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 78.672973] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 78.882971] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 79.092977] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 79.302973] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 79.512974] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
--
10: [ 79.722975] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 79.932974] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 80.142971] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 80.352975] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 80.562976] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3
-- [ 80.772988] rk3x-i2c ff320000.i2c: timeout, ipd: 0x00, state: 3

Not what I expected, I checked the wiring and it is ok, pullups are on the beakout board, and it worked on another board without porblems. How does one use i2c on this board?

Hello, this error indicates a timeout in i2c bus communication. First, check that the hardware connection is correct. Additionally, burn the latest image provided by us and reconfigure through luckfox-config. If these issues cannot be resolved, consider the possibility of hardware damage and contact the seller for repair.