(camera_auto_detect won't work at all on a CM, but always best to disable it anyway)Hey, I know that problems with Arducam hardware are best resolved on their forum. Indeed, I've asked this there (Multi-camera board and cm4: no cameras found) but their support haven't picked up on it.
Do I need to do any special firmware configuration for a CM4 for it to detect the Multi Camera Adapter Module? The config.txt setup that worked well on a Raspberry Pi 4 with 4× v3 Wide cameras:results in no cameras found and no mention of cameras or muxes in the dmesg output.Code:
camera_auto_detect=0dtoverlay=camera-mux-4port,cam0-imx708,cam1-imx708,cam2-imx708,cam3-imx708
As far as I know, our CM4 carrier board is passing through all the correct signals to the 40-pin header, and is using the CAM0 port for the camera connection.
All camera overlays default to using CAM1 as the camera port on Pi0-4 is wired to CSI1. If you're using CAM0, then most camera overlays (including camera-mux-4port) have a "cam0" override. Using CAM0 will assume that I2C is connected to GPIOs 0&1 (CAM1 assumes 44&45).
Add "dtdebug=1" to /boot/firmware/config.txt, and "sudo vclog -m" will dump out a load more information regarding applying the overlays.
You can also check /sys/kernel/debug/v4l2-async/pending_async_subdevices for details of any devices that V4L2 is waiting to probe.
I2C is muxed through a pca9544, so "i2cdetect -l" should list those outputs.
CSI mux control is via GPIOs 4, 17, and 18, so those should all be configured as outputs. (Enabling something like 1-wire which defaults to gpio 4 would cause the mux to fail to load).
I would be surprised if there really was nothing in the kernel logs, but it may be a case of knowing what to look for.
Statistics: Posted by 6by9 — Thu Mar 14, 2024 4:45 pm
