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.

[brightproject]

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

Good day @MBlackmagic
I'm also trying to somehow run my JC3636W518 display using the library TFT_eSPI.

So far, I have only been able to do this using the arduino_gfx library and the lvgl built into it.
But the main difficulty is to make the library code work TFT_eSPI via the quad SPI, so I became interested in how mr. @Basitadam implemented this.
Because here you can't do with just drivers, you need to add some functionality inside the files

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

What kind of display do you have @MBlackmagic ?

[MBlackmagic]

I am also using the JC3636W518 with the Arduino_GFX so far, but most of my project are build with the TFT_eSPI library, it would be very handy for me if the TFT_eSPI would run on the ST77916 Display of the JC3636W518.

[brightproject]

I am also using the JC3636W518 with the Arduino_GFX so far, but most of my project are build with the TFT_eSPI library, it would be very handy for me if the TFT_eSPI would run on the ST77916 Display of the JC3636W518.

I have a similar situation to yours, many of my graphic projects use sprites to display images, and this is only the TFT_eSPI library.
Perhaps Mr. @Bodmer will join the discussion and provide any help he can?

[MBlackmagic]

This would be great, sure we are not the only one using this display type. This needs to be done by an expert like @Bodmer.

[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

[brightproject]

My solution is based on TFT_eSPI 2.5.43 and ESP32 3.0.4 board libraries. With Arduino IDE 2.3.2.

Thank you @Basitadam for your work and files!
To my great regret, I couldn't adapt your code for JC3636W518.
It didn't work either via vscode + platformio or via arduino IDE.
It seems to me that the reason is a separate microcontroller chip, and not an assembly like wroom.

Separately chip.

Although according to the datasheet there seem to be no differences.

Could you post a photo to show that your display is actually displaying an image?
Just for the record in this discussion.
I just read a lot of threads on GitHub that with the migration from 2.0 to version 3.0 of ESP-IDF, the TFT_eSPI library partially broke, but write down that you tried it on version 2.5.43 and everything is OK.
Also, as far as I remember, the display initialization should be

tft.init(); // initialize the display

Yours is different

tft.begin(); // initialize the display

SPI mode SPI_MODE0, everything seems to be fine here.
Although for the sake of experiment I changed it to SPI_MODE3

TFT_eSPI/TFT_eSPI.h

Line 132 in 5793878

#if defined(ST7789_DRIVER) || defined(ST7789_2_DRIVER)

Could you somehow find out what revision of esp32s3 you have?
Please show me the connection diagram of your hardware.

Only for some reason you have pin DC replaced with CS.

// for Timucin KANATLI device
#define TFT_MISO -1
#define TFT_MOSI 11
#define TFT_SCLK 9
#define TFT_CS 8 // Chip select control pin
#define TFT_DC 10//7 // Data Command control pin
#define TFT_RST -1 // Reset pin (could connect to RST pin)
//#define TFT_RST -1 // Set TFT_RST to -1 if display RESET is connected to ESP32 board RST
#define TOUCH_CS -1 // Chip select pin (T_CS) of touch screen
#define TFT_BLK 15

Settings for my hardware

// for JC3636W518
#define TFT_SCLK 9
#define TFT_CS 10
#define TFT_MOSI 11
#define TFT_MISO 12
#define TFT_DC -1
// #define TFT_DC 13
// #define TFT_DC 14
// #define TFT_DC 10
#define TFT_RST 47
// #define TFT_BACKLIGHT_ON 1
// #define TFT_BL 15
#define TOUCH_CS -1

I tried both this way and the other way around, but it didn't give any result.
Probably when a separate esp32s3 chip is used it makes adjustments.
Or the initialization of this display is different, even though the driver ST77916.

Here is the wiring diagram for this device.

2_S3R8.pdf

You used esp32s3 wroom and a separate display, and connected it with a classic SPI.

But it seems to me that for my hardware I need to use the quad SPI, as is done in Arduino_GFX:

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 */);

Here the code compiles, loads into the device normally and works.

I hope @MBlackmagic will also write about his experiments.
It would be great if you also work in the environment vscode + platformio.
It is possible that I am doing something wrong🙂

[5orwt9]

Hi, @brightproject , i'm MickeyJeong

i also have "JC3636W518", and i'm trying to join "ELM327" module(*Car OBD) to visualize "somethings" in my car

i have tried several times to write my own code, but i failed..

.
there is some demo code based on LVGL from seller's Link, obviously you have it too,

is there any other way to use the demo code to our own code?

the demo code already has all kind of drivers and function, i think sombody can modify that code to make some wonderful ART

ps. I ask for your generous understanding of my inexperience. ^^

Demo_Arduino.zip

[brightproject]

there is some demo code based on LVGL from seller's Link, obviously you have it too,

Hello @5orwt9
I haven't tried loading this example into the device, I tried loading examples from the library Arduino_GFX.
And only a few examples started for me.
You sent the example code for the LVGL version
Configuration file for v8.3.0-dev.
This is an old version, now it's 9.2.0.
I'm not sure if this example will work with the new version.
I didn't quite understand what you want?
Based on this example, create what?
What interface sample do you want to repeat to display data from the car?
It seems to me that you need to start from the original idea and design of your application, and not from what a beautiful design was provided to us in the examples - examples usually remain examples.
I don't know of a single case when a working interface was made based on an example.
This is just advertising and nothing more.
And you won't find really good interfaces in the source codes, the same device author JC3636W518 just gave a *bin file without the source codes.
The LVGL library is based on tft_espi, it certainly allows you to implement more beautiful projects, but it is very painstaking work.
It is easier and more practical for me to work with an old but reliable library tft_espi.
I have been programming in it for quite a long time.

[5orwt9]

Thank you for your reply @brightproject !

I have tried demo examples provided from seller
But it was powered only in very limited environment--versions of librarys and provided source codes, as you mentioned.

So, I tried to use newest library to convert it, some of LVGL grammar has been changed

Other library seems doesn't matter,

But as you said so, convert an old code to new code was extremely hard job to me.. so i gave up ^^

However the project that I want to make is "Vehicle Information System"

Here is some drawing about my project, I hope my drawing can make you understand

and also here is the interface of my project I want to try

Actually, I'm really not good at programming and coding, also not my major..

But I want to try this project as my hobby to enjoy it while I get home

You and other users may help me to solve my problems-- it gonna be sooooo nice ^^

But I know already that the problem I'm having is a fairly rudimentary problem.

even my code can't initialize tft from beginning and rebooting all day ㅜㅡㅜ

Therefore, can you share some of your files.??

Files form TFT_eSPI library folder(user setup.h, drivers files, etc..)

And your example code that you used with your development environments

Then, I may can solve my issues myself and processing my little project

I'm really thank you for your interest^^

[brightproject]

So, I tried to use newest library to convert it, some of LVGL grammar has been changed

Is the photo yours?

Did you run this code or did none of the examples run for you?
If this is your photo, then you managed to connect the contacts correctly and select the right library.
Now the work is more related to design than programming.
Master squareline or another tool.
Try, test, everyone learned this way.
Although these are discussions, they are dedicated to the library TFT_eSPI.
You can ask questions in the thread Arduino_GFX or lvgl.
The hardest thing for a beginner when working with any graphic library is to connect the hardware correctly and set up the pins in the library.
And then, using examples, change the graphics, draw some elements or convert pictures into bitmaps.
You won't get ready-made code as such here, here on GitHub there are people like you, some are good at programming, some are not so good.
You need to study and learn everything yourself.

[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

[brightproject]

Hoped I could change the communication mode to simple SPI via

Oh my🙂
You gave me some good food for thought, I had no idea to change the display from QSPI to SPI.
Perhaps the pull-up resistors on the 20-pin display are located under the touchscreen FPC cable, which is soldered on top of the display cable.
I am also looking for opportunities to use QSPI for the library.

https://github.com/ChuckM/stm32f469i/blob/master/demos/qspi/qspi.c

The most annoying thing is that this quad spi is neither one thing nor the other.
Standard SPI gives a good data rate of 40-60 MHz of real frequency.
If you need more speed, then usually use a parallel 8- or 16-bit interface.
With QSPI, you only get problems and few people use it.

[Basitadam]

QSPI mode is useful if you are using a hardware QSPI driver. Otherwise it is bit banging. For hardware QSPI, you need vendor specific driver libraries, APIs. I would not waste time with other than ESP-IDF

tft.init() and tft.begin are the same by the way:

[brightproject]

tft.init() and tft.begin are the same by the way:

By the way, does your display also have a CST816 touch driver?
Have you tried to use it via TFT_eSPI?

[Basitadam]

Nope. No touch on this display