You can't write Python code to control a camera - there is no way to configure the kernel appropriately for the image properties.
All sensors require a V4L2 subdevice driver, as found in https://github.com/raspberrypi/linux/tr ... /media/i2c. imx219 (the Pi v2 camera module) is probably a reasonable example to take, although it does have a few bells and whistles in supporting multiple bit depths.
You'll also need a device tree (DT) overlay to configure the kernel and associate the sensor driver with a CSI2 receiver.
If using a Pi0-4, then the camera connector I2C is i2c-10, aka i2c_csi_dsi in DT.
On a Pi5 the two CAM/DISP connectors use i2c-4 and i2c-6, but I forget which way around they are.
Autodetection is only relevant for the official Pi camera modules
- v1 / ov5647
- v2 / imx219
- v3 / imx708
- HQ / imx477
- GS / imx296
All third party modules (which yours is) will require a "dtoverlay=..." line in config.txt.
All sensors require a V4L2 subdevice driver, as found in https://github.com/raspberrypi/linux/tr ... /media/i2c. imx219 (the Pi v2 camera module) is probably a reasonable example to take, although it does have a few bells and whistles in supporting multiple bit depths.
You'll also need a device tree (DT) overlay to configure the kernel and associate the sensor driver with a CSI2 receiver.
If using a Pi0-4, then the camera connector I2C is i2c-10, aka i2c_csi_dsi in DT.
On a Pi5 the two CAM/DISP connectors use i2c-4 and i2c-6, but I forget which way around they are.
Autodetection is only relevant for the official Pi camera modules
- v1 / ov5647
- v2 / imx219
- v3 / imx708
- HQ / imx477
- GS / imx296
All third party modules (which yours is) will require a "dtoverlay=..." line in config.txt.
Statistics: Posted by 6by9 — Wed Jul 10, 2024 1:56 pm