Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8035

Interfacing (DSI, CSI, I2C, etc.) • Re: CM4 I2C Clarification

$
0
0
I can't see any immediate error.
I've just checked that "dtoverlay=i2c0" (or with ",pins_44_45" override) gives me only i2c-0 from "i2cdetect -l" on a Pi4 (should be the same on CM4). I also get i2c-20 and i2c-21 for the HDMI DDC channels.

You can check that the alias has been changed by running "cat /proc/device-tree/aliases/i2c0". i2c0if should be "/soc/i2c@7e205000", whilst it'll be "/soc/i2c0mux/i2c@0" if still pointing to the mux.

Actually I want to query what kernel version you are running ("uname -a"). With "dtparam=i2c_vc" on the latest kernel (6.6.62) I get

Code:

pi@bookworm64-1:~ $ i2cdetect -li2c-0i2c       i2c-22-mux (chan_id 0)          I2C adapteri2c-10i2c       i2c-22-mux (chan_id 1)          I2C adapteri2c-20i2c       fef04500.i2c                    I2C adapteri2c-21i2c       fef09500.i2c                    I2C adapteri2c-22i2c       bcm2835 (i2c@7e205000)          I2C adapter
i2c0if has no alias assigned, so it is adopting the next highest number. That appears to have been the case since Feb 2023 on 6.1, so I'd want that resolved.

Statistics: Posted by 6by9 — Thu Nov 21, 2024 3:02 pm



Viewing all articles
Browse latest Browse all 8035

Trending Articles