-
Notifications
You must be signed in to change notification settings - Fork 77
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
ILI9342 driver #150
Comments
Hi, Where did you find this screen? in the m5stack? I have made a working driver for it. I'll send a pull request. edit: Sorry I did not find this issue sooner! |
Well in fact I did it before and it is still not pushed upstream. Do you have this problem? #100 |
Yes, it was for the M5stack, and yes it was a blank area as problem #100. I managed to eventually modify the ILI9341 driver and create an ILI9342 driver that works. |
I updated my fork with my code. Match is very close, except for UCG_VARX and UCG_VARY. Not sure which is right (?) |
I like the ILI9342 name instead of my use of m5stack. I had doubt the ILI9342 was the chip name for the portrait screen but I see new docs now and it seem to be the right choice. I had a look at the differences:
But for UCG_VARY:
I have no idea what the differences are. These are the definitions from ucg.h
I have used the same values in varx and vary by symmetry, what was your reason to use s=0 and a=0 instead? |
I reversed what was used in the 9341 since X is swapped with Y in the 9342. Pure guess at this time, and display works OK, so I didn't check further.
|
OK, makes sense, and thanks. I hope your driver gets integrated. It is frustrating that this project is not maintained anymore. |
I have been trying to modify the ILI9341 driver to make an ILI9342 driver but I am not successful so far. There is a blank area on the right when in landscape mode and an blank area at the top when rotated 90 deg. Can't seem to find a register that would explain this offset. Would you have time to generate a proper ILI9342 driver ?
The text was updated successfully, but these errors were encountered: