ST77916

[Basitadam]

Hi,
Made a working driver set for ST77916. I can share anyone interested
BR,
Tim

[brightproject]

Hi, Made a working driver set for ST77916. I can share anyone interested BR, Tim

Hello @Basitadam
This is a good work.
Definitely worth sharing, I'm interested.
Have you tested the display with the ST77916 driver on this library?
What microcontroller did you use and what pins did you connect?
I repeat, you raised an important and interesting discussion, but gave very little information, only intrigued🙂
The most interesting thing is how you indicated the contacts, because for the display ST77916 as far as I understand, additional quad SPI pins are needed:

Arduino_ESP32QSPI::Arduino_ESP32QSPI(
int8_t cs, int8_t sck, int8_t mosi, int8_t miso, int8_t quadwp, int8_t quadhd, bool is_shared_interface /* = false */)
: _cs(cs), _sck(sck), _mosi(mosi), _miso(miso), _quadwp(quadwp), _quadhd(quadhd), _is_shared_interface(is_shared_interface)

From another project

https://github.com/moononournation/Arduino_GFX/blob/1c4362eb4045edb9a8e8b922db783de2d91f42f7/examples/PDQgraphicstest/Arduino_GFX_dev_device.h#L421

Because the library TFT_eSPI is initialized much differently, and requires a simple SPI connection:

void TFT_eSPI::initBus(void) {

#ifdef TFT_CS
  if (TFT_CS >= 0) {
    pinMode(TFT_CS, OUTPUT);
    digitalWrite(TFT_CS, HIGH); // Chip select high (inactive)
  }
#endif

// Configure chip select for touchscreen controller if present
#ifdef TOUCH_CS
  if (TOUCH_CS >= 0) {
    pinMode(TOUCH_CS, OUTPUT);
    digitalWrite(TOUCH_CS, HIGH); // Chip select high (inactive)
  }
#endif

// In parallel mode and with the RP2040 processor, the TFT_WR line is handled in the  PIO
#if defined (TFT_WR) && !defined (ARDUINO_ARCH_RP2040) && !defined (ARDUINO_ARCH_MBED)
  if (TFT_WR >= 0) {
    pinMode(TFT_WR, OUTPUT);
    digitalWrite(TFT_WR, HIGH); // Set write strobe high (inactive)
  }
#endif

#ifdef TFT_DC
  if (TFT_DC >= 0) {
    pinMode(TFT_DC, OUTPUT);
    digitalWrite(TFT_DC, HIGH); // Data/Command high = data mode
  }
#endif

#ifdef TFT_RST
  if (TFT_RST >= 0) {
    pinMode(TFT_RST, OUTPUT);
    digitalWrite(TFT_RST, HIGH); // Set high, do not share pin with another SPI device
  }
#endif

#if defined (TFT_PARALLEL_8_BIT)

  // Make sure read is high before we set the bus to output
  if (TFT_RD >= 0) {
    pinMode(TFT_RD, OUTPUT);
    digitalWrite(TFT_RD, HIGH);
  }

  #if  !defined (ARDUINO_ARCH_RP2040)  && !defined (ARDUINO_ARCH_MBED)// PIO manages pins
    // Set TFT data bus lines to output
    pinMode(TFT_D0, OUTPUT); digitalWrite(TFT_D0, HIGH);
    pinMode(TFT_D1, OUTPUT); digitalWrite(TFT_D1, HIGH);
    pinMode(TFT_D2, OUTPUT); digitalWrite(TFT_D2, HIGH);
    pinMode(TFT_D3, OUTPUT); digitalWrite(TFT_D3, HIGH);
    pinMode(TFT_D4, OUTPUT); digitalWrite(TFT_D4, HIGH);
    pinMode(TFT_D5, OUTPUT); digitalWrite(TFT_D5, HIGH);
    pinMode(TFT_D6, OUTPUT); digitalWrite(TFT_D6, HIGH);
    pinMode(TFT_D7, OUTPUT); digitalWrite(TFT_D7, HIGH);
  #endif

  PARALLEL_INIT_TFT_DATA_BUS;

#endif
}

[MBlackmagic]

Hi @Basitadam,

would be nice if you can share it, thanks in advance.

[aramix]

@brightproject I have this display and the source code they have is a bit outdated, do you have a public repo that I can take a look to see how you got this working? That would be a good kickstart for me. Thanks in advance!

[brightproject]

I have this display and the source code they have is a bit outdated

Hello @aramix
This topic already describes many modifications of displays and many codes.
My display is in the JC3636W518 device, its connection interface is QSPI, it does not work with the TFT_eSPI library.
For its operation, I use the Arduino_GFX library and additional libraries from esp-idf:

#include <ESP_IOExpander.h>
#include <ESP_Panel_Library.h>

I also use platformio + vscode to build the code.
Could you indicate which display, which IDE you use and what code you want to use, otherwise I do not understand what you want to get?🙂

[aramix]

I have JC3636W518 too, I started with the example code that comes with it but I wans't able to get it build even though I followed the readme. I would like to run it in platformio too, the example code is an arduino ide code

[brightproject]

I would like to run it in platformio too

Tell me, have you worked with Platformio before?
If not, then you will first have to study Platformio and launch a simple project on a simpler device.
Perhaps you have a telegram or email, we can write there and I will tell you how and what to do.
If you have already worked with .pio, then simply download the archive from the link and add the project to .pio

#3477 (reply in thread)

[aramix]

I did, a lot. I have worked with touch screens too, but I am unfamiliar with the driver of this screen and there is not much documentation around this. Thanks for the link to thread post. This was a really long one and I didn't go through everything, sorry :)

[brightproject]

I decided to post my files, but they are not working yet, only the display backlight turns on and that's it🙂
Perhaps they will become a starting point for someone until @Basitadam posts his drivers in this discussion.
In addition to the files from the archive, I added several functions to the files:

https://github.com/Bodmer/TFT_eSPI/blob/master/TFT_eSPI.h

// Some ST7789 and ST77916 boards do not work with Mode 0
#ifndef TFT_SPI_MODE
  #if defined(ST7789_DRIVER) || defined(ST7789_2_DRIVER) || defined(ST77916_DRIVER)
    #define TFT_SPI_MODE SPI_MODE3
  #else
    #define TFT_SPI_MODE SPI_MODE0
  #endif
#endif

           // Functions for ST77916 round display
  // void     WRITE_BYTES(uint8_t numBytes, const uint8_t* data);
  void     WRITE_BYTES(uint8_t numBytes, std::initializer_list<uint8_t> data);
  void     WRITE_COMMAND(uint8_t cmd);
  void     WRITE_CMD_DATA8(uint8_t cmd, uint8_t data);
  void     WRITE_CMD_DATA16(uint8_t cmd, uint8_t data1, uint8_t data2);

and

https://github.com/Bodmer/TFT_eSPI/blob/master/TFT_eSPI.cpp

#elif defined (ST77916_DRIVER)
    #include "TFT_Drivers/ST77916_Init.h"

#elif defined (ST77916_DRIVER)
    #include "TFT_Drivers/ST77916_Rotation.h"

// Functions for ST77916 round display

// This function writes a specified number of bytes to the display.
// void TFT_eSPI::WRITE_BYTES(uint8_t numBytes, const uint8_t* data) {
//   for (uint8_t i = 0; i < numBytes; i++) {
//     writedata(data[i]);
//   }
// }

// This function writes a specified number of bytes from an initializer list to the display.
void TFT_eSPI::WRITE_BYTES(uint8_t numBytes, std::initializer_list<uint8_t> data) {
  uint8_t i = 0;
  for (auto byte : data) {
    if (i >= numBytes) break; // Check the number of bytes
    writedata(byte);
    i++;
  }
}

// This function writes a command to the display.
void TFT_eSPI::WRITE_COMMAND(uint8_t cmd) {
  writecommand(cmd);
}

// This function sends a command followed by two data bytes to the display.
void TFT_eSPI::WRITE_CMD_DATA16(uint8_t cmd, uint8_t data1, uint8_t data2) {
  // Send the command
  writecommand(cmd);
  // Send the first data byte
  writedata(data1);
  // Send the second data byte
  writedata(data2);
}

// This function sends a command followed by one data byte to the display.
void TFT_eSPI::WRITE_CMD_DATA8(uint8_t cmd, uint8_t data) {
  // Send the command
  writecommand(cmd);
  // Send the data byte
  writedata(data);
}

The archive contains files for the platformio and libraries TFT_eSPI.

tft_eSPI_st77916.zip

By the way, a remark, when I compile under

PLATFORM: Espressif 32 (6.8.1)

then after loading the firmware esp32-wroom reboots in panic.
With the framework version

PLATFORM: Espressif 32 (6.6.0)

There are no reboots and only the display backlight turns on, because I can't yet write code for normal display initialization.

Since the device JC3636W518 has an esp32s3 microcontroller, it is necessary to somehow initialize the QUAD SPI, as is done in third-party drivers.

  spi_bus_config_t buscfg = {
      .mosi_io_num = _mosi,
      .miso_io_num = _miso,
      .sclk_io_num = _sck,
      .quadwp_io_num = _quadwp,
      .quadhd_io_num = _quadhd,
      .data4_io_num = -1,
      .data5_io_num = -1,
      .data6_io_num = -1,
      .data7_io_num = -1,
      .max_transfer_sz = (ESP32QSPI_MAX_PIXELS_AT_ONCE * 16) + 8,
      .flags = SPICOMMON_BUSFLAG_MASTER | SPICOMMON_BUSFLAG_GPIO_PINS,
      .intr_flags = 0};

[Basitadam]

Hi, Made a working driver set for ST77916. I can share anyone interested BR, Tim

Hello everyone,

My solution is based on TFT_eSPI 2.5.43 and ESP32 3.0.4 board libraries. With Arduino IDE 2.3.2.
Bought this 1.8inch round display from Aliexpress ( https://tr.aliexpress.com/item/1005007316063855.html?spm=a2g0o.order_list.order_list_main.31.4a783d1277oQyW&gatewayAdapt=glo2tur) and run it SPI mode (no DMA at the moment).
There is another 1.8 inch round display module runs in QSPI mode, did not test the solution with it.

My MCU is ESP32-S3 on an ESP32-S3-Zero board.

Attached are the all TFT_eSPI files and an Arduino sample sketch.

• There are minor changes, simple define lines to TFT_eSPI.cpp and TFT_eSPI.h.
• Three ST77916 diver files to be copied to ..\Arduino\libraries\TFT_eSPI\TFT_Drivers
• Setup27tk_1_8Round_ST77916_ESP32.h file to be copied to ..\Arduino\libraries\TFT_eSPI\User_Setups
• An entry added to User_Setup_Select.h file for the Setup27tk_1_8Round_ST77916_ESP32.h file

I made some trials to run in DMA mode. There might be some extra lines commented in files.

Hope these help and make it their way into the new version of TFT_eSPI (with professionally edited versions of course)
ESP32_S3_Zero_ST77916_TFT_eSPI_TEST.zip
TFT_eSPI_for_ST77916.zip

BR,
Tim

[NehalAR]

Friends. I read everything here. But I've been trying to build my own version for a long time. And I can't do anything. I would be very happy if someone could give me instructions on exactly how to build a project. I tried with manufacturer settings but it doesn't work for me.

What mcu and dev env are you using (specifically like esp32 wroom32 etc) . Considering display is st77916.

[FullMetalRico]

@cmigun Sadly i can not tell you which board to get because i designed and manufactured a custom board for this display but i can tell you the steps i did to make it work (I used an ESP32-S3-N16R8):
I used a bare display with only the 15 Pin flex cable and touch. The touch controller is a CST820.
This list may not be complete, i created the project some while ago.

1. Create a platformio project and select a variant of the esp32-s3 as board and Arduino as framework
   a. The board should not matter that much as long as you pick the esp32-s3. I created my own board definition to get the 16 MB flash but i only use like 15% of it currently
2. Download the TFT_eSPI library (i use version 2.5.0) and put it into the lib folder of your platformio project
3. Download the ST77916 files mentioned in a post in this discussion here (*_Defines.h, *_Init.h, *_Rotation.h) and put them into the TFT-Drivers of the TFT_eSPI library)
4. Get the color fix code mentioned in this discussion here and patch the ST77916_Init.h file (not needed to make it work i think but fixes the color errors)
5. Create a Setup148_ESP32_ST77916_SPI.h and define the pins of your display.
   a. I have the SPI version of the display (SPI, not QSPI)
   b. Those are mine:

   #define TFT_CS    10    // Chip select control pin
   #define TFT_MOSI  11    // SPI data pin
   #define TFT_MISO  -1    // not used
   #define TFT_SCLK  13    // SPI clock pin
   #define TFT_DC    21    // Data Command control pin - Also called TFT_RS (Register Select) 
   #define TFT_RST    4    // Reset pin (could connect to RST pin)
   

6. Add the following below the last already defined TFT_Driver init:

#elif defined (ST77916_DRIVER)
     #include "TFT_Drivers/ST77916_Defines.h"
     #define  TFT_DRIVER 0x835D

8. Add your Setup148... file to the User_Setup_Select.h file and comment any other
9. Connect everything up and dont forget the backlight (needs a transistor circuit for control, examples are also somewhere in this discussion here)
10. Create a main.cpp, add the TFT_eSPI library and use one of the examples here to create a test program
11. For touch you need another library (i used bb_captouch)

Hope that helps

[cmigun]

Thank you very much, I appreciate your intention to help.
But I encountered basic difficulties. I have no ability to develop anything and I don't understand this world at all. I would be happy if there is someone willing to go into depth with me and build me something customized. Of course, with fair compensation

[FullMetalRico]

Creating something custom needs time and quite some knowledge of software- and electrical engineering so most of the time it is not worth it to do for a single item (for others). What exactly do you have in mind to build? Maybe i already created something similar which i can show/sell to you.

[uzi18]

@martinroger you got this library with this display support on my fork

[brightproject]

@Basitadam I'm having studied your display a little, I realized that your solution is not suitable for the JC3636W518 hardware.
The display has 15 contacts.

You are using a classic connection to the SPI bus, the so-called 3-SPI.
In the JC3636W518 hardware, the display has 20 contacts and is connected via QUAD SPI or 4-SPI.

https://www.jblopen.com/qspi-nor-flash-part-3-the-quad-spi-protocol/

Which changes things dramatically and is not yet supported by the library.
I hope @Bodmer will tell me if it is possible to implement QUAD SPI using TFT_eSPI.

[Basitadam]

@brightproject you are correct. My display has 15pins but QSPI one has 20. I have QSPI module also:

Hoped I could change the communication mode to simple SPI via

These type of pins have pull-up / pull-down resistor located on display flat cable. But not on this one.
When I realized I can't run it QSPI or simple SPI mode with TFT_eSPI, switched to 15 pinned model.

Here are my setup, MCU and sample visuals:

Tim

[Basitadam]

@TheKerbecs these are before and after photos:

Before:

After:

[TheKerbecs]

do you by any chance know how to use the touch screen version?

[Basitadam]

Not at the moment. I will need to use it soon. Will let you know

[SowaKillerr]

Hi. Cen you show how you set the simple SPI interface? Some photos maybe?

[Basitadam]

Hi,
This is the setup I use:

[julienGowind]

Hello,
Thanks you so much for all you're work.
That's work great (on IDE ARDUINO for me, can't use it with platformIo yet)

If i can a question, did you test it with all rotation ? (by your function setRotation). Maybe there is a little bug on it. For me Screen is not center on 2 kind of rotation (setRotation(2); and setRotation(1); i think). I make an example with a LVGL_METER, and it's not center on those rotation. And that make parasite en bottom or right on the screen.

Did you see that too ?

(sorry for my English)

Julien

[Basitadam]

Hi @julienGowind. Thank you,

I didn't check it really. I just checked that rotation works. Now I looked at the code, I realized I did not set TFT_HIGHT, TFT_WIDTH. They are in TFT processor init file, so should library should work but you can try these:

1- include height and width in user select file ( Setup27tk_1_8Round_ST77916_ESP32.h )
#define TFT_WIDTH 360
#define TFT_HEIGHT 360

2- include height and width in Arduino sketch
#define TFT_WIDTH 360
#define TFT_HEIGHT 360

3- in Adruino sketch
modify this line:
TFT_eSPI tft = TFT_eSPI();
as
TFT_eSPI tft = TFT_eSPI(360,360);

4- Or maybe it is the nature of some rotations: Some rotations are like flip or mirror in nature. Defining absolute coordinates like tft.setCursor(90,120) might be causing to see as if not centered. To test this put a circle or rectangle at the middle of the screen. Center point of circle/rectangle must be (180,180). Try doing rotations now. The circle/rectangle should not change position.

Let me know the results please.
I don't have a ready to use setup now to test.

BR,
Tim

• No idea about LVGL

[SowaKillerr]

Hi, great job! I’m really glad someone has tackled this topic. I bought the same 15-pin touchscreen display. However, before diving into the touch functionality, I first want to get it running in general.

I'm having an issue, though. Despite placing the files in the correct folders — TFT_Drivers, User_Setups, and modifying TFT_eSPI.cpp and TFT_eSPI.h — the display remains black. Here’s how I’ve connected it:

LCD PIN 1 <> GND ESP
LCD PIN 2 <> GND ESP
LCD PIN 3 <> 3.3V ESP
LCD PIN 4 <> 3.3V ESP
LCD PIN 5 <> 23 ESP
LCD PIN 6 <> 22 ESP
LCD PIN 7 <> 21 ESP
LCD PIN 8 <> 19 ESP
LCD PIN 9 <> NC
LCD PIN 10 <> NC
LCD PIN 11 <> GND ESP

And the definition in User_Setup.h:

#define TFT_MISO -1
#define TFT_MOSI 19
#define TFT_SCLK 21
#define TFT_CS 22
#define TFT_DC 23
#define TFT_RST -1

I’m also not sure how to set it up so the display operates in SPI mode. Is that the default operating mode? How should I configure the jumper settings? Thank you for your response, and great job! I’m also looking forward to the part where you explain the touch setup. Take care!

[uzi18]

@Basitadam @SowaKillerr @brightproject https://github.com/uzi18/TFT_eSPI/tree/ST77916

[uzi18]

@Basitadam could you please share link to your FFC adapter?
Thanks

[Basitadam]

@uzi18 I have three:

Vertical: https://www.digikey.com/en/products/detail/molex/5022311500/2818922?s=N4IgTCBcDaIKwAYxgMwEY2ISAugXyA
Right Angle, top contact: https://www.digikey.com/en/products/detail/amphenol-cs-fci/F32Q-1A7H1-11015/11564633
Right Angle, bottom contact: https://www.digikey.com/en/products/detail/cvilux-usa/CF5015FD0R0-05-NH/15793072

[SowaKillerr]

It works. On AliExpress, there was information stating that the FFC tape raster is 0.3 mm, but the correct raster is 0.5 mm

[Basitadam]

Thank you @SowaKillerr . Forgot to mention. On Aliexpress page says 0.3mm for the pitch but it is 0.5mm

[uzi18]

TouchPad :

https://github.com/bitbank2/bb_captouch

Not tested yet

[SowaKillerr]

Hi, I have a question because I want to generate a 360x360 sprite (to cover the entire screen). However, I know that the sprite size is limited by the ESP32's RAM capacity. (Now I use it esp32 DevKitC) Do you know how to solve this problem? Is it possible to expand the RAM or cache size? In my project assumptions, I wanted to manage 3 such displays independently at the same time. Processing power wouldn’t be an issue, but I can see that the cache memory already is.

[Bodmer]

Use an ESP32 board with PSRAM fitted.

[SowaKillerr]

It worked. However, there's an issue with the speed :/ I'm considering using a different processor, but which one would be faster and more powerful? Maybe some Raspberry Pi, but which model, and would I be able to easily handle such a display with it? How can I use this library on a Raspberry Pi, if it's even possible...

Do you have any ideas? I'm open to anything that could help solve this problem.

[ChrisZang0815]

question: has anyone got the integrated 1.85" ESP32-S3 device from Waveshare: https://www.waveshare.com/wiki/ESP32-S3-LCD-1.85 to work with TFT_eSPI?

[uzi18]

@ChrisZang0815 I think QSPI is not supported here

[brightproject]

Good day @Basitadam and @uzi18 🙂
I would like to suggest that we think together how to launch this library via the Quad SPI bus and worked with the LVGL plugin, which uses

#include <ESP_IOExpander.h>
#include <ESP_Panel_Library.h>

To easily connect to the display inside the JC3636W518 device.

It seemed to me that this is not such a difficult task, the main thing is to understand it correctly.
The task is to run the display via the QSPI bus on the library TFT_eSPI.
Let's take the simplest example

#include "SPI.h"
#include "TFT_eSPI.h"

TFT_eSPI myGLCD = TFT_eSPI();

unsigned long runTime = 0;
void setup()
{
// Backlight ON
pinMode(TFT_BLK, OUTPUT);
digitalWrite(TFT_BLK, HIGH);

// Display INIT
myGLCD.init();
myGLCD.setRotation(1);

// Filled screen
myGLCD.fillScreen(TFT_RED);
}

void loop()
{
// empty now
}

The initial entry point is the file

#include "TFT_eSPI.h"

Which includes the file

TFT_eSPI.cpp

Which is where the main magic happens.

Declaring the library in the code

TFT_eSPI myGLCD = TFT_eSPI();

We include the settings files

#include <User_Setup_Select.h>

Which have the display driver we need added

#include <User_Setups/Setup916_ST77916.h>

Inside which the required driver is specified

#define ST77916_DRIVER

And the necessary pins.
In the files
TFT_eSPI.h and TFT_eSPI.cpp
The necessary defines have been added for the ST77916 display initialization files.
Further in the SETUP section the display initialization BEGIN
Here I have added to the standard call

init(tc);

initialization of the display and the QSPI bus.

void TFT_eSPI::begin(uint8_t tc)
{
init(tc);

 static ESP_PanelLcd *myGLCD = NULL;

 ESP_PanelBus_QSPI *panel_bus = new ESP_PanelBus_QSPI(TFT_CS, TFT_SCK, TFT_SDA0, TFT_SDA1, TFT_SDA2, TFT_SDA3);
 // panel_bus->configQspiFreqHz(TFT_SPI_FREQ_HZ);
 panel_bus->configQspiFreqHz(50 * 1000 * 1000);
 panel_bus->begin();

 myGLCD = new ESP_PanelLcd_ST77916(panel_bus, 16, TFT_RST);
 myGLCD->init();
 myGLCD->reset();
 myGLCD->begin();

 myGLCD->invertColor(true);

 myGLCD->displayOn();

}

After several attempts and code editing, it was successfully assembled.
The display lights up, and error data is sent to the serial port

Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0xb (SPI_FAST_FLASH_BOOT)
Saved PC:0x40379992
#0 0x40379992 in esp_cpu_wait_for_intr at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_hw_support/cpu.c:121

SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3818,len:0x109c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xb50
load:0x403cc700,len:0x2fe4
entry 0x403c98ac
[ 126][E][esp32-hal-periman.c:180] perimanGetPinBus(): Invalid pin: 23
[ 133][E][esp32-hal-periman.c:180] perimanGetPinBus(): Invalid pin: 23
[ 139][E][esp32-hal-periman.c:122] perimanSetPinBus(): Invalid pin: 23
[ 146][E][esp32-hal-gpio.c:120] __pinMode(): Deinit of previous bus from IO 23 failed
[ 153][E][esp32-hal-periman.c:122] perimanSetPinBus(): Invalid pin: 23
[ 160][E][esp32-hal-periman.c:122] perimanSetPinBus(): Invalid pin: 23
[ 166][E][esp32-hal-spi.c:270] spiAttachMISO(): Failed to set pin bus to SPI for pin 23
[ 174][E][SPI.cpp:116] begin(): Attaching pins to SPI failed.
Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception was unhandled.

Core 1 register dump:
PC : 0x42002d3f PS : 0x00060230 A0 : 0x82002db8 A1 : 0x3fcebf50
A2 : 0x00000010 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
A6 : 0x000000ff A7 : 0x00000010 A8 : 0x08000000 A9 : 0x00000400
A10 : 0x3fc98534 A11 : 0x00000001 A12 : 0x01312d00 A13 : 0xffffffff
A14 : 0x00000031 A15 : 0x00000000 SAR : 0x0000000f EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000010 LBEG : 0x4201c9b0 LEND : 0x4201c9f7 LCOUNT : 0x00000002

Backtrace: 0x42002d3c:0x3fcebf50 0x42002db5:0x3fcebf80 0x42002040:0x3fcebfa0 0x420047ea:0x3fcebfc0 0x4037edf2:0x3fcebfe0
#0 0x42002d3c in TFT_eSPI::begin_tft_write() at lib/TFT_eSPI/TFT_eSPI.cpp:81
(inlined by) TFT_eSPI::spiwrite(unsigned char) at lib/TFT_eSPI/TFT_eSPI.cpp:992
#1 0x42002db5 in TFT_eSPI::init(unsigned char) at lib/TFT_eSPI/TFT_eSPI.cpp:709
#2 0x42002040 in setup() at src/tft_e_spi_test.cpp:18
#3 0x420047ea in loopTask(void*) at C:/Users/brigh/.platformio/packages/framework-arduinoespressif32@src-98cb8087edcca5875bec152528484d34/cores/esp32/main.cpp:59
#4 0x4037edf2 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162

but the display is not yet filled with red.
I understand that I am on the right track and need to somehow insert the QUAD SPI bus bus into TFT_eSPI, but I don't yet understand how to do it.

If we think about this together, then perhaps display output will be implemented.

I downloaded the project archive for .pio, because of the file size limitation

att_round_display.zip

I deleted the LVGL folder from the lib folder, you just need to download it

"version": "8.3.11"

Link to the archive

https://github.com/lvgl/lvgl/archive/refs/tags/v8.3.11.zip

[Basitadam]

This task needs undivided attention. I can't right now. I am deep in a new project. And would be best if @Bodmer is joining in. I see more and more quad spi TFT controllers. TFT_eSPI library should include this bus, too. Another reason to an update to 2.5.43

[brightproject]

I am deep in a new project.

It's great that you're upgrading your skills on a new project🙂

would be best if @Bodmer is joining in

Perhaps it is more difficult to support this project alone with each new version, or there are other reasons.
However, I think a community like us can also provide some help in the development of the project.
For example, the Arduino_GFX library uses a similar architecture of drawing functions to TFT_eSPI, although Arduino_GFX does not clearly use the double buffer drawing technology or Sprite.
There are two files for this in the TFT_eSPI library:

https://github.com/Bodmer/TFT_eSPI/blob/master/Extensions/Sprite.h
https://github.com/Bodmer/TFT_eSPI/blob/master/Extensions/Sprite.cpp

The first thought was to call the functionality like this:

Arduino_DataBus *bus = new Arduino_ESP32QSPI(
10 /* CS */, 9 /* SCK */, 11 /* D0 - mosi */, 12 /* D1 - miso */, 13 /* D2 - quadwp */, 14 /* D3 - quadhd */);
Arduino_GFX *gfx = new Arduino_ST77916(bus, 47 /* RST */, 0 /* rotation */, true /* IPS */, 360 /* width */, 360 /* height */);
TFT_eSprite sprite = TFT_eSprite(&gfx);

To draw primitives in sprites later.

sprite .fillCircle (px0, py0, 2 * SCREEN_Y/80, TFT_YELLOW);
sprite .drawCircle (px0, py0, 2 * SCREEN_Y/80, TFT_BLACK);

But I haven't tested this in practice yet.

[brightproject]

I think this is right way - union tft_espi and esp-idf originally code💻

https://github.com/esp-arduino-libs/ESP32_Display_Panel

example

https://github.com/esp-arduino-libs/ESP32_Display_Panel/blob/master/examples/LCD/QSPI/QSPI.ino

[uzi18]

@brightproject indeed, so ESP_PanelBus support should be added to TFT_eSPI

[ChrisZang0815]

Unfortunately this is way beyond my skill set, but it would great if someone smarter than me would figure it out.
I would love to use that display.

[uzi18]

@ChrisZang0815 you see error - Invalid pin 23

[uzi18]

@brightproject On 15 pin flex it is 3wire interface and it shouldn't pass. So everytime you update screen all data are sent to driver memory. So framerate is affected.

[brightproject]

On 15 pin flex it is 3wire interface

I don't have a SPI 3 wire display, I only have a QSPI.

[Basitadam]

@brightproject @Basitadam Hi guys please give us feedback with read test PASS or FAIL for You? https://github.com/Bodmer/TFT_eSPI/blob/master/examples/Test%20and%20diagnostics/TFT_ReadWrite_Test/TFT_ReadWrite_Test.ino

Pixel value read = 0
ERROR ^^^^

For all instances.
And display turns to purple

[uzi18]

@Basitadam thx, what's your framerate for this LCD? Is it possible for you to meassure millis of whole screen update?

[Basitadam]

TFT_eSPI library test!
360 x 360 pixels
Benchmark                Time (microseconds)
Screen fill              140967
Text                     13728
Lines                    132673
Horiz/Vert Lines         13536
Rectangles (outline)     11308
Rectangles (filled)      573886
Circles (filled)         66227
Circles (outline)        50169
Triangles (outline)      41493
Triangles (filled)       214452
Rounded rects (outline)  31890
Rounded rects (filled)   589574
Done!

@80MHz SPI clock

[NehalAR]

@Basitadam I used your code for st77916 display and it works.
The only problem I have is that the display is inverted.

I use it with lvgl tft in arduino IDE:

lv_display_t *lv_tft_espi_create(uint32_t hor_res, uint32_t ver_res, void *buf0, void *buf1, uint32_t buf_size_bytes, lv_display_render_mode_t mode)
{
    lv_tft_espi_t * dsc = (lv_tft_espi_t *)lv_malloc_zeroed(sizeof(lv_tft_espi_t));
    LV_ASSERT_MALLOC(dsc);
    if(dsc == NULL) return NULL;

    lv_display_t * disp = lv_display_create(hor_res, ver_res);
    if(disp == NULL) {
        lv_free(dsc);
        return NULL;
    }

    dsc->tft = new TFT_eSPI(hor_res, ver_res);
    dsc->tft->begin();          /* TFT init */
    dsc->tft->setRotation(0);
    lv_display_set_driver_data(disp, (void *)dsc);
    lv_display_set_flush_cb(disp, flush_cb);
    lv_display_add_event_cb(disp, resolution_changed_event_cb, LV_EVENT_RESOLUTION_CHANGED, NULL);
    lv_display_set_buffers(disp, (void *)buf0, (void *)buf0, buf_size_bytes, mode);
    return disp;
}

the setRotation doesn't work for me I use 2,3,5,7 for flipping or mirroring with respect to x-axis. I then tried changing the flush_cb it corrected it but when I use the indev as input driver for lvgl with keypad it read original direction.

So, the question is there a command in init file that I can use to flip it during initialization.

[Basitadam]

More fancy. Easier to design user interface especially if you use Squareline Studio

[uzi18]

@Basitadam so need to give it a try.

[NehalAR]

@Basitadam Your link goes to page not found

[Basitadam]

https://www.filemail.com/d/jnedixaxczalfwk
This should work

[NehalAR]

@uzi18 I tested your repo code too, and both of your and Basitadam's previous code works. The problem was with TFT display rotation.
I disabled it and set the set rotation to 5 dsc->tft->setRotation(5); and it worked perfectly. Thank you!

[FullMetalRico]

I just tested the code from @Basitadam with the color fix in the "ST77916_Init.h" file and added the touch lib mentioned from @uzi18 in a PlatformIO project and everything is working fine together. Rotations are also working, the non mirrored ones are 4-7 btw.

Big thank you for the hard work so far.

[Uspizig]

Could you please be so kind and put it all together into one Zip and Upload somwhere?
Your help is highly appreciated.

[uzi18]

@Uspizig just go to my fork and download zip

[HmblEngineer]

Has anyone tried 8bit parallel with this display, should the drivers be the same?

[HmblEngineer]

Yes, I know, doesn't it need drivers as well?

[brightproject]

Yes, I know, doesn't it need drivers as well?

I recommend you migrate the project to this library

https://github.com/lovyan03/LovyanGFX

Unfortunately, everyone's favorite TFT_eSPI is fading into history, dear Bodmer cannot support a greatly increased code base on its own, especially with the release of so many new displays and interfaces.
The specified LovyanGFX library almost completely mimics the functions of the TFT_eSPI library and thus minimizes migration.
Using LovyanGFX, you can quite easily connect the ST77916 display even via an 8-bit parallel interface.
You just need to add data on your ST77916 display driver.
The file will look like this.

https://github.com/lovyan03/LovyanGFX/blob/master/src/lgfx/v1/panel/Panel_ST7796.hpp

If you do not have enough programming skills, then it will be quite difficult for you to do this.
I can probably help you in this case, but it won’t be very fast, due to my lack of free time.

[HmblEngineer]

This data I can find in the display's pdf I suppose, right?

Thank you for your time

[brightproject]

This data I can find in the display's pdf I suppose, right?

You can also take it from the display manufacturer's documentation, but it seems easier to me to take it from this file

https://github.com/moononournation/Arduino_GFX/blob/master/src/display/Arduino_ST77916.h

or from this

https://github.com/moononournation/Arduino_GFX/blob/master/src/display/Arduino_GC9106.h

And move it to this file, changing its name

https://github.com/lovyan03/LovyanGFX/blob/master/src/lgfx/v1/panel/Panel_ST7796.hpp

I repeat that you must have some knowledge of the display operation processes, what code is in the specified files and what function it carries.
Do you have such knowledge?🙂

I don't have a 77916 display with an 8-bit parallel bus and I can't check the code even if I help you with the files.
This complicates the work if you don't understand the processes.
As you were told above, the 77916 display mainly uses QSPI and I recommended using more well-known connection schemes until you gain experience in this.
You should also try connecting any other display bySPI or another bus to the LovyanGFX library and work with the code so that you understand the processes.
This is quite an exciting activity🙂

[HmblEngineer]

Yeah, I don't have much experience with those, but I'm learning 😁

I do have a working prototype with an SPI display but it goes to 16fps, which is impressive, but not quite good for what I'm trying to accomplish.

[ChrisZang0815]

I’m well versed in TFT_eSPI, but I guess I now have to learn LovyanGFX. Sounds like a fun challenge! Unfortunately, I don’t speak Japanese ☹ Is there anywhere a “getting started” primer? Especially I would like to figure out what I have to do to support a certain display, example – let’s start with something simple - GC9A01 The example below from Vladislav seems to be for the Arduino_GFX library, but not for the LovyanGFX library? Thanks Christopher From: Vladislav ***@***.***> Sent: Sunday, July 6, 2025 11:35 PM To: Bodmer/TFT_eSPI ***@***.***> Cc: ChrisZang0815 ***@***.***>; Mention ***@***.***> Subject: Re: [Bodmer/TFT_eSPI] ST77916 (Discussion #3477) This data I can find in the display's pdf I suppose, right? You can also take it from the display manufacturer's documentation, but it seems easier to me to take it from this file https://github.com/moononournation/Arduino_GFX/blob/master/src/display/Arduino_ST77916.h And move it to this file, changing its name https://github.com/lovyan03/LovyanGFX/blob/master/src/lgfx/v1/panel/Panel_ST7796.hpp or this https://github.com/moononournation/Arduino_GFX/blob/eb305947cbe4026efe73245fc9598bd3457efdbc/src/display/Arduino_GC9106.h I repeat that you must have some knowledge of the display operation processes, what code is in the specified files and what function it carries. Do you have such knowledge?🙂 I don't have a 77916 display with an 8-bit parallel bus and I can't check the code even if I help you with the files. This complicates the work if you don't understand the processes. As you were told above, the 77916 display mainly uses QSPI and I recommended using more well-known connection schemes until you gain experience in this. You should also try connecting any other display bySPI or another bus to the LovyanGFX library and work with the code so that you understand the processes. This is quite an exciting activity🙂 — Reply to this email directly, view it on GitHub <#3477 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4F7SMIR52D7GKJUYABG4KT3HIIHNAVCNFSM6AAAAABN4C2PX2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRXHE4DMNI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A4F7SMLFF5N6IZNE5NC2ZJL3HIIHNA5CNFSM6AAAAABN4C2PX2WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA2C6PS.gif> Message ID: ***@***.*** ***@***.***> >

[brightproject]

I’m well versed in TFT_eSPI, but I guess I now have to learn LovyanGFX.

Hello @ChrisZang0815 🙂

The file serves as an example of display initialization, where the settings for the display are specified:

#define GC9106_NOP 0x00
#define GC9106_SWRESET 0x01
#define GC9106_RDDID 0x04
#define GC9106_RDDST 0x09

Many libraries work with ST77916 displays, so you need to take any file with initialization and rewrite it for LovyanGFX.
At the moment, I am rewriting the LovyanGFX library files for the ST77916 display for the QSPI bus.

I look at the code in a separate branch of QSPI

https://github.com/lovyan03/LovyanGFX/tree/QSPI

To work with the LovyanGFX library, you don't need to know Japanese, there are only Japanese comments, the code is written in C/C++.
Just take examples and study and flash your device by analogy with TFT_eSPI.

[brightproject]

Hello @Basitadam, @HmblEngineer, @ChrisZang0815🙂

I managed to set up QSPI on ST77196 for the library LovyanGFX

lovyan03/LovyanGFX#547 (comment)

[HmblEngineer]

You are awesome, thank you very much, I ordered a QSPI display, I'll let you know when it gets here. Is this FPS reading on full screen refresh?

[brightproject]

Is this FPS reading on full screen refresh?

The device on the left is running on LVGL, when the display is not animated the FPS is quite high, when movement starts it can drop to 10 FPS.
I use freeRTOS.

[Basitadam]

Hello @Basitadam, @HmblEngineer, @ChrisZang0815🙂

I managed to set up QSPI on ST77196 for the library LovyanGFX

lovyan03/LovyanGFX#547 (comment)

Awsome job. Not an easy task

[ChrisZang0815]

Fantastic! Thank you so much!!! Cheers Christopher From: Vladislav ***@***.***> Sent: Wednesday, July 9, 2025 7:38 AM To: Bodmer/TFT_eSPI ***@***.***> Cc: ChrisZang0815 ***@***.***>; Mention ***@***.***> Subject: Re: [Bodmer/TFT_eSPI] ST77916 (Discussion #3477) Hello @Basitadam <https://github.com/Basitadam> , @HmblEngineer <https://github.com/HmblEngineer> , @ChrisZang0815 <https://github.com/ChrisZang0815> 🙂 I managed to set up QSPI on ST77196 for the library LovyanGFX 5435893472801453137.jpg (view on web) <https://github.com/user-attachments/assets/5c47da13-1860-43b7-8548-38aca16db45a> lovyan03/LovyanGFX#547 (comment) <lovyan03/LovyanGFX#547 (comment)> — Reply to this email directly, view it on GitHub <#3477 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4F7SMKRDFZT7JZU6ACKHJT3HUSKXAVCNFSM6AAAAABN4C2PX2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZRGAYDQNY> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A4F7SMJURDZ5ADUPJSBQL4L3HUSKXA5CNFSM6AAAAABN4C2PX2WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA2EZQO.gif> Message ID: ***@***.*** ***@***.***> >

[BojoteX]

Hi, whats the latest set of patches for the TFT_eSPI library? I downloaded the zip by the OP, have the correct pins, even used the diagram by the OP, used 100Ω res on GND, connected LEDA to 3V (5V should also work as its 3 LEDs in series) have the correct verified GPIO to LCD pins, every single one, one by one, using ESP32-S3 Hardware SPI pins as per datasheet. LCD connected using FPC 15 Pin 0.5 PCB converter board (so, almost impossible to make a mistake with wrong pins) all tested with multimeter and I get a blank screen on both my LCDs. Seems the backlight is permanently ON, I can't turn it ON or OFF no matter if I connect directly to a pin. 100Ω Resistor is between LEDK and GND. So, I know I have everything setup correctly. Double checked my TFT_eSPI config file, USE_HSPI_PORT is also correctly defined. I have used this library with other displays with no issues, but going crazy with this ST77916 so either I have two bad units (very unlikely) or the zip file from the OP is not the most current patch to the library. Also have the "Exact" unit (no touch) from Aliexpress:
https://www.aliexpress.us/item/3256807129749103.html?spm=a2g0o.order_list.order_list_main.5.38c718022U11iW&gatewayAdapt=glo2usa#nav-specification

[brightproject]

Hi, whats the latest set of patches for the TFT_eSPI library?

The library TFT_eSPI has not been updated for a long time, st77916 is a new display driver and its full support and operation in this library is not guaranteed.
Use an analogue

https://github.com/lovyan03/LovyanGFX

In the future, write text divided into paragraphs, preferably attach a picture of the display pinout and the bus used.
What is OP?
According to your link, you have a display with a 4-wire SPI bus.
You can attach a photo of the display and cable, perhaps you have a mode resistor there, which may need to be re-soldered to activate the SPI mode.

[BojoteX]

Hi, whats the latest set of patches for the TFT_eSPI library?

The library TFT_eSPI has not been updated for a long time, st77916 is a new display driver and its full support and operation in this library is not guaranteed.

Use an analogue

https://github.com/lovyan03/LovyanGFX

In the future, write text divided into paragraphs, preferably attach a picture of the display pinout and the bus used.

What is OP?

According to your link, you have a display with a 4-wire SPI bus.

You can attach a photo of the display and cable, perhaps you have a mode resistor there, which may need to be re-soldered to activate the SPI mode.

Thanks! OP is Original Poster. So, lets assume I have my wiring correct, you say that even with the patches the original poster uploaded here, this will not work? LovyanGFX has the correct init sequence for the display? I have not tried that library yet, will try again tonight. Question, are you open to be compensated for dedicated help/support? I'm very familiar with MCUs and C+ programing, including LCDs, 7seg etc much more complex than this, but I'm going crazy trying to make this work. I'm suspecting something is fundamentally wrong with my approach

[Basitadam]

Hi @BojoteX ,

Can you send contents of your "User_Setup_Select.h" file? Which setup is uncommented in? Can you send contents of that file too?
Tim

[BojoteX]

Hi @BojoteX ,

Can you send contents of your "User_Setup_Select.h" file? Which setup is uncommented in? Can you send contents of that file too? Tim

Absolutely, thanks for helping! in User_Setup_Select.h all are commented except:

#include <User_Setup_New.h>

Which has the following contents:

#define USER_SETUP_ID 27

// Only define one driver
#define ST77916_DRIVER

// ----------------- Display Size -------------------
#define TFT_WIDTH 360
#define TFT_HEIGHT 360

#define TFT_MOSI 11 // SDA (Yellow)
#define TFT_SCLK 12 // SCL (Orange)
#define TFT_CS 10 // Chip Select (Blue)
#define TFT_DC 13 // Data/Command (Green)
#define TFT_RST 14 // Reset (White)

// Common Pins / misc
#define TFT_MISO -1
#define TOUCH_CS -1 // Chip select pin (T_CS) of touch screen

#define TFT_BL -1 // If you want to use backlight, set correct pin, else -1
#define TFT_BLK -1
// #define TFT_BL 15 // If you want to use backlight, set correct pin, else -1
// #define TFT_BLK 15

#define LOAD_GLCD // Font 1. Original Adafruit 8 pixel font needs ~1820 bytes in FLASH
#define LOAD_FONT2 // Font 2. Small 16 pixel high font, needs ~3534 bytes in FLASH, 96 characters
#define LOAD_FONT4 // Font 4. Medium 26 pixel high font, needs ~5848 bytes in FLASH, 96 characters
#define LOAD_FONT6 // Font 6. Large 48 pixel font, needs ~2666 bytes in FLASH, only characters 1234567890:-.apm
#define LOAD_FONT7 // Font 7. 7 segment 48 pixel font, needs ~2438 bytes in FLASH, only characters 1234567890:.
#define LOAD_FONT8 // Font 8. Large 75 pixel font needs ~3256 bytes in FLASH, only characters 1234567890:-.
#define LOAD_GFXFF // FreeFonts. Include access to the 48 Adafruit_GFX free fonts FF1 to FF48 and custom fonts
#define SMOOTH_FONT

#define SPI_FREQUENCY 50000000
#define USE_HSPI_PORT
// #define SPI_TOUCH_FREQUENCY 2500000
#define SPI_READ_FREQUENCY 16000000 // 6 MHz is the maximum SPI read speed for the ST7789V

[BojoteX]

Here's the full User_Setup_Select.h too:

// This header file contains a list of user setup files and defines which one the
// compiler uses when the IDE performs a Verify/Compile or Upload.
//
// Users can create configurations for different boards and TFT displays.
// This makes selecting between hardware setups easy by "uncommenting" one line.

// The advantage of this hardware configuration method is that the examples provided
// with the library should work with immediately without any other changes being
// needed. It also improves the portability of users sketches to other hardware
// configurations and compatible libraries.
//
// Create a shortcut to this file on your desktop to permit quick access for editing.
// Re-compile and upload after making and saving any changes to this file.

// Example User_Setup files are stored in the "User_Setups" folder. These can be used
// unmodified or adapted for a particular hardware configuration.

#ifndef USER_SETUP_LOADED // Lets PlatformIO users define settings in
// platformio.ini, see notes in "Tools" folder.

///////////////////////////////////////////////////////
// User configuration selection lines are below //
///////////////////////////////////////////////////////

// Only ONE line below should be uncommented to define your setup. Add extra lines and files as needed.

// #include <User_Setup.h>
#include <User_Setup_New.h>

//#include <User_Setups/Setup1_ILI9341.h> // Setup file for ESP8266 configured for my ILI9341
//#include <User_Setups/Setup2_ST7735.h> // Setup file for ESP8266 configured for my ST7735
//#include <User_Setups/Setup3_ILI9163.h> // Setup file for ESP8266 configured for my ILI9163
//#include <User_Setups/Setup4_S6D02A1.h> // Setup file for ESP8266 configured for my S6D02A1
//#include <User_Setups/Setup5_RPi_ILI9486.h> // Setup file for ESP8266 configured for my stock RPi TFT
//#include <User_Setups/Setup6_RPi_Wr_ILI9486.h> // Setup file for ESP8266 configured for my modified RPi TFT
//#include <User_Setups/Setup7_ST7735_128x128.h> // Setup file for ESP8266 configured for my ST7735 128x128 display
//#include <User_Setups/Setup8_ILI9163_128x128.h> // Setup file for ESP8266 configured for my ILI9163 128x128 display
//#include <User_Setups/Setup9_ST7735_Overlap.h> // Setup file for ESP8266 configured for my ST7735
//#include <User_Setups/Setup10_RPi_touch_ILI9486.h> // Setup file for ESP8266 configured for ESP8266 and RPi TFT with touch

//#include <User_Setups/Setup11_RPi_touch_ILI9486.h> // Setup file configured for ESP32 and RPi TFT with touch
//#include <User_Setups/Setup12_M5Stack_Basic_Core.h>// Setup file for the ESP32 based M5Stack (Basic Core only)
//#include <User_Setups/Setup13_ILI9481_Parallel.h> // Setup file for the ESP32 with parallel bus TFT
//#include <User_Setups/Setup14_ILI9341_Parallel.h> // Setup file for the ESP32 with parallel bus TFT
//#include <User_Setups/Setup15_HX8357D.h> // Setup file for ESP8266 configured for HX8357D
//#include <User_Setups/Setup16_ILI9488_Parallel.h> // Setup file for the ESP32 with parallel bus TFT
//#include <User_Setups/Setup17_ePaper.h> // Setup file for ESP8266 and any Waveshare ePaper display
//#include <User_Setups/Setup18_ST7789.h> // Setup file for ESP8266 configured for ST7789

//#include <User_Setups/Setup19_RM68140_Parallel.h> // Setup file configured for RM68140 with parallel bus

//#include <User_Setups/Setup20_ILI9488.h> // Setup file for ESP8266 and ILI9488 SPI bus TFT
//#include <User_Setups/Setup21_ILI9488.h> // Setup file for ESP32 and ILI9488 SPI bus TFT

//#include <User_Setups/Setup22_TTGO_T4.h> // Setup file for ESP32 and TTGO T4 version 1.2
//#include <User_Setups/Setup22_TTGO_T4_v1.3.h> // Setup file for ESP32 and TTGO T4 version 1.3
//#include <User_Setups/Setup23_TTGO_TM.h> // Setup file for ESP32 and TTGO TM ST7789 SPI bus TFT
//#include <User_Setups/Setup24_ST7789.h> // Setup file for DSTIKE/ESP32/ESP8266 configured for ST7789 240 x 240
//#include <User_Setups/Setup25_TTGO_T_Display.h> // Setup file for ESP32 and TTGO T-Display ST7789V SPI bus TFT
//#include <User_Setups/Setup26_TTGO_T_Wristband.h> // Setup file for ESP32 and TTGO T-Wristband ST7735 SPI bus TFT

//#include <User_Setups/Setup27_RPi_ST7796_ESP32.h> // ESP32 RPi MHS-4.0 inch Display-B
//#include <User_Setups/Setup28_RPi_ST7796_ESP8266.h> // ESP8266 RPi MHS-4.0 inch Display-B

//#include <User_Setups/Setup29_ILI9341_STM32.h> // Setup for Nucleo board
//#include <User_Setups/Setup30_ILI9341_Parallel_STM32.h> // Setup for Nucleo board and parallel display
//#include <User_Setups/Setup31_ST7796_Parallel_STM32.h> // Setup for Nucleo board and parallel display
//#include <User_Setups/Setup32_ILI9341_STM32F103.h> // Setup for "Blue/Black Pill"

//#include <User_Setups/Setup33_RPi_ILI9486_STM32.h> // Setup for Nucleo board

//#include <User_Setups/Setup34_ILI9481_Parallel_STM32.h> // Setup for Nucleo board and parallel display
//#include <User_Setups/Setup35_ILI9341_STM32_Port_Bus.h> // Setup for STM32 port A parallel display

//#include <User_Setups/Setup36_RPi_touch_ST7796.h> // Setup file configured for ESP32 and RPi ST7796 TFT with touch

//#include <User_Setups/Setup42_ILI9341_ESP32.h> // Setup file for ESP32 and SPI ILI9341 240x320
//#include <User_Setups/Setup43_ST7735.h> // Setup file for ESP8266 & ESP32 configured for my ST7735S 80x160
//#include <User_Setups/Setup44_TTGO_CameraPlus.h> // Setup file for ESP32 and TTGO T-CameraPlus ST7789 SPI bus TFT 240x240
//#include <User_Setups/Setup45_TTGO_T_Watch.h> // Setup file for ESP32 and TTGO T-Watch ST7789 SPI bus TFT 240x240
//#include <User_Setups/Setup46_GC9A01_ESP32.h> // Setup file for ESP32 and GC9A01 SPI bus TFT 240x240

//#include <User_Setups/Setup47_ST7735.h> // Setup file for ESP32 configured for ST7735 128 x 128 animated eyes

//#include <User_Setups/Setup50_SSD1963_Parallel.h> // Setup file for ESP32 and SSD1963 TFT display

//#include <User_Setups/Setup51_LilyPi_ILI9481.h> // Setup file for LilyGo LilyPi with ILI9481 display
//#include <User_Setups/Setup52_LilyPi_ST7796.h> // Setup file for LilyGo LilyPi with ST7796 display

//#include <User_Setups/Setup60_RP2040_ILI9341.h> // Setup file for RP2040 with SPI ILI9341
//#include <User_Setups/Setup61_RP2040_ILI9341_PIO_SPI.h> // Setup file for RP2040 with PIO SPI ILI9341
//#include <User_Setups/Setup62_RP2040_Nano_Connect_ILI9341.h> // Setup file for RP2040 with SPI ILI9341

//#include <User_Setups/Setup66_Seeed_XIAO_Round.h> // Setup file for Seeed XIAO with GC9A01 240x240

//#include <User_Setups/Setup70_ESP32_S2_ILI9341.h> // Setup file for ESP32 S2 with SPI ILI9341
//#include <User_Setups/Setup70b_ESP32_S3_ILI9341.h> // Setup file for ESP32 S3 with SPI ILI9341
//#include <User_Setups/Setup70c_ESP32_C3_ILI9341.h> // Setup file for ESP32 C3 with SPI ILI9341
//#include <User_Setups/Setup70d_ILI9488_S3_Parallel.h> // Setup file for ESP32 S3 with SPI ILI9488

//#include <User_Setups/Setup71_ESP32_S2_ST7789.h> // Setup file for ESP32 S2 with ST7789
//#include <User_Setups/Setup72_ESP32_ST7789_172x320.h> // Setup file for ESP32 with ST7789 1.47" 172x320

//#include <User_Setups/Setup100_RP2040_ILI9488_parallel.h> // Setup file for Pico/RP2040 with 8-bit parallel ILI9488
//#include <User_Setups/Setup101_RP2040_ILI9481_parallel.h> // Setup file for Pico/RP2040 with 8-bit parallel ILI9481
//#include <User_Setups/Setup102_RP2040_ILI9341_parallel.h> // Setup file for Pico/RP2040 with 8-bit parallel ILI9341
//#include <User_Setups/Setup103_RP2040_ILI9486_parallel.h> // Setup file for Pico/RP2040 with 8-bit parallel ILI9486
//#include <User_Setups/Setup104_RP2040_ST7796_parallel.h> // Setup file for Pico/RP2040 with 8-bit parallel ST7796

//#include <User_Setups/Setup105_RP2040_ST7796_16bit_parallel.h> // Setup file for RP2040 16-bit parallel display
//#include <User_Setups/Setup106_RP2040_ILI9481_16bit_parallel.h> // Setup file for RP2040 16-bit parallel display
//#include <User_Setups/Setup107_RP2040_ILI9341_16bit_parallel.h> // Setup file for RP2040 16-bit parallel display
//#include <User_Setups/Setup108_RP2040_ST7735.h> // Setup file for Waveshare RP2040 board with onboard ST7735 0.96" 160x80 display

//#include <User_Setups/Setup135_ST7789.h> // Setup file for ESP8266 and ST7789 135 x 240 TFT

//#include <User_Setups/Setup136_LilyGo_TTV.h> // Setup file for ESP32 and Lilygo TTV ST7789 SPI bus TFT 135x240
//#include <User_Setups/Setup137_LilyGo_TDisplay_RP2040.h> // Setup file for Lilygo T-Display RP2040 (ST7789 on SPI bus with 135x240 TFT)

//#include <User_Setups/Setup138_Pico_Explorer_Base_RP2040_ST7789.h> // Setup file for Pico Explorer Base by Pimoroni for RP2040 (ST7789 on SPI bus with 240x240 TFT)

//#include <User_Setups/Setup200_GC9A01.h> // Setup file for ESP32 and GC9A01 240 x 240 TFT

//#include <User_Setups/Setup201_WT32_SC01.h> // Setup file for ESP32 based WT32_SC01 from Seeed

//#include <User_Setups/Setup202_SSD1351_128.h> // Setup file for ESP32/ESP8266 based SSD1351 128x128 1.5inch OLED display

//#include <User_Setups/Setup203_ST7789.h> // Setup file for ESP32/ESP8266 based ST7789 240X280 1.69inch TFT

//#include <User_Setups/Setup204_ESP32_TouchDown.h> // Setup file for the ESP32 TouchDown based on ILI9488 480 x 320 TFT

//#include <User_Setups/Setup205_ESP32_TouchDown_S3.h> // Setup file for the ESP32 TouchDown S3 based on ILI9488 480 x 320 TFT

//#include <User_Setups/Setup206_LilyGo_T_Display_S3.h> // For the LilyGo T-Display S3 based ESP32S3 with ST7789 170 x 320 TFT
//#include <User_Setups/Setup207_LilyGo_T_HMI.h> // For the LilyGo T-HMI S3 based ESP32S3 with ST7789 240 x 320 TFT
//#include <User_Setups/Setup209_LilyGo_T_Dongle_S3.h> // For the LilyGo T-Dongle S3 based ESP32 with ST7735 80 x 160 TFT
//#include <User_Setups/Setup210_LilyGo_T_Embed_S3.h> // For the LilyGo T-Embed S3 based ESP32S3 with ST7789 170 x 320 TFT
//#include <User_Setups/Setup211_LilyGo_T_QT_Pro_S3.h> // For the LilyGo T-QT Pro S3 based ESP32S3 with GC9A01 128 x 128 TFT
// #include <User_Setups/Setup212_LilyGo_T_PicoPro.h> // For the LilyGo T-PICO-Pro with ST7796 222 x 480 TFT
// #include <User_Setups/Setup213_LilyGo_T_Beam_Shield.h> // For the LilyGo T-BEAM V1.x with ST7796 222 x 480 TFT

//#include <User_Setups/Setup250_ESP32_S3_Box_Lite.h> // For the ESP32 S3 Box Lite
//#include <User_Setups/Setup251_ESP32_S3_Box.h> // For the ESP32 S3 Box

//#include <User_Setups/Setup301_BW16_ST7735.h> // Setup file for Bw16-based boards with ST7735 160 x 80 TFT
//#include <User_Setups/Setup302_Waveshare_ESP32S3_GC9A01.h> // Setup file for Waveshare ESP32-S3-Touch-LCD-1.28 board with GC9A01 240*240 TFT

//#include <User_Setups/SetupX_Template.h> // Template file for a setup

//#include <User_Setups/Dustin_ILI9488.h> // Setup file for Dustin Watts PCB with ILI9488
//#include <User_Setups/Dustin_ST7796.h> // Setup file for Dustin Watts PCB with ST7796
//#include <User_Setups/Dustin_ILI9488_Pico.h> // Setup file for Dustin Watts Pico PCB with ST7796
//#include <User_Setups/Dustin_ST7789_Pico.h> // Setup file for Dustin Watts PCB with ST7789 240 x 240 on 3.3V adapter board
//#include <User_Setups/Dustin_GC9A01_Pico.h> // Setup file for Dustin Watts PCB with GC9A01 240 x 240 on 3.3V adapter board
//#include <User_Setups/Dustin_GC9A01_ESP32.h> // Setup file for Dustin Watts PCB with GC9A01 240 x 240 on 3.3V adapter board
//#include <User_Setups/Dustin_STT7789_ESP32.h> // Setup file for Dustin Watts PCB with ST7789 240 x 240 on 3.3V adapter board
//#include <User_Setups/Dustin_ILI9341_ESP32.h> // Setup file for Dustin Watts PCB with ILI9341
//#include <User_Setups/ILI9225.h>

#endif // USER_SETUP_LOADED

/////////////////////////////////////////////////////////////////////////////////////
// //
// DON'T TINKER WITH ANY OF THE FOLLOWING LINES, THESE ADD THE TFT DRIVERS //
// AND ESP8266 PIN DEFINITONS, THEY ARE HERE FOR BODMER'S CONVENIENCE! //
// //
/////////////////////////////////////////////////////////////////////////////////////

// Identical looking TFT displays may have a different colour ordering in the 16-bit colour
#define TFT_BGR 0 // Colour order Blue-Green-Red
#define TFT_RGB 1 // Colour order Red-Green-Blue

// Legacy setup support, RPI_DISPLAY_TYPE replaces RPI_DRIVER
#if defined (RPI_DRIVER)
#if !defined (RPI_DISPLAY_TYPE)
#define RPI_DISPLAY_TYPE
#endif
#endif

// Legacy setup support, RPI_ILI9486_DRIVER form is deprecated
// Instead define RPI_DISPLAY_TYPE and also define driver (e.g. ILI9486_DRIVER)
#if defined (RPI_ILI9486_DRIVER)
#if !defined (ILI9486_DRIVER)
#define ILI9486_DRIVER
#endif
#if !defined (RPI_DISPLAY_TYPE)
#define RPI_DISPLAY_TYPE
#endif
#endif

// Invoke 18-bit colour for selected displays
#if !defined (RPI_DISPLAY_TYPE) && !defined (TFT_PARALLEL_8_BIT) && !defined (TFT_PARALLEL_16_BIT) && !defined (ESP32_PARALLEL)
#if defined (ILI9481_DRIVER) || defined (ILI9486_DRIVER) || defined (ILI9488_DRIVER)
#define SPI_18BIT_DRIVER
#endif
#endif

// Load the right driver definition - do not tinker here !
#if defined (ILI9341_DRIVER) || defined(ILI9341_2_DRIVER) || defined (ILI9342_DRIVER)
#include <TFT_Drivers/ILI9341_Defines.h>
#define TFT_DRIVER 0x9341
#elif defined (ST7735_DRIVER)
#include <TFT_Drivers/ST7735_Defines.h>
#define TFT_DRIVER 0x7735
#elif defined (ILI9163_DRIVER)
#include <TFT_Drivers/ILI9163_Defines.h>
#define TFT_DRIVER 0x9163
#elif defined (S6D02A1_DRIVER)
#include <TFT_Drivers/S6D02A1_Defines.h>
#define TFT_DRIVER 0x6D02
#elif defined (ST7796_DRIVER)
#include "TFT_Drivers/ST7796_Defines.h"
#define TFT_DRIVER 0x7796
#elif defined (ILI9486_DRIVER)
#include <TFT_Drivers/ILI9486_Defines.h>
#define TFT_DRIVER 0x9486
#elif defined (ILI9481_DRIVER)
#include <TFT_Drivers/ILI9481_Defines.h>
#define TFT_DRIVER 0x9481
#elif defined (ILI9488_DRIVER)
#include <TFT_Drivers/ILI9488_Defines.h>
#define TFT_DRIVER 0x9488
#elif defined (HX8357D_DRIVER)
#include "TFT_Drivers/HX8357D_Defines.h"
#define TFT_DRIVER 0x8357
#elif defined (EPD_DRIVER)
#include "TFT_Drivers/EPD_Defines.h"
#define TFT_DRIVER 0xE9D
#elif defined (ST7789_DRIVER)
#include "TFT_Drivers/ST7789_Defines.h"
#define TFT_DRIVER 0x7789
#elif defined (R61581_DRIVER)
#include "TFT_Drivers/R61581_Defines.h"
#define TFT_DRIVER 0x6158
#elif defined (ST7789_2_DRIVER)
#include "TFT_Drivers/ST7789_2_Defines.h"
#define TFT_DRIVER 0x778B
#elif defined (RM68140_DRIVER)
#include "TFT_Drivers/RM68140_Defines.h"
#define TFT_DRIVER 0x6814
#elif defined (SSD1351_DRIVER)
#include "TFT_Drivers/SSD1351_Defines.h"
#define TFT_DRIVER 0x1351
#elif defined (SSD1963_480_DRIVER)
#include "TFT_Drivers/SSD1963_Defines.h"
#define TFT_DRIVER 0x1963
#elif defined (SSD1963_800_DRIVER)
#include "TFT_Drivers/SSD1963_Defines.h"
#define TFT_DRIVER 0x1963
#elif defined (SSD1963_800ALT_DRIVER)
#include "TFT_Drivers/SSD1963_Defines.h"
#define TFT_DRIVER 0x1963
#elif defined (SSD1963_800BD_DRIVER)
#include "TFT_Drivers/SSD1963_Defines.h"
#define TFT_DRIVER 0x1963
#elif defined (GC9A01_DRIVER)
#include "TFT_Drivers/GC9A01_Defines.h"
#define TFT_DRIVER 0x9A01
#elif defined (ILI9225_DRIVER)
#include "TFT_Drivers/ILI9225_Defines.h"
#define TFT_DRIVER 0x9225
#elif defined (RM68120_DRIVER)
#include "TFT_Drivers/RM68120_Defines.h"
#define TFT_DRIVER 0x6812
#elif defined (HX8357B_DRIVER)
#include "TFT_Drivers/HX8357B_Defines.h"
#define TFT_DRIVER 0x835B
#elif defined (HX8357C_DRIVER)
#include "TFT_Drivers/HX8357C_Defines.h"
#define TFT_DRIVER 0x835C
#elif defined (ST77916_DRIVER)
#include "TFT_Drivers/ST77916_Defines.h"
#define TFT_DRIVER 0x835D

                          // <<<<<<<<<<<<<<<<<<<<<<<< ADD NEW DRIVER HERE
                          // XYZZY_init.h and XYZZY_rotation.h must also be added in TFT_eSPI.cpp

#elif defined (XYZZY_DRIVER)
#include "TFT_Drivers/XYZZY_Defines.h"
#define TFT_DRIVER 0x0000
#else
#define TFT_DRIVER 0x0000
#endif

// These are the pins for ESP8266 boards
// Name GPIO NodeMCU Function
#define PIN_D0 16 // GPIO16 WAKE
#define PIN_D1 5 // GPIO5 User purpose
#define PIN_D2 4 // GPIO4 User purpose
#define PIN_D3 0 // GPIO0 Low on boot means enter FLASH mode
#define PIN_D4 2 // GPIO2 TXD1 (must be high on boot to go to UART0 FLASH mode)
#define PIN_D5 14 // GPIO14 HSCLK
#define PIN_D6 12 // GPIO12 HMISO
#define PIN_D7 13 // GPIO13 HMOSI RXD2
#define PIN_D8 15 // GPIO15 HCS TXD0 (must be low on boot to enter UART0 FLASH mode)
#define PIN_D9 3 // RXD0
#define PIN_D10 1 // TXD0

#define PIN_MOSI 8 // SD1 FLASH and overlap mode
#define PIN_MISO 7 // SD0
#define PIN_SCLK 6 // CLK
#define PIN_HWCS 0 // D3

#define PIN_D11 9 // SD2
#define PIN_D12 10 // SD4

[Basitadam]

They seem to be in order.
1- is your "User_Setup_New.h" file in the same folder as "User_Setup_Select.h" file?

2- Can you run this ino and send its serial output :

[Basitadam]

I will check the connections in detail soon. But these cable lengths, 50MHz might not work. Try lowering SCLK to 16-20MHz. But @brightproject is correct. You may supply backlight at 5V with proper resistance but pin4 VDD should be at 3.3V. Even a short time 5V to VDD pin is enough to kill the display driver ST77916.
As I see in the photos, backlight is on. Means ribbon cable connected at the right surface.
If you didn't connect 5V to VDD pin, try with 16MHz SCL and let us know

[Basitadam]

These are not bridges (shorts), right? Sometimes it is skipped:

[Basitadam]

I can't figure out from the photo. Is pin1 at the bottom (black cable) or top (not connected) from the leftmost side of the pin header?

[BojoteX]

I will check the connections in detail soon. But these cable lengths, 50MHz might not work. Try lowering SCLK to 16-20MHz. But @brightproject is correct. You may supply backlight at 5V with proper resistance but pin4 VDD should be at 3.3V. Even a short time 5V to VDD pin is enough to kill the display driver ST77916. As I see in the photos, backlight is on. Means ribbon cable connected at the right surface. If you didn't connect 5V to VDD pin, try with 16MHz SCL and let us know

Yeah well, clearly I did NOT and will not connect Pin 4 VDD to 5V. Its 2.8-3.3v, only LEDA with proper resistance can get 5V. Its 3 LEDs in series. forward voltage aprox 2.7. LEDA is PIN3, LEDK (PIN2) has the 100Ohm resistance. As shown in the PIC. I also tried several FPCs (have 4 of them).

So far, of all the feedback I believe your suggestion to lower SCL is worth trying. I still suspect there might be something wrong with the actual displays, in any case, I truly appreciate your willigness to help

[BojoteX]

You can see traces better here:

[lohikarhu]

2.7 V is about the forward voltage of some white LEDs, and it's also the typical minimum voltage for a lot of mobile phone ICs. Lohi

…

On Wed, Jul 30, 2025, 17:40 Vladislav ***@***.***> wrote: Would you agree with me that this points to the LCDs being defective? The datasheet says 2.7 volt, a very strange voltage. I have a st77916 with a QSPI bus and there are 3.3 volt. Your initiative with a 5 volt resistor does not seem very good to me. — Reply to this email directly, view it on GitHub <#3477 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGBMPKS5QVMEFV3C3QGOJDD3LDRQTAVCNFSM6AAAAABN4C2PX2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJTGYYDOMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[BojoteX]

I need to get home to double check, but I might have LEDK and GND swaped, both will show continuity in the multimeter as it should be shared ground but one has a resistance

LEDK is a grey cable (with the resistance) it goes in PIN2. PIN1 is BLACK cable but according to my own evidence, seems GND is connected to PIN2 and most likely LEDK is connected to PIN1

Not sure how this will affect operation as both connect to GND on the ESP32-S3, just that one has a resistance. But if I'm not mistaken I did test at the very begining without a resistance and connecting LEDA to 3.3. so I do not think a short test would fry the LCD.

[Basitadam]

There should be no connection to pin10 and pin12 and pin11 should be GND:

Worth to recheck them all

[BojoteX]

Thanks!! really helpful! I will ditch the multimeter, just follow the traces and image reference here on a spare FPC and re-wire.

[BojoteX]

I'll try again next week. I believe they don't work because I fried them. I know this because on my tests I was noticing how hot the flex PCB was getting, after your re-wire suggestion LED now is more dim and flex PCB is cold to the touch, so yes, definitely fried, by me. Thanks anyway for the help, I'll follow up next week when I get the new ones I ordered.

[brightproject]

I believe they don't work because I fried them.

My first experience with TFT displays was the same.

I was laying out a printed circuit board in Kikad and mirrored the FPC connector by mistake.
I soldered the ribbon cable and powered the board, the cable was heating up, there was no image.

When I fixed the situation, the display controller had already burned out.

Moreover, only the backlight worked.

Still, you will correct the situation with the power supply, and correctly connect the display with the ESP32 wires, preferably by soldering.

[BojoteX]

I got 5 displays for testing. Should get here on Monday. I'm simply trying to replace my analog gauges with TFTs and the ST77916 is the only one with the "exact" size (1.8 inches)... its also the newest and least supported display

[BojoteX]

Just a quick update... my TFTs (the previous ones) were clearly damaged by connecting the backlight directly without a resistor. Just got the new screens with the updated wiring as suggested by @Basitadam and the basic sample that I had worked.

Now I need to decide if I should keep the TFT_eSPI library with the suggested modifications OR if I'm better of using a newer, faster library. I believe @brightproject has been advocating for a different one, would love to hear opinions here on whats the consensus as to the best library to use for the ST77916.

Thanks everyone for the help!

[brightproject]

Thanks everyone for the help!

Hello @BojoteX 😀
The question of choosing a graphics library depends on your tasks and preferences.
TFT_eSPI was a cool library, but with the advent of new displays and interfaces, it certainly loses to others.
I like both LovyanGFX and ArduinoGFX, they are the closest to TFT_eSPI.
You can also use lvgl.
If you need a fairly fast display, then use ESP32_Display_Panel.

[Basitadam]

Just a quick update... my TFTs (the previous ones) were clearly damaged by connecting the backlight directly without a resistor. Just got the new screens with the updated wiring as suggested by @Basitadam and the basic sample that I had worked.

Now I need to decide if I should keep the TFT_eSPI library with the suggested modifications OR if I'm better of using a newer, faster library. I believe @brightproject has been advocating for a different one, would love to hear opinions here on whats the consensus as to the best library to use for the ST77916.

Thanks everyone for the help!

Glad you made it work. Nice.
If TFT_eSPI were maintained as before, would be my choice. For new interfaces like qspi , 16bit parallel I found LovyanGFX pretty neat. For rgb mode displays ESP32_Display_Panel is the one I am currently using

[BojoteX]

@Basitadam & @brightproject just wanted to give you an update.... ended up following your advise. Was able to use LovyanGFX without modifications (there is clearly a typo in one of their drivers) they list it as ST77961 (which does NOT exists) is in reality ST77916 (our round 1.8 inch LCD) tested some of my gauges and they worked with no issues and the sprites/draw function is 3 times faster with LovyanGFX compared to TFT_eSPI which is impressive! again, thanks again for all the help. I ended up choosing LovyanGFX as it was an easier migration from TFT_eSPI considering I do sprites/rotate/pivot for my gauges which LovyanGFX supports out of the box.

[Basitadam]

Hi @BojoteX. Thanks for the update

[ChrisZang0815]

@BojoteX Hi, could you please share the driver definition? I don't seem to be able to find it.
Thanks!

[BojoteX]

Hi @ChrisZang0815, just make sure you are using the latest version. The file is located in:

libraries\LovyanGFX\src\lgfx\v1\panel\Panel_ST77961.hpp

So you simply do (notice the lgfx::Panel_ST77961 _panel;) and NOT ST77916. Its a typo!

// --- Panel binding (LovyanGFX, ST77916/61) ---
class LGFX : public lgfx::LGFX_Device {
lgfx::Bus_SPI _bus;
lgfx::Panel_ST77961 _panel;
public:
LGFX() {
{ auto cfg = _bus.config();
cfg.spi_host = SPI2_HOST;
cfg.spi_mode = 0;
cfg.freq_write = 80000000;
cfg.freq_read = 16000000;
cfg.spi_3wire = false;
cfg.use_lock = true;
cfg.dma_channel = 1;
cfg.pin_mosi = 11;
cfg.pin_miso = -1;
cfg.pin_sclk = 12;
cfg.pin_dc = 13;
_bus.config(cfg);
_panel.setBus(&_bus);
}
{ auto pcfg = _panel.config();
pcfg.pin_cs = 10;
pcfg.pin_rst = 14;
pcfg.pin_busy = -1;
pcfg.memory_width = 360;
pcfg.memory_height = 360;
pcfg.panel_width = 360;
pcfg.panel_height = 360;
pcfg.offset_x = 0;
pcfg.offset_y = 0;
pcfg.offset_rotation = 0;
pcfg.invert = true;
pcfg.rgb_order = true;
_panel.config(pcfg);
}
setPanel(&_panel);
}
};

[Basitadam]

Wow. Good one. I was too lazy to switch to Lovyan for this controller. Now I can. Thank you @BojoteX

[ChrisZang0815]

Many thanks!!!

[ChrisZang0815]

very general question: can someone tell me which Arduino graphic libraries support QSPI?

[Basitadam]

GFX_Library_for_Arduino known as ArduinoGFX : https://github.com/moononournation/Arduino_GFX

[ChrisZang0815]

sorry for my stupid question, you had answered it before - my bad