[agl-discussions] Flounder demo
Marc Murphy
marc.murphy at sancloud.co.uk
Mon Oct 15 06:58:43 UTC 2018
Getting further with identifying but still need some input.
I went back to Eel and built in the same way, deployed and modified the westland config file for resolution and it starts up, displays and I can navigate through screens.
I can plug in the touch screen interface and its happy. Connecting a mouse stops the app from launching. Enabling the bluetooth interface prevents app from launching. Some of the behaviour is strange with peripherals but essentially Eel comes up.
So what has changed in the application framework between Eel and Flounder that could cause a dependency or startup error?
Also why would plugging in a mouse cause the app not to display?
Any input appreciated.
Thanks
Marc
________________________________
From: automotive-discussions-bounces at lists.linuxfoundation.org <automotive-discussions-bounces at lists.linuxfoundation.org> on behalf of Marc Murphy <marc.murphy at sancloud.co.uk>
Sent: 11 October 2018 20:25:01
To: Kazumasa Mitsunari
Cc: automotive-discussions at lists.linuxfoundation.org
Subject: Re: [agl-discussions] Flounder demo
Still something weird going on.
If I stop Weston I can access the frame buffer directly;
beaglebone:/# systemctl stop weston
Then blit to the frame buffer and it will display. So usual sanity check;
# cat /dev/urandom > /dev/fb0
Displays expected noise
I then start Weston again
beaglebone:/# systemctl start weston
Screen gets cleared so Weston is writing to the frame buffer.
Does anyone know if there are any test applications that I can run with Weston to check rendering?
Regards
Marc
From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Marc Murphy
Sent: 11 October 2018 16:17
To: Kazumasa Mitsunari
Cc: automotive-discussions at lists.linuxfoundation.org
Subject: Re: [agl-discussions] Flounder demo
Hi Kazumasa
Thanks for giving some pointers. I will try to remove systemd-notify
The build was configured as agl-demo and contains the following;
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "arm-agl-linux-gnueabi"
MACHINE = "beaglebone"
DISTRO = "poky-agl"
DISTRO_VERSION = "6.0.0"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-ti
meta-qt5
meta-agl-profile-graphical-qt5
meta-agl-profile-graphical
meta-hmi-framework
meta-audio-4a-framework
meta-agl-demo
meta-oe
meta-multimedia
meta-networking
meta-python
meta-filesystems
meta-agl-profile-core
meta-agl-distro
meta-agl-bsp
meta-security
meta-perl
meta-security
meta-app-framework
meta
meta-poky
Kind Regards
Marc
From: Kazumasa Mitsunari [mailto:knimitz at witz-inc.co.jp]
Sent: 11 October 2018 11:17
To: Marc Murphy
Cc: automotive-discussions at lists.linuxfoundation.org<mailto:automotive-discussions at lists.linuxfoundation.org>
Subject: Re: [agl-discussions] Flounder demo
Hi
How about trying the following to go to next step for weston.
* open /etc/xdg/weston/weston.ini and delete(or comment out) modules=systemd-notify.so
That module is not always necessary.
But this is not related to homescreen I think.
I'm not sure how you created the image for beaglebone, then did you contain agl-demo-platform feature on bitbake?
There is no service binder, homescreen, windowmanager in the log you sent, so if weston is launched, homescreen doesn't exist
BR
Kazumasa Mitsunari
On 2018/10/11 18:57, Marc Murphy wrote:
Is there any chance I can have some real world weston logs of successful initialisation and displaying of the home screen please?
Kind Regards
Marc
________________________________
From: Jos¨¦ Bollo <jose.bollo at iot.bzh><mailto:jose.bollo at iot.bzh>
Sent: 10 October 2018 15:03:55
To: Marc Murphy
Cc: automotive-discussions at lists.linuxfoundation.org<mailto:automotive-discussions at lists.linuxfoundation.org>
Subject: Re: [agl-discussions] Flounder demo
On Wed, 10 Oct 2018 13:52:28 +0000
Marc Murphy <marc.murphy at sancloud.co.uk><mailto:marc.murphy at sancloud.co.uk> wrote:
> [21:15:27.372] set mode failed: Invalid argument
That's it I guess because the last line of mine is
[08:40:55.799] Loading module '/usr/lib/weston/systemd-notify.so'
Best regards
Jos¨¦
_______________________________________________
automotive-discussions mailing list
automotive-discussions at lists.linuxfoundation.org<mailto:automotive-discussions at lists.linuxfoundation.org>
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
--
*******************************
WITZ Corporation
»ù±P¼¼Ðgé_°k²¿ êÓûù±P¼¼ÐgÊÒ
Base Technology Development Dept.
¡¡Advanced Basic Technology Sect.
¡¡Kazumasa Mitsunari
Mail:knimitz at witz-inc.co.jp<mailto:Mail:knimitz at witz-inc.co.jp>
*******************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20181015/9ec7f66c/attachment-0001.html>
More information about the automotive-discussions
mailing list