Camera OV5647 error

lebossejames · July 22, 2025, 12:50pm

Dear,

I activate overlay Raspberry camera 1.3 on my Zero 3W (BullEye) when i execute this command:

gst-launch-1.0 v4l2src device=/dev/video11 io-mode=4 ! videoconvert ! video/x-raw,format=NV12,width=1920,height=1080 ! jpegenc ! multifilesink location=file.name.jpg;
Setting pipeline to PAUSED ...
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video11'.
Additional debug info:
../sys/v4l2/v4l2_calls.c(608): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: No such file or directory
ERROR: pipeline doesn't want to preroll.
Failed to set pipeline to PAUSED.
Setting pipeline to NULL ...
Freeing pipeline ...

I get this error, how can i resolve please?

avaf · July 23, 2025, 12:27pm

try with

device=/dev/video0

And it should be something like:
gst-launch-1.0 v4l2src device=/dev/video0 io-mode=dmabuf num-buffers=1 ! video/x-raw,format=NV12,width=640,height=480 ! mppjpegenc ! filesink location=file.name.jpg

lebossejames · July 24, 2025, 8:27am

I have the same problem /dev/video0 not recognized:

radxa@radxa-zero3:~$ ls /dev/video*
/dev/video-enc0
/dev/video-dec0

So i boot with other OS system Bookworm KDE, less issues on this OS.

radxa@radxa-zero3:~$ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=dmabuf num-buffers=1 ! video/x-raw,format=NV12,width=640,height=480 ! mppjpegenc ! filesink location=file.name.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
rga_api version 1.10.1_[4]
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:00.657538604
Setting pipeline to NULL ...
Freeing pipeline ...
radxa@radxa-zero3:~$

Now, when i open file.name.jpg, it’s black screen.

radxa@radxa-zero3:~$ ls /dev/video*
/dev/video0  /dev/video2  /dev/video4  /dev/video6  /dev/video8  /dev/video-camera0  /dev/video-enc0
/dev/video1  /dev/video3  /dev/video5  /dev/video7  /dev/video9  /dev/video-dec0

avaf · July 24, 2025, 11:55am

check the output of

ls -la /dev/video-camera0

maybe you should enable the camera with rsetup?

lebossejames · July 24, 2025, 12:07pm

radxa@radxa-zero3:~$ ls -la /dev/video-camera0
lrwxrwxrwx 1 root root 6 Jul 24 11:17 /dev/video-camera0 -> video0

I enable my camera on rsetup:

radxa@radxa-zero3:~$ journalctl -xb > test.txt

journalctl.zip (15.6 KB)

avaf · July 24, 2025, 6:09pm

Check the output of:
sudo systemctl status rkaiq_3A

lebossejames · July 25, 2025, 10:05am

radxa@radxa-zero3:~$ sudo systemctl status rkaiq_3A
● rkaiq_3A.service - Enable Rockchip camera engine rkaiq
 Loaded: loaded (/lib/systemd/system/rkaiq_3A.service; enabled; preset: enabled)
 Active: active (running) since Thu 2025-07-24 11:17:43 CEST; 24h ago
  Tasks: 9 (limit: 4660)
 Memory: 10.3M
    CPU: 279ms
 CGroup: /system.slice/rkaiq_3A.service
         ├─308 /usr/bin/rkaiq_3A_server
         └─309 logger -t rkaiq

Jul 24 11:17:44 radxa-zero3 rkaiq[309]: DBG: /dev/media0: wait stream start event...
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: /dev/media0: wait stream start event success ...
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: device manager start
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: CAMHW:K:cid[0] start success. isGroup:0, isOnline:1, isMultiIsp:0, init_ens:0x1bf88>
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: XCORE:K:cid[0] rk_aiq_uapi_sysctl_start success.
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: rkisp_init engine succeed
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: /dev/media0: wait stream stop event...
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: /dev/media0: wait stream stop event success ...
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: XCORE:K:cid[0] rk_aiq_uapi_sysctl_stop success.
Jul 24 14:10:55 radxa-zero3 rkaiq[309]: DBG: /dev/media0: wait stream start event...

avaf · July 25, 2025, 12:17pm

Everything looks fine.

My last guess is that the iqfile for OV5647 is not compatible with the kernel version you are using.
You may check this by doing:
1 - Stop the camera engine
sudo systemctl stop rkaiq_3A

2- point the camera at a strong light source (powerful)
Take the photo and check the picture

3- try using cheese or ffplay to double check

if it is still black, check the sensor with:
sudo dmesg|grep -i ov
and
sudo dmesg|grep -i isp

lebossejames · July 25, 2025, 2:03pm

i point a strong light, the picture display my light with black background.

radxa@radxa-zero3:~$ sudo dmesg|grep -i ov
[103308.106643] ov5647 2-0036: stream start
[103308.106653] ov5647 2-0036: OV5647 power on
[103308.789815] ov5647 2-0036: stream stop
[103308.791294] ov5647 2-0036: OV5647 power off
[103314.282395] ov5647 2-0036: stream start
[103314.282406] ov5647 2-0036: OV5647 power on
[103314.968303] ov5647 2-0036: stream stop
[103314.969698] ov5647 2-0036: OV5647 power off
radxa@radxa-zero3:~$ sudo dmesg|grep -i isp
[103307.079405] rkisp_hw fdff0000.rkisp: set isp clk = 297000000Hz
[103308.106517] rkisp-vir0: waiting on params stream on event timeout
[103308.729376] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.729435] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.735909] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.735941] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.736000] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.737242] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.737333] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.737366] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.737561] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.737658] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.742151] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.742243] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.742273] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.742602] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.742729] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.743803] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.743931] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.744224] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.744320] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.744353] rkisp-vir0: MIPI error: packet: 0x01000000
[103308.789631] rkisp-vir0: MIPI error: packet: 0x00000100
[103313.270593] rkisp_hw fdff0000.rkisp: set isp clk = 297000000Hz
[103314.282270] rkisp-vir0: waiting on params stream on event timeout
[103314.907600] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.907633] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.907723] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.908019] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.908115] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.908146] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.914037] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.914065] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.914161] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.914209] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915464] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915494] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915592] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915621] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915786] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.915915] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.940650] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.940712] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.940745] rkisp-vir0: MIPI error: packet: 0x01000000
[103314.968116] rkisp-vir0: MIPI error: packet: 0x00000100

avaf · July 25, 2025, 3:39pm

“The error code 0x01000000 often points to a synchronization or data integrity issue within the MIPI stream.”

I would suggest downgrading the kernel version if possible.