I2c timeout errors

#1

Anyone have any ideas on what this means? As soon as I plugin my Radxa Zero 3W with emmc, the console is filled with these messages:

rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state 1

#2

fe5c0000.i2c was defined as i2c3.

Does your usb3.0 works rightly?

#3

Not really, is there something wrong there? Sometimes I don’t have any of these then as soon as I plug in a USB device this happens.

#4

What do you mean?

#5

Did you burn the system into the EMMC? The fe5c0000.i2c is I2C_3 , which is used by usb3.0.
Is your USB3.0 type-c port working?

#6

@Nasca @Mitchell
I’d like to revisit this issue since this message started to appear for me as well.

Currently, i am using i2c3 connected to an MPU6050 because i need the other i2c for some other sensors. Initially, i disabled fusb, well i thought so, but i left fusb node in the dts, just changed to pinctrl-names = “default”; and pinctrl-0 = <&i2c3m0_xfer>;.
It worked for a long time, and the USB3 was working (most likely as USB2). It is still working with a keyboard attached to it.
After stressing the Wifi a lot, suddenly after a reboot, the timeout kicked in, and i can’t use the sensor anymore.

[   59.053558] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.196990] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.300122] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.433499] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.536862] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.680040] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.783453] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   59.916808] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.020069] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.163512] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.201796] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   60.201817] Bluetooth: BNEP filters: protocol multicast
[   60.201860] Bluetooth: BNEP socket layer initialized
[   60.269902] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.403343] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.506826] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.653437] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.760083] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   60.896722] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   61.003187] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1
[   61.149777] rk3x-i2c fe5c0000.i2c: timeout, ipd: 0x00, state: 1

If I disconnect SDA (i2c3) from the MPU, I don’t get the message.

I then removed the fsub node and the message stopped appearing, but I can no longer use the sensor; the timeout has occurred again when trying to communicate with the sensor.

To determine if my configuration damaged the i2c3 or if the MPU is to blame (I don’t have a spare, and I’m afraid of connecting any sensor to the i2c3 and damaging it), and to prevent this from happening, can you share some additional information about what might have happened?

the MPU6050 is connected using 3.3v and not 5v.

  • i tested the MPU on i2c5 and i get timeout as well.
    [ 4802.715390] rk3x-i2c fe5e0000.i2c: timeout, ipd: 0x00, state: 2

Update:
Tested the mpu on Rock5C, seems the mpu is damaged. It looks like it’s not a good idea to use i2c3 (pins 3 and 5). I wonder what might have caused the issue.