1,602
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
I2c bus number and video node (view source)
Revision as of 11:37, 27 February 2022
, 11:37, 27 February 2022no edit summary
== I2c bus number on different boards ==
== I2c bus number on different boards ==
For camera modules with MIPI CSI-2 interface, the i2c bus is commonly provided as the communication channel for parameter configuration. Users use the i2c protocol to access the camera registers. A series of shell scripts are provided to facilitate this operation, such as [[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-X I2C.sh]],[[CS-MIPI-X i2c|CS-MIPI-X I2C.sh]],[[5m mipi i2c user guide|VEYE-MIPI-IMX335 i2c script]].
Generally, there is a matching i2c bus for each MIPI CSI-2 interface on each motherboard. For all our scripts, we can use the <code>-b [bus numer]</code> option to indicate which i2c bus is targeted for this operation. Below, we have summarized the i2c bus serial numbers for commonly used motherboards.
===Raspberry pi===
For a Raspberry Pi with only one mipi csi-2 interface, the i2c bus is 10. If your piOS is very old, then maybe it is 0.
Special, for the Computer module series. Make the following description.
====CM3====
CM3 use I2C-1 to control 2 cameras，It is time-sharing multiplexing.
<code>./camera_i2c_config [cameranum]</code>
{| class="wikitable"
!cameranum
!description
|-
|0
|CAM0
|-
|1
|CAM1
|}
====CM4====
The CM4 module uses two I2C to communicate with two cameras respectively.
<code>./camera_i2c_config</code>
{| class="wikitable"
!i2c bus num
!description
|-
|0
|CAM0
|-
|10
|CAM1
|}
== Description of video nodes ==
== Description of video nodes ==