-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
White Screen? #15
Comments
Can you post the output of the serial monitor on 115200 baud? To see if it actually boots correct. You can also post the User_Setup.h you are using at the moment to see if it is actually correct. It could also be a bad solder joint, but let's rule things out one at a time... |
I get no output on 115200 baud.
|
I edited your post, because you posted the TFT_eSPI.h file. I meant the User_Setup.h. Also, try keeping the serial monitor open and resetting the board. This should output something. |
|
`// USER DEFINED SETTINGS // ################################################################################## // Define STM32 to invoke optimised processor support (only for STM32) // Defining the STM32 board allows the library to optimise the performance // STM32 8 bit parallel only: // Tell the library to use 8 bit parallel mode (otherwise SPI is assumed) // Display type - only define if RPi display // Only define one driver, the other ones must be commented out // Some displays support SPI reads via the MISO pin, other displays have a single // #define TFT_SDA_READ // This option is for ESP32 ONLY, tested with ST7789 and GC9A01 display only // For ST7735, ST7789 and ILI9341 ONLY, define the colour order IF the blue and red are swapped on your display // #define TFT_RGB_ORDER TFT_RGB // Colour order Red-Green-Blue // For M5Stack ESP32 module with integrated ILI9341 display ONLY, remove // in line below // #define M5STACK // For ST7789, ST7735, ILI9163 and GC9A01 ONLY, define the pixel width and height in portrait orientation // For ST7735 ONLY, define the type of display, originally this was based on the // #define ST7735_INITB // If colours are inverted (white shows as black) then uncomment one of the next // #define TFT_INVERSION_ON // ################################################################################## // If a backlight control signal is available then define the TFT_BL pin in Section 2 #define TFT_BL 32 // LED back-light control pin // We must use hardware SPI, a minimum of 3 GPIO pins is needed. // ###### 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_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 //#define TFT_SPI_OVERLAP // In ESP8266 overlap mode the TFT chip select MUST connect to pin D3 // ###### EDIT THE PIN NUMBERS IN THE LINES FOLLOWING TO SUIT YOUR ESP32 SETUP ###### // For ESP32 Dev board (only tested with ILI9341 display) #define TFT_MISO 19 // For ESP32 Dev board (only tested with GC9A01 display) //#define TFT_MOSI 15 // In some display driver board, it might be written as "SDA" and so on. #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 // ###### EDIT THE PINs BELOW TO SUIT YOUR ESP32 PARALLEL TFT SETUP ###### // The library supports 8 bit parallel TFTs with the ESP32, the pin // Parallel bus is only supported for the STM32 and ESP32 // Tell the library to use 8 bit parallel mode (otherwise SPI is assumed) // The ESP32 and TFT the pins used for testing are: //#define TFT_WR 4 // Write strobe control pin - must use a pin in the range 0-31 //#define TFT_D0 12 // Must use pins in the range 0-31 for the data bus // ###### EDIT THE PINs BELOW TO SUIT YOUR STM32 SPI TFT SETUP ###### // The TFT can be connected to SPI port 1 or 2 //#define TFT_SPI_PORT 2 // SPI port 2 maximum clock rate is 27MHz // Can use Ardiuno pin references, arbitrary allocation, TFT_eSPI controls chip select //#define TFT_RST -1 // Set TFT_RST to -1 if the display RESET is connected to processor reset // ################################################################################## // Comment out the #defines below with // to stop that font being loaded #define LOAD_GLCD // Font 1. Original Adafruit 8 pixel font needs ~1820 bytes in FLASH // Comment out the #define below to stop the SPIFFS filing system and smooth font code being loaded // ################################################################################## // Define the SPI clock frequency, this affects the graphics rendering speed. Too // #define SPI_FREQUENCY 1000000 // Optional reduced SPI frequency for reading TFT // The XPT2046 requires a lower SPI clock rate of 2.5MHz so we define that here: // The ESP32 has 2 free SPI ports i.e. VSPI and HSPI, the VSPI is the default. // Comment out the following #define if "SPI Transactions" do not need to be // Transaction support is needed to work with SD library but not needed with TFT_SdFat // Transactions are automatically enabled by the library for an ESP32 (to use HAL mutex) // #define SUPPORT_TRANSACTIONS |
The User_Setup.h looks fine. You can try this example from the TFT_eSPI library: https://github.com/Bodmer/TFT_eSPI/tree/master/examples/480%20x%20320/TFT_Rainbow480 If that also doesn't work you know it has something to do with your board, and not the code. It seems to be "hanging" on drawing the splash screen to the screen. I would try and reflow/resolder the connections to the screen and the ESP32. Giving extra special attention to pins 2,4,15,18,19, and 23. And also the data pins on the screen. |
Ok just reflowed it no luck and tried a seperate complete pcb and same issue |
is there a way to test the screen to ensure me they sent me the correct screen that ii purchased? |
Yes, you can connect everything using breadboard wires, without the PCB. Also the example is a way to test things. |
how do i know that my screen runs on that driver? |
I assume this issue is resolved after so many months, so closing it. |
Hi Dustin,
love the design and the idea.
I bought all the products you recommended, pcb from pcbway ILI9488 screen and ESP32-WROOM-32D and ive followed your youtube tutorial https://www.youtube.com/watch?v=s2X4BQ9VmEU&t=515s&ab_channel=DustinWatts.
I've got an issue which im sure is on my end with my config.
I have a white screen it strobes a little bit my user_setup.h is exactly as the video any suggestions on how to fix?
The text was updated successfully, but these errors were encountered: