Which board does this documentation cover?
ESP32-2432S028 is the model covered by the troubleshooting guide's examples and information. Check the gold model marking beside the speaker connector on the back before applying its pin settings. The repository README introduces the board as ESP32-2432S028R, so the supplied pages use differing labels; they do not establish compatibility with every similarly named board.
The README describes a 2.8-inch, 320 x 240 LCD with resistive touch, USB programming and an SD slot. This repository provides community documentation and examples for that hardware. Start with board identification, then choose the example that uses the peripherals your project needs.
What did our Rust run establish?
Our run on October 8, 2026, at commit 0564a14 recorded an installation failure in Examples/Rust/1-HelloWorld. Our sandbox used lab-rust:1 with 3 CPUs and 12 GB of memory. Its log identifies the immediate obstacle:
error: custom toolchain 'esp' specified in override file '/work/repo/Examples/Rust/1-HelloWorld/rust-toolchain.toml' is not installed
Installation returned exit code 1 without timing out. The stored install duration is 2 seconds, the raw step duration is 2056 milliseconds, and the stored overall duration is 7 seconds. The overall duration must not be presented as installation time.
Our harness stores command outcomes separately. Build and test are null here, leaving no compilation result or passing-test count to report. Our sandbox did not exercise flashing, display output, touch input, SD access or the Arduino route. The toolchain error explains this installation failure; it does not establish that the Rust example is defective.
The MrKeyoor testing methodology explains command reporting and its limits. The supplied methodology page was retrieved after this run and provides provenance context; it does not establish which procedure version the October 8 run used. This correction uses the stored record without a new execution. No dependency audit result or scan coverage is recorded.
What must Arduino users configure?
TFT_eSPI requires the repository's User_Setup.h configuration, according to the setup guide. Installing the library alone does not complete the documented setup: the guide instructs users to copy that file into the Arduino libraries\TFT_eSPI folder.
The CYD setup guide also calls for ESP32 support in Arduino IDE and a CH340 driver if one is missing. It names ESP32 Dev Module as an example board selection and suggests 115200 upload speed when uploading fails. We reviewed these instructions but did not execute them.
Can display, touch and SD work together?
Using all three devices together requires software SPI for one device, according to the troubleshooting guide. The board assigns them to separate buses, while the ESP32 has two usable hardware SPI buses. The guide usually assigns software SPI to touch because it needs less bandwidth.
The CYD troubleshooting guide therefore matters when combining examples. A display-only result would not establish that display, touch and storage work together. Verify the combined configuration on your board; our sandbox did not test it.
When should you consider another route?
The standard T-Display-S3 board has no onboard SD card slot. LilyGO's repository documents a different ESP32-S3 board with a 1.9-inch, 170x320 display and a PlatformIO setup route. Consider that hardware alternative when its specifications fit your project, accounting for storage requirements and its own configuration instructions. We did not test it.
The m5stack/M5Stack library is deprecated; its README directs readers to M5GFX and M5Unified. If you are considering M5 hardware, use that notice to choose where to investigate software support. The supplied evidence does not establish CYD compatibility for those libraries.
ESPHome is a complementary route listed in the CYD README, rather than a replacement board. The supplied ESPHome extract contains only navigation labels, so it does not support a claim that this route is easier or more capable.
What do the editorial scores mean?
Setup ease is 2/5 because our Rust installation stopped at a prerequisite and Arduino needs manual display configuration. Documentation is 4/5 for the supplied setup, board-identification and troubleshooting coverage. Maturity is 3/5 for a documented starting point with a combined-peripheral constraint and no build or hardware validation from our run. Community is unassessed because the supplied extracts do not establish current participation or responsiveness.
The rubric uses 1 for major documented obstacles, 2 for substantial prerequisites, 3 for a usable starting point with material qualifications, 4 for broad relevant guidance with explicit limits, and 5 for comprehensive evidence with validated outcomes in the assessed scope. These are editorial judgments, not performance measurements. Unknown dimensions receive no numerical rating.

