core-image-weston segmentation fault?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

core-image-weston segmentation fault?

1,110 Views
woutervh
Contributor IV

I'm using fsl-community yocto bsp, on the morty branch.

I'm working on a custom board. core-image-x11 is working fine.

But when I make a core-image-weston, everything builds fine but when booting the board, it bails out to the console login, throwing a "Segmentation fault".

Anyone has an idea of where to start looking?

Weston_log just shows:

Date: 2017-06-29 UTC
[08:59:47.385] weston 1.11.0
http://wayland.freedesktop.org
Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.11.0
Build: 1.10.93-2-g2d825ed configure.ac: bump to version 1.11.0 for the official release (2016-05-31 17:10:40 -0700)
[08:59:47.386] OS: Linux, 4.1.38-01921-g5095894-dirty, #11 SMP PREEMPT Thu Jun 29 11:16:02 CEST 2017, armv7l
[08:59:47.390] Starting with no config file.
[08:59:47.398] Output repaint window is 7 ms maximum.
[08:59:47.403] Loading module '/usr/lib/weston/fbdev-backend.so'
[08:59:47.543] initializing fbdev backend
[08:59:47.548] Loading module '/usr/lib/weston/gl-renderer.so'
[08:59:47.607] warning: either no EGL_EXT_platform_base support or specific platform support; falling back to eglGetDisplay.
[08:59:47.661] warning: EGL_EXT_swap_buffers_with_damage not supported. Performance could be affected.
[08:59:47.661] Retrieving EGL client extension string failed.
[08:59:47.661] Creating fbdev output. /dev/fb0 x=0 y=0
[08:59:47.661] Opening fbdev frame buffer.
[08:59:47.661] Calculating pixman format from:
- type: 0 (aux: 0)
- visual: 2
- bpp: 24 (grayscale: 0)
- red: offset: 16, length: 8, MSB: 0
- green: offset: 8, length: 8, MSB: 0
- blue: offset: 0, length: 8, MSB: 0
- transp: offset: 0, length: 0, MSB: 0
[08:59:47.662] failed to create egl surface
[08:59:47.662] gl_renderer_output_create failed.

Trying to run it manually (XDG_RUNTIME_DIR=/var/run/user/0 weston --tty=2) gives me the same log, ended with

"Segmentation fault"

0 Kudos
2 Replies

771 Views
woutervh
Contributor IV

To answer my own question. If I change in my dts file:

default_bpp = <16>; (where it was 24 before), it works

But can one explain why?

0 Kudos

771 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hi wouter,

16bpp should correspond to your display settings, please check:

https://community.nxp.com/thread/298990 

Regards

0 Kudos