Sato image runs, but doesn't start its GUI

Sato image runs, but doesn't start its GUI

[Mike Looijmans]

I finally got around to trying to use our custom board's BSP with Yocto images.

Since the board has a touchscreen (well, actually it has two) I built the 
core-image-sato.

I had to tweak the startup a bit, because our framebuffer is in the FPGA it 
won't be available until after programming it and loading the modules.

Setting psplash to S05 instead of S00, and modutils to load at S04 fixes the 
initialization order problems I saw.

What I get now is a nice Yocto logo on the screen, and a progress bar that 
almost fills up. But nothing else happens. I'd expect the GUI to start then, 
but apparently there's nothing to trigger that?

Display works, touch works, everything seems in perfect working order.

I can't find anything that attempts to start anything. There's nothing in 
inittab, and there's nothing in rc3.d that resembles an attempt at starting 
something desktop GUI application or so.

Am I missing something, is this a bug, or is this expected behaviour and am I 
supposed to type some magic command first?


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image runs, but doesn't start its GUI

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 374 bytes --]

On 13 November 2014 12:59, Mike Looijmans <mike.looijmans@topic.nl> wrote:

> I can't find anything that attempts to start anything. There's nothing in
> inittab, and there's nothing in rc3.d that resembles an attempt at starting
> something desktop GUI application or so.
>

core-image-sato should be shipping the xserver-nodm init script, which
starts X.

Ross

[-- Attachment #2: Type: text/html, Size: 789 bytes --]

Re: Sato image runs, but doesn't start its GUI

[Mike Looijmans]

On 11/13/2014 02:07 PM, Burton, Ross wrote:
>
> On 13 November 2014 12:59, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     I can't find anything that attempts to start anything. There's nothing in
>     inittab, and there's nothing in rc3.d that resembles an attempt at
>     starting something desktop GUI application or so.
>
>
> core-image-sato should be shipping the xserver-nodm init script, which starts X.
>
> Ross

Ah, thanks, found it. It's set to run at runlevel 5 and somehow my inittab has 
"3" as its level. Setting it to 5 displays the desktop.

Next challenge is to calibrate the touch screen...


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image runs, but doesn't start its GUI

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

On 13 November 2014 13:10, Mike Looijmans <mike.looijmans@topic.nl> wrote:

> Next challenge is to calibrate the touch screen...
>

This is something that regressed, the calibrator doesn't get installed out
of the box properly.  Install xinput-calibrator in your image and it should
start on boot if required.

Ross

[-- Attachment #2: Type: text/html, Size: 716 bytes --]

Sato image touchscreen calibration is borked

[Mike Looijmans]

On 11/13/2014 02:10 PM, Mike Looijmans wrote:
> Next challenge is to calibrate the touch screen...

Hmm. That's a big disappointment.

I've been using "ts_calibrate" in the past, and that worked just fine on this 
board.

Sato uses an X application for this, and it's apparently borked or so.

It does not run at startup, as I'd expect it to do (though it seems to be 
setup for that).

running "DISPLAY=0:0 xinput_calibrator_once.sh" displays it, but it doesn't 
really work. I can only "touch" the crosses in the upper left and right 
corner, but it does not accept the lower right one.

I ran it with the "-v" option to get some more info, and this is what it 
displays when I click the crosses. The lower left one causes the "Not 
adding..." output.


root@topic-miami-florida-med-xc7z015:~# xinput_calibrator -v
DEBUG: XInputExtension version is 2.3
DEBUG: Skipping virtual master devices and devices without axis valuators.
DEBUG: Skipping device 'Virtual core XTEST pointer' id=4, does not report 
Absolute events.
DEBUG: Selected device: AD7879 Touchscreen
DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device
DEBUG: Read axes swap value of 0.
DEBUG: Read InvertX=0, InvertY=0.
Calibrating EVDEV driver for "AD7879 Touchscreen" id=6
         current calibration values (from XInput): min_x=0, max_x=1024 and 
min_y=0, max_y=600
DEBUG: Adding click 0 (X=1023, Y=599)
DEBUG: Adding click 1 (X=607, Y=599)
DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click
DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click
DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click




Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image touchscreen calibration is borked

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Hi,

On 13 November 2014 13:19, Mike Looijmans <mike.looijmans@topic.nl> wrote:

> I've been using "ts_calibrate" in the past, and that worked just fine on
> this board.
>

Modern X servers don't use tslib, so this won't work since we stopped using
kdrive about two years ago.

DEBUG: Adding click 0 (X=1023, Y=599)
> DEBUG: Adding click 1 (X=607, Y=599)
> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
> click
> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
> click
> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
> click


Well, it's not within seven pixels is it...  I wonder if there's a bug in
the logic.  It might be worth bumping the xinput-calibrator revision to the
latest commit in the upstream git repo in case this has been fixed already
there.

I bought a HDMI display with an integrated touchscreen to test this sort of
thing, but the device was so dodgy that it often caused the kernel to hang
on boot...

Ross

[-- Attachment #2: Type: text/html, Size: 1614 bytes --]

Re: Sato image touchscreen calibration is borked

[Mike Looijmans]

On 11/13/2014 02:28 PM, Burton, Ross wrote:
> Hi,
>
> On 13 November 2014 13:19, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     I've been using "ts_calibrate" in the past, and that worked just fine on
>     this board.
>
>
> Modern X servers don't use tslib, so this won't work since we stopped using
> kdrive about two years ago.

Maybe, but it demonstrates that the hardware and drivers are working just fine.


>
>     DEBUG: Adding click 0 (X=1023, Y=599)
>     DEBUG: Adding click 1 (X=607, Y=599)
>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click
>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click
>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous click
>
>
> Well, it's not within seven pixels is it...  I wonder if there's a bug in the
> logic.  It might be worth bumping the xinput-calibrator revision to the latest
> commit in the upstream git repo in case this has been fixed already there.

Tried, but that did not help, same problem.

> I bought a HDMI display with an integrated touchscreen to test this sort of
> thing, but the device was so dodgy that it often caused the kernel to hang on
> boot...

I have one of those attached to the system as well. Explaining that I have two 
touch screens might be a bit of a challenge though, so I started with the 
little LVDS screen first.




Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image touchscreen calibration is borked

[Mike Looijmans]

On 11/13/2014 02:54 PM, Mike Looijmans wrote:
> On 11/13/2014 02:28 PM, Burton, Ross wrote:
>> Hi,
>>
>> On 13 November 2014 13:19, Mike Looijmans <mike.looijmans@topic.nl
>> <mailto:mike.looijmans@topic.nl>> wrote:
>>
>>     I've been using "ts_calibrate" in the past, and that worked just fine on
>>     this board.
>>
>>
>> Modern X servers don't use tslib, so this won't work since we stopped using
>> kdrive about two years ago.
>
> Maybe, but it demonstrates that the hardware and drivers are working just fine.
>
>
>>
>>     DEBUG: Adding click 0 (X=1023, Y=599)
>>     DEBUG: Adding click 1 (X=607, Y=599)
>>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>>     DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>>
>>
>> Well, it's not within seven pixels is it...  I wonder if there's a bug in the
>> logic.  It might be worth bumping the xinput-calibrator revision to the latest
>> commit in the upstream git repo in case this has been fixed already there.
>
> Tried, but that did not help, same problem.
>
>> I bought a HDMI display with an integrated touchscreen to test this sort of
>> thing, but the device was so dodgy that it often caused the kernel to hang on
>> boot...
>
> I have one of those attached to the system as well. Explaining that I have two
> touch screens might be a bit of a challenge though, so I started with the
> little LVDS screen first.

That one works,

root@topic-miami-florida-med-xc7z015:~# DISPLAY=0:0 xinput_calibrator -v --devic
e event1
DEBUG: XInputExtension version is 2.3
DEBUG: Skipping virtual master devices and devices without axis valuators.
DEBUG: Selected device: PixArtImaging OpticalTouchScreen
DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device
DEBUG: Evdev Axis Calibration not set, setting to axis valuators to be sure.
         Setting calibration data: 0, 32767, 0, 32767
DEBUG: Successfully applied axis calibration.
DEBUG: Read axes swap value of 0.
DEBUG: Read InvertX=0, InvertY=0.
Calibrating EVDEV driver for "PixArtImaging OpticalTouchScreen" id=6
         current calibration values (from XInput): min_x=0, max_x=32767 and 
min_y=0, max_y=32767
DEBUG: Found that 'PixArtImaging OpticalTouchScreen' is a sysfs name.
INFO: width=1920, height=1080
DEBUG: Adding click 0 (X=229, Y=147)
DEBUG: Adding click 1 (X=1699, Y=144)
DEBUG: Adding click 2 (X=231, Y=943)
DEBUG: Adding click 3 (X=1685, Y=942)

Doing dynamic recalibration:
         Setting calibration data: -233, 33034, 384, 32625


So it seems related to the little I2C touchscreen controller, or some kind of 
rotation. The coordinate system for the small touchscreen looks rotated 180 
degrees, looking at the numbers. xinput cannot handle that?




Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image touchscreen calibration is borked

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

On 13 November 2014 14:09, Mike Looijmans <mike.looijmans@topic.nl> wrote:

> So it seems related to the little I2C touchscreen controller, or some kind
> of rotation. The coordinate system for the small touchscreen looks rotated
> 180 degrees, looking at the numbers. xinput cannot handle that?


My touchscreen is Y-inverted and worked fine once calibrated.  Not sure if
this is a problem with the calibrator/xi not handling both axis being
inverted, or something else is misbehaving.  You're rapidly reaching the
limits of my experience here - have you tried using the partial numbers
that xinput-calibrator gave you for the broken touchscreen and
extrapolating calibration setting to set manually?

Ross

[-- Attachment #2: Type: text/html, Size: 1068 bytes --]

Re: Sato image touchscreen calibration is borked

[Michael Gloff]

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]

On Thu, Nov 13, 2014 at 7:28 AM, Burton, Ross <ross.burton@intel.com> wrote:

> Hi,
>
> On 13 November 2014 13:19, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>
>> I've been using "ts_calibrate" in the past, and that worked just fine on
>> this board.
>>
>
> Modern X servers don't use tslib, so this won't work since we stopped
> using kdrive about two years ago.
>
> BTW, you can use tslib with xorg. This is what I have set up as I find
ts_calibrate easier to work with.


> DEBUG: Adding click 0 (X=1023, Y=599)
>> DEBUG: Adding click 1 (X=607, Y=599)
>> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>> DEBUG: Not adding click 2 (X=1023, Y=599): within 7 pixels of previous
>> click
>
>
> Well, it's not within seven pixels is it...  I wonder if there's a bug in
> the logic.  It might be worth bumping the xinput-calibrator revision to the
> latest commit in the upstream git repo in case this has been fixed already
> there.
>
> I bought a HDMI display with an integrated touchscreen to test this sort
> of thing, but the device was so dodgy that it often caused the kernel to
> hang on boot...
>
> Ross
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
Michael Gloff

[-- Attachment #2: Type: text/html, Size: 2728 bytes --]

Re: Sato image touchscreen calibration is borked

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 363 bytes --]

On 13 November 2014 17:58, Michael Gloff <mgloff@emacinc.com> wrote:

> BTW, you can use tslib with xorg. This is what I have set up as I find
> ts_calibrate easier to work with.


The only mention of e.g. ts_read() that I can see in the xserver source is
in the kdrive server.  Is there some compatibility mode or something that
I'm unaware of?

Ross

[-- Attachment #2: Type: text/html, Size: 708 bytes --]

Re: Sato image touchscreen calibration is borked

[Michael Gloff]

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

On Thu, Nov 13, 2014 at 5:05 PM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 13 November 2014 17:58, Michael Gloff <mgloff@emacinc.com> wrote:
>
>> BTW, you can use tslib with xorg. This is what I have set up as I find
>> ts_calibrate easier to work with.
>
>
> The only mention of e.g. ts_read() that I can see in the xserver source is
> in the kdrive server.  Is there some compatibility mode or something that
> I'm unaware of?
>
> Ross
>

Ross,
I am using the xf86-input-tslib X driver. I forgot about that piece of the
puzzle.
And the following in xorg.conf

Section "ServerLayout"
        InputDevice    "TouchScreen0" "CorePointer"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
EndSection

:
:

Section "InputDevice"
        Identifier "TouchScreen0"
    Driver "tslib"
        Option "Device" "/dev/input/touchscreen0"
    Option "CorePointer" "on"
    Option "SendCoreEvents" "on"
    Option "Protocol" "Auto"
        Option "ScreenNo" "0"
EndSection

I've also found that I need to comment out the touchschreen section of
10-evdev.conf as it tries to interfere.
That 'should' work, although I haven't tried on any standard build.

Michael Gloff

[-- Attachment #2: Type: text/html, Size: 2319 bytes --]

Re: Sato image touchscreen calibration is borked

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

On 14 November 2014 08:17, Michael Gloff <mgloff@emacinc.com> wrote:

> I am using the xf86-input-tslib X driver. I forgot about that piece of the
> puzzle.
>

Genuinely surprised that still works, but good to know!

Ross

[-- Attachment #2: Type: text/html, Size: 590 bytes --]

Re: Sato image touchscreen calibration is borked

[Mike Looijmans]

On 11/13/2014 06:58 PM, Michael Gloff wrote:
> On Thu, Nov 13, 2014 at 7:28 AM, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
>     Hi,
>
>     On 13 November 2014 13:19, Mike Looijmans <mike.looijmans@topic.nl
>     <mailto:mike.looijmans@topic.nl>> wrote:
>
>         I've been using "ts_calibrate" in the past, and that worked just fine
>         on this board.
>
>
>     Modern X servers don't use tslib, so this won't work since we stopped
>     using kdrive about two years ago.
>
> BTW, you can use tslib with xorg. This is what I have set up as I find
> ts_calibrate easier to work with.

Interesting option, can you elaborate on that (in particular, in combination 
with Yocto builds)?





Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

Re: Sato image touchscreen calibration is borked

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 467 bytes --]

On 17 November 2014 07:25, Mike Looijmans <mike.looijmans@topic.nl> wrote:

> BTW, you can use tslib with xorg. This is what I have set up as I find
>> ts_calibrate easier to work with.
>>
>
> Interesting option, can you elaborate on that (in particular, in
> combination with Yocto builds)?


meta-oe has xf86-input-tslib.  Installing that might still work.  It's been
untouched since 2009 which is why I assumed it would have bit-rotted by now.

Ross

[-- Attachment #2: Type: text/html, Size: 960 bytes --]

Re: Sato image runs, but doesn't start its GUI

[Iorga, Cristian]

Hi Mike,

What poky version are you using?
Have you tried to build your core-image-sato for a qemu machine and see if that runs correctly?
Sato starts with a graphical launcher/desktop/window manager.
Regards,
Cristian

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Mike Looijmans
Sent: Thursday, November 13, 2014 3:00 PM
To: yocto@yoctoproject.org
Subject: [yocto] Sato image runs, but doesn't start its GUI

I finally got around to trying to use our custom board's BSP with Yocto images.

Since the board has a touchscreen (well, actually it has two) I built the core-image-sato.

I had to tweak the startup a bit, because our framebuffer is in the FPGA it won't be available until after programming it and loading the modules.

Setting psplash to S05 instead of S00, and modutils to load at S04 fixes the initialization order problems I saw.

What I get now is a nice Yocto logo on the screen, and a progress bar that almost fills up. But nothing else happens. I'd expect the GUI to start then, but apparently there's nothing to trigger that?

Display works, touch works, everything seems in perfect working order.

I can't find anything that attempts to start anything. There's nothing in inittab, and there's nothing in rc3.d that resembles an attempt at starting something desktop GUI application or so.

Am I missing something, is this a bug, or is this expected behaviour and am I supposed to type some magic command first?


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at Bits & Chips Smart Systems 20th November, 1931 Congrescentum Brabanthallen 's-Hertogenbosch, stand number 34
http://bc-smartsystems.nl

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: Sato image runs, but doesn't start its GUI

[Gary Thomas]

On 2014-11-13 05:59, Mike Looijmans wrote:
> I finally got around to trying to use our custom board's BSP with Yocto images.
>
> Since the board has a touchscreen (well, actually it has two) I built the core-image-sato.
>
> I had to tweak the startup a bit, because our framebuffer is in the FPGA it won't be available until after programming it and loading the modules.
>
> Setting psplash to S05 instead of S00, and modutils to load at S04 fixes the initialization order problems I saw.
>
> What I get now is a nice Yocto logo on the screen, and a progress bar that almost fills up. But nothing else happens. I'd expect the GUI to start then, but apparently there's
> nothing to trigger that?
>
> Display works, touch works, everything seems in perfect working order.
>
> I can't find anything that attempts to start anything. There's nothing in inittab, and there's nothing in rc3.d that resembles an attempt at starting something desktop GUI
> application or so.
>
> Am I missing something, is this a bug, or is this expected behaviour and am I supposed to type some magic command first?

If you are running the stock core-image-sato, X is started
by /etc/rc5.d/S09xserver-nodm

Do you have a serial console?  You can learn a lot from that.
Also try looking at /var/log/Xorg.0.log

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------