Skip to content

Troubleshooting

Notice

When the camera works abnormally, reconfirm the following basic

details:

  • Make sure the cable line connection is normal and stable
  • Make sure the camera you are using is normal version instead of specific version for camarray board.
  • Make sure you are using the appropriate bullseye OS version (legacy buster version is not recommended)
  • Follow the libcamera installation guide, make sure the driver, specific libcamera-dev and libcamera-apps installed normal.

More ways to check:

  1. Check that the driver is loaded correctly
dmesg | grep -E "imx477|imx219|arducam"

6D18409B 9D5D 40cd A7DD AC37498150B3 3

  1. Check if video0 has been found
ls /dev/video0

A8577CA2 3101 4f71 A851 6428C50F49E1

Before contacting arducam, please provide the following information so that we can help you solve problems efficiently.

  • Hardware related:
    Camera module number(e.g. SKU) or purchase link
    Hardware connection diagram
  • Screenshot of operation commnad
  • system related informaton which can be obtained by the following commands: 
    uname -a
cat /etc/os-release
cat /proc/meminfo
cat /boot/config.txt
  • System log 
    dmesg | grep -E "imx477|imx219|arducam"
  • Application log
  • Provide error log or screenshots about application throw out.

1. Streaming Errors when Physically Disconnecting Cameras (Quad-Camera Kit)

🛑 Problem Description

The user reports inability to obtain a video stream when attempting to operate the Quadrascopic Camera Kit with fewer than four cameras physically connected. While the system streams successfully with all four sensors attached, physically disconnecting one or more cameras to achieve a dual or single camera setup causes the video feed to fail.

🔍 Root Cause / Technical Analysis

The CamArray synchronous HAT board acts as a bridge that aggregates signals from multiple sensors. By default, the firmware expects all four camera ports to be occupied and initialized to maintain signal synchronization. Physically removing the camera interrupts this hardware check, causing the system to fail.

To reduce the number of active feeds (e.g., changing from Quad view to Dual or Single view), the user must not physically unplug the cameras. Instead, the composition mode must be changed via software (I2C commands) to tell the bridge chip to ignore specific channels or alter the layout.

✅ Solution / Troubleshooting Steps

To use fewer than four cameras, please follow these steps:

  1. Hardware Connection: Ensure all four camera modules are physically connected to the HAT board. The board requires them to be present for successful initialization, even if they are not being used in the final image.

  2. Switching Modes (Software): You must switch the "Composition Mode" using I2C commands to change how many cameras are displayed (e.g., Full, Dual, or Single mode). You can run the specific i2cset commands in your terminal to change the channel configuration. Please refer to the specific command values in the documentation link below:

2. Raspberry Pi Official HQ Camera Not Detected on Multi-Camera Adapter V2.2

Symptom

When connecting the Raspberry Pi Official HQ Camera (IMX477) to a Raspberry Pi via the Arducam Multi-Camera Adapter Module V2.2, the system fails to capture video, and the camera is not recognized by rpicam.

Interestingly, if you replace the official Raspberry Pi HQ Camera with an Arducam-branded IMX477 camera module on the exact same setup, it works flawlessly.

Cause

The issue is caused by the Raspberry Pi's early-boot auto-detection feature (camera_auto_detect=1) conflicting with the multi-camera multiplexer board.

During the boot process, when camera_auto_detect=1 is active, the Pi's underlying firmware aggressively probes the I2C bus searching for a specific cryptographic/authentication chip that is physically present only on official Raspberry Pi cameras. However, because the camera is connected through the Arducam Multiplexer (which has not yet been initialized or switched by the user-space software during early boot), this I2C probe encounters routing blocks or timeouts. This hardware probing conflict ultimately causes the camera initialization to fail.

Note: Arducam IMX477 modules do not carry this specific authentication chip. Consequently, the firmware skips this aggressive probing phase, naturally avoiding the I2C conflict and allowing the Arducam modules to function normally through the adapter.

Resolution

To fix this issue, you must disable the Raspberry Pi firmware's camera auto-detection feature and manually declare the IMX477 driver overlay in the system configuration file.

Step 1: Open the configuration file

Open a terminal on your Raspberry Pi and edit your main configuration file:

Note: On newer versions of Raspberry Pi OS (Bookworm/Trixie), the file is located in /boot/firmware/config.txt. On older OS versions (Bullseye and older), it is located in /boot/config.txt.

sudo nano /boot/firmware/config.txt

Step 2: Disable camera auto-detection

Scroll down through the file to find the following line:

camera_auto_detect=1

Change the value from 1 to 0:

camera_auto_detect=0

Step 3: Save and Reboot

Save your modifications in the nano editor:

  1. Press Ctrl + O

  2. Press Enter to confirm

  3. Press Ctrl + X to exit

Finally, reboot your Raspberry Pi to apply the changes:

sudo reboot

Once the Pi reboots, your multiplexer script and rpicam commands will work correctly, and the Multi-Camera Adapter will successfully output video from your Official Raspberry Pi HQ cameras.