Driving an ILI9341 SPI Display and Touch Controller from ESP32-S3

Sat, 19 Sep 2026 00:00:00 +0000

A 2.4-inch 240 × 320 TFT module built around the ILI9341 is a practical match for an ESP32-S3 because the display controller accepts a serial SPI interface. The module is not necessarily one device: a typical board can contain the ILI9341 for pixels, a separate resistive-touch controller, and sometimes a microSD socket.

That distinction determines the wiring. The devices may share SPI clock and data lines, while each peripheral keeps its own chip-select signal.

Streaming Sensor Graphs to ILI9341 Without a Framebuffer on ESP32-C3

Sat, 19 Sep 2026 00:00:00 +0000

An ILI9341 panel is large enough for a useful live sensor graph, but a 240 × 320 RGB565 framebuffer costs 153,600 bytes:

copied = false, 1600)" class="absolute right-3 top-3 z-10 rounded-lg border border-line-strong bg-surface px-2 py-1 font-mono text-[0.8rem] text-muted opacity-0 transition group-hover:opacity-100 hover:bg-ink hover:text-white dark:border-night-line dark:bg-night dark:text-night-muted dark:hover:bg-white dark:hover:text-ink">

240 * 320 * 2 bytes = 153,600 bytes

That is a poor default allocation on a small microcontroller when the graph itself may need only a few hundred samples. The display controller already contains its own graphics RAM. An ESP32-C3 can therefore treat the panel as the destination, keep only the application state it needs, and send changed pixels over SPI.

ILI9341 on Nalar

Driving an ILI9341 SPI Display and Touch Controller from ESP32-S3

Streaming Sensor Graphs to ILI9341 Without a Framebuffer on ESP32-C3