Hi all, hoping someone can point me in the right direction. I’ve got a Raspberry Pi 4 running the latest Bullseye 64-bit and an Arducam 64 MP camera from the Raspberry Pi Cameras series. Whenever I run libcamera-still -o test1.jpg I just get “No cameras available”. I followed Arducam’s online libcamera instructions. So far I’ve reinstalled the OS, tried two different cameras, and double-checked the ribbon cable seating (blue strip on the Pi end toward the USB ports, blue strip on the camera end away from the board). Still nothing. Any ideas?
Thanks for the details. Before we go further I’d like to see a bug report from the Pi. Can you reboot, then run these commands:
wget -O arducam-camera-bug-report https://github.com/ketai-dhr/arducam-camera-bug-report/releases/download/tools/arducam-camera-bug-report
chmod +x ./arducam-camera-bug-report
./arducam-camera-bug-report
That will create an arducam-bug-report.txt in the current directory. Attach it here and I’ll take a look at why the camera isn’t being detected.
Here’s the report: arducam-bug-report.txt
Looking at your bug report, the camera driver doesn’t appear to be installed at all. That’s why libcamera reports “No cameras available” — the 64 MP (IMX519/Hawkeye) driver and Arducam’s libcamera build aren’t present. Follow the Quick Start Guide here to install the 64 MP driver and libcamera:
Then reboot and try libcamera-still -o test1.jpg again.
Okay, so I installed the driver and libcamera from the Quick Start Guide. Progress, sort of. From the Desktop, the default command fails with “unable to allocate capture buffers”. But if I exit the Desktop and run the same libcamera-still -o test1.jpg from the console, it works and captures a 16 MP image with the default options. Is the Desktop buffer error expected?
Good to hear the camera is now detected — that confirms the original “No cameras available” error was just the missing driver. The remaining “unable to allocate capture buffers” failure when running from the Desktop looks like a resource/memory allocation issue with libcamera in the desktop session. The workaround you found — exit the Desktop and run the capture from the console — is the current way around it, and with default options it captures a 16 MP image. If you want, the next step would be testing the full 64 MP capture mode from the console to see how memory behaves there.