Open mgrouch opened 6 months ago
There's a PR (#6050) that may help with this issue. Similar failures are seen when the device fails to ACK data in time, and the PR changes the mark/space ratio on SCL to give the device longer to respond at any given clock speed.
You can install a trial, beta kernel containing the fix by running sudo rpi-update pulls/6050
. Take care to back up any important data in your image before updating in case there is a regression.
Is there workaround for an existing released kernel?
Is that due to i2c bus being faster on pi5? Is there a way to slow down i2c bus with some options?
thanks
Is there workaround for an existing released kernel?
Not really, no, other than to run it slower. You may be able to improve matters by forcing an internal pull-down on SDA (pinctrl 2 pd
), but I would advise anyone to upgrade instead.
Is there a way to slow down i2c bus with some options?
The default with dtparam=i2c_arm
is 100kHz, which is not fast. Specific overlays may force higher clock speeds.
Describe the bug
dmesg errors with 2024-03-12 bookworm
Steps to reproduce the behaviour
just let it run with IMU attached
Device (s)
Raspberry Pi 5
System
Logs
No response
Additional context
No response