1,602
edits
Changes
Jump to navigation
Jump to search
Line 111:
Line 111: + + + + + + + + + + + +
I2c bus number and video node (view source)
Revision as of 13:45, 27 February 2022
, 13:45, 27 February 2022→google Coral board
==== google Coral board ====
==== google Coral board ====
i2c bus number is 1.
i2c bus number is 1.
=== 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.
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.