I’ve been trying to get an Arducam 1MP 4 Quadrascopic Camera Bundle (IMX219) working on a Raspberry Pi 4 running the latest Raspbian 64-bit, and I’m stuck with ‘no cameras’.
Environment:
Pi 4, Raspbian 64-bit
Arducam 1MP 4 Quadrascopic bundle, IMX219
No kernel driver package installed (I couldn’t find one appropriate for IMX219)
I installed libcamera and libcamera_apps using the pivariety package script:
That dmesg is a big clue. The arducam-pivariety overlay is for Arducam’s pivariety sensors, not the IMX219. The pivariety_read: Reading register 0x103 failed / probe failed lines are the sensor driver failing to talk through the wrong overlay.
For IMX219 you want the standard imx219 overlay.
Try this:
In /boot/config.txt, change dtoverlay=arducam-pivariety to dtoverlay=imx219
Reboot the Pi
Try libcamera-still again after it comes up
Leave camera_auto_detect=0 for now. Can you do that and post back what libcamera-still says?
Thanks, I changed the overlay to imx219 and rebooted.
Now I have two IMX219 cameras connected on RX0 and RX1. dmesg no longer shows the pivariety probe failure, but I do see:
[ 8.333309] imx219 10-0010: Consider updating driver imx219 to match on endpoints
I ran:
i2cset -y 10 0x24 0x24 0x01
libcamera-still -t 0
And got a camera frontend timeout:
[0:03:09.837305978] [1512] INFO Camera camera_manager.cpp:297 libcamera v0.0.0+4367-ad9428b4
[0:03:09.884975201] [1514] WARN RPI vc4.cpp:390 Mismatch between Unicam and CamHelper for embedded data usage!
f 1000000.00us has expired!
[0:04:02.120780373] [1723] ERROR RPI pipeline_base.cpp:1356 Camera frontend has timed out!
[0:04:02.120805318] [1723] ERROR RPI pipeline_base.cpp:1357 Please check that your camera sensor connector is attached securely.
[0:04:02.120827818] [1723] ERROR RPI pipeline_base.cpp:1358 Alternatively, try another cable and/or sensor.
ERROR: Device timeout detected, attempting a restart!!!
That frontend timeout usually means the camera started enumerating but libcamera never got valid frames back from the sensor. Since you have two cameras on RX0/RX1, let’s check what the Pi actually sees on the I2C buses.
Thanks. The bus map tells us the mux is present (bus 22 is the parent, 10/0 are the two mux channels), and 0x24 on bus 10/22 looks like the expected mux address. Buses 20 and 21 are showing the address ranges behind the two sides of the HAT.
But with only two cameras on RX0 and RX1, one side of the board may be effectively empty, and the frontend can still time out waiting on the camera path that isn’t there. If you have all four cameras available, try plugging all four in and re-run libcamera-still. That will tell us whether the remaining problem is just port population vs. something else.
Good to hear it’s working. Yes, you can run it with only two cameras, but the placement matters.
Connect them like this:
One camera on the Rx0/Rx1 port
Another camera on the Rx2/Rx3 port
The key point is: don’t leave one side of the HAT empty. At least one camera must be connected on each side, because of how the ports are routed through the mux. If both cameras are on the same side, you’ll likely hit the same frontend timeout behavior again.