Display: WT32-SC01 3.5"

[last updated: 2024-08-21]
TFT_eSPI library
LovyanGFX Library functions
WT32-SC01 SPI
-----------------------------

This page is mostly a log of fumbling attempts (successful in the end) to get the screen functioning,
that is, to display graphics that I draw onto it, and to respond to touches per my programming.

------------------------

It is a 3.5" touch screen display
attached to a ESP32 Wrover B mcu module
Bought this:
https://www.seeedstudio.com/ESP32-Development-board-WT32-SC01-p-4735.htm...
Packaging list shows this site for support, however my advice is to stay away from it.
As often, documentation is lacking.
See other links below.
Note the expansion connectors (2x20 = 40-pin) are 2.0mm pitch, instead of more common 2.54mm.
connectors are available...
------------------------------------------------------------------
Powered up with included USB-C cable. It goes through demo screens, then stops, displaying a graphic, but does not respond to touches.
After much trial and error, web surfing, reading docs, and gnashing of teeth, finally got it to work.
Minimal successful program:
... ... link ... ... WT32_SC01_01f_MIN_BTN
This minimal program draws graphics on the screen, including sprites,
and monitors for screen touches and responds as programmed.
When you examine the code, you'll see:
- This program uses both the TFT_eSPI and LovyanGFX libraries:
- Install both libraries using library manager:
  Sketch --> Include library --> Manage libraries, or:
  Tools --> Manage libraries
- The Lovyan library:
  - When you install the library (via library manager as noted above),
    it will put the unzipped files into a folder ...
    (apologies, did not record where online I got these instructions...)
    check this out too... https://github.com/lovyan03/LovyanGFX/blob/master/src/lgfx_user/LGFX_ESP...
    Configure LVGL:
    - In the lvgl directory is the file:
      lv_conf_template.h
      Save/preserve this file by copying and renaming it to lv_conf_template_Orig.h
      Then rename original ...template.h to:
      lv_conf.h
    - Move lv_conf.h up one directory, into the libraries folder.
      
      Edit the conf.h and change the first #if 0 to #if 1 to enable the content of the file
      Set the color depth of your display in LV_COLOR_DEPTH
- The TFT_eSPI library,:
  - When you first install the library into your Arduino IDE,
    and examine the ... files ... find setup.h ... find sco1 template ...see pin designations being used ... code those into the setup.h
  - Basically what you're doing is specifying the SPI pins that your hardware (the touch screen in this case) uses to communicate to your MCU.
    For the GT32-SC01, there is a file ... that contains that info, that you copy or whatever into your setup.h
    That file specifies: MISO-12, MOSI-13, SCLK-14, SS-15, "DC"-21, RST-22, and BL-23.
------------------------------------------------------------------
Misc tips:
- Opened Arduino IDE, selected board: ESP32 wrover module.
- Here's what I did to edit the setup config files:
  - Successfully installed the lvgl library with library manager.
  - Set up Drivers:
    Successfully installed TFT_eSPI library v. 2.5.43 from library manager
    now instructions are:
  ------------------------------------------------------------------
- Misc unsorted, unedited notes:
  - From Github TFT_eSPI (https://github.com/Bodmer/TFT_eSPI):
    "The screen controller, interface pins and library configuration settings must be defined inside the library. They can NOT be defined in the Arduino sketch. See the User_Setup_Select.h file for details. This approach has significant advantages, it keeps the examples clean from long configuration options and once the setup is defined any example can be run without modification. ..."
  - In the User_setups folder, there is a file:
    In addition, in the TFT_eSPI library folder, there are files:
  - "If you load a new copy of TFT_eSPI then it will overwrite your setups if they are kept within the TFT_eSPI folder. To avoid this, create a new folder in your Arduino library folder called "TFT_eSPI_Setups". You then place your custom setup.h files in there. After an upgrade simply edit the User_Setup_Select.h file to point to your custom setup file e.g.:
    You must make sure only one setup file is called. In the custom setup file I add the file path as a commented out first line that can be cut and pasted back into the upgraded User_Setup_Select.h file. The ../ at the start of the path means go up one directory level. Clearly you could use different file paths or directory names as long as it does not clash with another library or folder name.
    You can take this one step further and have your own setup select file and then you only need to replace the Setup.h line reference in User_Setup_Select.h to, for example:
    To select a new setup you then edit your own my_setup_select.h file (which will not get overwritten during an upgrade)."
  ------------------------------------------------------------------
------------------------------------------------------------------
Refs/Links:

Main Menu

Main menu

Site Menu

You are here