TTGO T-Display simulator, an ESP32 with a 1.14 inch screen
LilyGO’s TTGO T-Display is a classic ESP32, of which one Xtensa LX6 core runs here, with a 1.14 inch 135x240 ST7789 screen and two buttons on the board. TFT_eSPI gets LilyGO’s setup with no file to install, the screen keeps its real offsets and its inverting glass, and WiFi joins a simulated network.
- 7peripheral areas modeled
- 1project ready to run
- Real timeon your own machine
What is modeled
Taken from the board's own contract document and put in plain words, with what is missing beside it.
Modeled
- Core
- One Xtensa LX6 core, the DevKit V1 model whole
- GPIO
- The twenty-four header pins, numbered as the silkscreen numbers them
- The screen
- The ST7789 part at 135x240 on MOSI 19, SCLK 18, CS 5, DC 16, RST 23, backlight on GPIO 4
- TFT_eSPI
- LilyGO’s Setup25_TTGO_T_Display.h built in, so a sketch that names no pins draws on the screen
- The buttons
- BUTTON1 on GPIO 35 with the board’s pull-up, and BUTTON2 on GPIO 0, which is BOOT
- ADC1
- 32, 33 and 36 to 39
- WiFi, simulated
- WiFi.h over a network written in software: no radio, no 802.11, no real internet
Not modeled
- The battery connector and its charger.
- The battery divider on GPIO 34, switched by GPIO 14.
- The second core, ADC2, Bluetooth and a real radio.
Open one and press Run
Each of these opens in the editor exactly as it is drawn here.
Every built-in project on the T-Display
Each has its own page with the circuit running, the code and a parts list.
Tutorials that use this board
Each one ends in a running circuit, on this same board.
Questions
Is it free?
Yes. Every board and every part is on the free plan, with no account needed.
Do I need to edit User_Setup_Select.h?
Not here. If your sketch names no TFT pins, TFT_eSPI gets LilyGO’s setup: ST7789_DRIVER at 135x240, MOSI 19, SCLK 18, CS 5, DC 16, RST 23, backlight 4. On a real board you install that setup in the TFT_eSPI library folder by choosing Setup25_TTGO_T_Display.h.
Why does my own driver draw in the wrong place, or in negative colors?
The glass is a 135x240 window into memory from column 52 and row 40, and it is IPS, so it shows colors inverted until the driver sends INVON. TFT_eSPI handles both. A driver that does not is wrong here and on the board.
Which pins are the buttons?
BUTTON1 is GPIO 35 and BUTTON2 is GPIO 0, which is BOOT. Both read LOW while pressed. GPIO 35 has no pull of its own, so the board carries one.
The other boards
Every one of these runs today, and every one is free.
A RISC-V chip at 160 MHz, on the real memory map.
The classic Arduino, with an ATmega328P running at 16 MHz.
The Uno’s chip on a small board that fits a breadboard.
The big Arduino, with 54 digital pins and four serial ports.
An Uno-shaped board whose chip does its own USB serial.
A second RISC-V board, with 31 pins and simulated WiFi.
The classic ESP32 at 240 MHz, with simulated WiFi.
The ESP32-S3 at 240 MHz, with USB serial and an RGB LED.
Try it on your own firmware
What you build here runs on the board on your desk, unchanged. Nothing to install and no account needed.