Hi,Thanks for your response,Hardware designations and software designations don't always match.
The I2C bus in 2.11 is mapped in Linux to i2c10 (IIRC, may be i2c11).
The I2C bus in 2.12 is mapped in Linux to i2c0.
They are two separate I2C controllers (unlike CM4), so no conflict at all.
As per the note, ID_SD and ID_SC will be probed by default at boot by the firmware for a connected HAT, but otherwise won't be used. Use it for whatever you need. Yes you can select UART1 to come out on GPIOs 0&1.
The two MIPI interfaces on CM5 are identical. You can use whichever you wish, and could choose alternate I2C interfaces. If you use alternative connections then you will need to create your own overlays for whatever you connect to it.
actually, i missed to see this response,
I hope you answered my queries,
I have one doubt from which you responded on this line - The I2C bus in 2.11 is mapped in Linux to i2c10 (IIRC, may be i2c11).
from the attached snip(rp1_dtsi), i am seeing 38 and 39 pins were representing I2c6, but you mentioned I2c10 or 11,
can you please confirm this?
I have configured UART1(GPIO0 and GPIO1)- using sudo pinctrl set 0 a2 and sudo pinctrl 1 a2 and enable the UART1 in config.txt- able to send and receive data form PC terminal,
but when I configured it as for boot logs in cmdline.txt(console=serial0,115200 console=ttyAMA1,115200 console=tty1 root=PARTUUID=26260a32-02 rootfstype=ext4 fsck.repair=yes rootwait loglevel=7 cfg80211.ieee80211_regdom=IN)
- after this configuration boot getting failed and going initramfs,
Cant we use the UART1 at GPIO0 and GPIO1 pins to boot logs?
Statistics: Posted by shivajiyannaboina — Fri Jul 25, 2025 1:16 pm