Choosing the wrong display interface is one of the most expensive mistakes in embedded product design—it can force a main-board respin, a processor upgrade or months of firmware rework.
Choosing the right one is mostly a matter of matching three things: your display's resolution, your processor's capabilities and your product's physical constraints. This guide compares the five interfaces used by virtually every TFT LCD module on the market, from the perspective of an engineer selecting a display for a real product.
The Five Interfaces at a Glance
| Interface | Typical resolution range | Signal pins (approx.) | Frame buffer location | Typical use case |
|---|---|---|---|---|
| MCU (8080/6800) | Up to ~480×320 | 8–18 data + control | In the display module | Small instrument panels, appliance controls |
| SPI | Up to ~320×480 | 4–6 | In the display module | Wearables, small IoT devices, simple UIs |
| RGB (TTL parallel) | ~320×240 to 1024×600 | 18–28 | In the host processor | HMIs, thermostats, mid-size industrial panels |
| LVDS | ~800×480 to 1920×1080 | 8–12 (differential pairs) | In the host processor | Industrial monitors, medical displays, kiosks |
| MIPI DSI | ~480×800 to 1920×1080+ | 4–10 (differential lanes) | In the host processor | Smartphone-class SoCs, modern embedded Linux/Android devices |
Now the practical detail behind each.
MCU Interface (8080 / 6800 Parallel)
The classic embedded display interface. The display module contains its own controller and frame memory—your microcontroller writes pixels only when something changes, then the display refreshes itself.
Choose it when: Your processor is a small MCU (STM32, PIC, 8051-class), your resolution is modest and your UI updates are partial—menus, numbers and icons rather than full-motion graphics.
Watch out for: Bandwidth. Full-screen animation at higher resolutions gets sluggish. Above roughly 480×320, MCU interface stops being practical.
SPI Interface
Functionally similar to MCU interface—controller and memory live on the display—but serialized down to as few as four wires.
Choose it when: Pin count matters more than speed. It suits battery devices, small round or bar displays, and products where the display sits far from the main board on a thin cable.
Watch out for: It is the slowest of the five. It is fine for a smartwatch face or status screen, but wrong for anything resembling video.
RGB Interface (TTL Parallel)
The host processor drives the panel directly, pixel clock and all, from its own LCD controller and frame buffer. There is no intelligence on the display side, which makes the panel cheaper.
Choose it when: Your processor has a built-in LCD controller—many Cortex-A and higher-end Cortex-M parts do—and your resolution sits in the sweet spot of 480×272 to 1024×600. This is the workhorse interface of industrial HMIs and appliance touchpanels.
Watch out for: More than 20 signal wires must run short and clean. RGB is not a long-cable interface, and EMI discipline matters at higher pixel clocks.
LVDS
The same video concept as RGB, but signals travel on differential pairs—far fewer wires, much better noise immunity and cable runs measured in tens of centimeters instead of a few.
Choose it when: Resolution is 800×480 and up, the display is physically separated from the main board—such as monitor-style mechanics, elevator panels or medical carts—or the environment is electrically noisy.
Watch out for: Your processor needs an LVDS transmitter, or you add a converter chip. RGB-to-LVDS bridges are common and are a standard path we design for customers.
MIPI DSI
The modern high-bandwidth standard, born in smartphones and now the default on many embedded Linux and Android SoCs, including i.MX8, Rockchip, Qualcomm and Allwinner platforms.
Choose it when: Your platform is a modern SoC that exposes DSI lanes, you want high resolution at low power, or you are using a panel from the mobile supply chain, which often provides better price per pixel.
Watch out for: DSI initialization sequences are panel-specific and less forgiving than older interfaces. A display supplier that provides validated initialization code and driver support can save real engineering time.
A Note on Replacement Projects
If you are replacing a discontinued panel rather than designing new, the interface is usually the one thing you cannot change without touching hardware and firmware. A proper replacement module matches the original interface and timing exactly—which is why identifying the interface correctly is step one of any replacement project.
When the original interface is genuinely extinct, a small converter board, such as RGB-to-LVDS, inside the original mechanical envelope is often the bridge that keeps the rest of your product untouched.
Quick Decision Guide
- Small MCU, simple UI, small screen → MCU or SPI
- Processor with built-in LCD controller, 4–7 inch panel → RGB
- Bigger panel, longer cable, noisy environment → LVDS
- Modern application SoC, high resolution, low power → MIPI DSI
- Replacing a discontinued display → match the original, whatever it is