Waveshare · ESP32-S3 · 1.43" · 466×466

Waveshare ESP32-S3-Touch-AMOLED-1.43C specifications

This page collects the pinout, free GPIOs and hardware details of the ESP32-S3-Touch-AMOLED-1.43C. The board isn't in the LCD Ultra Pro™ editor yet, so there's no driver for it there.

466×466 on a 1.43-inch circle is a dense screen, roughly 326 pixels per inch. Waveshare's 1.43C pairs that CO5300 AMOLED with an ESP32-S3-PICO-1-N8R8, a system-in-package that puts the chip, 8 MB of flash and 8 MB of PSRAM into one small module.

Flash is the thing to watch. At 8 MB it's half of what most Waveshare S3 boards carry, and image-heavy watch faces fill it quickly. Keep assets compressed or load them from somewhere else.

The pin map is its own. QSPI data sits on GPIO 9 to 12, clock on 14, CS on 15, reset on 13 and the tearing-effect line on 8. Touch is a CST820 with reset on 16 and interrupt on 17. Audio runs through an ES8311 and ES7210 with a separate LDO enable (GPIO 18) and amplifier enable (GPIO 46). For the battery there's an ETA6098 charger with its status on GPIO 7, a voltage divider on GPIO 4 and an LED on GPIO 5.

ESP32-S3-Touch-AMOLED-1.43C board diagram with an example screen: 1.43" 466×466, ESP32-S3
Annotated diagram of the Waveshare ESP32-S3-Touch-AMOLED-1.43C, drawn by LCD Ultra Pro™.
Screen
1.43" · 466×466
Chip
ESP32-S3
Memory
8 MB flash, 8 MB PSRAM (OPI)
Input
capacitive touch

Key features

  • Round 1.43-inch AMOLED, 466×466, CO5300
  • CST820 capacitive touch
  • ESP32-S3-PICO-1-N8R8 (8 MB flash, 8 MB PSRAM)
  • ES8311 speaker codec, ES7210 dual microphones
  • ETA6098 charger with status and voltage sense
  • Tearing-effect line for smooth updates

Specifications

Waveshare ESP32-S3-Touch-AMOLED-1.43C technical specifications
ManufacturerWaveshare
Screen size1.43"
Resolution466×466 px
Colour depth16-bit
Display controllerCO5300 (QSPI AMOLED)
Display interfaceQSPI
TouchCST820 (capacitive, I2C)
MicrocontrollerESP32-S3
ModuleESP32-S3-PICO-1-N8R8
CPU clock240 MHz
Internal SRAM512 KB
PSRAM8 MB (OPI)
Flash8 MB
Wi-FiYes
BluetoothYes
Hardware variantRound 466x466 AMOLED on an ESP32-S3-PICO-1-N8R8 system-in-package (8 MB flash, 8 MB octal PSRAM). ETA6098 battery charger, ES8311 speaker codec with NS4150 amplifier, ES7210 dual-microphone ADC.
Display466×466 AMOLED, QSPI: D0-D3 GPIO 9 to 12, CLK 14, CS 15, RST 13, TE 8
TouchCST820, RST 16, INT 17
AudioMCLK 38, SCLK 39, LRCLK 40, DIN 41, DOUT 42, LDO 18, amplifier 46
I2CSDA 47, SCL 48
BatteryETA6098; status GPIO 7, voltage GPIO 4, LED GPIO 5
Memory8 MB flash, 8 MB octal PSRAM

GPIO pinout

The GPIOs the board itself uses for the display, touch and on-board peripherals, as published in the manufacturer’s documentation.

Waveshare ESP32-S3-Touch-AMOLED-1.43C GPIO pinout
GPIOFunction
GPIO 0BOOT button
GPIO 1Unassigned GPIO
GPIO 2Unassigned GPIO
GPIO 3Unassigned GPIO
GPIO 4Battery voltage (ADC)
GPIO 5Battery LED
GPIO 6Unassigned GPIO
GPIO 7Charger status
GPIO 8LCD tearing effect (TE)
GPIO 9LCD data 0
GPIO 10LCD data 1
GPIO 11LCD data 2
GPIO 12LCD data 3
GPIO 13LCD reset
GPIO 14LCD QSPI clock
GPIO 15LCD CS
GPIO 16Touch reset
GPIO 17Touch interrupt
GPIO 18Audio codec enable
GPIO 19USB D-
GPIO 20USB D+
GPIO 21Unassigned GPIO
GPIO 38I2S MCLK
GPIO 39I2S SCLK
GPIO 40I2S LRCLK
GPIO 41I2S DSDIN
GPIO 42I2S DSOUT
GPIO 43UART0 TX (unassigned)
GPIO 44UART0 RX (unassigned)
GPIO 45Unassigned GPIO (strapping pin)
GPIO 46Speaker amplifier enable
GPIO 47I2C SDA (touch, codecs)
GPIO 48I2C SCL (touch, codecs)

Source: github.com, docs.waveshare.com, docs.waveshare.com. Always check against your board revision before wiring.

Free GPIOs and connectors

These GPIOs are not used by the display, touch or on-board peripherals, so you can wire your own sensors, buttons or relays to them.

Free GPIO pins of the Waveshare ESP32-S3-Touch-AMOLED-1.43C
PinCapabilitiesNote
GPIO 1GPIO, PWM, ADCNot assigned in Waveshare's GPIO table
GPIO 2GPIO, PWM, ADCNot assigned in Waveshare's GPIO table
GPIO 3GPIO, PWM, ADCNot assigned in Waveshare's GPIO table
GPIO 6GPIO, PWM, ADCNot assigned in Waveshare's GPIO table
GPIO 21GPIO, PWMNot assigned in Waveshare's GPIO table
GPIO 43GPIO, PWM, UART_TXUART0 TX, not assigned on the board
GPIO 44GPIO, PWM, UART_RXUART0 RX, not assigned on the board
GPIO 45GPIO, PWMNot assigned; strapping pin, keep it free at boot

Good to know before you start

  • This board is in the wiki only; the LCD Ultra Pro editor does not support it yet.
  • 8 MB flash is tight for many full-screen images.
  • Not pin-compatible with the plain AMOLED-1.43: the QSPI and SD pins moved.

What it is good for

  • •Premium-looking round watch faces
  • •Compact voice gadgets
  • •Battery-powered indicators

LVGL support in LCD Ultra Pro™

This board is documented in the wiki, but it is not in the LCD Ultra Pro™ editor yet, so you can’t pick it there or export a project for it. The specs, pins and connectors on this page come from the manufacturer’s own material and are there to help you wire and configure it. See the board list for boards the editor supports today.

Arduino IDE settings

From the manufacturer's documentation (not tested by us yet)

BoardESP32S3 Dev Module
USB CDC On BootEnabled
Flash ModeQIO 80MHz
Flash Size8MB (64Mb)
Partition SchemeHuge APP (3MB No OTA/1MB SPIFFS)
PSRAMOPI PSRAM

Board package: esp32 by Espressif Systems

Menu items the manufacturer doesn't mention are left at their defaults. We haven't compiled a driver for this board ourselves yet. Manufacturer's source

Frequently asked questions

How much flash does the AMOLED-1.43C have?

8 MB, inside the ESP32-S3-PICO-1-N8R8 package, together with 8 MB of octal PSRAM.

Which touch controller is used?

A CST820 on I2C (GPIO 47/48), with reset on GPIO 16 and interrupt on GPIO 17.

Can I read the battery voltage?

Yes, on GPIO 4 through a divider. GPIO 7 reports the charger status.

Sources

Specifications cross-checked against the manufacturer’s documentation (last checked 2026-11-04):

More in the Waveshare round display family

Tools for this board

All free tools →

Connect sensors and parts

All sensors and parts →

Last updated:

Adding I2C sensors to this board?See which addresses its own chips already use, and what would clash.

Something wrong on this page?

Tell me what you found. I check every report and fix the page.