2,021
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: + + + + + + + + + + + + Line 18:
Line 30: − + Line 44:
Line 56: − + Line 79:
Line 91: − + + + + + + + + + + + + + + + + + + + + + + + + Line 111:
Line 146: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→CM3
Special, for the Computer module series. Make the following description.
Special, for the Computer module series. Make the following description.
==== Raspberry Pi 5 ====
{| class="wikitable"
!i2c bus num
!description
|-
|6
|CAM0
|-
|4
|CAM1
|}
====CM3====
====CM3====
CM3 use I2C-1 to control 2 cameras，It is time-sharing multiplexing.
CM3 use I2C-1 to control 2 cameras，It is time-sharing multiplexing.
<code>./camera_i2c_config [cameranum]</code>
<code>./camera_i2c_config [cameranum]</code>
{| class="wikitable"
{| class="wikitable"
!cameranum
!i2c bus num
!description
!description
|-
|-
=== Nvidia Jetson ===
=== Nvidia Jetson ===
The following description is only for official Nvidia development boards, third party board need to be confirmed with the manufacturer.
The following description is only for official Nvidia development boards, third party board need to be confirmed with the manufacturer.
==== AGX-Xavier, TX2 Devkit====
==== AGX-Xavier,AGX-Orin,TX2 Devkit====
[[ADP-N1-V2.0 Adapter Board Data Sheet|ADP-N1-V2.0]] has 6 MIPI CSI-2 interfaces, corresponding to the i2c bus numbers 30-35.
[[ADP-N1-V2.0 Adapter Board Data Sheet|ADP-N1-V2.0]] has 6 MIPI CSI-2 interfaces, corresponding to the i2c bus numbers 30-35.
{| class="wikitable"
{| class="wikitable"
|9
|9
|}
|}
====Nano A02, Nano 2GB====
OR：
{| class="wikitable"
!cam index
!i2c number
|-
|0
|9
|-
|1
|10
|}<br />
==== Orin Nano , Orin NX ====
{| class="wikitable"
!cam index
!i2c number
|-
|0
|9
|-
|1
|10
|}
====Nano B01====
{| class="wikitable"
{| class="wikitable"
!cam index
!cam index
==== google Coral board ====
==== google Coral board ====
i2c bus number is 1.
i2c bus number is 1.
=== Rockchip platform ===
==== ROC-RK3566-PC ====
i2c bus number is 4.
==== ROC-RK3588S-PC ====
i2c bus number is 7.
=== Tools ===
The following two tools can assist in understanding and finding problems.
==== i2cdetect ====
Under linux command, execute the following command to probe all the i2c device addresses on the i2c bus. Usually our module address is 0x3b.
<code>i2cdetect -y -r [busnumber]</code>
==== dmesg ====
dmesg prints out the logs of the linux kernel boot phase and also the driver logs of our camera modules. It shows the i2c probe process during the boot phase and whether it was successful or not.
== Description of video nodes ==
== Description of video nodes ==
In general, we have implemented v4l2 standard drivers for mipi modules on different platforms. The Linux kernel will find the corresponding driver and probe the camera according to the dts when booting. After success, the /dev/videoX device node is generated, where X is a number based on the order of the probe to.
This tends to cause a common misunderstanding, which is explained here.
For motherboards that support multiple mipi cameras, the i2c bus number of each camera is determined by the camera installation location, but the generated /dev/videoX node name cannot be determined in advance.
For example, if we install two cameras on the agx board, mounted to cam2 and cam4 positions, then:
{| class="wikitable"
|+xavier agx
!camera number
!location
!i2c bus
!/dev/video node
|-
|1
|cam2
|32
|/dev/video0
|-
|2
|cam4
|34
|/dev/video1
|}
<br />