Hello,
Based on the attached CM5-datasheet snippet, I have the following observations:
1. I noticed a conflict when utilizing MIPI0 and the internal I2C bus assigned to GPIO38 and GPIO39 pins. Therefore, we can only use one of these interfaces at a time.
- Could you please clarify the reason for this conflict? The MIPI lines are dedicated pins, while the I2C0 bus operates on different lines.
- Additionally, can you confirm if we can eliminate this dependency in our custom image and operate both interfaces independently?
2. ID_SD ID_SC (GPIO0 and GPIO1) - This I2C bus is typically employed for identifying HATs and managing CSI0 and DSI0 devices. If the firmware does not utilize the I2C bus, for instance, if MIPI1 is not in use, then these pins can be repurposed as GPIO 0 and GPIO 1 if necessary.
i. Is it possible to utilize this I2C bus for our custom I2C applications?
ii. We intend to use these lines for debugging UART purposes; can we proceed with that?
iii. In our custom image, can we remove this dependency and use both interfaces independently?
3. Which MIPI interface is preferable from the Raspberry perspective?
I mean, does one have advantages over the other?
Please help me on this above queries
Based on the attached CM5-datasheet snippet, I have the following observations:
1. I noticed a conflict when utilizing MIPI0 and the internal I2C bus assigned to GPIO38 and GPIO39 pins. Therefore, we can only use one of these interfaces at a time.
- Could you please clarify the reason for this conflict? The MIPI lines are dedicated pins, while the I2C0 bus operates on different lines.
- Additionally, can you confirm if we can eliminate this dependency in our custom image and operate both interfaces independently?
2. ID_SD ID_SC (GPIO0 and GPIO1) - This I2C bus is typically employed for identifying HATs and managing CSI0 and DSI0 devices. If the firmware does not utilize the I2C bus, for instance, if MIPI1 is not in use, then these pins can be repurposed as GPIO 0 and GPIO 1 if necessary.
i. Is it possible to utilize this I2C bus for our custom I2C applications?
ii. We intend to use these lines for debugging UART purposes; can we proceed with that?
iii. In our custom image, can we remove this dependency and use both interfaces independently?
3. Which MIPI interface is preferable from the Raspberry perspective?
I mean, does one have advantages over the other?
Please help me on this above queries
Statistics: Posted by shivajiyannaboina — Thu Jul 24, 2025 7:24 am