Problem with Arducam Pivariety 8MP Synchronized Stereo 360° Camera Kit for Raspberry Pi

  1. Where did you get the camera module(s)?
    Arducam Pivariety 8MP Synchronized Stereo 360° Camera Kit for Raspberry Pi | The Pi Hut

  2. Model number of the product(s)?
    Arducm UC-512 Rev.D1

  3. What hardware/platform were you working on?
    Raspberry Pi 4 Model B Rev 1.2

========
$ uname -a
Linux awd-base 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

==================
$ cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian

  1. Instructions you have followed. (link/manual/etc.)
    They have now been removed from your site and simply replaced with a getting started page outlining the use of Bullseye OS.

  2. Problems you were having?
    Okay, after a while of purchasing the camera i managed to get the camera assembly working correctly using Raspian Buster. Unfortunately after about a month the camera assembly stopped working displaying a segmentation fault as outlined below, after a poweroff.

$ libcamera-hello
[0:05:19.178840680] [1849] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3139-5baab39e
[0:05:19.184382516] [1854] WARN CameraSensor camera_sensor.cpp:197 ‘arducam-pivariety 10-000c’: Recommended V4L2 control 0x009a0922 not supported
[0:05:19.219286913] [1854] WARN CameraSensor camera_sensor.cpp:249 ‘arducam-pivariety 10-000c’: The sensor kernel driver needs to be fixed
[0:05:19.219681149] [1854] WARN CameraSensor camera_sensor.cpp:251 ‘arducam-pivariety 10-000c’: See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information
[0:05:19.222420022] [1854] WARN CameraSensorProperties camera_sensor_properties.cpp:141 No static properties available for ‘arducam-pivariety’
[0:05:19.222606548] [1854] WARN CameraSensorProperties camera_sensor_properties.cpp:143 Please consider updating the camera sensor properties database
[0:05:19.222751854] [1854] WARN CameraSensor camera_sensor.cpp:414 ‘arducam-pivariety 10-000c’: Failed to retrieve the camera location
[0:05:19.592889534] [1854] WARN RPiController controller.cpp:47 No algorithm found for “version”
[0:05:19.593026730] [1854] WARN RPiController controller.cpp:47 No algorithm found for “target”
[0:05:19.593105540] [1854] WARN RPiController controller.cpp:47 No algorithm found for “algorithms”
[0:05:19.595085498] [1854] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009a090a but control is not exposed by device /dev/video0
[0:05:19.597295886] [1849] INFO Camera camera.cpp:937 configuring streams: (0) 1920x540-YUV420
[0:05:19.597642310] [1854] INFO RPI raspberrypi.cpp:122 Mode: 1600x600 fmt RG10 Score: 4821.67 (best 4821.67)
[0:05:19.597816115] [1854] INFO RPI raspberrypi.cpp:122 Mode: 2560x720 fmt RG10 Score: 1705 (best 1705)
[0:05:19.597917146] [1854] INFO RPI raspberrypi.cpp:122 Mode: 3840x1080 fmt RG10 Score: 2115 (best 1705)
[0:05:19.598011659] [1854] INFO RPI raspberrypi.cpp:122 Mode: 5184x1944 fmt RG10 Score: 5333.67 (best 1705)
[0:05:19.598108005] [1854] INFO RPI raspberrypi.cpp:122 Mode: 6528x1848 fmt RG10 Score: 3048.26 (best 1705)
[0:05:19.598204536] [1854] INFO RPI raspberrypi.cpp:122 Mode: 6528x2464 fmt RG10 Score: 5851.61 (best 1705)
[0:05:19.598302253] [1854] INFO RPI raspberrypi.cpp:122 Mode: 1600x600 fmt pRAA Score: 4321.67 (best 1705)
[0:05:19.598398340] [1854] INFO RPI raspberrypi.cpp:122 Mode: 2560x720 fmt pRAA Score: 1205 (best 1205)
[0:05:19.598490742] [1854] INFO RPI raspberrypi.cpp:122 Mode: 3840x1080 fmt pRAA Score: 1615 (best 1205)
[0:05:19.598582644] [1854] INFO RPI raspberrypi.cpp:122 Mode: 5184x1944 fmt pRAA Score: 4833.67 (best 1205)
[0:05:19.598676675] [1854] INFO RPI raspberrypi.cpp:122 Mode: 6528x1848 fmt pRAA Score: 2548.26 (best 1205)
[0:05:19.598770021] [1854] INFO RPI raspberrypi.cpp:122 Mode: 6528x2464 fmt pRAA Score: 5351.61 (best 1205)
[0:05:19.731153990] [1854] INFO RPI raspberrypi.cpp:624 Sensor: /base/soc/i2c0mux/[email protected]/[email protected] - Selected mode: 2560x720-pRAA
Segmentation fault

  1. The dmesg log from your hardware?
    Do you need the whole log
    Otherwise are the following enough?
    =================
    $ dmesg | grep -E “imx477|imx219|arducam”
    [ 7.579526] arducam: loading out-of-tree module taints kernel.
    [ 7.595321] arducam-pivariety 10-000c: firmware version: 0x10003
    [ 31.836483] arducam_vddl: disabling
    [ 31.836510] arducam_vdig: disabling
    [ 31.836539] arducam_vana: disabling

=================
$ dmesg | grep -E “raspberrypi-firmware soc:firmware”
[ 0.100898] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-12-01T15:01:54, variant start
[ 0.110911] raspberrypi-firmware soc:firmware: Firmware hash is 71bd3109023a0c8575585ba87cbb374d2eeb038f

  1. Troubleshooting attempts you’ve made?
    I purchased a new assembly, which also did not work. So subsequently then tried the assembly using BullseyeOS and the camera works fine, but still not with buster. Other than the occasional apt-get install the OS and built kernel had remained the same.

  2. What help do you need?
    I would like to understand how to fix the camera assembly and getting it working again. I have spent many hours trying to do what I can to overcome this issue but it seems beyond my understanding.

Please help me!!

additional information taken:

$ cat /boot/config.txt (not i’ve deleted all commented parts out)

disable_overscan=1
dtparam=i2c_arm=on

[all]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
dtoverlay=arducam
dtparam=i2c_vc=on
gpu_mem=256

===============
$ cat /boot/cmdline.txt
console=serial0,115200 console=tty1 root=PARTUUID=d0f6923a-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles

=================
$ vcgencmd bootloader_version
2022/03/10 11:57:12
version 778c182c82ab673c60a476da6f4e73a03854cacd (release)
timestamp 1646913432
update-time 1672500918
capabilities 0x0000007f

=================
$ ls /dev/video* -l
crw-rw----+ 1 root video 81, 8 Jan 2 16:58 /dev/video0
crw-rw----+ 1 root video 81, 9 Jan 2 16:58 /dev/video1
crw-rw----+ 1 root video 81, 0 Jan 2 16:58 /dev/video10
crw-rw----+ 1 root video 81, 1 Jan 2 16:58 /dev/video11
crw-rw----+ 1 root video 81, 2 Jan 2 16:58 /dev/video12
crw-rw----+ 1 root video 81, 4 Jan 2 16:58 /dev/video13
crw-rw----+ 1 root video 81, 5 Jan 2 16:58 /dev/video14
crw-rw----+ 1 root video 81, 6 Jan 2 16:58 /dev/video15
crw-rw----+ 1 root video 81, 7 Jan 2 16:58 /dev/video16
crw-rw----+ 1 root video 81, 3 Jan 2 16:58 /dev/video18

==================
$ v4l2-ctl --list-formats-ext -d /dev/video0
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture

[0]: 'pRAA' (10-bit Bayer RGRG/GBGB Packed)
	Size: Discrete 1600x600
	Size: Discrete 2560x720
	Size: Discrete 3840x1080
	Size: Discrete 5184x1944
	Size: Discrete 6528x1848
	Size: Discrete 6528x2464
[1]: 'RG10' (10-bit Bayer RGRG/GBGB)
	Size: Discrete 1600x600
	Size: Discrete 2560x720
	Size: Discrete 3840x1080
	Size: Discrete 5184x1944
	Size: Discrete 6528x1848
	Size: Discrete 6528x2464

==================
$ v4l2-ctl --list-devices -d /dev/video0
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12
/dev/video18

bcm2835-isp (platform:bcm2835-isp):
/dev/video13
/dev/video14
/dev/video15
/dev/video16

unicam (platform:fe801000.csi):
/dev/video0
/dev/video1

=================
$ cat /proc/meminfo
MemTotal: 3748164 kB
MemFree: 2605748 kB
MemAvailable: 2973012 kB
Buffers: 45060 kB
Cached: 604236 kB
SwapCached: 0 kB
Active: 245320 kB
Inactive: 666308 kB
Active(anon): 1432 kB
Inactive(anon): 438652 kB
Active(file): 243888 kB
Inactive(file): 227656 kB
Unevictable: 118716 kB
Mlocked: 16 kB
HighTotal: 3080192 kB
HighFree: 2069924 kB
LowTotal: 667972 kB
LowFree: 535824 kB
SwapTotal: 524284 kB
SwapFree: 524284 kB
Dirty: 176 kB
Writeback: 0 kB
AnonPages: 381048 kB
Mapped: 322364 kB
Shmem: 177752 kB
KReclaimable: 21224 kB
Slab: 45356 kB
SReclaimable: 21224 kB
SUnreclaim: 24132 kB
KernelStack: 2944 kB
PageTables: 15352 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 2398364 kB
Committed_AS: 2907048 kB
VmallocTotal: 245760 kB
VmallocUsed: 6584 kB
VmallocChunk: 0 kB
Percpu: 576 kB
CmaTotal: 327680 kB
CmaFree: 285080 kB

===================
$ i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –

===================
$ i2cdetect -l
i2c-1 i2c bcm2835 ([email protected]) I2C adapter
i2c-22 i2c bcm2835 ([email protected]) I2C adapter
i2c-0 i2c i2c-22-mux (chan_id 0) I2C adapter
i2c-10 i2c i2c-22-mux (chan_id 1) I2C adapter

I have taken other details but didn’t want to fill the topic up. Is there anything I can also do to assist

Many thanks and thank you for any assistance you can give me

Hi Dave,
It seems like you have to use the camera assembly on the Buster OS, doesn’t it? We do not want to support the Buster OS anymore because of the Raspberry Pi’s updated Bullseye OS. Hence, we removed the content about Buster from the new DOC website.

Can the previous camera work fine on the Bulleye OS?

Hi Dion

I was wondering if you had any ideas on possible docker solutions for ubuntu.
I could possibly work with ROS from inside a container.
Does that sound like a solution Arducam could help me with?

Many thanks

Dear Dion

I hope I can put my case to you properly.

After purchasing the device, I have worked tirelessly for5-6 months developing code to work with ROS. Now unfortunately I find I am unable to use the camera assembly. This means that all my hard work
would have been wasted completely. I had been making SIM backups throughout the process, but had not realised a simple change in EEPROM would have such a major issue, as I am now unable even to put the OS back to an original state to control and work from.

Unfortunately, ROS now does not support Bullseye OS directly, and I have been unable to get it working on Bullseye. Whilst I understand the camera assembly works, it is not useful now. I have tried to work through my previous steps and it seems that Arducam have completely locked Buster out by further installing arducam_pivariety_v4l2_5.10.92_later.tar.gz as system of control.

Please can Arducam help me in some way, I am willing to lock the system down and make further eeprom backups afterwards so that the problem doesn’t occur again. But I feel I deserve some support even its for a short time.

As Arducam have stated the camera assembly can be used with Ubuntu but there are no instructions on how to do so. If I have missed these instructions, please could you reply with them. I have recently spent the past few weeks just trying to get the cameras working, time I will never get back on my project. And if I can’t, months of coding goes to waste.

Please help me in some way, I really do need it, either in Ubuntu 20.04 or Buster.

Yours sincerely

Dave Baker