Changes

Jump to navigation Jump to search
Line 126: Line 126:  
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-7 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>
   −
On the ROC-RK3588S-PC, the camera is mounted on i2c-7, with an i2c address of 0x3b.
+
For Radxa Zero 3W, the camera is connected to i2c-2.
 
  −
On the ROC-RK3566-PC, the camera is mounted on i2c-4.
      
*Check the video0 device node:
 
*Check the video0 device node:
Line 154: Line 152:  
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>
Line 168: Line 166:  
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>).
Line 200: Line 198:  
|}
 
|}
 
===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.
Line 239: Line 237:  
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=7</code>
  −
 
  −
*ROC-RK3566-PC
     −
<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.
Line 387: Line 381:  
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.
Line 434: Line 428:  
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.
Line 480: Line 474:     
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.
 
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===
+
===Compile drivers and dtb from source code===
   −
*ROC-RK3566-PC Manual
+
*RK356x
   −
[https://wiki.t-firefly.com/en/ROC-RK3566-PC/ https://wiki.t-Radxa.com/en/ROC-RK3566-PC/]
+
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.
   −
*ROC-RK3588S-PC Manual
+
https://github.com/veyeimaging/rk35xx_radxa/tree/main/i2c_cmd
   −
[https://wiki.t-firefly.com/en/ROC-RK3588S-PC/ https://wiki.t-Radxa.com/en/ROC-RK3588S-PC/]
+
using -b option to identify which bus you want to use.
   −
*Radxa Linux User Guide
+
*VEYE series
   −
[https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html https://wiki.t-Radxa.com/en/Radxa-Linux-Guide/index.html]
+
Video Control Toolkits Manual :[[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-327 I2C]]
===Document History===
+
===References===
   −
*2024-04-17
+
*Radxa Zero 3W Manual
   −
Support  RK3566.
+
https://docs.radxa.com/zero/zero3
   −
*2024-03-10
+
*BSP toolkit
   −
Add pictures and descriptions of hardware connections for the new version of ADP-MV2.
+
https://radxa-repo.github.io/bsp/
 
+
===Document History===
*2023-08-30
  −
 
  −
Add support for RAW-MIPI-IMX462M and RAW-MIPI-AR0234M.
  −
 
  −
*2023-07-31
  −
 
  −
Support V-by-One on ubuntu system.
     −
*2023-04-12
+
*2024-04-24
    
Release 1st version.
 
Release 1st version.

Navigation menu