Hi all, I’ve got an Arducam B0371 IMX519 autofocus camera module connected to a Raspberry Pi and it’s not being detected at all. I’ve already tried a few different config.txt variations, but the Pi still doesn’t see the camera. Anyone have any ideas before I go further down the rabbit hole?
Hi, thanks for the report. Before we get into the config side, can you confirm the failure timeline for this unit? Specifically, did the camera work when you first received it and then stop working after a while, or was it never detected from the moment you got it? That detail changes where we look first.
Sorry, I don’t have that info from the end user yet. All I know is the camera had been in their possession for about 5 days before the complaint came in. I’m not sure whether it was tested and working during that window or never detected from day one. I’ll try to get that confirmed.
No problem. While we wait on that, could you grab two things for me? First, photos of the physical connection at both ends - the Raspberry Pi camera connector and the camera module side. Second, the output of this command:
cat /boot/firmware/config.txt
That will show what overlays and camera settings are actually active right now.
Here’s the current config.txt. I’ve been through a bunch of possibilities already, so some lines are commented out or left over from testing:
For more options and information see
http://rptl.io/configtxt
Some settings may impact device functionality. See link above for details
Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
Enable audio (loads snd_bcm2835)
dtparam=audio=on
Additional overlays and parameters are documented
/boot/firmware/overlays/README
Automatically load overlays for detected cameras
param=i2c_arm=on
dtparam=i2c_vc=on
#camera_auto_detect=1 #tested
camera_auto_detect=0
dtoverlay=imx519
Automatically load overlays for detected DSI displays
display_auto_detect=1
Automatically load initramfs files, if found
auto_initramfs=1
Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2
Don’t have the firmware create an initial video= setting in cmdline.txt.
Use the kernel’s default instead.
disable_fw_kms_setup=1
Run in 64-bit mode
arm_64bit=1
Disable compensation for displays with overscan
disable_overscan=1
Run as fast as firmware / board allows
arm_boost=1
[cm4]
Enable host mode on the 2711 built-in XHCI USB controller.
This line should be removed if the legacy DWC2 controller is required
(e.g. for USB device mode) or if USB support is not required.
otg_mode=1
[all]
Photobooth
#IN
gpio=5,6,7,8,16,17,20,21,22,26,27=pu
#OUT
gpio=9,10,11,12,18,19,23,24,25=op
Photobooth End
I’ve also attached photos of the Pi end and the camera end. Camera is still not detected with this exact config.
Thanks, got the config and the photo. The key thing I see is that your current setup is manually loading the IMX519 overlay:
camera_auto_detect=0
dtoverlay=imx519
That’s a valid way to enable this module, but since the Pi still reports no camera, we need to keep the physical connection and the failure timeline in the picture. The photo helps, but I still need the timeline confirmation to decide whether this ever worked.
Right, still not detected. The camera doesn’t show up at all even with the overlay loaded manually. I’m still waiting to confirm whether it ever worked during those first 5 days.
Okay, so to summarize where we are right now: the camera is still reported as not detected, and the root cause hasn’t been pinned down yet. The config currently uses camera_auto_detect=0 with dtoverlay=imx519, which manually loads the IMX519 overlay, so that part of the setup is accounted for. Next, please confirm the failure timeline (did it work initially and then fail, or was it never detected), and make sure we have clear photos of the connection at both the Pi end and the camera end. I already have your config.txt output above. Once those are confirmed, we can go from there.