From 05f6474108278c6d9e4663bfe3b8a1b04aae11bd Mon Sep 17 00:00:00 2001 From: zelo533 Date: Sat, 22 Aug 2026 19:06:33 -0500 Subject: [PATCH] meshnology-w10: define HAS_SPI_TFT so the TFT screen initializes again (#11042) #10803 refactored main.cpp to key SPI-TFT Screen creation on HAS_SPI_TFT instead of the per-controller define list. The W10 variant (#10911) was written before that refactor and crossed it mid-air, so it never defines HAS_SPI_TFT and develop builds fall through to the I2C-OLED autodetect branch: no Screen is ever constructed and the display stays dark, while everything else (radio, GPS, BLE) works. Verified on a real W10: with the define, the boot log shows TFTDisplay creation, backlight power-on and the boot screen, and the ST7789 panel renders the UI again. Co-authored-by: Ben Meadors --- variants/esp32s3/meshnology-w10/variant.h | 1 + 1 file changed, 1 insertion(+) diff --git a/variants/esp32s3/meshnology-w10/variant.h b/variants/esp32s3/meshnology-w10/variant.h index 98677b218..cd1fe1e65 100644 --- a/variants/esp32s3/meshnology-w10/variant.h +++ b/variants/esp32s3/meshnology-w10/variant.h @@ -87,6 +87,7 @@ #define TFT_DC 16 // pg1: OLED_DC=GPIO16 #define TFT_BL 6 // pg1: OLED_BL=GPIO6 (backlight PWM) #define TFT_RST -1 // panel reset is EXIO1 on the expander, toggled in mcp23017EarlyInit() +#define HAS_SPI_TFT 1 // main.cpp keys SPI-TFT Screen creation on this since #10803 #define USE_TFTDISPLAY 1 #define SPI_FREQUENCY 75000000