Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Qt/Discussion/Qt General/Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy)./List of Posts
Forum Topic - Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).: (8 Items)
   
Update
Magnus Lovdahl
03/19/2012 10:21 AM
post92177
Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Hello,

I have a 'AM335x EVM board' and have downloaded the BSP “Texas Instruments AM335x EVM” project. I use QNX 6.5.0 and 
Momentics 4.7.0.

I have downloaded a simple QT application (qtEasy) that I have compiled and running in Momentics. (http://community.qnx.

com/sf/go/projects.qt/discussion.general.topc20245).

I see that the application starts up and showing the image. My problem is that I can see the mouse pointer at the screen

 but I cannot move it, either with the mouse or the touch screen. Before I start the QT application I have started the 
“devu-mouse &” and I see the console window showing “QQnxMouseHandler: connected” for the QT application in 
Momentics. Also I am not able to start the touchscreen driver.

When I remove the mouse the console is showing: 
QQnxScreen: Attached to Device, number of displays: 1
QQnxScreen: Attached to Display 0, resolution 800x480, refresh 60 Hz
QQnxMouseHandler: connected. 
QQnxMouseHandler: Unable to read from socket (No such device)
QSocketNotifier: Invalid socket 12 and type 'Read', disabling.. 

Should I be able to use the mouse or touchscreen for this QT application?
What could I have missed?

Regards

Magnus
Dennis Kellly
03/19/2012 10:56 AM
post92181
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
>>>Should I be able to use the mouse or touchscreen for this QT application?
Most definitely.

>>>Before I start the QT application I have started the 
“devu-mouse &” and I see the console window showing “QQnxMouseHandler: connected” for the QT application in 
Momentics. Also I am not able to start the touchscreen driver.

Assume you want to get the mouse working first.

If you run "pidin ar", you need to see these components running for input...

io-usb -duhci -dohci -dehci
io-hid -d usb /dev/io-usb/io-usb  (assuming usb mouse and keyboard)

(Do not start devu-mouse.)

Then - most importantly - you need to start devi-hid with "-Pr"  BEFORE starting Qt app.  Since the keyboard will no 
longer work, you should to do this (and starting the app) from a telnet or serial session...

/usr/photon/bin/devi-hid -Pr mouse kbd

You will need to make sure the shell variables are set before starting "cEasy -qws".

# export QWS_DISPLAY=qnx
# export QWS_KEYBOARD=qnx
# export QWS_MOUSE_PROTO=qnx

That should be it!

Dennis
Magnus Lovdahl
03/19/2012 11:17 AM
post92182
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Hello and thanks for the support..

This is what I got when I run "pidin ar"
# pidin ar
     pid Arguments
       1 procnto-instr -v
       2 slogger
       3 pipe
       4 devc-seromap -e -F -b115200 -c48000000/16 0x44E09000^2,72
       5 devb-mmcsd-jacinto5 cam blk automount=hd0t12:/fs/sd0 mmcsd verbose=5,ioport=0x48060100,irq=64,ioport=0x49000000
,dma=24,dma=25
       6 i2c-omap35xx-j5 -i 70 -p0x44E0B000
       7 i2c-omap35xx-j5 -i 71 -p0x4802A000
       8 i2c-omap35xx-j5 -i 30 -p0x4819C000
    8201 dumper
    8202 io-usb -vvv -d dm816x-mg ioport=0x47401400,irq=18 -d dm816x-mg ioport=0x47401c00,irq=19
    8203 devb-umass cam pnp
    8204 io-audio -vv -d mcasp-j5_aic3106 mcasp=1,i2c_dev=1,i2c_addr=0x1B,mclk=12000000
    8205 io-display -dvid=0,did=0
    8206 devb-ram ram capacity=8192
   28687 io-pkt-v4-hc -dam335x deviceindex=0
   32784 dhcp.client -i dm0
   45073 devc-pty
   45074 qconn port=8000
   45075 sh
   45076 pidin ar

Also I dont have the "devi-hid", actually I dont have the bin directory in "/usr/photon/".
See picture

/Magnus
Attachment: Image pic.jpg 299.07 KB
Dennis Kellly
03/19/2012 11:39 AM
post92183
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Well the out-of-the-box bsp is not setup to do Qt.  BSP's are "starting points" that you modify to get what you want.  
For example, you need to add the Qt libraries - which I assume you already did.

>>>8202 io-usb -vvv -d dm816x-mg ioport=0x47401400,irq=18 -d dm816x-mg ioport=0x47401c00,irq=19
Probably right (the io-usb line in my post is for x86).

You need ...
/proc/boot/io-hid -d usb /dev/io-usb/io-usb
and
/proc/boot/devi-hid -Pr mouse kbd

The fact that they are not present, just means you need to add them - to /proc/boot.  These components are present in 
your 6.5 installation.  In the IDE, right-click on "Binaries" and select "Add binary" to add them.

Eiither start io-hid and devi-hid from the .bsh script to go directly to Qt - or run them manually from a shell before 
you start cEasy.
Magnus Lovdahl
03/20/2012 5:28 AM
post92198
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Hello again,

I still have problems getting the mouse up and running.
I have added io-hid and devi.hid, also a couple of dlls that was needed.
Now I have this problem when I run "devi-hid -v -Pr mouse kbd"
Do you have any idea what's wrong?

#
# io-hid -d usb /dev/io-usb/io-usb
#
# devi-hid -v -Pr mouse kbd
Looking up mouse in module table

Process 49173 (devi-hid) terminated SIGBUS code=1 fltno=5 ip=0101d190(libc.so.3@_mmap2+0x98) mapaddr=0001d190. ref=
00000003
Bus error
# pidin ar
     pid Arguments
       1 procnto-instr -v
       2 slogger
       3 pipe
       4 devc-seromap -e -F -b115200 -c48000000/16 0x44E09000^2,72
       5 devb-mmcsd-jacinto5 cam blk automount=hd0t12:/fs/sd0 mmcsd verbose=5,ioport=0x48060100,irq=64,ioport=0x49000000
,dma=24,dma=25
       6 i2c-omap35xx-j5 -i 70 -p0x44E0B000
       7 i2c-omap35xx-j5 -i 71 -p0x4802A000
       8 i2c-omap35xx-j5 -i 30 -p0x4819C000
    8201 dumper
    8202 io-usb -vvv -d dm816x-mg ioport=0x47401400,irq=18 -d dm816x-mg ioport=0x47401c00,irq=19
    8203 devb-umass cam pnp
    8204 io-audio -vv -d mcasp-j5_aic3106 mcasp=1,i2c_dev=1,i2c_addr=0x1B,mclk=12000000
    8205 io-display -dvid=0,did=0
    8206 devb-ram ram capacity=8192
   28687 io-pkt-v4-hc -dam335x deviceindex=0
   32784 dhcp.client -i dm0
   45073 devc-pty
   45074 qconn port=8000
   45075 sh
   45076 io-hid -d usb /dev/io-usb/io-usb
   57365 pidin ar

/Magnus
Dennis Kellly
03/20/2012 9:09 AM
post92202
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Make sure these libraries are in /proc/boot or somewhere named in LD_LIBRARY_PATH variable.

Libraries needed for io-hid
            libhiddi.so.1      @78000000              32K  4096
            devh-usb.so        @78009000              16K  4096
            libusbdi.so.2      @7800e000              40K  8192

Libraries needed for devi-hid
            libgf.so.1         @78000000              96K  4096
            libhiddi.so.1      @78019000              32K  4096
Magnus Lovdahl
03/20/2012 9:40 AM
post92203
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
They are already added. Still same issue..

I read in post "http://community.qnx.com/sf/discussion/do/listPosts/projects.graphics/discussion.photon_microgui.
topc20567?pageSize=-1#post_post87404"
You input problems appears to be caused by mismatched binary files -- i.e. armle vs amrle.v7. In fact 6.5.0 has no devi-
hid for armle.v7. I recommend talking to your Sales Rep. about acquiring a v7 devi-hid version.
Could this be the reason?


By the way, what is the number after some libs meaning?
For example "libgf.so" vs "libgf.so.1"?

/Magnus
Dennis Kellly
03/20/2012 11:03 AM
post92206
Re: Mouse and TouchScreen problems with AM335x EVM board using the BSP and QT application (qtEasy).   
Your trap is indeed caused by the armle devi-hid.  See your sales rep for the armle-v7 version of devi-hid.

>>>By the way, what is the number after some libs meaning
GNU libraries append a digit to specify the dll version number.  Executables can load a specific version if they choose.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems