2.9. I2C (SDA0 SCL0)
This internal I2C bus is normally allocated to the CSI1 and DSI1, as these devices are controlled by the firmware. It can
be used as a general I2C bus if the CSI1 ad DSI1 interfaces aren’t being used, or are being controlled by the firmware.
For example libcamera runs on the ARM and doesn’t use the firmware, so in this case you may use CSI1 and this I2C
bus. SDA0 is connected to GPIO44 on the BCM2711 and SCL0 is connected to GPIO45.
2.10. I2C (ID_SD ID_SC)
This I2C bus is normally used for identifying HATs and controlling CSI0 and DSI0 devices. If the firmware isn’t using the
I2C bus e.g. CSI0 and DSI0 aren’t being used then these pins may be used as GPIO 0 and GPIO 1 if required.
Isn't ID_SD ID_SC also I2C0? Doesn't this cause conflict ?why ID_SD ID_SC become i2c1 in cm4 io board
This internal I2C bus is normally allocated to the CSI1 and DSI1, as these devices are controlled by the firmware. It can
be used as a general I2C bus if the CSI1 ad DSI1 interfaces aren’t being used, or are being controlled by the firmware.
For example libcamera runs on the ARM and doesn’t use the firmware, so in this case you may use CSI1 and this I2C
bus. SDA0 is connected to GPIO44 on the BCM2711 and SCL0 is connected to GPIO45.
2.10. I2C (ID_SD ID_SC)
This I2C bus is normally used for identifying HATs and controlling CSI0 and DSI0 devices. If the firmware isn’t using the
I2C bus e.g. CSI0 and DSI0 aren’t being used then these pins may be used as GPIO 0 and GPIO 1 if required.
Isn't ID_SD ID_SC also I2C0? Doesn't this cause conflict ?
- Image may be NSFW.
Clik here to view.
Statistics: Posted by cris8259 — Thu Aug 01, 2024 2:28 pm — Replies 3 — Views 30
