Qt-embedded-interest Archive, February 2007
serial touch screen in qt-embedded-3.3.5
Message 1 in thread
hi everyone,
i have a serial touch screen interfaced to /dev/ttyS1 of BF537-EZKIT . how to enable it in qt-embedded-3.3.5 ?
in the configure option i saw options for USB touch screens (touch screens connected to /dev/input/event0).but there were no options for serial touch screens. i gave "-qt-mouse-linuxtp" in the configure option and export the environment variables as follows:
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_CONFFILE=/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts
export TSLIB_TSDEVICE=/dev/ttyS1.
and
export QTDIR=/usr/local/qt-embedded
export QWS_MOUSE_PROTO=linuxtp:/dev/ttyS1
when i execute a qt application , the touch screen did not work and the mouse pointer disappears the moment i touch the touch screen. the following error is displayed :
"Could not read calibration: /etc/pointercal".
can any provide me suggestions or solutions for this ?
---------------------------------
Here?s a new way to find what you're looking for - Yahoo! Answers
Message 2 in thread
Hello,
Did you restart qtopia before attempting to run the application? I believe the touchscreen must be calibrated by qtopia before you can use it.
Check to see that /etc/pointercal exists before you run the application with:
ls -l /etc/pointercal
sdjf
saravanan sar <sar_van81@xxxxxxxxxxx> wrote:
> when i execute a qt application , the
> touch screen did not work and the
> mouse pointer disappears the moment i
> touch the touch screen. the following
> error is displayed :
> "Could not read calibration:
> /etc/pointercal".
> can any provide me suggestions or
> solutions for this ?
To unsubscribe - send "unsubscribe" in the subject to qt-embedded-interest-request@xxxxxxxxxxxxx
Message 3 in thread
hi,
yeah i found that the file was not there.can you say me how to caliberate the serial touch screen. ?
i found in net that we need to caliberate the touch screen using tslib package. in my case i cannot use that as everything in that depends on "/dev/input/event0" and since the touch screen i'm using is serial based,connected to "/dev/ttyS1".
thanks for your reply,
saravanan
---------------------------------
Here?s a new way to find what you're looking for - Yahoo! Answers
Message 4 in thread
It should happen automatically when qtopia starts up, but I don't know how to make it happen. On my Zaurus, if there is no calibration file, it gives me the calibration GUI when I do a reboot (hard reset).
I think you need to find a way to use tslib. I would guess there must be a way to equivalence /dev/input/event0 and /dev/ttyS1 in qpe.sh, but it may be above my current skills. I don't know if a symlink between /dev/input/event0 and /dev/ttyS1 would be okay, as event0 may already be defined. But if you don't have a /dev/input/event0, you might try that instead. Since you have already defined /dev/ttyS1:
ln -s /dev/ttyS1 /dev/input/event0
You might also look for clues about how to make sure qtopia recognizes any serial input device in 3.3.5.
Also, did you search:
/dev/input/event0 serial OR /dev/ttyS1
BTW, the calibration is based on a complex algorithm. Mine on an qtopia embedded 1.5.0 device looks like:
21114 0 298074 0 15340 631500 65536
sdjf
saravanan sar <sar_van81@xxxxxxxxxxx wrote:
>> hi,
> yeah i found that the file was not
> there.can you say me how to
> caliberate the serial touch screen. ?
> i found in net that we need to
> caliberate the touch screen using
> tslib package. in my case i cannot
> use that as everything in that
> depends on "/dev/input/event0" and
> since the touch screen i'm using is
> serial based,connected to
> "/dev/ttyS1".
> thanks for your reply,
> saravanan
To unsubscribe - send "unsubscribe" in the subject to qt-embedded-interest-request@xxxxxxxxxxxxx
Message 5 in thread
hi,
i tried linking as follows:
root:~> ln -s /dev/input/event0 /dev/ttyS1
ln: /dev/ttyS1: File exists
root:~>
i tried this also:
root:~> ln -s /dev/ttyS1 /dev/input/event0
ln: /dev/input/event0: File exists.
but nothing is working. also in qt-embedded. i think we should caliberate before executing the application. do u have the file ? if so can you send me that ?
---------------------------------
Here?s a new way to find what you're looking for - Yahoo! Answers
Message 6 in thread
On 2/20/07, saravanan sar <sar_van81@xxxxxxxxxxx> wrote:
> hi,
>
> i tried linking as follows:
>
> root:~> ln -s /dev/input/event0 /dev/ttyS1
> ln: /dev/ttyS1: File exists
> root:~>
>
> i tried this also:
> root:~> ln -s /dev/ttyS1 /dev/input/event0
> ln: /dev/input/event0: File exists.
Please do this:
ls -l /dev/input/event0 /dev/ttyS1
> .... i think we should caliberate
> before executing the application. do u have the file ? if so can you send me
> that ?
I agree you must calibrate before running the app. But that
calibration is not a separate program, it is part of the qpe startup
stuff AFAIK. And I have a very different version, 1.5.0.
We just had discussion about creating the /et/pointercal file at
oesf.org. I suggest you look at posts starting with #22 in the thread
at:
http://www.oesf.org/forums/index.php?showtopic=21766&st=22
You can follow the instructions there if you want to create the file
without it being a true calibration. I sent you the contents of my
/etc/pointercal in an earlier post. It is the result of
calibrating, not an executable. But it isn't likely to work
properly on your different device. That's the point of
calibration...it varies depending on the conditions.
I would expect that someone else on this list knows more than I do
about this but it's a short holiday week in the U.S. and some people
may be away.
sdjf
To unsubscribe - send "unsubscribe" in the subject to qt-embedded-interest-request@xxxxxxxxxxxxx
Message 7 in thread
hi i tried that also
root:~> ln -l /dev/input/event0 /dev/ttyS1
ln: illegal option -- l
BusyBox v1.00 (2007.02.17-00:43+0000) multi-call binary
Usage: ln [OPTION] TARGET... LINK_NAME|DIRECTORY
Create a link named LINK_NAME or DIRECTORY to the specified TARGET
You may use '--' to indicate that all following arguments are non-options.
Options:
-s make symbolic links instead of hard links
-f remove existing destination files
-n no dereference symlinks - treat like normal file
saravanan
---------------------------------
Here?s a new way to find what you're looking for - Yahoo! Answers
Message 8 in thread
No, the command is the list, not the symlink command:
ls -l /dev/input/event0 /dev/ttyS1
This will tell you about what the files are, their sizes, permissions.
My /var/log/dmesg includes the following, making me think you need to make sure you have a driver for the touchscreen. I don't know if "ucb" is really "ucb" or a typo in the code, but you may need a serial driver, although I have heard that if you define it as a qtopia input method, no driver is needed:
touch adj= 18305,24712,-1703936,-2883584
ucb1200 touch screen driver initialized
Unless something really obvious pops up when you do the list command, I really think we need to wait for someone who knows this stuff better to give you advice about what to do next to get qtopia to recognize the touchscreen and calibrate it.
sdjf
saravanan sar wrote:
> hi i tried that also
> root:~> ln -l /dev/input/event0 /dev/ttyS1
> ln: illegal option -- l
> BusyBox v1.00 (2007.02.17-00:43+0000)
> multi-call binary
> Usage: ln [OPTION] TARGET... LINK_NAME|DIRECTORY
To unsubscribe - send "unsubscribe" in the subject to qt-embedded-interest-request@xxxxxxxxxxxxx
