@sheko It looks like nothing is abnormal. You haven’t installed a lens, right?
-
RE: cssc132 (Raspberry pi 5). Not a video capture device. /dev/videoXX: No such deviceposted in CS MIPI camera
-
RE: cssc132 (Raspberry pi 5). Not a video capture device. /dev/videoXX: No such deviceposted in CS MIPI camera
cd veye_viewer chmod +x ./* chmod 755 ./config/*.sh ./start_veye_viewer.sh
-
RE: cssc132 (Raspberry pi 5). Not a video capture device. /dev/videoXX: No such deviceposted in CS MIPI camera
@sheko
Hi,
It looks like you downloaded the source code, but didn’t compile it. You can download the precompiled binary from the link below and run it directly.
https://github.com/veyeimaging/veye_viewer/releases/download/v1.1.4_rpi/veye_viewer_RaspberryPi_bin.zip
-
RE: cssc132 (Raspberry pi 5). Not a video capture device. /dev/videoXX: No such deviceposted in CS MIPI camera
You have successfully loaded the driver and detected the camera. Please refer to the instructions for the veye_viewer client software in the previous link to directly preview the images:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi#veye_viewer
-
RE: cssc132 (Raspberry pi 5). Not a video capture device. /dev/videoXX: No such deviceposted in CS MIPI camera
@sheko
The RAW-MIPI-SC132M module requires the mvcam driver, not cssc132.
-
RE: GX-MIPI-IMX662 driver source code for kernel 6.1posted in Rockchip App camera
@xlwvu7mx
The driver has been uploaded to GitHub, please check.
-
RE: Jetson Nano Orin IMX462posted in VEYE MIPI camera
@d_101 Sorry for the late reply. Based on the current situation, I can only suspect a hardware issue that is causing the I2C path to be unavailable. This could be a problem with your mainboard or with the camera itself. Please return the camera to us, and we will perform testing and inspection.
-
RE: MV-MIPI-IMX264M Mono12posted in VEYE MIPI camera
@ffgemanof
The veye_viewer client currently does not support the mono10 and mono12 formats. If you need to use these formats, please configure the data format using mv_mipi_i2c_new.sh, and then acquire the data using v4l2-ctl or the V4L2 API.