Continuation of lcd display error

This is an continuation of @Graphite s problem
27 Replies
…Aarav…
…Aarav…OP16h ago
I recommend checking if the solder is good. If you have the budget, maybe buy an esp32, and check if you can find the driver in the webpage where you bought the lcd from
Fireguy9143
Fireguy914316h ago
The TFT on wokwi is different from the 1.77 tft Graphite is using. I made a counter to display in the loop section, and it's upside down and backwards but it works.
//intialize a count variable at the top
int count=0;

void loop() {

for(count=0; count<100; count++){
tft.setTextColor(ST7735_WHITE);
tft.setTextSize(0);
tft.setCursor(30,90);
tft.println(count);
delay(500);
tft.setTextColor(ST7735_BLACK);
tft.setTextSize(0);
tft.setCursor(30,90);
tft.println(count);
}
}
//intialize a count variable at the top
int count=0;

void loop() {

for(count=0; count<100; count++){
tft.setTextColor(ST7735_WHITE);
tft.setTextSize(0);
tft.setCursor(30,90);
tft.println(count);
delay(500);
tft.setTextColor(ST7735_BLACK);
tft.setTextSize(0);
tft.setCursor(30,90);
tft.println(count);
}
}
…Aarav…
…Aarav…OP16h ago
I gtg in an few mins @Graphite if you have time, @Fireguy9143 might have found an solution for you The thing is, the code works in like the first second. So it might be a clock error, or communication SPI/I2c error. The wrong pins might be used, the arduino might be fried, or the wrong or corrupted driver might have been used @Graphite please share the place you got this screen for (the link) I gotta go
Fireguy9143
Fireguy914316h ago
If the display works on reset, it means the driver is working even if it "shouldn't". This seems like it must be a problem executing the code. I think it would be good to check the loop and see if it runs, and check the voltages on the pins.
…Aarav…
…Aarav…OP16h ago
Is this an hardware or software problem? If it’s code , then I think the next strip should be completely clearing the clash like I shared earlier *flash not clash 1. Open avrdude Folder Go to: C:\Program Files (x86)\Arduino\hardware\tools\avr\bin This folder contains avrdude.exe. ⸻ 2. Open Command Prompt in that Folder • Hold Shift + Right-Click inside the folder. • Select Open PowerShell window here (or Command Prompt). ⸻ 3. Run Erase Command Replace COM3 with your Arduino’s port: .\avrdude -c arduino -p atmega328p -P COM3 -b 115200 -e This erases the entire flash memory, including the bootloader. ^ to clear flash, but you would have to completely install the uploader which idk how to do
AnonEngineering
AnonEngineering16h ago
i would play with the bootloader as an absolute last resort if you can upload and run Blink the bootloader is OK
AnonEngineering
AnonEngineering16h ago
what is this all about?
No description
…Aarav…
…Aarav…OP16h ago
This is @Graphite s problem and he’s sleeping rn Wait that’s prob the problem And an cooked board
…Aarav…
…Aarav…OP15h ago
@AnonEngineering
No description
Fireguy9143
Fireguy914315h ago
Maybe found a major disconnect. In the wokwi there is only the larger TFT, and it has: 1 VCC => 5v 2 GND => virtual Nano GND 3 CS => Chip select virtual pin 10 4 RST => RESET virtual pin 8 5 D/C =>DATA/COMMAND virtual pin 9 6 MOSI =>Master out/Slave In virtual pin 11 7 SCK =>Serial Clock virtual pin 13 8 LED => 3.3V 9 MISO (which I didn't use) And the above setup worked with the code as it was written/provided... On the pic that Graphite sent, it has: 1 GND => Nano GND 2 VCC => 5V 3 SCK => PIN D8 (Maybe should be A5?) 4 SDA => PIN D12? (Maybe should be A4?) 5 RES =>RESET PIN 13? (Maybe should not be the MOSI variable in the code?) 6 RS =>Data/Command PIN 9? 7 CS => CHIP SELECT PIN 10? 8 LEDA =>3.3V? 9 LEDA 10 GT_CS 11 GT_SI 12 GT_SO 13 GT_SCL 14 GND It looks like maybe your TFT is mixing up the clock and reset pins?
AnonEngineering
AnonEngineering15h ago
the story continues, it's going to turn out to be one or more of the above issues 🙂
Fireguy9143
Fireguy914315h ago
Well, it's been an interesting puzzle. I hope we hear back on what's what.
…Aarav…
…Aarav…OP15h ago
It’s very interesting…
DarwinWasWrong
DarwinWasWrong15h ago
No description
DarwinWasWrong
DarwinWasWrong15h ago
The OP "confirmed" the wiring.
Fireguy9143
Fireguy914315h ago
Yeah, I know. My chart is best guess from the overlapping wires
…Aarav…
…Aarav…OP15h ago
Is it hardware or software?
AnonEngineering
AnonEngineering15h ago
my bet is wiring of some sort
…Aarav…
…Aarav…OP15h ago
K OP has tried multiple different codes
AnonEngineering
AnonEngineering15h ago
that whole reset business is suspect
…Aarav…
…Aarav…OP15h ago
It’s probably an Brocken clock or bad clock Or bad comms With spi/i2c Clear pics of wirring and an explanation to this could help 🤣
DarwinWasWrong
DarwinWasWrong15h ago
I do not believe the OP removed the wires and redid them as requested. the space/time between request and confirmation was too short, resulting in a reset of beliefs, from a watchdog timer
…Aarav…
…Aarav…OP14h ago
True He needs to remove the soldered jumper shorting the +-
DarwinWasWrong
DarwinWasWrong14h ago
there isnt anything on that rail
…Aarav…
…Aarav…OP14h ago
That jumper is just an ticking time bom* For future projects he might forget
DarwinWasWrong
DarwinWasWrong14h ago
Dont be so short. (joke)
…Aarav…
…Aarav…OP13h ago
(I am short) I’m 5 2 (To be fair I’m 13) :uno:

Did you find this page helpful?