MIPI Camera Not Streaming? A Linux Troubleshooting Checklist

When a MIPI CSI-2 camera produces no image, start by finding the first stage that fails. Record whether the sensor is detected, a capture device is available, buffers arrive, and the captured image can be interpreted. Each observation gives you a different place to investigate.

This checklist is for Linux-based camera integration. Commands depend on the installed tools and camera stack. Use the documentation for your exact module, carrier board, and software release when checking electrical connections or changing configuration.

1. Record the symptom and configuration

Save the module model and hardware revision, host board, camera port, cable or adapter, OS image, kernel, driver version, and requested image mode. Include resolution, frame rate, pixel format, lane configuration, and the number of simultaneous streams.

Describe the failure precisely. “No camera device,” “capture times out,” and “frames arrive but look black” lead to different checks. Keep the first relevant error and the command that produced it. Change one setting at a time so the next result can be compared with the previous one.

For the information to confirm before connecting a module, use our MIPI camera integration checklist.

2. Check the physical connection and sensor startup

Power down before reseating a cable, following the board manufacturer's procedure. Compare connector pin numbering, contact orientation, cable type, and adapter wiring with the exact hardware documentation. A connector that fits mechanically can still have incompatible wiring.

Ask the hardware integrator to verify the documented power rails, reset and power-down sequence, and external clock requirements. Linux sensor drivers manage clocks, regulators, and GPIOs as part of powering a device. A sensor may also be powered down between operations through runtime power management. Account for that state when interpreting measurements or register-access failures. Linux sensor driver documentation

A successful, documented chip-ID read helps establish control-path communication. It leaves the CSI-2 image path to be tested separately. Use the module's approved diagnostic method for its I²C bus and address. Register writes and bus probing need hardware-specific guidance.

3. Identify the capture device and media pipeline

Start with the device inventory exposed by your camera stack. On systems with v4l2-ctl installed, a useful discovery command is shown below.

v4l2-ctl --list-devices

Match the listed device to the intended camera. Video nodes can also belong to codecs, metadata outputs, or other cameras. Record the selected path and check permissions if opening it fails.