[BUG] MKS TFT32 L V3.0 Screen H Flip
stef-ladefense opened this issue · 13 comments
hi,
I just did a test on an MKS 32L V3.0 that I had in a drawer.
I simply took the following basic files:
config.ini
MKS_TFT28_V3.0.27.x.bin renames MKSTFT28.bin
folder TFT28
the MKS TFT32 shares the firmware of the MKS TFT28 and must therefore be named the same for the firmware update to work.
the update works until the end but the displays are mirrored horizontally and vertically at 180°.
at the end the touch adjustment procedure does not follow the inversions of the screen, it is therefore necessary to touch in the opposite diagonal.
I put the additional photos in the next post
I hope it will help to fix the firmware
Stéphane
Did you download the update files from the Master branch?
@radek8
it's MKS display and the .bin has 2 day, 2.15.2023 10;53 from master
Also try resetting the display with an empty reset.txt file
I applied without effect
it restarts on the reverse calibration
The problem will be that your display is not among the supported versions of MKS displays
yes but the MKS TFT32 V3.0 has the same hardware as the MKS TFT28 V3.0 so it shouldn't be very complicated to correct.
I will look at the sources and make the correction as soon as I have some time.
on the other hand the firmware for the MKS TFT35 does not work at all.
And I'm not the only one here having the problem.
MKS TFT 35 V1 uses
#define TFTLCD_DRIVER (ILI9488 | NT35310)
MKS TFT 28 V3 is used
#define TFTLCD_DRIVER ILI9325
You can try it
MKS_TFT32_V1_3
exactly the same problem.
so I cloned the sources and searched.
in fact, the H and V mirrors are not good, finally for this TFT32L.
the SS and GS bits must be identical and not inverted relative to each other.
ditto in the rotation routine.
I posted the changes to my github for testing.
stef-ladefense@b0a717d
I'll do a PR when others have tested it too.
Stef
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.