ShopLearnFluxgrid
Lonely Binary
ESP32TinkerBlockProductsFundamentalsTools
Screens
Before the wires2
01How much data is a screen02A screen is not one thing
Screens with their own memory4
03I2C OLED04SPI TFT05QSPI displays068080 parallel
Screens you have to keep feeding5
07Where a frame lives08Frame buffer, PSRAM and DMA09RGB timing10RGB565, 666 and 88811Tearing and double buffering
Fast links5
12MIPI DSI lanes13DSI command and video mode14LVDS15eDP16Start with your MCU
All fundamentals →
Fundamentals/Screens/Before the wires
Chapter · Screens

Before the wires

How much data a picture is, and why a screen is a panel, a controller, a backlight and a host that have to agree.

2 articlesabout 8 minutesNo board required
  1. 01How much data is a screen4 minEvery screen problem starts with arithmetic. Count the bits in one frame, divide by what the link can carry, and you know the floor before any protocol overhead is added.
  2. 02A screen is not one thing4 minThe word screen covers a panel, a backlight, a controller and sometimes a touch layer. Each can fail alone, and two questions sort them out. Where do the pixels live, and who owns the refresh timing?

Start at 01 and read down — the order is the order things get easier in. Or take the one with your part in it; every article stands on its own, and links back to whatever it needs.

← Previous chapterWider belts4 articlesNext chapter →Screens with their own memory4 articles
Lonely Binary

From Zeros to Heroes, One Bit at a Time.

Sydney, Australia · office@lonelybinary.com

Shop
BoardsKitsSensors & InputDisplaysBest SellersWholesale
Learn
ESP32TinkerBlockProduct handbooksFundamentalsDownloadsProduct codes
Fluxgrid
Get startedCheat sheetDocsLibrary on GitHub
Help
Contact usDeliveryReturnsWarranty
© 2026 Lonely BinaryTermsRefund policy