Hi all,
I’ve got a Raspberry Pi 4B with an Arducam IMX477 camera. I changed dtoverlay to imx477 in /boot/config.txt and now the camera just gives me a blank screen. I’ve attached photos of the config.txt change, the camera connections, and what the display shows.
Anything I’m missing here?
Thanks for the photos. To debug this properly I need the arducam-bug-report.txt file from your Pi. Can you generate it and attach it here?
Here’s how:
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
This will create arducam-bug-report.txt in the current directory. Attach that file here.
Make sure dtoverlay=imx477 is set in config.txt and reboot the Pi before running the script. You can also check the driver with:
dmesg | grep imx477
And if it’s been a while since you updated, run:
sudo apt -y update && sudo apt -y upgrade
Quick start guide: https://docs.arducam.com/Raspberry-Pi-Camera/Native-camera/Quick-Start-Guide/#software
Quick problem - after I changed dtoverlay to imx477, the Pi doesn’t seem to start back up. The screen just stays black and it never comes back, so I can’t get to a terminal to run the bug report tool. How do I run the bug report if the system won’t boot after the change?
A black screen doesn’t necessarily mean the Pi failed to boot. The system may just be running headless. When you plug in power, check the green LED on the Pi - if it flashes, the Pi is booting and you can connect to it from your PC via SSH to run the bug report tool. The display staying black on its own isn’t proof that boot failed.
Okay, I was able to SSH in - the Pi actually was booting, the display was just black. I’ve generated the bug report and attached it below.
One thing I noticed while testing: the camera works from the CLI, but the GUI (libcamera software) still doesn’t display anything.
Thanks, the bug report helps a lot. The camera is being detected by the Pi and it captured an image successfully, so the camera itself is working fine. If the GUI you’re referring to is libcamera software, take a look at your config.txt - the dtoverlay=vc4-kms-v3d line is commented out. Uncomment that line, save, and reboot. That setting doesn’t affect HDMI or power, so it shouldn’t cause any boot problems.
That did it - the camera is working now, thanks for the help. I didn’t realize dtoverlay could have multiple entries like imx477 and vc4-kms-v3d at the same time. I had been replacing one with the other instead of having both.