Gavinmc42 wrote: ↑
Sun Jun 20, 2021 12:03 am
Just trying to figure out how to test that the cameras are working on a CM4 I/O.
Do I use VC or ARM? Neither work out of the box with Raspberry Pi OS.
It seems to be one or the other and swapping between modified overlays and rebooting.
hasn't it been discussed why dual cam is not 'working out of the box'?
Starting point for using dual camera on CM4IO - assuming you have not messed around with the OS yet - is doing an update/full-upgrade/rpi-update, then connecting the cameras as described here
https://www.raspberrypi.org/documentati ... -camera.md
Compute Module 4
On the Compute Module 4 IO board the CAM1 connector is already wired to the I2C on GPIOs 44 & 45, and the shutdown line is connected to GPIO 5 on the GPIO expander. There is no LED signal wired through. No hardware changes are required to use CAM1 other than connecting the 22pin FFC to the CAM1 connector (flex contacts face down).
To connect a second Raspberry Pi camera (to CAM0), two jumpers must be added to J6 in a vertical orienation. The CAM0 connector shares the shutdown line with CAM1.
then you need to download the dual cam dt-blob source file, which has all definitions for using dual camera. Find it here https://www.raspberrypi.org/documentati ... ualcam.dts
That needs to be compiled and placed in the bootvpartition which is described here https://www.raspberrypi.org/documentati ... uration.md
Once completed you can reboot and use raspistill for testing your dual camera.
Only when this is working you should change to libcamera to rule out any other issues as libcamera requires some additonal steps.
https://www.raspberrypi.org/documentati ... /README.md
As stated in libcamera docu
Next, the /boot/config.txt file must be updated to load and use the camera driver, by adding the following to the bottom.
If you are using a sensor other than the imx219 you will need to supply the alternative name here (for example, ov5647 for the V1 camera, or imx477 for the HQ Cam).
NOTE: after rebooting, control of the camera system will be passed to the ARM cores, and firmware-based camera functions (such as raspistill and so forth) will no longer work. Setting /boot/config.txt back and rebooting will restore the previous behaviour.
So you can only have one or the other(!), so what's the point? For using libcamera you need to include a camera overlay info config.txt. If there is none you can keep using Openmax applications.
If you want to switch legacy and new camera SW change your config.txt and reboot.