LilyGo T-Display-S3 AMOLED Touch

USB-C Native USB
LilyGo T-Display-S3 AMOLED Touch board
60 × 25.5 mm
ESP32-S3
MCU
240MHz
clock
16MB
flash
512KB
SRAM
18· 10 ADC
GPIO
BLE 5.0+ WiFi
radio
On this page

Pinout

21 pins · 2.54 mm pitch
View:
LilyGo T-Display-S3 AMOLED Touch pinout diagram
PinGPIOLabelsStatusCapabilitiesNotes
1-3V33.3Vpower-3.3V regulated output
2-GNDground-Ground
3-VSYSVBUSpower-USB 5V / system power rail
41IO1safeadc · touch · pwmLeft header; ADC1_CH0, capacitive-touch capable
52IO2SCLsafeadc · touch · i2c · pwmLeft header; I2C SCL - shared with CST816 touch controller
63IO3SDAstrappingadc · touch · i2c · pwmLeft header; I2C SDA - shared with CST816 touch controller (strapping pin)
710IO10SSstrappingadc · touch · spi · pwmLeft header; default FSPI CS (SS), ADC1_CH9
811IO11MOSIstrappingadc · touch · spi · pwmLeft header; default FSPI MOSI, ADC2_CH0
912IO12SCKstrappingadc · touch · spi · pwmLeft header; default FSPI SCK, ADC2_CH1
1013IO13MISOstrappingadc · touch · spi · pwmLeft header; default FSPI MISO, ADC2_CH2
1114IO14strappingadc · touch · pwmLeft header; ADC2_CH3, capacitive-touch capable
1215IO15safeadc · pwmLeft header; ADC2_CH4, U0RTS
1316IO16safeadc · pwmLeft header; ADC2_CH5, U0CTS
1439IO39strappingpwmRight header; MTCK (JTAG)
1540IO40strappingpwmRight header; MTDO (JTAG)
1641IO41strappingpwmRight header; MTDI (JTAG)
1742IO42strappingpwmRight header; MTMS (JTAG)
1843IO43TXstrappinguart · i2c · pwmRight header; UART0 TX (U0TXD), also on Qwiic/STEMMA QT I2C connector
1944IO44RXstrappinguart · i2c · pwmRight header; UART0 RX (U0RXD), also on Qwiic/STEMMA QT I2C connector
2045IO45strappingpwmRight header; strapping pin
2146IO46strappingpwmRight header; strapping pin

Start with these

4 pins with no boot or system involvement
IO1IO2SCLIO15IO16

Freely assignable - no strapping, flash, USB or JTAG duties. Ideal first picks for buttons, sensors and LEDs.

Fine - with a little care

sampled at boot or shared with debug/serial
PinLabelWhat to knowRole
IO3GPIO3Sampled at reset to select JTAG interface (USB Serial/JTAG controller vs. external pins). Improper use can disable external JTAG or alter debug interface.Strapping
IO39MTCK (GPIO39)Default JTAG debugging TCK pin. If JTAG is needed, this pin must be free; it may also be used internally for PSRAM chip select on certain modules, so avoid repurposing it.Other
IO40MTDO (GPIO40)Default JTAG TDO output for debugging. Using it as GPIO will interfere with JTAG debugging functionality.Other
IO41MTDI (GPIO41)Default JTAG TDI input for debugging. Should be reserved for JTAG or left unused if JTAG is to remain available.Other
IO42MTMS (GPIO42)Default JTAG TMS signal for debugging. Using this pin for other purposes will disable the JTAG interface (unless JTAG is rerouted to USB).Other
IO43U0TXD (GPIO43)Used for bootloader output and UART console logs. If repurposed, you will lose the default serial output (and programming via UART0).Other
IO44U0RXD (GPIO44)Used for bootloader input (download mode via serial). If repurposed, you cannot use the default UART0 download mode for programming the chip.Other
IO45GPIO45Determines flash/PSRAM power voltage (3.3 V vs 1.8 V) at boot. Must match hardware configuration; using as GPIO can upset flash supply setting.Strapping
IO46GPIO46Must be at a defined level during reset (with GPIO0) to select normal or download boot and UART/USB print mode. This pin is input-only (no output drive), so it should be left for its intended strapping function.Strapping

Only if you know the tricks

wired to flash or USB - expect a fight
PinLabelWhat to knowRole
IO10FSPICS0Used to select the external flash chip. It is required for flash access and cannot be repurposed without losing flash connectivityFlash
IO11FSPIDUsed as a data line for flash (and in-package PSRAM). It should not be used as GPIO when the flash/PSRAM is in use.Flash
IO12FSPICLKDrives the flash (and PSRAM) clock. This critical signal must be reserved for memory and not used as general GPIO.Flash
IO13FSPIQUsed as a data line for flash/PSRAM transfers. Not available for other uses when flash/PSRAM is connected.Flash
IO14FSPIWPConnected to external flash (data/write-protect signal). Not recommended as GPIO because it’s reserved for flash operations.Flash
These are recommendations, not hard rules - with the right pull-ups, timing and boot-state awareness most pins can be made to work. When in doubt, start green.
Pinout notes Across 21 pins (2.54 mm pitch), the LilyGo T-Display-S3 AMOLED Touch exposes 18 GPIO plus 3V3 , GND and VSYS for power. For peripherals, I²C is mapped to SDA…

Across 21 pins (2.54 mm pitch), the LilyGo T-Display-S3 AMOLED Touch exposes 18 GPIO plus 3V3, GND and VSYS for power.

For peripherals, I²C is mapped to SDA on GPIO3 and SCL on GPIO2; the SPI bus (MOSI, MISO, SCK, SS) is broken out in full; TX/RX on GPIO43 and GPIO44 cover serial logging and flashing.

On the analog side there are 10 ADC-capable pins for sensors and battery monitoring, PWM on every GPIO and 8 capacitive-touch inputs.

If you want zero surprises, IO1, IO2, IO15 and IO16 are free of any such role - the safest first picks. 9 of the exposed pins carry boot-time or system duties on the ESP32-S3 (IO3, IO39, IO40 and 6 more).

Getting started

flash your first firmware in ~2 minutes
Tool:
1
Connect over USB
Native USB - no driver, no serial chip. Not detected? Hold BOOT while plugging in.
2
Flash with your tool
Arduino IDE, PlatformIO, ESPHome or esptool - copy the settings on the right.
3
Verify it runs
The blink example uses GPIO1 - swap for your board's LED pin if different.
Tools → Board settings Copy
Board:            
USB CDC On Boot:  Enabled
Flash Size:       16MB
Upload Speed:     921600

// blink
pinMode(1, OUTPUT);
digitalWrite(1, LOW);   // on (often inverted)
platformio.ini Copy
[env:lilygo_t_display_s3_amoled_touch]
platform = espressif32
board = esp32-s3-devkitc-1
framework = arduino
monitor_speed = 115200
upload_speed = 921600
device.yaml Copy
esp32:
  board: esp32-s3-devkitc-1
  variant: 
  framework:
    type: esp-idf

# blink - GPIO1
output:
  - platform: gpio
    pin: 1
    id: led_out
light:
  - platform: binary
    name: "LED"
    output: led_out
shell Copy
esptool.py --chip esp32s3 --port /dev/ttyACM0 \
  write_flash 0x0 firmware.bin

Specifications

ESP32-S3 · 60 × 25.5 mm
Compute
MCU
ESP32-S3
Clock
240 MHz
SRAM · Flash
512 KB · 16MB · 8MB (OPI) PSRAM
Radio
Wi-Fi
802.11 b/g/n
Bluetooth
5.0 LE
Antenna
PCB
I/O
GPIO · ADC
18 · 10
UART · I²C · SPI
3 · 2 · 4
PWM
8 channels
Power
USB
USB-C
Serial
Native (CDC)
Boot address
0x0
Display
Screen
AMOLED · 1.91" · 240x536
Driver
RM67162
Touch
CST816
Flashing
Upload · OTA
esptool_py · esp_ota
Flash · Boot mode
- · -
Sketch · Data
- · -
25.5 mm60 mm
60 × 25.5 mm · pin pitch 2.54 mm
The LilyGo T-Display-S3 AMOLED Touch uses esptool_py for firmware uploads, esp_ota for over-the-air (OTA) updates.

About this board

At its core is the ESP32-S3 - a dual-core Xtensa with vector extensions suited to AI workloads.

Expect to pay about $33.98 - in line with other ESP32-S3 boards.

Onboard you'll find 8MB (OPI) PSRAM, an AMOLED 1.91" 240x536 display with touch, battery charging via JST 1.25 and Boot/Reset buttons.

It flashes over native USB - no serial-converter driver needed, which isn't a given among ESP32-S3 boards.


The LilyGo T-Display-S3 AMOLED Touch is a cutting-edge development board featuring an ESP32-S3 chip with integrated WiFi and Bluetooth 5 capabilities. It boasts a 1.91-inch AMOLED display with a resolution of 536x240 pixels, driven by an RM67162 controller, offering vibrant visuals for embedded applications. Now featuring capacitive touch support for intuitive user interactions.

Where to buy

prices are typical street prices
LilyGo T-Display-S3 AMOLED Touch
LilyGo T-Display-S3 AMOLED Touch
$33.98per unit, typical

Resources

Similar boards