2,577
edits
Changes
Jump to navigation
Jump to search
→State Detection and Environment Variable Configuration
Line 145:
Line 145:
===='''State Detection and Environment Variable Configuration'''====
−[https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/mv_tools_rockchip/i2c_tools Here], we provide an <code>mv_probe.sh</code> script that automatically detects the connected camera and configures environment variables with its default model, width, height, frame rate, and other information.
−Usage:
−<code>source ./mv_probe.sh</code>
−A typical output:
−<code>$ source ./mv_probe.sh</code>
−<code>The mvcam driver is loaded on i2c-10, but the camera is not detected!</code>
−<code>Found veye_mvcam camera on i2c-11.</code>
−<code>Setenv CAMERAMODEL = RAW-MIPI-SC535M</code>
−<code>Setenv FPS = 49</code>
−<code>Setenv HEIGHT = 2048</code>
−<code>Setenv WIDTH = 2432</code>
−You can verify the environment variable output using:
−<code>echo $CAMERAMODEL</code>
−Note that these environment variables are only valid for the current session.
−'''Important Notes:'''
−*This script requires the <code>mvcam</code> driver version '''1.1.06 or later'''.
−*If your driver version is '''earlier than 1.1.06''' or you need to use different width, height, or frame rate values, refer to the camera module manual and manually configure the following environment variables. Otherwise, subsequent programs may not function correctly.
−Example:
−<code>export WIDTH=2432</code>
−<code>export HEIGHT=2048</code>
−<code>export FPS=50</code>
−====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>
After successfully identifying the camera, the camera will be recognized as /dev/video0.
After successfully identifying the camera, the camera will be recognized as /dev/video0.
+===='''State Detection and Environment Variable Configuration'''====
+[https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/mv_tools_rockchip/i2c_tools Here], we provide an <code>mv_probe.sh</code> script that automatically detects the connected camera and configures environment variables with its default model, width, height, frame rate, and other information.
+
+Usage:
+
+<code>source ./mv_probe.sh</code>
+
+A typical output:
+
+<code>$ source ./mv_probe.sh</code>
+
+<code>The mvcam driver is loaded on i2c-10, but the camera is not detected!</code>
+
+<code>Found veye_mvcam camera on i2c-11.</code>
+
+<code>Setenv CAMERAMODEL = RAW-MIPI-SC535M</code>
+<code>Setenv FPS = 49</code>
+
+<code>Setenv HEIGHT = 2048</code>
+
+<code>Setenv WIDTH = 2432</code>
+
+You can verify the environment variable output using:
+
+<code>echo $CAMERAMODEL</code>
+
+Note that these environment variables are only valid for the current session.
+
+'''Important Notes:'''
+
+*This script requires the <code>mvcam</code> driver version '''1.1.06 or later'''.
+*If your driver version is '''earlier than 1.1.06''' or you need to use different width, height, or frame rate values, refer to the camera module manual and manually configure the following environment variables. Otherwise, subsequent programs may not function correctly.
+
+Example:
+
+<code>export WIDTH=2432</code>
+
+<code>export HEIGHT=2048</code>
+
+<code>export FPS=50</code>
+====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>
==== Using media-ctl to view topology ====
==== Using media-ctl to view topology ====
Using the media-ctl command can clearly display the current topography structure.
Using the media-ctl command can clearly display the current topography structure.
Line 248:
Line 298:
=== Application examples ===
=== Application examples ===
−==== Configure parameters using v4l2-ctl ====
==== Configure parameters using v4l2-ctl ====
<code>$ v4l2-ctl -d /dev/v4l-subdev2 -L</code>
<code>$ v4l2-ctl -d /dev/v4l-subdev2 -L</code>