E-Ink / E-Paper
Interfacing GDEW0154 E-Ink / E-Paper with ESP32
What is the GDEW0154?
GDEW0154 practical reference
The GDEW0154 is a 200×200 pixel, 1.54-inch e-paper panel that holds its last image with zero power draw — only refreshing (which takes ~1-2 seconds and briefly flashes black/white) actually uses current. That makes it a natural fit for battery-powered badges, price tags, and status signs that update rarely.
It's a partial-refresh-capable panel over SPI, driven almost universally through Jean-Marc Zingg's GxEPD2 library on Arduino-family boards, which abstracts away the panel's row/column update sequencing.
Key specifications
- Resolution: 200 × 200 pixels, monochrome (black/white)
- Operating voltage: 3.3V
- Interface: SPI
- Full refresh time: ~1-2 seconds, visible black/white flash
- Power draw when static: ~0 (image persists with no power)
Pinout and connection notes
This panel is 3.3V logic only - do not feed it 5V on VCC even on 5V boards like the Uno, or you risk damaging the panel. BUSY must be checked (the library handles this for you) before starting a new update; writing mid-refresh corrupts the image.
- VCC: Power, 3.3V
- GND: Ground
- DIN: SPI data in (MOSI)
- CLK: SPI clock (SCK)
- CS: SPI chip select
- DC: Data/command select
- RST: Reset, active low
- BUSY: Goes high during a refresh - poll or interrupt on this before sending new data
Integration checklist
- Confirm the exact part number and breakout-board revision.
- Verify supply voltage, current demand, logic levels, and signal direction against the datasheet.
- Check controller pin assignments and bus address or interface mode against the example code.
- Power up with external loads disconnected, then test signals before full integration.
- If readings or communication fail, check power and ground first, then pin mapping, interface settings, and library initialization.
Troubleshooting and reproducibility
Record the board used, wiring, library/version, supply arrangement, and measured behavior. Use the selected board-specific wiring example as the source of truth. Never assume visually similar modules share identical voltage tolerance or pin order.
Setting Up GDEW0154 with ESP32
Library
GxEPD2 by Jean-Marc Zingg
Arduino IDE → Library Manager → search "GxEPD2" → Install
Wiring
| Component pin | ESP32 pin | Note |
|---|---|---|
| VCC | 3V3 | |
| GND | GND | |
| DIN | GPIO23 (MOSI) | |
| CLK | GPIO18 (SCK) | |
| CS | GPIO5 | |
| DC | GPIO17 | |
| RST | GPIO16 | |
| BUSY | GPIO4 |
Swipe sideways to see every column →
- ESP32 has plenty of RAM for a full-buffer (non-paged) GxEPD2 variant if you want simpler code - the paged version above works everywhere and is worth keeping for consistency across boards.
- Pair with deep sleep for battery projects - the display holds its image through a full ESP32 power-down.
Related Components
Related Guides & Projects
MicroPython vs Arduino on ESP32: Which Should You Learn First?
An honest comparison for beginners: where MicroPython is easier, where Arduino C++ is faster, how libraries and memory differ, and how to choose based on your project instead of hype.
MicroPython ESP32 Web Server: Control an LED or Relay from Your Browser
Create a working web server with the socket module, parse requests, serve a responsive control page for an LED or a relay, keep the displayed state truthful, choose a safe relay startup state and make the server survive bad or repeated requests.
MicroPython on ESP32 and Raspberry Pi Pico W: The Complete Guide
A structured MicroPython learning path for ESP32 and Pico W. Set up your tools, control GPIO, read sensors, connect to WiFi, build web servers, publish MQTT data and make projects reliable. Start here, then follow the links by level.
boot.py vs main.py in MicroPython: What Runs, When and Why
Understand the difference between boot.py and main.py in MicroPython, startup order, Wi-Fi setup, project structure, and recovery from boot errors.