1,8 dazio TFT su ESP-32 Dev Kit C

Salve e Benvenuti al nostro contributo di oggi.

Il nostro vantaggio 1,8 Zoll SPI TFT Display consente di ottenere informazioni Colorata con risoluzione di: 128 x 160 Fare pixel. 

Grazie all'interfaccia SPI e al chip di controllo ST7735 e alla molteplicità di biblioteche Arduino, L'attuazione nei propri progetti è molto semplice.

Anche la Microcontrollore con ESP-32 il Display TFT può essere attivato tramite SPI. A tal fine, tuttavia, è necessaria una biblioteca adeguata.

L'installazione della Libreria è piuttosto semplice, ma uno dei file deve essere adattato manualmente per funzionare con L'ESP-32.

Come ha installato L'ESP-32 tramite L'amministratore della Arduino board, le abbiamo già "Installa ESP32 tramite L'amministratore del Board" fatto. Riteniamo quindi che le attuali definizioni di Board per L'ESP-32 siano già state installate.

Installazione della libreria

Per controllare il Display, usiamo la libreria. "TFT_eSPI" di Bodmer. La biblioteca non fa parte dell'installazione di base Arduino, ma può essere utilizzata in vari modi. Gestore di biblioteche Nell'IDE Arduino.

Sul menu "Sketch" -> "Collegare la libreria" -> "Gestione biblioteche ..."apriamo il gestore della biblioteca. In alternativa, Combinazione tasto "Strg" + "Shift" + " i" usare.

Nel campo di ricerca del bibliotecario, "TFT_eSPI"on e installa "TFT_eSPI by Bodmer"nella versione attuale.

Adeguamenti Necessari

Per far funzionare la biblioteca con il nostro ESP-32, dobbiamo modificare un file manualmente. Questa modifica deve essere attuata una sola volta.

A tal fine, il gestore dei file è inserito nella directory. C:\Users\<nome utente>\Documents\Arduino\libraries\TFT_eSPI e apre il file User_Setup.h in un editor di testo come Notepad.

Cliccando a destra sul file, apriamo il menu contestuale e scegliamo L'opzione "Apri con esso"..."e poi come programma "Notepad".

Nella User_Setup.h File offre Un'ampia gamma di opzioni di assunzione.

Un "/ / " All'inizio della riga è una sezione di commento. Occorre quindi completare tutte le righe non necessarie e, per le righe importanti, eliminare le righe "//" all'inizio della riga.

Ho gia 'fatto questo lavoro per lei, quindi puo' leggere il contenuto di User_Setup.sostituire h con il seguente codice:

// USER DEFINED SETTINGS
// Set driver type, fonts to be loaded, pins used and SPI control method etc
//
// See the User_Setup_Select.h file if you wish to be able to define multiple
// setups and then easily select which setup file is used by the compiler.
//
// If this file is edited correctly then all the library example sketches should
// run without the need to make any more changes for a particular hardware setup!
// Note that some sketches are designed for a particular TFT pixel width/height


// ##################################################################################
//
// Section 1. Call up the right driver file and any options for it
//
// ##################################################################################

// Only define one driver, the other ones must be commented out
// #define ILI9341_RIVER
# define # ST7735_RIVER      // Define additional parameters below for this display
// #define ILLI9163_DRIVER / / Define additional parameters below for this display
// #define S6D02A1_RIVER
//#define RPI_ILI9486_RIVER / / 20MHz maximum SPI
// #define HX8357D_RIVER
// #define IL9481_RIVER
// #define ILI9486_RIVER
//#define ILI9488_DRIVER / / WARNING: Do not connect ILI9488 display SDO to MISO if other devices share the SPI bus (TFT SDO does NOT tristate when CS is high)
// #define ST7789_DRIVER / / Define additional parameters below for this display
// #define R61581_RIVER

// Some displays support SPI reads via the MISO pin, other displays have a single
// bi-directional SDA pin and the library will try to read this via the MOSI line.
// To use the SDA line for reading data from the TFT uncomment the following line:

// #define TFT_SDA_READ / / This option if for ESP32 ONLY, tested with ST7789 display only

// For ST7789 ONLY, define the colour order IF the blue and red are swapped on your display
// Try ONE option at a time to find the correct colour order for your display

// #define TFT_RGB_ORDER TFT_RGB / / Colour order Red-Green-Blue
// #define TFT_RGB_ORDER TFT_BGR / / Colour order Blue-Green-Red

// For M5Stack ESP32 module with integrated ILI9341 display ONLY, remove // in line below

// #define M5STACK

// For ST7789, ST7735 and ILI91163 ONLY, define the pixel width and height in portrait orientation
// #define TFT_WIDTH 80
 # define # TFT_WIDTH  128
// #define TFT_WIDTH 240 / / ST7789 240 x 240 and 240 x 320
 # define # TFT_HEIGHT 160
// #define TFT_HEIGHT 128
// #define TFT_HEIGHT 240 / / ST7789 240 x 240
// #define TFT_HEIGHT 320 / / ST7789 240 x 320

// For ST7735 ONLY, define the type of display, originally this was based on the
// colour of the tab on the screen protector film but this is not always true, so try
// out the different options below if the screen does not display graphics correctly,
// e. g. colours wrong, mirror images, or tray pixels at the edges.
// Comment out ALL BUT ONE of these options for a ST7735 display Drive, save this
// this User_Setup file, then rebuild and upload the sketch to the board again:

// #define ST7735_INITB
// #define ST7735_GREENTAB
// #define ST7735_GREENTAB2
// #define ST7735_GREENTAB3
// #define ST7735_GREENTAB128 / / For 128 x 128 display
// #define ST7735_GREENTAB160x80 / / For 160 x 80 display (BGR, inverted, 26 offset)
 # define # ST7735_REDTAB
// #define ST7735_BLACKTAB
// #define ST7735_REDTAB160x80 / / For 160 x 80 display with 24 pixel offset

// If colours are inverted( White shows as black) then uncomment one of the next
// 2 lines try both options, one of the options should correct the inversion.

// #define TFT_INVERSION_ON
// #define TFT_INVERSION_OFF

// If a backlight control signal is available then define the TFT_BL pin in Section 2
/- below. The backlight will be turned ON when tft.begin () is called, but the library
// needs to know if the LEDs are ON with the pin HIGH or LOW. If the LEDs are to be
// driven with a PWM signal or turned OFF / ON then this must be handled by the user
/ sketch. e.g. with digitalWrite(TFT_BL, LOW));

// #define TFT_BACKLIGHT_ON HIGH / / HIGH or LOW are options

// ##################################################################################
//
// Section 2. Define the pins that are used to interface with the display here
//
// ##################################################################################

// We must use hardware SPI, a minimum of 3 GPIO pins is neededed.
// Typical setup for ESP8266 NodeMCU ESP-12 is :
//
// Display SDO / MISO to Nodecu pin D6 (or leave disconnected if not reading TFT)
// Display LED to NodeMCU pin VIN (or 5V, see below)
// Display SCK to Nodecu pin D5
// Display SDI / MOSI to Nodecu pin D7
// Display DC (RS/AO)to Nodecu pin D3
// Display RESET to NodeMCU pin D4 (or RST, see below)
// Display CS to Nodecu pin D8 (or GND, see below)
// Display GND to Nodecu pin GND (0V)
// Display VCC to Nodecu 5V or 3.3 V
//
// The TFT RESET pin can be connected to the NodeMCU RST pin or 3.3 V to free up a control pin
//
// The DC (Data Command) pin may be labeled AO or RS (Register Select))
//
// With some displays such as the ILI9341 the TFT CS pin can be connected to GND if no more
// SPI devices (e.g. an SD Card) are connected, in this case comment out the #define TFT_CS
// line below so it is NOT defined. Other displays such at the ST7735 require the TFT CS pin
// to be toggled during setup, so in these cases the TFT_CS line must be defined and connected.
//
// The NodeMCU D0 pin can be used for RST
//
//
// Note: only some versions of the Nodencu provide the USB 5V on the VIN pin
// If 5V is not available at a pin you can use 3.3 V but backlight bright brighttness
/ will be lower.


// # # # # EDIT THE PIN NUMBERS IN THE LINES FOLLOWING TO SUIT YOUR ESP8266 SETUP #  ######

// For NodeMCU-use pin numbers in the form PIN_Dx where Dx is the NodeMCU pin designation
// #define TFT_CS PIN_D8 / / Chip select control pin D8
//#define TFT_DC PIN_D3 / / Data Command control pin
//#define TFT_RST PIN_D4 / / Reset pin (could connect to NodeMCU RST, see next line)
//#define TFT_RST -1 / Set TFT_RST to -1 if the display RESET is connected to Nodecu RST or 3.3 V

//#define TFT_BL PIN_D1 / / LED back-light (only for ST7789 with backlight control pin))

//#define TOUCH_CS PIN_D2 / / Chip select pin (T_CS) of touch screen

//#define TFT_WR PIN_D2 / / Write strobe for modified Raspberry Pi TFT only


// # # # # FOR ESP8266 OVERLAP MODE EDIT THE PIN NUMBERS IN THE FOLLOWING LINES  ######

// Overlap mode shares the ESP8266 FLASH SPI bus with the TFT so has a performance impact
// but saves pins for other functions.
// Use NodeMCU SD0=MISO, SD1=MOSI, CLK=SLK to connect to TFT in overlap mode

// In ESP8266 overlap mode the following must be defined
//#define TFT_SPI_OVERLAP

// In ESP8266 overlap mode the TFT chip select MUST connect to pin D3
//#define TFT_CS PIN_D3
// #define TFT_DC PIN_D5 / / Data Command control pin
//#define TFT_RST PIN_D4 / / Reset pin (could connect to NodeMCU RST, see next line)
//#define TFT_RST -1 / Set TFT_RST to -1 if the display RESET is connected to Nodecu RST or 3.3 V


// # # # # EDIT THE PIN NUMBERS IN THE LINES FOLLOWING TO SUIT YOUR ESP32 SETUP #    ######

// For ESP32 Dev board (only tested with ILI9341 display)
// The hardware SPI can be mapped to any pins

# define # TFT_MISO 19
//#define TFT_MOSI 23
# define # TFT_SCLK 18
# define # TFT_CS   17// Chip select control pin
" #define " TFT_DC    2  // Data Command control pin
" #define " TFT_RST   14  // 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 TFT_BL 32 // LED back - light (only for ST7789 with backlight control pin)

//#define TOUCH_CS 21 // Chip select pin (T_CS) of touch screen

//#define TFT_WR 22 // Write strobe for modified Raspberry Pi TFT only

// For the M5Stack module use these #define lines
//#define TFT_MISO 19
//#define TFT_MOSI 23
//#define TFT_SCLK 18
//#define TFT_CS 14 // Chip select control pin
//#define TFT_DC 27 // Data Command control pin
//#define TFT_RST 33 // Reset pin (could connect to Arduino RESET pin)
//#define TFT_BL 32 // LED back - light (required for M5Stack)

// ###### EDIT THE PINs BELOW TO SUIT YOUR ESP32 PARALLEL TFT SETUP ######

// The library supports 8 bit parallelo TFTs with the ESP32, the pin
// selection belov is compatible with ESP32 boards in formato ONU.
// Wemos D32 boards need to be modified, see diagram in Tools folder.
// Only ILI9481 and ILI9341 have fays tested!

// Parallelo is only supported on ESP32
// Uncomment line below to use ESP32 Parallel interface instead of SPI

//#define ESP32_PARALLEL

// The ESP32 and TFT the pins used for testing are:
//#define TFT_CS 33 // Chip select control pin (library pulls permanently low)
//#define TFT_DC 15 // Data Command control pin - must use a pin in the range 0 - 31
//#define TFT_RST 32 // Reset pin, toggles on startup

//#define TFT_WR 4 // Write strobe control pin - must use a pin in the range 0 - 31
//#define TFT_RD 2 // Read strobe control pin

//#define TFT_D0 12 // Must use pins in the range 0 - 31 for the data bus
//#define TFT_D1 13 // a un singolo registro write set / clear all bits.
//#define TFT_D2 26 // Pins can be randomly assigned, this does not affect
//#define TFT_D3 25 // TFT screen update performance.
//#define TFT_D4 17
//#define TFT_D5 16
//#define TFT_D6 27
//#define TFT_D7 14


// ##################################################################################
//
// Sezione 3. Define the fonts tha are to be used here
//
// ##################################################################################

// Comment out the #defines below with // to stop tha font contiene loaded
// The ESP8366 and ESP32 have plenty of memory so commenting out fonts is not
// normally necessary. If all fonts are loaded the extra FLASH space required is
// about 17Kbytes. To save FLASH space only enable the fonts you need!

" #define " LOAD_GLCD   // Font 1. Originale 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_FONT8N // Font 8. Alternativa to Font 8 above, slightly narrower, 3 digits fit a 160 pixel TFT
" #define " LOAD_GFXFF  // FreeFonts. Include access to the 48 Adafruit_GFX free fonts FF1 to FF48 and custom fonts

// Comment out the #define bow to stop the SPIFFS filing system and smooth font code e smooth loaded
// this vuole save ~ 20kbytes of FLASH
" #define " SMOOTH_FONT


// ##################################################################################
//
// Sezione 4. Other options
//
// ##################################################################################

// Define the SPI clock frequency, this affects the graphics - speed. Too
// quasi and the TFT driver will not keep up and display corruption appears.
// With a ILI9341 display 40MHz works OK, 80MHz sometimes fails
// With a ST7735 display more than 27MHz may not work (spurious tagels and line)
// With a ILI9163 display a 27 MHz Framework.
// The RPi typically only works at 20MHz maximum.

// #define SPI_FREQUENCY 1000000
// #define SPI_FREQUENCY 5000000
// #define SPI_FREQUENCY 10000000
// #define SPI_FREQUENCY 20000000
" #define " SPI_FREQUENCY  27000000 // Actually set it to 26.67MHz = 80/3
// #define SPI_FREQUENCY 40000000 // massimo per use SPIFFS
// #define SPI_FREQUENCY 80000000

// Facoltativo reduced SPI frequency for reading TFT
" #define " SPI_READ_FREQUENCY  20000000

// The XPT2046 requires a lower SPI clock rate of 2.5MHz ha definito la we define there here:
" #define " SPI_TOUCH_FREQUENCY  2500000

// The ESP32 has 2 free SPI ports i.e. VSPI and HSPI, the VSPI is the default.
// If the VSPI port is in use and pins are not accessible (e.g. TTGO T-Beam)
// then uncomment the following line:
//#define USE_HSPI_PORT

// Comment out the following #define if "SPI Transactions" do not need to be
// supported. When commented out the code size vuole foca e sketches.
// run slightly faster, così leave it commented out unless you need it.

// Transaction support is needed to work with SD library but not needed with TFT_SdFat
// Transaction support is required if other SPI devices are connected.

// Transactions are automatically enabled by the library for an ESP32 (to use HAL mutex)
// così changing it here has no effect

// #define SUPPORT_TRANSACTIONS

Successivamente, è necessario salvare le modifiche apportate al file User_Setup.h.

cablaggio del display con il PSP - 32

Nel file appena modificato, abbiamo stabilito quale funzione assumerà la funzione. Affinché questa configurazione funzioni, il display deve essere collegato al ESP - 32 come riportato di seguito:

Campionamento di campioni di esempio

Nell'IDE di Arduino ora siamo sicuri di aver selezionato il modulo "ESP-32 Dev Kit C" nel menu Strumenti.

A questo punto, tramite il menu File - > Esempi - > TFT_eSPI - > "160x128", è possibile accedere a un chetch di esempio e non caricare ulteriori modifiche o configurazioni al nostro ESP - 32. 

Questa è una foto del chetario di Pong_V3.ino in azione:

Ci auguriamo che il contributo di oggi contribuisca alla messa in servizio del TFT del PSE32 e le auguriamo di essere molto più divertente nella costruzione di quest' oggi.

Il vostro Markus Neumann
Team AZ - Delivery