2,021
edits
Changes
Jump to navigation
Jump to search
Line 133:
Line 133: − + − + − + Line 154:
Line 154: + + + + Line 192:
Line 196: − + Line 269:
Line 273: + + + + + + + + + + Line 403:
Line 417: − + − + Line 422:
Line 436: − + Line 464:
Line 478: − + Line 482:
Line 496: − + Line 523:
Line 537: + + + + Line 532:
Line 550: + + + +
→Upgrade Firefly Ubuntu system
=== Upgrade Firefly Ubuntu system ===
=== Upgrade Firefly Ubuntu system ===
For the ROC-RK3588S-PC, we have provided an image of the release system.
For the ROC-RK3566-PC and ROC-RK3588S-PC, we have provided an image of the release system.
Download the latest rk358x_firefly_ubuntu.tar.gz from https://github.com/veyeimaging/rk35xx_firefly/releases/ .
Download the latest Ubuntu imge from https://github.com/veyeimaging/rk35xx_firefly/releases/ .
Refer to the [https://wiki.t-firefly.com/en/ROC-RK3588S-PC/upgrade_bootmode.html Firefly documentation] to burn in a standard system.
Refer to the Firefly documentation [https://wiki.t-firefly.com/en/ROC-RK3588S-PC/upgrade_bootmode.html ROC-RK3588S-PC] [https://wiki.t-firefly.com/en/ROC-RK3566-PC/03-upgrade_firmware.html ROC-RK3566-PC]to burn in a standard system.
===Check system status===
===Check system status===
<code>mvcam 7-003b: firmware version: 0x1290133</code>
<code>mvcam 7-003b: firmware version: 0x1290133</code>
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.
* Check the video0 device node:
* Check the video0 device node:
You can see that:
You can see that:
* The complete name of this entity is: <code>m00_b_mvcam 7-003b</code>.
* 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.)
* 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>).
====Configuring global variables====
====Configuring global variables====
Based on the board model, configure the I2C_BUS global variable as follows:
* ROC-RK3588S-PC
<code>export I2C_BUS=7</code>
* ROC-RK3566-PC
<code>export I2C_BUS=4</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.
use the following command to configure the camera's data format, resolution, and frame rate using <code>media-ctl</code>:
use the following command to configure the camera's data format, resolution, and frame rate using <code>media-ctl</code>:
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam 7-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
Among them: <code>"m00_b_mvcam 7-003b"</code> refers to the complete name of the camera entity, <code>Y8_1X8</code> is the mbus-code, <code>'"$WIDTH"'x'"$HEIGHT"'</code> indicates the resolution, <code>1/'"$FPS"'</code> indicates the resolution frame rate.
Among them: <code>"m00_b_mvcam '"$I2C_BUS"'-003b"</code> refers to the complete name of the camera entity, <code>Y8_1X8</code> is the mbus-code, <code>'"$WIDTH"'x'"$HEIGHT"'</code> indicates the resolution, <code>1/'"$FPS"'</code> indicates the resolution frame rate.
The width and height here cooperate with the roi_x and roi_y of the v4l2-ctl command to form the ROI parameter.
The width and height here cooperate with the roi_x and roi_y of the v4l2-ctl command to form the ROI parameter.
<code>v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0</code>
<code>v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam 7-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
=====Frame rate statistics=====
=====Frame rate statistics=====
In streaming mode, the following commands can be used for frame rate statistics：
In streaming mode, the following commands can be used for frame rate statistics：
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</code>
<code>python ./v4l2dev_2_opencv_show_grey.py --width 1456 --height 1088 --fps 60 --i2c 7</code>
===== Example of gstreamer application =====
===== Example of gstreamer application =====
<code>v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0</code>
<code>v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam 7-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
<code>media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'</code>
=====Software trigger mode=====
=====Software trigger mode=====
======Set mode======
======Set mode======
===References===
===References===
*ROC-RK3566-PC Manual
https://wiki.t-firefly.com/en/ROC-RK3566-PC/
*ROC-RK3588S-PC Manual
*ROC-RK3588S-PC Manual
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html
===Document History===
===Document History===
* 2024-04-17
Support RK3566.
* 2024-03-10
* 2024-03-10