Board: Raspberry Pi 5 (8 GB)
OS: Raspberry Pi OS Bookworm 64-bit (fully updated)
Camera(s):
• OV5647 (v1) — works and streams
• IMX708 (Camera Module 3 class, wide FOV) — not detected
Cable: 22-pin (Pi 5) ↔ 15-pin camera cable for Pi 5, contacts oriented correctly
Packages: rpicam-apps, python3-picamera2, v4l-utils
libcamera: v0.5.0+59-d83ff0a4 (from logs)
libpisp: v1.2.1 981977ff21f3 (29-04-2025)
What works (OV5647)
On CAM/DISP 0 (also tested on CAM/DISP 1), the OV5647 enumerates and captures reliably:
$ rpicam-hello --list-cameras
Available cameras
-----------------
0 : ov5647 [2592x1944 10-bit GBRG] (/base/axi/pcie@1000120000/rp1/i2c@88000/ov5647@36)
Modes: 'SGBRG10_CSI2P' : 640x480 (~59 fps)
1296x972 (~46 fps)
1920x1080 (~33 fps)
2592x1944 (~15.6 fps)
# Headless still capture
$ rpicam-jpeg -n -t 1000 -o ov.jpg && ls -lh ov.jpg
(Also validated with Picamera2: RGB array frames and JPEG stills save as expected.)
What fails (IMX708)
Using the same port and the same 22↔15 camera cable, I power off, swap only the camera board to IMX708, re-seat both ends (contacts-to-contacts, latches flat), power on, then:
$ rpicam-hello
[...]
ERROR: no cameras available
The IMX708 never appears in --list-cameras, and still captures fail accordingly.
I²C observations (Pi 5 camera buses)
/dev/i2c-13 and /dev/i2c-14. Results:
With OV5647 attached: I see a single device at 0x36 on one of these buses (as expected), and rpicam apps work.
With IMX708 attached: I do not see the usual single device at 0x1a. In some attempts I’ve observed an abnormal scan where many addresses appear to ACK on the camera bus; after a full power removal and careful reseat that clears for OV5647 but the IMX708 still won’t enumerate.
(For completeness, /dev/i2c-1 on the 40-pin header behaves normally.)
Things I’ve tried
Ensured software is current:
sudo apt update
sudo apt full-upgrade -y
sudo apt install -y rpicam-apps python3-picamera2 v4l-utils
Reset camera config to auto-detect (Bookworm path), and also tried forcing overlays per port:
# reset to auto
sudo sed -i '/^camera_auto_detect=/d;/^dtoverlay=imx/d;/^dtoverlay=ov/d' /boot/firmware/config.txt
echo 'camera_auto_detect=1' | sudo tee -a /boot/firmware/config.txt
# (also tested, one at a time when IMX708 was attached)
# echo 'camera_auto_detect=0' | sudo tee -a /boot/firmware/config.txt
# echo 'dtoverlay=imx708,cam0' | sudo tee -a /boot/firmware/config.txt
# (and cam1 if using the other port)
Multiple cold power cycles (removed power 60–90 s), reseated the ribbon at both ends, tested both CAM/DISP ports.
Headless-safe captures (-n) and modest modes (e.g., 1296×972 @ 30 fps) to avoid preview plane limits.
Total reinstall of OS.
Ask / guidance needed
On Pi 5 (Bookworm), should an IMX708 (Camera Module 3 class) enumerate out-of-the-box exactly like OV5647, i.e., appear in rpicam-hello --list-cameras without extra configuration?
Are there known gotchas with Pi 5 camera adapter cables (22↔15) — e.g., camera-wired vs display-wired, or directional ends — that would let OV5647 work but prevent IMX708 from enumerating? Tips to positively identify the correct cable type would be helpful.
Any further diagnostics you’d like me to run (e.g., exact i2cdetect outputs with IMX708 attached on 13/14, dmesg | grep -i 'csi\|unicam\|pisp\|imx') to distinguish overlay vs. hardware differences?
I’m happy to gather more logs or test specific overlays. The key point is: OV5647 works flawlessly on both CAM/DISP ports with the same cable; IMX708 on the same setup is consistently “no cameras available.” Any pointers much appreciated!
OS: Raspberry Pi OS Bookworm 64-bit (fully updated)
Camera(s):
• OV5647 (v1) — works and streams
• IMX708 (Camera Module 3 class, wide FOV) — not detected
Cable: 22-pin (Pi 5) ↔ 15-pin camera cable for Pi 5, contacts oriented correctly
Packages: rpicam-apps, python3-picamera2, v4l-utils
libcamera: v0.5.0+59-d83ff0a4 (from logs)
libpisp: v1.2.1 981977ff21f3 (29-04-2025)
What works (OV5647)
On CAM/DISP 0 (also tested on CAM/DISP 1), the OV5647 enumerates and captures reliably:
$ rpicam-hello --list-cameras
Available cameras
-----------------
0 : ov5647 [2592x1944 10-bit GBRG] (/base/axi/pcie@1000120000/rp1/i2c@88000/ov5647@36)
Modes: 'SGBRG10_CSI2P' : 640x480 (~59 fps)
1296x972 (~46 fps)
1920x1080 (~33 fps)
2592x1944 (~15.6 fps)
# Headless still capture
$ rpicam-jpeg -n -t 1000 -o ov.jpg && ls -lh ov.jpg
(Also validated with Picamera2: RGB array frames and JPEG stills save as expected.)
What fails (IMX708)
Using the same port and the same 22↔15 camera cable, I power off, swap only the camera board to IMX708, re-seat both ends (contacts-to-contacts, latches flat), power on, then:
$ rpicam-hello
[...]
ERROR: no cameras available
The IMX708 never appears in --list-cameras, and still captures fail accordingly.
I²C observations (Pi 5 camera buses)
/dev/i2c-13 and /dev/i2c-14. Results:
With OV5647 attached: I see a single device at 0x36 on one of these buses (as expected), and rpicam apps work.
With IMX708 attached: I do not see the usual single device at 0x1a. In some attempts I’ve observed an abnormal scan where many addresses appear to ACK on the camera bus; after a full power removal and careful reseat that clears for OV5647 but the IMX708 still won’t enumerate.
(For completeness, /dev/i2c-1 on the 40-pin header behaves normally.)
Things I’ve tried
Ensured software is current:
sudo apt update
sudo apt full-upgrade -y
sudo apt install -y rpicam-apps python3-picamera2 v4l-utils
Reset camera config to auto-detect (Bookworm path), and also tried forcing overlays per port:
# reset to auto
sudo sed -i '/^camera_auto_detect=/d;/^dtoverlay=imx/d;/^dtoverlay=ov/d' /boot/firmware/config.txt
echo 'camera_auto_detect=1' | sudo tee -a /boot/firmware/config.txt
# (also tested, one at a time when IMX708 was attached)
# echo 'camera_auto_detect=0' | sudo tee -a /boot/firmware/config.txt
# echo 'dtoverlay=imx708,cam0' | sudo tee -a /boot/firmware/config.txt
# (and cam1 if using the other port)
Multiple cold power cycles (removed power 60–90 s), reseated the ribbon at both ends, tested both CAM/DISP ports.
Headless-safe captures (-n) and modest modes (e.g., 1296×972 @ 30 fps) to avoid preview plane limits.
Total reinstall of OS.
Ask / guidance needed
On Pi 5 (Bookworm), should an IMX708 (Camera Module 3 class) enumerate out-of-the-box exactly like OV5647, i.e., appear in rpicam-hello --list-cameras without extra configuration?
Are there known gotchas with Pi 5 camera adapter cables (22↔15) — e.g., camera-wired vs display-wired, or directional ends — that would let OV5647 work but prevent IMX708 from enumerating? Tips to positively identify the correct cable type would be helpful.
Any further diagnostics you’d like me to run (e.g., exact i2cdetect outputs with IMX708 attached on 13/14, dmesg | grep -i 'csi\|unicam\|pisp\|imx') to distinguish overlay vs. hardware differences?
I’m happy to gather more logs or test specific overlays. The key point is: OV5647 works flawlessly on both CAM/DISP ports with the same cable; IMX708 on the same setup is consistently “no cameras available.” Any pointers much appreciated!
Statistics: Posted by reppich — Wed Aug 20, 2025 11:21 am — Replies 2 — Views 123