Driver ICs We Use, and Why the Controller Matters to Your Firmware

The driver IC is the part your firmware actually talks to. It sets the initialisation sequence, the command set, the addressing mode and often the maximum interface speed - which is why swapping a panel for one with a different controller is a firmware task, not just a purchasing one. This page lists the controllers across our published models so you can check compatibility before you design in a part.

Written by the Junxian applications engineering team. Figures quoted for “our models” are calculated from the 103 models on this site that carry a full parameter set, so they change when the catalogue changes.

What does the display driver IC decide?

Four things you will meet in firmware. The initialisation sequence: the specific register writes that bring the panel up, which differ between controllers even when they look interchangeable on paper. The command set and addressing: how you set a window, write pixels, rotate or invert. The interface options the glass supports: many controllers offer SPI and parallel modes, selected by a strap resistor on the module - which is why the same glass appears with different interfaces in our catalogue. And timing limits: the maximum clock the controller accepts, which caps your frame rate.

The controllers used across our published models

The table below is what we actually ship, not a market survey. Use it to check whether a controller you already have a driver for exists in the size you need.

Taken from the published specification of each model. A further 21 published models do not name the controller on the public page - that is deliberate on glass where the source can change; ask and we will confirm the current IC for a specific order.

Why some models do not name the controller publicly

Because on some glass the controller is a second-source item and naming it publicly would turn a normal supply-chain substitution into a specification breach. We would rather leave the field open on the website and confirm the exact controller for your order in writing, than publish a number we might not be able to hold for three years. Ask for the current controller for any model and you will get a straight answer, including whether it is fixed or may change.

Handling a controller change without a rewrite

Isolate the initialisation sequence and the low-level write functions from the rest of your display code. If those live in one file with a clear interface, changing controller means replacing an init table and possibly a pixel-format call. If they are spread through the UI code, the same change becomes a project. This is the single cheapest piece of design advice on this site and costs nothing to follow before the first prototype.

Controller compatibility is not the same as pin compatibility

Two modules with the same controller can still differ in FPC pin order, connector type, backlight drive and the strap options set on the module. Conversely, two modules with different controllers can be pin compatible and need only a firmware change. When you evaluate a replacement, check both: the controller decides firmware, the FPC and connector decide hardware, and they are independent.

What to send us so we can confirm compatibility

The controller you have a working driver for, the interface and its speed, the colour format you use, and the size and resolution you need. If you are replacing a part, add its datasheet or clear photos of the module markings. That is normally enough for us to say either 'same controller, drop in', 'different controller, expect an init sequence change' or 'not compatible, here is what is'.