To other that may be watching this thread. The driver is working,
it was a problem with the custom hardware I was using.
“Mario Charest” <mcharest@zinformatic.com> wrote in message
news:9kp8ia$a9a$1@inn.qnx.com…
“Alex Chapiro” <> achapiro@qnx.com> > wrote in message
news:9kp7t7$gni$> 1@nntp.qnx.com> …
Does fd module also fails?
Yes they both fail.
With the uart module, there is no receive interrupt.
I’m using quite ancient AccuTouch 2210MX 0480499 with external power
supply.
“Mario Charest” <> mcharest@zinformatic.com> > wrote in message
news:9kp3sp$7rp$> 1@inn.qnx.com> …
“Alex Chapiro” <> achapiro@qnx.com> > wrote in message
news:9kp314$duo$> 1@nntp.qnx.com> …
What I wrote in my previous posting, is incorrect. uart input module
also
works fine. Could it be a difference in ELO controllers we are
using?
Some time ago there was also a problem with location of calib file
(should
be in /etc/system/trap directory). Could it be your case?
I’m starting the driver with 8 -v and it does show that it finds the
calib
file.
I don’t know what controler I’m working with. I’ll see if I can find
out.
Alex Chapiro
“Mario Charest” <> mcharest@zinformatic.com> > wrote in message
news:9kp0s3$5tt$> 1@inn.qnx.com> …
“Alex Chapiro” <> achapiro@qnx.com> > wrote in message
news:9kovku$bue$> 1@nntp.qnx.com> …
I tried devi-elo on 6.1… It works good if uses fd -d/dev/ser1.
Try
with
uart device module failed. There were positevely no changes in
uart8250.c
since 6.0. It takes me a short while to figure out what the
problem
is,
apologize for delay.
“Mario Charest” <> mcharest@zinformatic.com> > wrote in message
news:9kmr1r$oq9$> 1@inn.qnx.com> …
The devi-elo executable with 6.1 doesn’t work for me.
I took the ddk in an attempt to figure out what is wrong.
I still haven’t figure out what but so far I found:
First devi/lib/nto/x86/a.o/Makefile is missing.
There is a problem with uart module (ser8250.c).
uart_reset() was making use of IpCoid variable.
The variable wasn’t initialised. I beleive devi_get_coid()
should be use instead.
That is correct. Will be fixed in next release.
After changing this option driver works with uart device module
as
well,
but
not stable. I need some time to fix a problem.
If I rebuild the 6.0 ddk source on 6.1 it doesn’t
work either. But the 6.0 ddk source built on
6.0 runs fine on the 6.1.
It seems the touch screen isn’t initialize properly,
as it doesn’t send anything when pressed.
In my case it is not correct. It works perfect via fd and at
leat
works
for
a while via uart. Means that initialization works correct.
Here is why I came to that conclusion. If I slay the 6.0 driver
and then start qtalk and press the touchscreen, qtalk will
receive data. However if I try the 6.1 driver (which
doesn’t work) then kill it and start qtalk it will not receive
data. The touch screen appears to be dead. I assume it
hasn’t been initialized properly.
Since you say it should be working I will resume
my investigation. Thanks.
- Mario
Thank you for cooperation,
Alex Chapiro
\