FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

2x VD66GY on STEVAL P-board with Raspberry Pi 5 — CSI1 V4L2 failed to queue buffe

tanguy1
Associate

‎2026-05-07 10:22 AM

I am trying to capture video streams from two VD66GY cameras connected to the CSI0 and CSI1 ports of a Compute Module 5 IO Board. My OS is : Linux raspberrypi 6.12.75+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/Linux

Both seem to be recognized:

screen1_cam_detect.png

However, when I try to capture video from both cameras simultaneously, only the CSI0 port works. The CSI1 port returns the following error with this command ( rpicam-hello --camera 1):

screen2_error_V4L2.png

2screen2_error_V4L2.png

I also tried a GStreamer command, but it didn't make any difference.

I don't have much experience with V4L2 or camera systems in general, so I'm not really sure how to fix this problem. Maybe I missed a step during setup, but that seems unlikely. Even after searching for similar issues, I haven't found anything conclusive.

What I have already tested:

  • When using two different cameras — CSI0 = VD66GY and CSI1 = IMX296 — I can capture both video streams successfully. The reverse configuration does not work if VD66GY is connected to csi1.
  • I tested different resolutions and frame rates, but the issue remains the same.
  • I correctly modified the /boot/firmware/config.txt file with:
    • camera_auto_detect=0
    • dtoverlay=pcb4280_vd66gY,cam0
    • dtoverlay=pcb4280_vd66gY,cam1
  • I tested both VD66GY cameras individually, and both work correctly when connected to CSI0.
  • I tried the v4l2vd56g3 driver from both the main and Debian branches, but the issue persists.
    Driver: https://github.com/STMicroelectronics/vd56g3-linux-driver
  • I also tried installing libcamera from both the main and Debian branches, and I still have the same problem.
    Libcamera: https://github.com/STMicroelectronics/libcamera

It seems to me that even though both cameras are detected correctly, V4L2 may somehow confuse them at some point.

Does anyone have any ideas on how to solve this problem?

Thanks in advance for your help.

 

Labels:
0 Kudos
2 REPLIES 2
Jean_Poire
ST Employee

‎2026-05-18 7:44 PM

Hello @tanguy1 ,

 

I am not able to reproduce your error. That works fine on my side.

Here are some questions/tests to run to try to understand a bit better the issue:

  1. Are you able to stream with vd66gy on cam1 when doing single camera streaming?
  2. The error you mention only occurs when streaming simultaneously or it also occurs when streaming only with cam1 while cam0 is connected but not streaming?

Can you also check if you have more details about the error in dmesg?

 

Best regards,

Jean

0 Kudos
tanguy1
Associate
In response to Jean_Poire

‎2026-05-26 12:42 AM

Hello,

  • When I disconnect the camera on CSI0 and leave the one on CSI1, nothing changes: I still cannot view the stream on CSI1.
  • Same thing if the camera on CSI0 is connected but not active.
  • And obviously when I am trying to show two streams at the same time it is not working.

However, I have no issues if I perform exactly the same operations with cameras from Arducam and Raspberry.

The command I use to show the streams for my tests is : rpicam-hello --camera 0 or 1.

 

I carried out tests with only one camera connected on CSI1 of the dev board and I get the following results:

rogne_screen1_cam_detect.pngrogne_screen_error_meson2.png

Note that I repeated the tests, but this time on CSI0, and the error related to memory_lifetime_test no longer appears.

Here is an excerpt from the kernel error messages when I try to display the stream on the devboard's physical CSI1 port:

 

[ 2195.157931] ------------[ cut here ]------------
[ 2195.157932] WARNING: CPU: 0 PID: 15529 at drivers/media/v4l2-core/v4l2-subdev.c:457 call_s_stream+0xf4/0x108 [videodev]
[ 2195.157948] Modules linked in: cfg80211 snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill binfmt_misc vd56g3(O) v4l2_cci regmap_i2c spidev aes_ce_blk aes_ce_cipher ghash_ce gf128mul libaes sha2_ce sha256_arm64 sha1_ce sha1_generic raspberrypi_hwmon spi_bcm2835 rp1_cfe rpi_hevc_dec pisp_be v4l2_fwnode v4l2_mem2mem v4l2_async videobuf2_dma_contig i2c_brcmstb videobuf2_memops gpio_keys videobuf2_v4l2 pwm_fan rp1_pio videodev rp1_fw raspberrypi_gpiomem videobuf2_common spi_dw_mmio rp1_adc mc i2c_designware_platform i2c_designware_core spi_dw rp1_mailbox nvmem_rmem i2c_dev ledtrig_pattern fuse dm_mod ip_tables x_tables ipv6 vc4 snd_soc_hdmi_codec snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm v3d snd_timer drm_shmem_helper snd drm_display_helper drm_dma_helper cec drm_kms_helper gpu_sched drm drm_panel_orientation_quirks backlight uio_pdrv_genirq uio
[ 2195.157999] CPU: 0 UID: 1000 PID: 15529 Comm: rpicam-hello Tainted: G        W  O       6.12.75+rpt-rpi-2712 #1  Debian 1:6.12.75-1+rpt1~bookworm
[ 2195.158001] Tainted: [W]=WARN, [O]=OOT_MODULE
[ 2195.158003] Hardware name: Raspberry Pi Compute Module 5 Rev 1.0 (DT)
[ 2195.158004] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2195.158006] pc : call_s_stream+0xf4/0x108 [videodev]
[ 2195.158021] lr : cfe_stop_streaming+0xdc/0x210 [rp1_cfe]
[ 2195.158025] sp : ffffc0008bcc3ae0
[ 2195.158026] x29: ffffc0008bcc3ae0 x28: ffffd06f9a8a0be8 x27: ffffd06f9a7090f8
[ 2195.158030] x26: 0000000000000000 x25: ffff800180c236a8 x24: ffff800301ca9200
[ 2195.158033] x23: ffff800180c20370 x22: 0000000000000000 x21: 0000000000000000
[ 2195.158036] x20: ffff800180c20000 x19: 0000000000000008 x18: 0000000000000000
[ 2195.158040] x17: 0000000000000000 x16: ffffd06fcf1cf250 x15: 00007fff5c045cd0
[ 2195.158043] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[ 2195.158046] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffd06f9a88f28c
[ 2195.158049] x8 : ffffc0008bcc3d48 x7 : 0000000000000005 x6 : 0000000000000025
[ 2195.158053] x5 : ffff800180c24358 x4 : 0000000000000000 x3 : ffffd06f9a6cebb0
[ 2195.158056] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff80018119b088
[ 2195.158059] Call trace:
[ 2195.158060]  call_s_stream+0xf4/0x108 [videodev]
[ 2195.158076]  cfe_stop_streaming+0xdc/0x210 [rp1_cfe]
[ 2195.158079]  __vb2_queue_cancel+0x34/0x2d8 [videobuf2_common]
[ 2195.158084]  vb2_core_streamoff+0x2c/0xd0 [videobuf2_common]
[ 2195.158089]  vb2_ioctl_streamoff+0x54/0xa0 [videobuf2_v4l2]
[ 2195.158093]  v4l_streamoff+0x2c/0x40 [videodev]
[ 2195.158108]  __video_do_ioctl+0x170/0x3e0 [videodev]
[ 2195.158123]  video_usercopy+0x1c0/0x790 [videodev]
[ 2195.158138]  video_ioctl2+0x20/0x38 [videodev]
[ 2195.158152]  v4l2_ioctl+0x48/0x70 [videodev]
[ 2195.158167]  __arm64_sys_ioctl+0xb4/0x100
[ 2195.158170]  invoke_syscall+0x50/0x120
[ 2195.158173]  el0_svc_common.constprop.0+0x48/0xf0
[ 2195.158176]  do_el0_svc+0x24/0x38
[ 2195.158179]  el0_svc+0x30/0x100
[ 2195.158182]  el0t_64_sync_handler+0x100/0x130
[ 2195.158184]  el0t_64_sync+0x190/0x198
[ 2195.158186] ---[ end trace 0000000000000000 ]---
[ 2195.158214] ------------[ cut here ]------------
[ 2195.158216] WARNING: CPU: 0 PID: 15529 at drivers/media/common/videobuf2/videobuf2-core.c:2215 __vb2_queue_cancel+0x238/0x2d8 [videobuf2_common]
[ 2195.158222] Modules linked in: cfg80211 snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill binfmt_misc vd56g3(O) v4l2_cci regmap_i2c spidev aes_ce_blk aes_ce_cipher ghash_ce gf128mul libaes sha2_ce sha256_arm64 sha1_ce sha1_generic raspberrypi_hwmon spi_bcm2835 rp1_cfe rpi_hevc_dec pisp_be v4l2_fwnode v4l2_mem2mem v4l2_async videobuf2_dma_contig i2c_brcmstb videobuf2_memops gpio_keys videobuf2_v4l2 pwm_fan rp1_pio videodev rp1_fw raspberrypi_gpiomem videobuf2_common spi_dw_mmio rp1_adc mc i2c_designware_platform i2c_designware_core spi_dw rp1_mailbox nvmem_rmem i2c_dev ledtrig_pattern fuse dm_mod ip_tables x_tables ipv6 vc4 snd_soc_hdmi_codec snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm v3d snd_timer drm_shmem_helper snd drm_display_helper drm_dma_helper cec drm_kms_helper gpu_sched drm drm_panel_orientation_quirks backlight uio_pdrv_genirq uio
[ 2195.158273] CPU: 0 UID: 1000 PID: 15529 Comm: rpicam-hello Tainted: G        W  O       6.12.75+rpt-rpi-2712 #1  Debian 1:6.12.75-1+rpt1~bookworm
[ 2195.158276] Tainted: [W]=WARN, [O]=OOT_MODULE
[ 2195.158277] Hardware name: Raspberry Pi Compute Module 5 Rev 1.0 (DT)
[ 2195.158278] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2195.158280] pc : __vb2_queue_cancel+0x238/0x2d8 [videobuf2_common]
[ 2195.158285] lr : __vb2_queue_cancel+0x34/0x2d8 [videobuf2_common]
[ 2195.158290] sp : ffffc0008bcc3b50
[ 2195.158291] x29: ffffc0008bcc3b50 x28: ffffd06f9a8a0be8 x27: ffffd06f9a7090f8
[ 2195.158294] x26: 0000000000000000 x25: ffff800180c236a8 x24: ffff800301ca9200
[ 2195.158297] x23: 0000000000000000 x22: ffff800180c23530 x21: ffffd06f9a7090f8
[ 2195.158301] x20: 000000000000000d x19: ffff800180c23530 x18: 0000000000000000
[ 2195.158304] x17: 0000000000000000 x16: ffffd06fcec40700 x15: 00007fff5c045cd0
[ 2195.158307] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[ 2195.158310] x11: 00000000000000c0 x10: 0000000000001a40 x9 : ffffd06fce4e0658
[ 2195.158314] x8 : ffff80018ab3e8a0 x7 : 0000000000000008 x6 : 0000000000000000
[ 2195.158317] x5 : 0000000000000001 x4 : 0000000000001ab0 x3 : 0000000000000008
[ 2195.158321] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001
[ 2195.158324] Call trace:
[ 2195.158325]  __vb2_queue_cancel+0x238/0x2d8 [videobuf2_common]
[ 2195.158330]  vb2_core_streamoff+0x2c/0xd0 [videobuf2_common]
[ 2195.158335]  vb2_ioctl_streamoff+0x54/0xa0 [videobuf2_v4l2]
[ 2195.158340]  v4l_streamoff+0x2c/0x40 [videodev]
[ 2195.158354]  __video_do_ioctl+0x170/0x3e0 [videodev]
[ 2195.158369]  video_usercopy+0x1c0/0x790 [videodev]
[ 2195.158384]  video_ioctl2+0x20/0x38 [videodev]
[ 2195.158398]  v4l2_ioctl+0x48/0x70 [videodev]
[ 2195.158414]  __arm64_sys_ioctl+0xb4/0x100
[ 2195.158417]  invoke_syscall+0x50/0x120
[ 2195.158420]  el0_svc_common.constprop.0+0x48/0xf0
[ 2195.158423]  do_el0_svc+0x24/0x38
[ 2195.158426]  el0_svc+0x30/0x100
[ 2195.158428]  el0t_64_sync_handler+0x100/0x130
[ 2195.158430]  el0t_64_sync+0x190/0x198
[ 2195.158432] ---[ end trace 0000000000000000 ]---
[ 2195.158434] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state
[ 2195.159635] rp1-cfe 1f00128000.csi: Using a link rate of 804 Mbps
[ 2195.159776] rp1-cfe 1f00128000.csi: stream on failed in subdev
[ 2195.161721] rp1-cfe 1f00128000.csi: Using a link rate of 804 Mbps
[ 2195.161869] rp1-cfe 1f00128000.csi: stream on failed in subdev
[ 2195.164106] rp1-cfe 1f00128000.csi: Using a link rate of 804 Mbps
[ 2195.164290] rp1-cfe 1f00128000.csi: stream on failed in subdev
[ 2195.165736] rp1-cfe 1f00128000.csi: Using a link rate of 804 Mbps
[ 2195.166017] rp1-cfe 1f00128000.csi: stream on failed in subdev
[ 2195.168147] ------------[ cut here ]------------

Could you please provide your configuration so I can try to reproduce it?

  • Which OS and which version are you using?
  • Which STSW-IMG503_RPI libcamera package are you using ? The main branch or the Debian branch? https://github.com/STMicroelectronics/libcamera
  • What version of libcamera do you have ? (In the meantime, I reinstalled the OS from scratch and now I have libcamera 0.5.2 pre-installed.)
  • Is the version of  libcamera proposed by STMicroelectronics required to make  St cameras work correctly ? Or can I use the libcamera pre-installed (version 0.5.2) with the OS ?
  • For the V4L2 package: STSW-IMG503_V4L2, are you using the main branch or the Debian package? https://github.com/STMicroelectronics/vd56g3-linux-driver

Could libcamera already present during the OS installation cause issues with the libcamera provided by ST?

I've already tried displaying the camera stream from the physical CSI1 port using the pre-installed libcamera and the versions provided by St on GitHub, and I'm having the same issue with V4L2.

Best regards,

Tanguy maupetit

0 Kudos
Top