tbillion commented 2 years ago

To minimise effort to resolve issues the following should be provided as a minimum:

A description of the problem and the conditions that cause it to occur

i am attempting to combine two files (setup104.h for the rp2040 elements, and setup19.h for the rm68140.h elements) in order to create a custom setup file. i am trying to connect the open smart RM68140 tft to RP2040 and later RP2040W if they indeed ever come off back order. I cant really decipher how the pins for this should be best connected based on the two files that i have chosen as examples. it appears that there are constraints on the rp 2040 pis that an be used, but i cant deciper if the control pin markup used is for the st7735 that the original example comes with or if it is rp2040 specific. guidance is appreciated .

IDE (e.g. Arduino or PlatformIO) Arduino
TFT_eSPI library version (try the latest, the problem may have been resolved!) from the Manage Libraries... menu name=TFT_eSPI version=2.4.72 author=Bodmer maintainer=Bodmer sentence=TFT graphics library for Arduino processors with performance optimisation for RP2040, STM32, ESP8266 and ESP32 paragraph=Supports TFT displays using drivers (ILI9341 etc) that operate with hardware SPI or 8 bit parallel. category=Display url=https://github.com/Bodmer/TFT_eSPI architectures=* includes=TFT_eSPI.h
Board package version (e.g. 2.0.3) available from the Boards Manager... menu https://github.com/earlephilhower/arduino-pico
Procesor, e.g RP2040, ESP32 S3 etc rp2040
TFT driver (e.g. ILI9341), a link to the vendors product web page is useful too. RM68140
Interface type (SPI or parallel) parallel Plus further information as appropriate to the problem:
TFT to processor connections used undefined currently however if i had a preference i like all my ducks in a single line.

// This setup is for the RP2040 processor only when used with 8 bit parallel displays
// See SetupX_Template.h for all options available
#define USER_SETUP_ID 787

////////////////////////////////////////////////////////////////////////////////////////////
// Interface
////////////////////////////////////////////////////////////////////////////////////////////
#define TFT_PARALLEL_8_BIT

////////////////////////////////////////////////////////////////////////////////////////////
// Display driver type
////////////////////////////////////////////////////////////////////////////////////////////
#define RM68140_DRIVER

////////////////////////////////////////////////////////////////////////////////////////////
// RP2040 pins used
////////////////////////////////////////////////////////////////////////////////////////////

this is both pin configs from both files but i am not sure which is more correct or if either is correct at all. 

// ESP32 pins used for UNO format board
#define TFT_CS   33  // Chip select control pin
#define TFT_DC   15  // Data Command control pin - must use a pin in the range 0-31
#define TFT_RST  32  // Reset pin

#define TFT_WR    22  // Write strobe control pin - must use a pin in the range 0-31
#define TFT_RD    -1

  // PIO requires these to be sequentially increasing - do not change
  #define TFT_D0    6
  #define TFT_D1    7
  #define TFT_D2    8
  #define TFT_D3    9
  #define TFT_D4   10
  #define TFT_D5   11
  #define TFT_D6   12
  #define TFT_D7   13

//#define TFT_CS   -1  // Do not define, chip select control pin permanently connected to 0V

// These pins can be moved and are controlled directly by the library software
#define TFT_DC   28    // Data Command control pin
#define TFT_RST   2    // Reset pin

//#define TFT_RD   -1  // Do not define, read pin permanently connected to 3V3

// Note: All the following pins are PIO hardware configured and driven
// The pins are hard-coded at the moment and must not be changed here
// Connections MUST use the pins below
  #define TFT_WR   22

  // PIO requires these to be sequentially increasing - do not change
  #define TFT_D0    6
  #define TFT_D1    7
  #define TFT_D2    8
  #define TFT_D3    9
  #define TFT_D4   10
  #define TFT_D5   11
  #define TFT_D6   12
  #define TFT_D7   13
//*/

////////////////////////////////////////////////////////////////////////////////////////////
// Fonts to be available
////////////////////////////////////////////////////////////////////////////////////////////
#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

////////////////////////////////////////////////////////////////////////////////////////////

Bodmer commented 2 years ago

You can shoose the control pins as you wish. The data pins must be sequentially increasing pins but the start pin of the sequence can be chosen. So if GPIO 0 is the data bus start pin:

define TFT_D0 0

define TFT_D1 1

define TFT_D2 2

define TFT_D3 3

define TFT_D4 4

define TFT_D5 5

define TFT_D6 6

define TFT_D7 7

and another example if GPIO 6 is the data bus start pin:

define TFT_D0 6

define TFT_D1 7

define TFT_D2 8

define TFT_D3 9

define TFT_D4 10

define TFT_D5 11

define TFT_D6 12

define TFT_D7 13