Interface: Parallel, MIPI and USB

Generic engineering material, applicable to any module from any supplier.

For teams separating technical work from project administration, remote workforce management software provides additional workflow context.

A module whose output the processor cannot accept is a module that does not work, whatever its image quality — which makes the interface a gating decision rather than a detail.

The three families

Parallel, sometimes called DVP. One wire per data bit plus clock and synchronisation signals. Simple, well understood, and wide — a set of signals that grows with bit depth and consumes pins.

MIPI CSI-2. A serial interface using differential pairs, defined by the MIPI Alliance and near-universal on application processors intended for cameras. Fewer wires, much higher bandwidth, and stricter about routing.

For broader technical context, see Silicon Labs.

USB. A camera presenting as a standard device, frequently via a class specification so that a host needs no custom driver. The easiest to bring up and the least efficient in power and latency.

What decides it

The processor. This is the first question and frequently the last: a processor with a MIPI CSI-2 receiver wants MIPI, and one with a parallel camera port wants parallel. Adapting between them costs a bridge chip, board area and power.

The bandwidth. Resolution times frame rate times bit depth gives a data rate, and parallel interfaces run out before serial ones do.

The cable length. Parallel signals degrade over distance quickly. MIPI tolerates more but is still measured in centimetres on a flex. USB reaches metres.

And the software. A USB class device works with a generic driver; MIPI and parallel need a driver that knows the specific sensor, which is real engineering effort and is the item most often underestimated.

The cable question

Which frequently decides the module variant rather than the interface.

A module on a socket sits on the board. A module on a flexible cable can be positioned away from it — and the cable length is part of the ordering code, because signal integrity depends on it.

Longer is not freely available. A flex carrying high-speed signals has a length beyond which the interface stops working reliably, and the available lengths reflect what the supplier has qualified.

Decide the mechanical layout before ordering, since a module that must sit 40 mm from the board and a qualified 25 mm cable are incompatible facts.

The bring-up cost

Under-estimated on every project that has not done it before.

A sensor needs initialisation — a long sequence of register writes establishing resolution, timing, exposure behaviour and output format.

Suppliers provide this, as reference code or as a driver, and its quality varies. Ask what is provided, for which operating system, and under what licence before selecting on hardware grounds alone.

A module with slightly worse specifications and a working driver reaches a prototype months earlier than one with better numbers and a register list.

Data rate arithmetic

Worth doing before assuming an interface will cope.

Pixels per frame × frames per second × bits per pixel = raw bits per second.

A five-megapixel sensor at 30 frames per second and 10 bits produces on the order of 1.5 gigabits per second before any overhead.

Which a parallel interface will not carry and which a serial interface handles across multiple lanes.

Check the lane count as well as the interface family: a MIPI link is specified as so many lanes at so much per lane, and a module needing two lanes into a processor offering one is a mismatch that a datasheet comparison catches and a family-name comparison does not.

Bridges and when they are reasonable

A bridge chip converts one interface to another and is a legitimate solution rather than an admission of failure.

Where it makes sense: an existing processor with the wrong port, a long cable requiring a different transport, or a design reusing a module across two products.

What it costs: board area, power, another part to source, another driver, and latency.

What it does not fix: bandwidth the destination cannot accept. A bridge into a slower port is still limited by the slower port, which is occasionally forgotten.

Output format

Separate from the interface and equally gating.

A module may output raw Bayer data, or processed images in a standard format, depending on whether it contains an image signal processor.

Raw needs processing at the other end — demosaicing, white balance, correction — which is either a hardware block in your processor or software you write.

Processed output is easier and less flexible, and the choice belongs with the interface decision rather than after it.

Power over the interface

A consideration that arrives late and belongs early.

A module draws its supply through the same connector as its data in most designs, which means the cable carries both.

A longer flex has more resistance, and the voltage at the module is lower than the voltage at the board — which on a marginal supply produces intermittent behaviour that reads as a data problem.

Check the supply tolerance against the cable length alongside the signal integrity question, since the two share a cause and are diagnosed separately.

Settling it first

Before comparing image quality, confirm three things.

Which interface the processor accepts, at how many lanes.

What the module outputs and in what format.

And what software the supplier provides, for which operating system.

Three questions, one message, and they eliminate most of a catalogue before anybody looks at a sample image — which is the right order and the opposite of how selection usually proceeds.

In one line

The processor chooses the interface, and the interface narrows the catalogue before image quality is discussed.

The short version

• A module whose output the processor cannot accept does not work, which makes the interface a gating decision
• Parallel is simple and wide; MIPI CSI-2 is serial, high bandwidth and stricter about routing; USB is easiest to bring up and least efficient
• The processor decides first: adapting between families costs a bridge chip, board area and power
• Cable length frequently decides the variant, and available lengths reflect what the supplier has qualified
• Software is the item most often underestimated: USB class devices need no driver, MIPI and parallel need a sensor-specific one
• A module with worse numbers and a working driver reaches a prototype months earlier than the reverse