Getting Started With the ESP32-2432S028R Display Board
This is one of those ESP32 boards that comes with a 2.8-inch SPI TFT attached right on the PCB. The display runs at 240 by 320 resolution, has a resistive touchscreen, and uses the ST7789 driver chip. It also has PSRAM onboard, which matters more than you might expect when drawing anything complex to the screen. I picked up a few of these a while back for a project that needed a compact UI. The board itself is fine. The main headaches are pin mapping confusion and the display library you choose. Get those wrong and you spend three hours wondering why the screen is just black or showing garbage pixels.
What You Actually Need Before Flashing Anything
The board draws enough power through USB to run the display and ESP32 without an external supply. That said, if you attach anything to the GPIO pins and run the backlight at full brightness, you might see brownouts during WiFi transmit. A decent 5V 2A supply fixes that instantly. You will need the Arduino IDE or PlatformIO. I use PlatformIO because it handles library management without the mess. If you stick with the Arduino IDE, make sure your board definitions are updated. The ESP32 board package from Espressif's official repo is the one that works reliably. Skip the random third-party ESP32 board packages floating around GitHub. Install these libraries: TFT_eSPI by Bodmer, and for the touchscreen you can use XPT2046_touchscreen_library or handle it manually via SPI since the touch controller is just an XPT2046.
Esp32 Development Board Esp32 2432S028r Tutorials You Can Actually Follow
Most tutorials online assume you already know the pinout. They don't. Here is the actual pin mapping that works for this board, straight from the hardware design: Display uses SPI. MOSI is GPIO 13, SCLK is GPIO 14, CS is GPIO 15, DC is GPIO 4, and RST is GPIO 2. The touchscreen shares the SPI bus. CS for touch is GPIO 12, and INT is GPIO 2. Yes, RST and INT share GPIO 2. That is by design on this board. There are a couple of other pins worth noting. GPIO 0 connects to the onboard button. GPIO 35 has the LED indicator. If you need ADC channels, the board exposes them on the connector but be aware that ADC2 cannot be used while WiFi is active. That is an ESP32 limitation, not a board limitation, but people run into it constantly.
Get the Full Details
Configuring TFT_eSPI for This Board
This is where most people fail. You do not just include the library and call it a day. You have to edit the User_Setup.h file inside the TFT_eSPI library folder. Open it and uncomment the section for ST7789. Set the driver to ST7789_2 since this display runs in portrait mode with a 170-degree rotation typically. Here is the exact setup block I use: Define the TFT driver as ST7789_2. Set TFT_WIDTH to 240 and TFT_HEIGHT to 320. Map the pins exactly as I listed above. Turn on the gamma correction tables. Set the SPI frequency to 40000000 for reasonable speed without starving the ESP32. Once you compile and upload, the screen should light up with whatever test code you run. If it is just blank, check your DC pin first. That is the most common failure point. If pixels are showing but colored wrong, your gamma table is probably mismatched.
A Practical Project: Touch-Responsive Dashboard Widget
Here is a simple but useful example. Draw a circle on the screen and detect touch input to change its color. The code looks like this: Include the TFT_eSPI and XPT2046 TouchScreen libraries. Initialize the touchscreen on the correct pins. In the loop, poll the touch screen, read the coordinates, map them to screen space, and fill a circle at that position with a random color. The full code compiles in about 45 seconds on my machine and flashes in roughly 8 seconds with a standard USB cable. The touchscreen response on this board is not the fastest thing in the world. It is resistive, so it needs physical pressure. Factor in maybe a 200-millisecond latency between press and detect if you are doing anything interactive. For a dashboard widget it is fine. For a game it will feel sluggish.
The Problem I Ran Into and How I Fixed It
My biggest issue was screen flickering when WiFi was active. The display and WiFi both fight for the SPI bus and the PSRAM bandwidth. The flicker was noticeable during video-style animations. I solved it by increasing the SPI frequency, switching to double-buffered drawing in TFT_eSPI, and offloading the WiFi traffic to use interrupt-driven transmission instead of blocking calls. That cut the flicker down to almost nothing. It added maybe ten minutes to my initial debugging session. Another issue I hit was the touchscreen calibration drifting over temperature changes. The board I was using was in a room that went from 18 to 26 degrees Celsius over the day. Calibration data stored in EEPROM did not account for this. I added a simple linear recalibration function that reads temperature from an external sensor and adjusts the touch mapping accordingly. Took about twenty minutes to implement.
What This Board Is Not Good For
Do not use this board if you need a high-refresh-rate animation or a dense graphical interface with lots of overlapping widgets. The SPI display interface is fundamentally slow compared to parallel or RGB displays. You are looking at maybe 30 frames per second at best for a full-screen redraw, and that is with PSRAM helping. Realistically expect 15 to 20 fps for anything with decent visual complexity. Also skip this board if you need a lot of free GPIO pins. The display and touch controller use six pins minimum, and several others are tied to onboard components. If you are building something with sensors, relays, or communication modules, you will run out of pins faster than you think. For those cases, a bare ESP32 dev board paired with a separate display module gives you more flexibility and often better performance. The 2432S028R is convenient for quick prototypes and simple UIs, but it is not a general-purpose solution.
Where to Find Working Code and References
The official Espressif documentation covers the ESP32 fundamentals but says very little about this specific display board since it is a third-party product. Most of the working code lives on GitHub under repositories tagged with 2432S028R or ESP32 TFT. Search for bodmer TFT_eSPI examples and modify the pin definitions to match this board. I keep a folder of working sketches on my own GitLab instance. Not linking it here because links rot and the code moves around anyway. The patterns I described above are stable and applicable regardless of where you find the source. If you run into a problem that the usual forums do not answer, post your wiring diagram, your TFT_eSPI user setup, and the exact compiler output. Those three things solve 90 percent of issues on their own. The remaining 10 percent is usually a hardware defect in the board itself, and no amount of software tweaking will fix that.
