Hey everyone, I’m stuck with an Arducam Multi Camera Adapter Module V2.2 on a Raspberry Pi 4B. I’ve got multiple OV5647 cameras connected through it, but I keep getting “No cameras available” in libcamera / raspistill and basically anything that tries to access the cameras. This thing has literally never worked since I got it — I’ve tried reseating the ribbon cables a bunch of times, double-checked the connections on both the camera boards and the Pi side, but no luck. Has anyone run into this before? Any ideas on what I should check first?
Hi there — let’s start with a couple of diagnostic steps so we can see exactly what’s going on. Could you do the following?
1. Photos — Take clear, well-lit photos of:
- Where the ribbon cable connects to the camera board
- Where the ribbon cable connects to the Raspberry Pi itself
Post those here so we can check the physical connections.
2. Diagnostic log — Run these four commands on your Pi in order:
sudo reboot
After it comes back up:
wget -O arducam-camera-bug-report https://github.com/Dion4cen/arducam-camera-bug-report/releases/download/Tool/arducam-camera-bug-report
chmod +x ./arducam-camera-bug-report
./arducam-camera-bug-report
This will generate a file called arducam-bug-report.txt in your current directory. Attach that file in your reply along with the photos and we’ll go from there.
Alright, here are the photos of the connections:
And here’s the diagnostic report: arducam-bug-report.txt
Let me know what you find.
Thanks for those — the physical connections actually look fine from the photos, so that rules out a cabling issue.
Looking at your arducam-bug-report.txt, I can see the problem right away. In your /boot/config.txt, the device tree overlay for the 4-port camera multiplexer is commented out:
#dtoverlay=camera-mux-4port,cam0-ov5647,cam1-ov5647,cam2-ov5647,cam3-ov5647
That leading # means the line is treated as a comment and completely ignored at boot. Without that overlay loaded, the Pi has no idea the multiplexer board is even there, so no cameras ever show up.
Fix: Edit /boot/config.txt and change that line from:
#dtoverlay=camera-mux-4port,cam0-ov5647,cam1-ov5647,cam2-ov5647,cam3-ov5647
to:
dtoverlay=camera-mux-4port,cam0-ov5647,cam1-ov5647,cam2-ov5647,cam3-ov5647
(Just remove the # at the beginning.)
Then reboot:
sudo reboot
That should get the multiplexer recognized and your cameras detected. Give that a try and let me know how it goes.
Okay so I uncommented that line in config.txt exactly as you described and rebooted the Pi. Unfortunately I’m still seeing the exact same “No cameras available” error — nothing changed. I verified the line is definitely uncommented now after the reboot, so it’s not reverting or anything. Any other ideas? This is getting pretty frustrating.
Hmm, that’s unexpected — with the overlay properly loaded, the multiplexer and cameras should at least show up. Since the dtoverlay fix didn’t resolve it, there may be something else going on at a lower level that’s hard to diagnose through forum posts alone.
I’ve sent you a private message with details on setting up a remote support session so we can take a look at your Pi directly. In a nutshell, we’d use AnyDesk to connect, and you can book a time slot that works for you. Please check your messages and we’ll get this sorted out.
Quick note on scheduling: our support team operates on UTC+8, so keep that in mind when picking a time. Also, the 10:00 PM (22:00) slot on the calendar is reserved for sales — so just avoid that one for technical support bookings.