Waveshare ESP32‑S3‑Touch‑LCD‑7 — RGB Panel Sync Issue (Stable Fuzz, No Response to Timing Changes)

[Spaldagetti]

Hi all,

I’m working with the Waveshare ESP32‑S3‑Touch‑LCD‑7 (800×480 RGB panel) using ESP‑IDF v5.2.7.
The ESP32‑S3 is successfully driving HSYNC, VSYNC, DE, and PCLK. The panel responds with an initial aqua flash, then shows stable but incorrect fuzzy output.

Over several weeks I’ve tried:

Verified pinmap against Waveshare demo

Corrected RGB565 bit order (DATA0–DATA15)

Multiple polarity combinations

Multiple pixel clocks (9–21 MHz)

Correct ST7262 timing (1/46/16 and 1/23/7)

Waveshare demo timing (4/8/8)

Verified DE polarity

Verified RGB565 formatting

Verified double‑buffering

Verified that sync signals are stable

Despite this, the image never changes at all, regardless of timing, polarity, or pixel clock.
This strongly suggests the panel is not using ST7262 timing, or is operating in DE‑only mode, or uses a different LCD controller IC (EK79007, EK9716, ST7701, HX8264, etc).

I need the actual timing parameters for the LCD module Waveshare uses in this product:

LCD controller IC model

Pixel clock requirements

HSYNC pulse width / back porch / front porch

VSYNC pulse width / back porch / front porch

Required polarity for HSYNC, VSYNC, DE, PCLK

Whether the panel uses DE‑only mode

Whether 16‑bit or 24‑bit RGB mode is required

If anyone has a working esp_lcd_rgb_panel_config_t for this exact Waveshare board, that would be extremely helpful.

Thanks in advance — any insight appreciated.

Aaron
Newcastle, NSW, Australia

[mikemoy]

Waveshare does make cool things. But they are so out of touch with the latest firmware. Even their I2C drivers are still using the old drivers. When working with Waveshare, I have learned the best/fastest way to get going with them is to us AI.
Tell the agent what kit your using and if in visual studio code you have your agent in there it will quite quickly fix things and get it going. Otherwise you're going to spend allot of time fixing their old source code.