I am attempting to configure a dual camera setup on my Raspberry Pi CM5 and have followed the recommendations provided by the engineers for testing. However, I have encountered a perplexing I2C bus identification issue for which I would appreciate further assistance.
Problem Description
Following the recommendations, I executed these steps:
Confirmed that the J6 jumpers are installed
Removed the dtoverlay configuration lines from config.txt
Enabled the I2C interfaces for both camera/display connectors using sudo dtparam i2c_csi_dsi1 and sudo dtparam i2c_csi_dsi0
Checked for camera devices using i2cdetect
Observations
When running sudo i2cdetect -y 0 and sudo i2cdetect -y 11, I successfully detected camera devices (address 0x1A) as well as EEPROMs (addresses 0x50 and 0x58) on both buses.
However, when I execute sudo i2cdetect -l to list all I2C buses, the list includes i2c-0, i2c-1, i2c-10, i2c-13, and i2c-14, but does not show i2c-11, despite my ability to directly access this bus using sudo i2cdetect -y 11 and observe the connected devices.
Questions
Why is i2c-11 directly accessible and shows connected devices, yet remains invisible in the system's bus listing?
In this situation, how should I correctly configure the device tree overlay to enable dual camera functionality?
Is it normal that i2c-0 appears to be connected to a camera, rather than the traditionally used i2c-10 and i2c-11?
Thank you for your assistance!
![Image]()
Problem Description
Following the recommendations, I executed these steps:
Confirmed that the J6 jumpers are installed
Removed the dtoverlay configuration lines from config.txt
Enabled the I2C interfaces for both camera/display connectors using sudo dtparam i2c_csi_dsi1 and sudo dtparam i2c_csi_dsi0
Checked for camera devices using i2cdetect
Observations
When running sudo i2cdetect -y 0 and sudo i2cdetect -y 11, I successfully detected camera devices (address 0x1A) as well as EEPROMs (addresses 0x50 and 0x58) on both buses.
However, when I execute sudo i2cdetect -l to list all I2C buses, the list includes i2c-0, i2c-1, i2c-10, i2c-13, and i2c-14, but does not show i2c-11, despite my ability to directly access this bus using sudo i2cdetect -y 11 and observe the connected devices.
Questions
Why is i2c-11 directly accessible and shows connected devices, yet remains invisible in the system's bus listing?
In this situation, how should I correctly configure the device tree overlay to enable dual camera functionality?
Is it normal that i2c-0 appears to be connected to a camera, rather than the traditionally used i2c-10 and i2c-11?
Thank you for your assistance!
Statistics: Posted by LchiChung — Tue Feb 25, 2025 2:47 am