Hi everyone, I’m trying to use the IMX708 camera from the Arducam Quad-Camera Kit and I can’t get it to capture images. I’ve tested on both a Raspberry Pi 4 and a Raspberry Pi 5. If I connect the camera directly to the Pi, image capture works, but when I go through the Arducam module I get a camera front-end error. Has anyone run into this?
Can you post the exact error text and the command you’re running? Also run libcamera-hello --list-cameras (or rpicam-hello --list-cameras depending on the OS version) and share the output. First thing to rule out is an out-of-date system, so please run:
sudo apt update
sudo apt upgrade -y
I ran the full update first:
sudo apt update
sudo apt upgrade -y
After that I also tried the pull request firmware update that keeps getting mentioned for this camera:
sudo rpi-update pulls/5691
It failed with these errors:
gzip: stdin: unexpected end of file
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Invalid artifact specified. Response: 404.
The rpi-update failure is a separate issue. Invalid artifact specified. Response: 404. means the pull request artifact isn’t available from the rpi-update server, so that command never actually applied anything. Let’s leave rpi-update alone for now. For the capture timeout, try editing rpi_apps.yaml and increase camera_timeout_value_ms to 10000, then test again. Also, are you currently testing on the Pi 4 or the Pi 5?
I changed camera_timeout_value_ms to 10000 in rpi_apps.yaml and the same camera front-end error still happens.
Which rpi_apps.yaml did you edit? The path matters. On a Pi 5 it should be:
/usr/share/libcamera/pipeline/rpi/pisp/rpi_apps.yaml
On a Pi 4 it should be:
/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml
And libcamera needs to actually pick it up via LIBCAMERA_RPI_CONFIG_FILE. Let me know which board you’re on and I can give you the exact export line.
Okay, I went through both boards. Pi 5 first: I placed rpi_apps.yaml at /usr/share/libcamera/pipeline/rpi/pisp/rpi_apps.yaml, then ran:
export LIBCAMERA_RPI_CONFIG_FILE=/usr/share/libcamera/pipeline/rpi/pisp/rpi_apps.yaml
echo 'export LIBCAMERA_RPI_CONFIG_FILE=/usr/share/libcamera/pipeline/rpi/pisp/rpi_apps.yaml' >> ~/.bashrc
source ~/.bashrc
For the Pi 4 I edited /usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml and added the line:
"camera_timeout_value_ms": 50000,
then did the same export/echo/source for the vc4 path and rebooted with sudo reboot.
Thanks, that’s the right config setup for each board. After the reboot, did the error change at all? Please run the capture command again and post the verbose log. Also let me know the libcamera/rpicam version with rpicam-still --version or libcamera-still --version.
After the reboot I ran another full update (sudo apt update and sudo apt upgrade -y) and retried sudo rpi-update pulls/5691. It failed with the same errors:
gzip: stdin: unexpected end of file
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Invalid artifact specified. Response: 404.
I also tried camera_timeout_value_ms at both 10000 and 50000, and the front-end error persists either way.
Okay, don’t worry about rpi-update for now—it’s failing before it can change anything, so it isn’t part of the fix. The fact that both 10000 and 50000 timeouts don’t help points to something else. Can you attach the bug report file and a few photos of the camera/module wiring so I can check the connections?
.jpeg)
Thanks, those came through. Can you also post the updated bug report and the other set of photos from the expanded report? I’d like to compare the two captures.
.jpeg)
Thanks for the extra logs and photos. From everything you’ve posted, this capture failure is being tracked in the libcamera issue tracker rather than being caused by your specific wiring. Please follow the ongoing discussion here:
Both the IMX708 front-end capture problem and the rpi-update pulls/5691 failure (Invalid artifact specified. Response: 404.) are referenced in that thread. At the moment the best next step is to stay tuned to that issue—I don’t have a separate fix that resolves it yet.