Hi everyone, I’m trying to get an Arducam 64MP camera working with my Raspberry Pi 5 (8GB model), running the latest Raspberry Pi kernel. I followed the Arducam 64MP documentation and a few forum threads to set things up.
The camera is detected fine when I run:
rpicam-still --list
It shows up in the list, so the hardware seems to be enumerating correctly. But when I actually try to open a stream and capture from it, the operation fails. I’ve attached screenshots of the error:
That’s an odd one — detected at the enumeration level but failing on capture definitely points toward a software/driver/kernel issue rather than a physical connection problem.
Could you share which kernel version you’re on? You can check with:
uname -r
Also, have you tried any basic troubleshooting yet? Things like checking dmesg output right after the capture attempt, or trying a lower resolution to see if it’s bandwidth-related?
Kernel version is 6.6.51+rpt-rpi-2712 — that’s the latest available through apt as of a couple days ago.
I actually suspected a hardware issue at first and swapped out the FCC cable entirely with a new one, but the exact same error persists. So I think we can rule out the physical connection.
I also checked dmesg after the failed capture and nothing obvious jumps out — no i2c errors or anything like that. The camera probe seems fine, but the stream just won’t start.
Is this maybe a compatibility issue between the 64MP driver and the newer Pi 5 kernel?
The Pi 5 + latest kernel combination could definitely be a factor. The 64MP module relies on some kernel driver components that don’t always keep pace with the rolling Raspberry Pi kernel updates.
Let’s try a few things before we go deeper:
Can you run dmesg | grep -i arducam and post the output?
Try with libcamera-still instead of rpicam-still and see if the behavior is any different: libcamera-still -o test.jpg --verbose
What does libcamera-hello --list-cameras report? Sometimes the verbose output there can reveal format negotiation issues.
If none of that gives us a lead, this might need a closer look through a remote session.
dmesg | grep -i arducam returns nothing at all after boot — the driver seems to load silently.
libcamera-still -o test.jpg --verbose fails with a similar error during the stream configuration step. It looks like the pipeline sets up but then fails when it tries to actually pull frames.
libcamera-hello --list-cameras does show the Arducam 64MP sensor listed correctly with all expected resolutions, so the driver is definitely loaded and talking to the sensor at some level.
The error seems to happen right at the point where the ISP tries to start processing frames. Not sure where to go from here.
Thanks for running those. The fact that --list-cameras reports the sensor and all resolutions correctly but the pipeline fails at frame acquisition is a pattern I’ve seen before with this sensor on newer kernels — it usually comes down to a subtle mismatch in the media controller pipeline configuration.
Rather than going back and forth with command output here, I think the fastest route would be for me to take a look at your setup directly. I’ve sent you a private message with instructions for setting up a remote session via AnyDesk — please check your inbox. Once you’ve got that ready, we can go through the pipeline configuration in real time and figure out where exactly the handoff is breaking.
Received the message — I’ll get AnyDesk installed on the Pi and book a slot. Appreciate the help, this one has been driving me nuts for a couple of days.
No problem, happy to dig into it with you. One quick heads-up though — our support team operates on UTC+8 time. When you’re booking a slot, just note that the 10:00 PM (22:00) slot is reserved for sales inquiries, not technical support, so please avoid booking that one for this. Pick any other available time that works for you and we’ll get to the bottom of it. I’ll keep an eye out for your booking confirmation and AnyDesk ID.
.png)