Hi everyone, I’m having trouble getting the 64 MP Hawkeye camera to work on a Raspberry Pi 4B. When I try to use libcamera I keep getting these errors:
Could not create camera helper for arducam_64mp
Failed to load a suitable IPA library
Failed to register camera arducam_64mp 10-001a: -22
Configuration file arducam_64mp.json not found for IPA module rpi/vc4
and then at the end:
ERROR: There are no cameras available
I’m not sure what I’m missing. Has anyone run into this before?
That set of errors usually means the Arducam custom libcamera software isn’t installed on the system. The 64 MP Hawkeye requires Arducam’s own camera helper and IPA library support for the arducam_64mp module - the stock libcamera build doesn’t include it.
Please work through the ‘Getting Started’ section of the Arducam Pivariety Libcamera User Guide:
https://docs.arducam.com/Raspberry-Pi-Camera/Pivariety-Camera/Libcamera-User-Guide/#getting-started
Once that’s installed, you should be able to access the camera using the normal libcamera commands.
Thanks for the reply. I went through the installation webpage (the 64MP Hawkeye software guide at 64MP Hawkeye - Arducam Wiki) and I’m still seeing the same errors. This camera has never worked on this Pi.
Things I’ve already tried:
The full errors I’m getting now:
[1:38:01.211255246] [18073] ERROR IPARPI ipa_base.cpp:138 Could not create camera helper for arducam_64mp
[1:38:01.211327207] [18073] ERROR RPI pipeline_base.cpp:814 Failed to load a suitable IPA library
[1:38:01.211369946] [18073] ERROR RPI vc4.cpp:216 Failed to register camera arducam_64mp 10-001a: -22
I’m wondering if there’s a missing file somewhere in the libraries. Could you tell me what the expected file structure should look like and what I should check next? I’ve also attached a screenshot of the error.
Since the error is persisting even after reinstalling, I’d like to get some diagnostic data from your device. Could you generate an Arducam camera bug report?
Here’s how:
That will produce an arducam-bug-report.txt in the current directory. Please attach that file here so I can dig into the camera registration failure.
I ran the tool and it generated the file. I’ve attached arducam-bug-report.txt. Let me know what you find.
Thanks for the report. From what I can see, the Arducam libcamera software is still not fully installed - specifically, the libcamera_dev and libcamera_apps packages are missing.
Please run these commands to install them:
wget -O install_pivariety_pkgs.sh https://github.com/ArduCAM/Arducam-Pivariety-V4L2-Driver/releases/download/install_script/install_pivariety_pkgs.sh
chmod +x install_pivariety_pkgs.sh
./install_pivariety_pkgs.sh -l
./install_pivariety_pkgs.sh -p libcamera_dev
./install_pivariety_pkgs.sh -p libcamera_apps
The -l flag lists the available packages, and -p installs the one you specify. After that, verify with:
libcamera-still -t 0
I re-ran all of those commands. The packages looked like they downloaded and installed fine, but the terminal still returns the exact same response - no change at all. I’ve attached a notes file with the full terminal output.
At this point I think a live screen/remote session would be the fastest way forward. Is that possible? Ideally with someone closer to the EST time zone if you have anyone.
I understand - let’s do a live remote session to look at this directly. I’ve sent you the scheduling link and remote support details by private message, so please pick a time that works for you.
One thing about timing: our support team is in UTC+8, so the late-night options in your time zone may not be available for a remote session.
I’ve scheduled the session and sent over the remote access details via private message. I picked Thursday Feb 27th at 9:00 pm EST, which should be Friday morning your time.
I’ve sent you the meeting link for the session by private message, and I’ve also sent an updated link that replaces the earlier one - please use the new one.
To recap where we’re at: the camera works on your second Pi but not this one, so it’s looking like a software/driver problem on this SD card rather than the camera itself. The fact that you had to manually copy arducam_64mp.json from the working Pi is a strong hint that the installer isn’t placing everything correctly. We’ll go through it live during the session and try to figure out why the arducam_64mp registration is still failing with -22.