Can not close window

[ko-hey]

Hi all

I'm using MCIMX6DL-SDP with Yocto Linux that provided from freescale.

In that situation, I can not close the window from touch pannel.

However, if I use a mouse that connect with USB, I can close it. (The button is like a attachment.)

I tried to re-calibration and reset but behavior does not change.

I can not understand the cause.

Please advise me!

Best Regards,

[CommunityBot · Accepted solution]

This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!

[daiane_angolini]

using evtest (i.e.) can you see if you can actually "click" over the X button?

It may be 2 problems:

calibration not working

exit not working

[ko-hey]

Hi Daiane & Yixing

Thank you for your response.

I checked a problem with using Terminal app that is in Yocto project.

The command is below.

$ evtest /dev/input/touchscreen

When I touched X button, some value are shown in terminal app. So I think touchscreen is work.

After that I retried a calibration with Calibration app. However, nothing was changed.

Finally, I checked a USB mouse behavior with a command as below.

It is no problem with a behavior of the USB mouse.

$ cat /dev/input/mice

Best Regards,

ko-hey

[daiane_angolini]

When you touch over the X (the X closer button), can the evtest return the right (x,y) values?

Or the (x,y) values are outside the X button?

And, additionally, take a look here http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-graphics/xinput-calibrator

on how to configure the calibration for your HW and your display

[ko-hey]

What is a correct value?

Some values are shown in display, when I touched the screen.

But I don't know whether the value is correct.

And I have a question about configuration method.

Can I use these commands to configure the calibration ?

xinput set-int-prop "eGalax Touch Screen" "Evdev Axis Calibration" 42060 2062 -8 -783544 1 1549 65536

xinput set-int-prop "eGalax Touch Screen" "Evdev Axes Swap" 8 0

[YixingKong]

Ko-Hey, if your issue is gone, please close the DI, otherwise please keep working with the engineers.

Thanks,

Yixing

[daiane_angolini]

the problem is exactly to find the right number to place in the conf file.

each panel has its own right number. you must to play around with your

[ko-hey]

Hi Daiane

Sorry for my late reply. I was on vacation until yesterday.

I understood each panel has its own value.

Which conf file do I check for find a correct value?

Addition to this, please let me know how to set a correct value.

I have a additional info.

When I touched a X button, below value was returned.

-------------- Report sync ------------

type 3 (Absolute), code 57 (Tracking ID), value 0

type 3 (Absolute), code 48 (Touch Major), value 1

type 3 (Absolute), code 53 (Position X), value 32176

type 3 (Absolute), code 54 (Position Y), value 288

-------------- Config sync ------------

Ko-hey

[daiane_angolini]

I have no idea ko-hey, I used the trial and error method.

[ko-hey]

Do you said that you don't know the location of the file?

If yes, please check to expert engineers.

If you tell me the file location, I will check the file too.

Also I would like to check your situation.

Was this problem occurred on your board?

[YixingKong]

Ko-Hey

There is no action for this isue for long time. If there is no issue, we will close this DI. If you still need help please kep commenting here.

Thanks,

Yixing

[daiane_angolini]

I´m sorry, I was unclear.

The file you should edit is the one I have already linked in this thread.

the *value* to put into the file is up to you to find out because it depends on your hardware piece.

Let me try to explain it again.

You hardware must be calibrated, because each hardware is unique.

You calibrate it using the calibration app.

But sometimes the base values is so far from real that even the calibration app can actually calibrate your panel. So you need to add *by hand* some guessing numbers. The example for this is in the link I have already sent to you.

However, I don't know if your problem is the calibration, because the very first question you made is regarding not closing the windows. I guessed it *may* be the calibration, but I cannot be sure.

Kernel is not, because you have already tested evtest and kernel is returning events.

So, if this is a calibration error, maybe you can get better help from the calibration app community

If this is really a QT error (are you using QT?) maybe you should contact QT community.

You asked for advises, I tried to help the in my best way. I'm sorry if this was not enough. The way I made the file I sent you the link, worked for me. It was a long time ago (2013-03-30) how you can see in meta-fsl-arm - Layer containing Freescale ARM hardware support metadata

[YixingKong]

The request has been assigned.

Thanks,

Yixing