-
Notifications
You must be signed in to change notification settings - Fork 29
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
display initialization problem #8
Comments
In
It seems strange to me that TFT_MISO, TFT_CS and TFT_RST. are all defined -1 (does that mean "undefined?) and I wonder what that commented block of alternative definitions is all about... but on the other hand, this seems to align with the pinout description here. |
Another observation: what seems to help is to power it on while connected to usb c power and then pressing the reset button. This method does not help without the device being plugged in. So maybe the small battery does not provide enough power for the (tiny) display? But on the other side, the grey screen happens also while powering on when plugged in sometimes... |
Hello, I had the same problem, the solution is simple. Open the library TFT_GC9D01N.cpp and disable the following lines int TFT_GC9D01N_Class::begin() Greetings from Bogota Col. |
Thank you, @alejovargas78 ! Removing my previous reply, as it was completely unrelated (and created a separate issue for this)... When I failed to initialize the original display, I tried to attach a bigger one, which would even be better for my project. Now I will try the suggested approach to get the original display working reliable, which would also be great! |
Unfortunately, I have the same result/problem with the adjustments in the library, still thanks for the suggestion! |
|
Sometimes the display does not initialize properly, it will only show some thin lines or a light grey background and it can't be written to by the program (apart from the display not showing anything the program works fine). Reseting the device by on/off or the reset button helps sometimes after a few tries, sometimes it seems to need "off-time", but I could not really figure out when it does not work and what gets it back on track. It is really unreliable like this. This happens on both of my T-keyboards.
What might cause this weirdness?
I found that when I enabled core debug level, at
TFT_099.begin();
I get this log:Could this be the cause of it? But those error messages will also be in the logs when it works. No idea how to debug this any further... :(
Any help appreciated, thanks and cheers!
The text was updated successfully, but these errors were encountered: