@alex_ai ./media_setting_rpi5**.sh is not necessary.
-
RE: IMX462M pixelformat on RPi5
-
RE: NVidia Jetson Jetpack 6 support?
@vitob We are working on the driver port and expect it to be done and released in a week.
-
RE: IMX462M pixelformat on RPi5
@alex_ai
You can use the latest libpisp and try again. -
RE: MIPI-VEYE462 menu on screen display
@oleg
This means you have some interference and noise on the i2c bus. Suggest you check your design, are there multiple peripherals mounted on the i2c bus and is it possible that communication on the bus is going into an uncontrollable state?
For this camera right now, it is recommended to power down and the menu will go away when you re-power up the camera. -
RE: IMX462M pixelformat on RPi5
@alex_ai
To facilitate the application of the mv series cameras, we have released a beta version of the libcamera support package.
It doesn't do isp tunning, so you can try it out. Please contact me if you have any questions.https://github.com/veyeimaging/libcamera
https://github.com/veyeimaging/raspberrypi_v4l2 -
RE: MV IMX 287 多相机12bit录制问题
@etherealhorizon
使用mv_mipi_i2c.sh脚本,只是直接写入了摄像头寄存器,配置了摄像头的数据格式,但是v4l2驱动中并未得到通知。建议你采用v4l2-ctl配置相机关于相机分辨率,帧率,数据格式的参数。
比如用下面这个脚本测测看。export WIDTH=704 export HEIGHT=544 export FPS=319 v4l2-ctl --set-ctrl roi_x=0 v4l2-ctl --set-ctrl roi_y=0 v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=XY12 v4l2-ctl --set-ctrl frame_rate=$FPS v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=XY12 --stream-mmap --stream-count=1000 -d /dev/video0 --verbose --stream-to=test1.raw
-
RE: ADP-N1-V2.0板载咨询
@fancong 你可以参考一下我们CSIMX307模组在agx xavier或者agx orin平台的device tree的源文件。
-
RE: MV-MIPI-130M throw V-by-one
export I2C_BUS=7 export WIDTH=1280 export HEIGHT=1024 export FPS=108 media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']' v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null
-
RE: different modules simultaneously on jetson nano mipi interface
@joe
Of course. What you need to do is to reintegrate the DTS based on our released code and compile it into the required DTB file.
Specifically, the DTB file we are currently releasing configures both CAM0 and CAM1 as the same camera model.
Now, you need to integrate the DTS files of the two camera models into one DTB file. This will specify that CAM0 is one model and CAM1 is another model of the camera.