BeagleBoneBlack QT building problem

[srkn]

Hi everyone,
I need your help. I have a beaglebone black and 3.5″ LCD display. I carried out every step on http://visualgdb.com/tutorials/beaglebone/qt-embedded/.
everything is fine except step 21.

In step 21 I am building example and then application (Hello World) is sent beaglebone black in tmp directory.
Then I am running app using putty (let say tmp# ./example1 -qws).
App is showing the same screen in step 20 on LCD (Hello World Button)
Problem is touchscreen dont work.

But in step 20 when I was debugging the app (Hello world), touchscreen was working.
I make the same settings in step 21.

İf you have any idea, please help me.
thank you by now.

Serkan

[support]

Hi,

This probably happens because the default session has some environment variables that point Qt to the touch screen. Please try the following to diagnose it:
1. Run your app from an SSH session (e.g. using SmarTTY or open it in VisualGDB). Ensure that the screen is not working.
2. Compare the environment variables in the SSH session and environment variables in the console session (the output of env).
3. Try setting relevant variables in the SSH session. See if this fixes the problem.

Once you figure out the correct variables, please specify them in the VisualGDB Project Properties so that VisualGDB can set them automatically.

[srkn]

Hello bazis,
Thanks for your quick reply. As you said, I checked environment variables. if I did correctly, I couldnt find any solution.

this is my steps.

First, My beaglebone black is in console screen, than I use env command using smartty

this is the output of env
TERM=xterm
SHELL=/bin/sh
SSH_TTY=/dev/pts/0
USER=root
QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
PWD=/home/root
EDITOR=/bin/vi
NODE_PATH=/usr/lib/node_modules
PS1=u@h:w$
SHLVL=1
HOME=/home/root
LOGNAME=root
SSH_CONNECTION=192.168.7.1 6875 192.168.7.2 22
TSLIB_TSDEVICE=/dev/input/touchscreen0
DISPLAY=localhost:10.0
_=/usr/bin/env

Second, beaglebone is running app while debugging, than I use env command using smartty (now touchscreen is working)

this is the output of env
TERM=xterm
SHELL=/bin/sh
SSH_TTY=/dev/pts/0
USER=root
QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
PWD=/home/root
EDITOR=/bin/vi
NODE_PATH=/usr/lib/node_modules
PS1=u@h:w$
SHLVL=1
HOME=/home/root
LOGNAME=root
SSH_CONNECTION=192.168.7.1 6846 192.168.7.2 22
TSLIB_TSDEVICE=/dev/input/touchscreen0
DISPLAY=localhost:10.0
_=/usr/bin/env

in the end, beaglebone is running the app after building, than I use env command using smartty (touchscreen doesnt work)

this is the output of env
TERM=xterm
SHELL=/bin/sh
SSH_TTY=/dev/pts/1
USER=root
QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
PWD=/home/root
EDITOR=/bin/vi
NODE_PATH=/usr/lib/node_modules
PS1=u@h:w$
SHLVL=1
HOME=/home/root
LOGNAME=root
SSH_CONNECTION=192.168.7.1 6875 192.168.7.2 22
TSLIB_TSDEVICE=/dev/input/touchscreen0
DISPLAY=localhost:11.0
_=/usr/bin/env

[support]

Hi,

Sorry, looks like there is a bit of confusion here. Please let me know if I understand correctly that:
1. Touch screen works if you launch the app from the console.
2. Touch screen does not work if you launch the app using SmarTTY.

If that is correct, please obtain the ‘env’ output from the console (not using SmarTTY). E.g. run “env > /tmp/env.log” in the console and then cat /tmp/env.log with SmarTTY to copy-paste its contents.
The environment in SmarTTY will not be affected by running the app from console, however the environment in a SmarTTY session can be different from the environment in the console session and those differences can be causing touchscreen problems.

[Author]

Posts