Closed jpasqua closed 6 months ago
The code is hard-coded for a 320 by 240 display. I would assume that the display you are using may have different hardware as well as a different screen resolution. No surprise that it will not boot.
This display is also 320x240 - just larger pixels. I've got it working with lvgl and the screen works well. However, the particular model I got has a capacitive touch screen rather than resistive. It uses the Touch_GT911 library rather than XPT2046_Touchscreen. It may not be worth the bother to support this since there is also a restive touch version of the 3.2" display which (as far as I can tell) uses the XPT2046. I've ordered a couple of those and will report my findings when they arrive. At that point I will probably just close this issue.
This display is also 320x240 - just larger pixels. I've got it working with lvgl and the screen works well. However, the particular model I got has a capacitive touch screen rather than resistive. It uses the Touch_GT911 library rather than XPT2046_Touchscreen. It may not be worth the bother to support this since there is also a restive touch version of the 3.2" display which (as far as I can tell) uses the XPT2046. I've ordered a couple of those and will report my findings when they arrive. At that point I will probably just close this issue.
Generally the capacitive screens are nicer to use than resistive screens. Have you noticed the capacitive screen on this budget device to still better than a resistive touch?
How about the 2,4" but with capacitive touch? Will it work?https://a.aliexpress.com/_msNFSXW
I will close this as ATM I will only support one screen... You can fork and make the needed changes... But I have not all the devices or the time to support more...
Feature Description
There is a board with a 3.2" display which is very similar to the 2.8" display which is recommended. It would be nice to support this slightly larger board. I'm happy to provide sample boards if useful.
Justification
Slightly easier to read and tap than the smaller display, but the same resolution so layouts need not change.
Suggested Implementation (if you have one)
Flashing the existing code causes a boot loop after a core dump. This happens after the log message:
appears.
Screenshots or Examples (if applicable)
Sample from the log (this repeats):