Thanks for the logs. The interesting part is that the kernel does enumerate the subdevice (arducam_pivariety@c), but then the driver probe fails when it tries to read register 0x103. That usually points to a communication/driver/config issue rather than the camera not being seen at all.
To dig further, could you share your full environment details - Pi model, OS version, and kernel? Also, it would help to see a picture of how the HAT is connected.
I’ve also sent you a bug report tool via private message - please check your messages. Once you have it, reboot, then run:
I followed the quick-start guide at the link above.
One more thing - the exact same CamArray HAT works fine on my Raspberry Pi 4 Model B running Debian Bullseye. So is the CamArray HAT actually supported on the Pi 5 with Debian Bookworm?
Yes, the CamArray HAT is supported on the Pi 5 and should work as expected there.
Based on what you’ve described, the most likely cause is a missing dtoverlay config and/or the Arducam Libcamera installation on the Pi 5 - it needs the same setup as the Pi 4.
Try this:
Connect the CamArray HAT to the camera 1 port on the Pi 5.
Add dtoverlay=arducam-pivariety under [all] in the config file (same as you did on the Pi 4).
The Pi 5 uses the same arducam-pivariety overlay and the same Arducam Libcamera install as the Pi 4 - just make sure the HAT is on the camera 1 port. Let me know how it goes.