-
Notifications
You must be signed in to change notification settings - Fork 26
Open
Description
Hi,
It looks like the file:
..\GitHub\CrowPanel-ESP32-Display-Course-File\CrowPanel_ESP32_Tutorial\File\TFT_eSPI Setup file\3.5inch\User_Setup.h
Is currently intended for the SPI version of the 3.5" display:
// For ESP32 Dev board (only tested with GC9A01 display)
// The hardware SPI can be mapped to any pins
#define TFT_MISO 12
#define TFT_MOSI 13 // In some display driver board, it might be written as "SDA" and so on.
#define TFT_SCLK 14
#define TFT_CS 15 // Chip select control pin
#define TFT_DC 2 // Data Command control pin
#define TFT_RST -1 // Reset pin (could connect to Arduino RESET pin)
#define TFT_BL 27 // LED back-light
#define TOUCH_CS 33 // Chip select pin (T_CS) of touch screenI was suspecting something like:
#define TFT_D0 47 // Must use pins in the range 0-31 for the data bus
#define TFT_D1 21 // so a single register write sets/clears all bits.
#define TFT_D2 14 // Pins can be randomly assigned, this does not affect
#define TFT_D3 13 // TFT screen update performance.
#define TFT_D4 12
#define TFT_D5 11
#define TFT_D6 10
#define TFT_D7 9
#define TFT_D8 3
#define TFT_D9 8
#define TFT_D10 16
#define TFT_D11 15
#define TFT_D12 7
#define TFT_D13 6
#define TFT_D14 5
#define TFT_D15 4But it looks like tft_espi is only accepting 16 bits parallel IO for an experimental version with the Raspberry Pi.
How can I configure my project for the parallel RGB version?
Kind regards,
HenkJan
Metadata
Metadata
Assignees
Labels
No labels