2,021
edits
Changes
Jump to navigation
Jump to search
Line 95:
Line 95: − + Line 124:
Line 124: − + − + − + − On the ROC-RK3588S-PC, the camera is mounted on i2c-7, with an i2c address of 0x3b.+ − − On the ROC-RK3566-PC, the camera is mounted on i2c-4. Line 154:
Line 152: − + Line 168:
Line 166: − + Line 200:
Line 198: − + Line 239:
Line 237: − + − − <code>export I2C_BUS=7</code> − − *ROC-RK3566-PC − + Line 387:
Line 381: − + Line 434:
Line 428: − + Line 476:
Line 470: − + − We are committed to providing richer possibilities for image applications on embedded platforms. Therefore, our software for embedded platforms is based on the principle of open source. − If you have any questions or suggestions about our existing software, please feel free to submit them to the [http://forum.veye.cc/ forum] or email our technical staff at xumm#csoneplus.com.+ − ===References=== − *ROC-RK3566-PC Manual+ + + − [https://wiki.t-firefly.com/en/ROC-RK3566-PC/ https://wiki.t-Radxa.com/en/ROC-RK3566-PC/]+ − *ROC-RK3588S-PC Manual+ − [https://wiki.t-firefly.com/en/ROC-RK3588S-PC/ https://wiki.t-Radxa.com/en/ROC-RK3588S-PC/]+ − *Radxa Linux User Guide+ + − [https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html https://wiki.t-Radxa.com/en/Radxa-Linux-Guide/index.html]+ − ===Document History=== − *2024-04-17+ − Support RK3566.+ − *2024-03-10+ − + − Add pictures and descriptions of hardware connections for the new version of ADP-MV2. − − *2023-08-30 − − Add support for RAW-MIPI-IMX462M and RAW-MIPI-AR0234M. − − *2023-07-31 − − Support V-by-One on ubuntu system. − +
→Check system status
We provide a deb installation package that can be installed directly.
We provide a deb installation package that can be installed directly.
====Burn Radxa standard system====
====Burn Radxa standard system====
Refer to the [https://wiki.t-firefly.com/en/ROC-RK3566-PC/01-bootmode.html Radxa documentation] to burn in a standard system.
Refer to the Radxa documentation to burn in a standard system.
====Using prebuilt Image and dtb file====
====Using prebuilt Image and dtb file====
Using the compiled debain installation package
Using the compiled debain installation package
You can see the camera model and the camera version number probed.
You can see the camera model and the camera version number probed.
A prompt as below indicates that the MV-MIPI-IMX296M camera is detected on the i2c-7 bus.
A prompt as below indicates that the MV-MIPI-IMX296M camera is detected on the i2c-2 bus.
<code>mvcam 7-003b: camera is：MV-MIPI-IMX296M</code>
<code>mvcam 2-003b: camera is：MV-MIPI-IMX296M</code>
<code>mvcam 7-003b: firmware version: 0x1290133</code>
<code>mvcam 2-003b: firmware version: 0x1290133</code>
For Radxa Zero 3W, the camera is connected to i2c-2.
*Check the video0 device node:
*Check the video0 device node:
Taking the MV-MIPI-IMX296M as an example:
Taking the MV-MIPI-IMX296M as an example:
<code>- entity 63: m00_b_mvcam 7-003b (1 pad, 1 link)</code>
<code>- entity 63: m00_b_mvcam 2-003b (1 pad, 1 link)</code>
<code> type V4L2 subdev subtype Sensor flags 0</code>
<code> type V4L2 subdev subtype Sensor flags 0</code>
You can see that:
You can see that:
*The complete name of this entity is: <code>m00_b_mvcam 7-003b</code>.(It is <code>m00_b_mvcam 4-003b</code>on ROC-RK3566-PC.)
*The complete name of this entity is: <code>m00_b_mvcam 2-003b</code>.
*It is a V4L2 subdev (Sub-Device) Sensor.
*It is a V4L2 subdev (Sub-Device) Sensor.
*Its corresponding node is <code>/dev/v4l-subdev2</code>, which can be opened and configured by applications (such as <code>v4l2-ctl</code>).
*Its corresponding node is <code>/dev/v4l-subdev2</code>, which can be opened and configured by applications (such as <code>v4l2-ctl</code>).
|}
|}
===Raw data format===
===Raw data format===
The VICAP module of RK3588 supports two data saving formats, Compact and Noncompact RAW. You can modify the mode using the RKCIF_CMD_SET_CSI_MEMORY_MODE ioctl command of RKCIF. By default, the output is in Compact RAW format.[[File:Compact raw and noncompact raw of rk3588 vicap.png|center|thumb|800x800px|Compact raw and noncompact raw of rk3588 VICAP|link=http://wiki.veye.cc/index.php/File:Compact_raw_and_noncompact_raw_of_rk3588_vicap.png]]
The VICAP module of RK35xx supports two data saving formats, Compact and Noncompact RAW. You can modify the mode using the RKCIF_CMD_SET_CSI_MEMORY_MODE ioctl command of RKCIF. By default, the output is in Compact RAW format.[[File:Compact raw and noncompact raw of rk3588 vicap.png|center|thumb|800x800px|Compact raw and noncompact raw of rk3588 VICAP|link=http://wiki.veye.cc/index.php/File:Compact_raw_and_noncompact_raw_of_rk3588_vicap.png]]
====Noncompact RAW====
====Noncompact RAW====
For pixel data with 10-bit depth or 12-bit depth, two bytes are always used to store one pixel. This storage method is convenient for software processing, but it has the disadvantage of occupying a large amount of space.
For pixel data with 10-bit depth or 12-bit depth, two bytes are always used to store one pixel. This storage method is convenient for software processing, but it has the disadvantage of occupying a large amount of space.
Based on the board model, configure the I2C_BUS global variable as follows:
Based on the board model, configure the I2C_BUS global variable as follows:
*ROC-RK3588S-PC
*Radxa Zero 3W
<code>export I2C_BUS=4</code>
<code>export I2C_BUS=2</code>
For the convenience of later descriptions, global variables are configured here according to the sensor size.
For the convenience of later descriptions, global variables are configured here according to the sensor size.
For example, for MV-MIPI-IMX296M, the command after variable replacement would be:
For example, for MV-MIPI-IMX296M, the command after variable replacement would be:
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam 7-003b":0[fmt:Y8_1X8/1456x1088@1/60 field:none]'</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam 2-003b":0[fmt:Y8_1X8/1456x1088@1/60 field:none]'</code>
You can not only configure the data format, resolution, and frame rate in one command, but also modify them separately as needed.
You can not only configure the data format, resolution, and frame rate in one command, but also modify them separately as needed.
See the [https://github.com/veyeimaging/rk356x_firefly/tree/main/linux/samples samples] directory on github for details.
See the [https://github.com/veyeimaging/rk356x_firefly/tree/main/linux/samples samples] directory on github for details.
<code>python ./v4l2dev_2_opencv_show_grey.py --width 1456 --height 1088 --fps 60 --i2c 7</code>
<code>python ./v4l2dev_2_opencv_show_grey.py --width 1456 --height 1088 --fps 60 --i2c 2</code>
=====Example of gstreamer application=====
=====Example of gstreamer application=====
To facilitate installation and debugging, the MV series cameras provide UYVY mode, which supports a maximum width of 2880 and can be previewed in real time using the following command.
To facilitate installation and debugging, the MV series cameras provide UYVY mode, which supports a maximum width of 2880 and can be previewed in real time using the following command.
[[mv_mipi_i2c.sh user guide]]
[[mv_mipi_i2c.sh user guide]]
===Question Feedback===
===Compile drivers and dtb from source code===
*RK356x
https://github.com/veyeimaging/rk35xx_radxa/tree/main/linux/drivers/rk356x
===i2c script for parameter configuration===
Because of the high degree of freedom of our camera parameters, we do not use V4L2 parameters to control, but use scripts to configure parameters.
https://github.com/veyeimaging/rk35xx_radxa/tree/main/i2c_cmd
using -b option to identify which bus you want to use.
*VEYE series
Video Control Toolkits Manual ：[[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-327 I2C]]
===References===
*Radxa Zero 3W Manual
https://docs.radxa.com/zero/zero3
*BSP toolkit
https://radxa-repo.github.io/bsp/
===Document History===
*2023-04-12
*2024-04-24
Release 1st version.
Release 1st version.