Where did you get the camera module(s)?
Model number of the product(s)?
New 64mp Hawkeye (arducam_64mp)
What hardware/platform were you working on?
Raspberry Pi 4 Model B Rev 1.2
Debian Bullseye 64-bit
Instructions you have followed. (link/manual/etc.)
(downloaded from Arducam website)
Problems you were having?
These errors occur each time a libcamera command is issued:
[0:37:04.875486311]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3572-e13ccdd5
[0:37:04.928394494]  WARN CameraSensorProperties camera_sensor_properties.cpp:163 No static properties available for ‘arducam_64mp’
[0:37:04.928448604]  WARN CameraSensorProperties camera_sensor_properties.cpp:165 Please consider updating the camera sensor properties database
[0:37:04.928843894]  ERROR CameraSensor camera_sensor.cpp:591 ‘arducam_64mp 10-001a’: Camera sensor does not support test pattern modes.
[0:37:04.952226129]  WARN RPI raspberrypi.cpp:1263 Mismatch between Unicam and CamHelper for embedded data usage!
[0:37:04.952886692]  ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009a090a but control is not exposed by device /dev/v4l-subdev0
[0:37:04.953089855]  INFO RPI raspberrypi.cpp:1386 Registered camera /base/soc/i2c0mux/[email protected]/[email protected] to Unicam device /dev/media0 and ISP device /dev/media2
The dmesg log from your hardware?
Not applicable, but if you really need the entire log, I can provide it
Troubleshooting attempts you’ve made?
Reinstalled, researched to no avail
What help do you need?
Why do these errors and warnings appear?
Should I be concerned?
Can I fix or eliminate them?
It seems like many other users of the new Pivariety cameras see similar errors and warnings.
I’m sorry you have this problem with your device, we need some more details before we can help you.
cat /proc/cpuinfo cat /etc/os-release cat /boot/config.txt ls /dev/video* dpkg -l | grep libcamera dmesg
Thank you, Edward, for your help. But are you implying that this is not a common problem to all users of the new 64mp Hawkeye camera? Hopefully, the info below will assist you, but I was under the impression that all new 64mp cameras (and perhaps other Pivariety cameras) were exhibiting this same behavior. I only say that because of numerous Google searches and results that others have posted.
Either way, I do truly appreciate your help!
$ cat /proc/cpuinfo
processor : 0 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 1 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 2 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 3 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 Hardware : BCM2835 Revision : c03112 Serial : 10000000a321b45d Model : Raspberry Pi 4 Model B Rev 1.2
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
$ cat /boot/config.txt
# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on # Automatically load overlays for detected cameras #camera_auto_detect=1 # Automatically load overlays for detected DSI displays display_auto_detect=1 # Enable DRM VC4 V3D driver #dtoverlay=vc4-kms-v3d #max_framebuffers=2 # Run in 64-bit mode arm_64bit=1 # Disable compensation for displays with overscan disable_overscan=1 [cm4] # Enable host mode on the 2711 built-in XHCI USB controller. # This line should be removed if the legacy DWC2 controller is required # (e.g. for USB device mode) or if USB support is not required. otg_mode=1 [pi4] # Run as fast as firmware / board allows arm_boost=1 [all] arm_boost=1 dtoverlay=vc4-kms-v3d,cma-512 max_framebuffers=2 dtoverlay=arducam_64mp gpu_mem=128
$ ls /dev/video*
/dev/video0 /dev/video11 /dev/video14 /dev/video18 /dev/video22 /dev/video1 /dev/video12 /dev/video15 /dev/video20 /dev/video23 /dev/video10 /dev/video13 /dev/video16 /dev/video21 /dev/video31
$ dpkg -l | grep libcamera
ii libcamera-apps 0.0.7 arm64 libcamera-apps ii libcamera-dev 0.0.7 arm64 libcamera
Regarding “dmesg” output, I cannot append it here. I tried, but it has over 500 lines, and then when I tried to complete this post, your forum software said I had exceeded the post size limit of 32000 characters. I can try adding it as a separate post later, or if you can tell me what specific info you are wanting to see in the dmesg log, I can extract that portion.
My ‘dmesg’ output is 509 lines with 36287 characters, so I can’t post the entire thing (there’s a 32000 character posting limit).
Give me something to grep for, and I will try to provide you what you need.
That’s enough information, I found your config file a bit odd, I’ll test it at work and give you a reply.
Before that, you can try to open the line ，reboot and try.
Thank you. For clarification, my camera DOES work, even without that autodetect enabled in the config.txt file. I just always get the originally posted errors every single time I issue any libcamera command. I commented out that line myself, trying to debug this. It did the same thing with or without that autodect line.
$ libcamera-still --list-cameras
[0:03:09.258171526]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3572-e13ccdd5 [0:03:09.272355158]  WARN CameraSensorProperties camera_sensor_properties.cpp:163 No static properties available for 'arducam_64mp' [0:03:09.272435819]  WARN CameraSensorProperties camera_sensor_properties.cpp:165 Please consider updating the camera sensor properties database [0:03:09.273040038]  ERROR CameraSensor camera_sensor.cpp:591 'arducam_64mp 10-001a': Camera sensor does not support test pattern modes. [0:03:09.321538440]  WARN RPI raspberrypi.cpp:1263 Mismatch between Unicam and CamHelper for embedded data usage! [0:03:09.322578610]  ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009a090a but control is not exposed by device /dev/v4l-subdev0 [0:03:09.322925809]  INFO RPI raspberrypi.cpp:1386 Registered camera /base/soc/i2c0mux/[email protected]/[email protected] to Unicam device /dev/media3 and ISP device /dev/media2 Available cameras ----------------- 0 : arducam_64mp [9248x6944] (/base/soc/i2c0mux/[email protected]/[email protected]) Modes: 'SRGGB10_CSI2P' : 1280x720 1920x1080 2312x1736 3840x2160 4624x3472 9152x6944
This error does not affect your use, you can completely ignore him.This information is more of a warning, and a small amount of error is useless. It’s a normal state to have these things on our devices as well.
Thank you, Edward. I’m willing to ignore these warnings and errors, but I do hope the Arducam engineers and device driver programmers have at least considered them. Some of them sound fixable and suggest incompatibilities between libcamera and the Pivariety 64mp.
This is a good suggestion.We are working with raspberrypi, these problems will have solutions and reasonable explanations in the future. I hope you will continue to pay attention to our development.