Skip to content
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

AC320005-5 TouchScreen-LCD resolution correlation #1

Open
LuisCRSousa opened this issue Sep 21, 2020 · 14 comments
Open

AC320005-5 TouchScreen-LCD resolution correlation #1

LuisCRSousa opened this issue Sep 21, 2020 · 14 comments

Comments

@LuisCRSousa
Copy link

LuisCRSousa commented Sep 21, 2020

I've built the EGT example following the build steps from Buidroot-External-Microchip with sama5d27_som1_ek_graphics_defconfig and I notice that the touch screen are not configured with the same resolution as the LCD.
I've taken a photo showing the problem using the whiteboard app. The blue lines is where touch is detected.
IMG_1500

@LuisCRSousa
Copy link
Author

@ldesroches
Copy link
Contributor

Hi,
Thanks for reporting the issue. I'll have a look.

@ldesroches
Copy link
Contributor

I can't reproduce it with the linux4sam 2020.04 Buildroot graphics image. Have you try with this image too?
Did you try with other applications? For instance evtest, can you reach 800,480?

@LuisCRSousa
Copy link
Author

I can't reproduce it with the linux4sam 2020.04 Buildroot graphics image. Have you try with this image too?
Did you try with other applications? For instance evtest, can you reach 800,480?

I've just tested the same image with the AC320005-4 4.3'' display/touch (480x272) and it works as designed with that display.
Both seems to be detected correctly by uboot, i.e 4.3'' is detected as pda=4301B and 5'' as pda=5000.

Can you provide the link for the image taht you are using?

@ldesroches
Copy link
Contributor

@LuisCRSousa
Copy link
Author

Here is the image: https://files.linux4sam.org/pub/demo/linux4sam-2020.04/linux4sam-buildroot-sama5d27_som1_ek-graphics-2020.04.img.bz2

Same problem with 5'' display/touch with that image

@ldesroches
Copy link
Contributor

And with something else than an EGT application? There is little chance of being related to EGT. You should have evtest which reports the coordinates.

@LuisCRSousa
Copy link
Author

And with something else than an EGT application? There is little chance of being related to EGT. You should have evtest which reports the coordinates.

With evtest these are the closest touch points I got at the 4 corners (x,y):

Top-Left (5, 150)
Top-Right (824,142)
Bottom-Right (817, 587)
Bottom-Left (10, 582)

@ldesroches
Copy link
Contributor

This is what I have:
Top-Left (5, 5)
Bottom-Right (798, 474)

Any chance you get another 5" display to check if it's a hardware issue or not?

@LuisCRSousa
Copy link
Author

This is what I have:
Top-Left (5, 5)
Bottom-Right (798, 474)

Any chance you get another 5" display to check if it's a hardware issue or not?

I have another one brand new that I can test. Will report the results today

@LuisCRSousa
Copy link
Author

This is what I have:
Top-Left (5, 5)
Bottom-Right (798, 474)
Any chance you get another 5" display to check if it's a hardware issue or not?

I have another one brand new that I can test. Will report the results today

We just tested a brand new 5'' display with a SAMA5D27 WLSOM1 EV and at91.com buildroot image.
Exact same result.

There's anything more that we can test?

MicrosoftTeams-image

@noglitch
Copy link
Member

Hi @LuisCRSousa,
I don't know if it will help but could you post the entire boot log. We can then compare if something is different on our side.
Thanks, best regards,
Nicolas

@ehristev
Copy link

Can I ask you to upload a photo of the backside of your display. It may be that your display is different from ours, this will help us compare.

Thanks !

@LuisCRSousa
Copy link
Author

LuisCRSousa commented Sep 28, 2020

Sorry fo the delay.

I've tested other external graphical library and the problem persisted. With that library I was able to map the input touch the following way and it worked:
X -> from(0, 831) to(0, 800)
Y -> from(106, 600) to(0, 480)

The problem could be the linux touch driver but I have no way how to test or debug it.

Hi @LuisCRSousa,
I don't know if it will help but could you post the entire boot log. We can then compare if something is different on our side.
Thanks, best regards,
Nicolas

File attached with boot log
boot log.txt

Can I ask you to upload a photo of the backside of your display. It may be that your display is different from ours, this will help us compare.

Thanks !

Image attached. We've bougth 2 of them last week.

IMG_1567

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants