Qt5.8 for arm:Could not open egl display



  • the below is the kernel boot information and program running status.
    I have 2 qt program Accel based on widget and qmlDemo based on qml,exe the 2 program
    with "-platform linuxfb" and "-platform eglfs".Please how to slove the problem "Could not open egl display".

    my board info:
    cpu:imx6d
    linux kernel:3.10.17
    qt version:5.8 (build based on Yocto Krogoth)

    [  OK  ] Started ADB Server Daemon.
    [  OK  ] Started WPA supplicant.
    [  OK  ] Started Network Time Service.
    
    Boot to Qt for Embedded Linux 2.1.1 b2qt-nitrogen6x ttymxc3
    
    b2qt-nitrogen6x login: root
    root@b2qt-nitrogen6x:~# ls
    8192cu.ko  8192cu_hf.ko  Accel  cal  qmlDemo
    root@b2qt-nitrogen6x:~# ./Accel -platform linuxfb
    libpng warning: iCCP: known incorrect sRGB profile
    ^Croot@b2qt-nitrogen6x:~#
    root@b2qt-nitrogen6x:~# ./Accel -platform eglfs
    QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2 to enable double buffering and vsync.
     If this is not desired, you can override this via: export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
    Could not open egl display
    Aborted (core dumped)
    root@b2qt-nitrogen6x:~# ./qmlDemo -platform linuxfb
    QML debugging is enabled. Only use this in a safe environment.
    This plugin does not support createPlatformOpenGLContext!
    Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSi
    Aborted (core dumped)
    root@b2qt-nitrogen6x:~# ./qmlDemo -platform eglfs
    QML debugging is enabled. Only use this in a safe environment.
    QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2 to enable double buffering and vsync.
     If this is not desired, you can override this via: export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
    Could not open egl display
    Aborted (core dumped)
    root@b2qt-nitrogen6x:~# uname -a
    Linux b2qt-nitrogen6x 3.10.17-80743-g257896a-dirty #46 SMP PREEMPT Tue Jan 17 23:58:01 CST 2017 armv7l armv7l armv7l GNU/Linux
    

    the above,JUST " ./Accel -platform linuxfb" is normal.



  • Would u mind to share ur local.conf and and ur layer(if u have it) ?



  • @aV_V my local.conf :

    
    ############################################################################
    ##
    ## Copyright (C) 2016 The Qt Company Ltd.
    ## Contact: https://www.qt.io/licensing/
    ##
    ## This file is part of the Boot to Qt meta layer.
    ##
    ## $QT_BEGIN_LICENSE:GPL$
    ## Commercial License Usage
    ## Licensees holding valid commercial Qt licenses may use this file in
    ## accordance with the commercial license agreement provided with the
    ## Software or, alternatively, in accordance with the terms contained in
    ## a written agreement between you and The Qt Company. For licensing terms
    ## and conditions see https://www.qt.io/terms-conditions. For further
    ## information use the contact form at https://www.qt.io/contact-us.
    ##
    ## GNU General Public License Usage
    ## Alternatively, this file may be used under the terms of the GNU
    ## General Public License version 3 or (at your option) any later version
    ## approved by the KDE Free Qt Foundation. The licenses are as published by
    ## the Free Software Foundation and appearing in the file LICENSE.GPL3
    ## included in the packaging of this file. Please review the following
    ## information to ensure the GNU General Public License requirements will
    ## be met: https://www.gnu.org/licenses/gpl-3.0.html.
    ##
    ## $QT_END_LICENSE$
    ##
    ############################################################################
    
    #
    # This file is your local configuration file and is where all local user settings
    # are placed. The comments in this file give some guide to the options a new user
    # to the system might want to change but pretty much any configuration option can
    # be set in this file. More adventurous users can look at local.conf.extended 
    # which contains other examples of configuration which can be placed in this file
    # but new users likely won't need any of them initially.
    #
    # Lines starting with the '#' character are commented out and in some cases the 
    # default values are provided as comments to show people example syntax. Enabling
    # the option is a question of removing the # character and making any change to the
    # variable as required.
    
    #
    # Parallelism Options
    #
    # These two options control how much parallelism BitBake should use. The first 
    # option determines how many tasks bitbake should run in parallel:
    #
    # Default to setting automatically based on cpu count
    BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
    # 
    # The second option controls how many processes make should run in parallel when
    # running compile tasks:
    #
    # Default to setting automatically based on cpu count
    PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
    #
    # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
    # be appropriate for example.
    #
    # Machine Selection
    #
    # You need to select a specific machine to target the build with. There are a selection
    # of emulated machines available which can boot and run in the QEMU emulator:
    #
    #MACHINE ?= "qemuarm"
    #MACHINE ?= "qemumips"
    #MACHINE ?= "qemuppc"
    #MACHINE ?= "qemux86"
    #MACHINE ?= "qemux86-64"
    #
    # There are also the following hardware board target machines included for 
    # demonstration purposes:
    #
    #MACHINE ?= "beaglebone"
    #MACHINE ?= "genericx86"
    #MACHINE ?= "genericx86-64"
    #MACHINE ?= "mpc8315e-rdb"
    #MACHINE ?= "edgerouter"
    #
    # This sets the default machine to be qemux86 if no other machine is selected:
    MACHINE ??= "qemux86"
    MACHINE_HOSTNAME ?= "b2qt-${MACHINE}"
    #
    # Where to place downloads
    #
    # During a first build the system will download many different source code tarballs
    # from various upstream projects. This can take a while, particularly if your network
    # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
    # can preserve this directory to speed up this part of subsequent builds. This directory
    # is safe to share between multiple builds on the same machine too.
    #
    # The default is a downloads directory under TOPDIR which is the build directory.
    #
    DL_DIR ?= "${TOPDIR}/../downloads"
    
    #
    # Where to place shared-state files
    #
    # BitBake has the capability to accelerate builds based on previously built output.
    # This is done using "shared state" files which can be thought of as cache objects
    # and this option determines where those files are placed.
    #
    # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
    # from these files if no changes were made to the configuration. If changes were made
    # to the configuration, only shared state files where the state was still valid would
    # be used (done using checksums).
    #
    # The default is a sstate-cache directory under TOPDIR.
    #
    SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"
    #
    # Where to place the build output
    #
    # This option specifies where the bulk of the building work should be done and
    # where BitBake should place its temporary files and output. Keep in mind that
    # this includes the extraction and compilation of many applications and the toolchain
    # which can use Gigabytes of hard disk space.
    #
    # The default is a tmp directory under TOPDIR.
    #
    #TMPDIR = "${TOPDIR}/tmp"
    
    #
    # Default policy config
    #
    # The distribution setting controls which policy settings are used as defaults.
    # The default value is fine for general Yocto project use, at least initially.
    # Ultimately when creating custom policy, people will likely end up subclassing 
    # these defaults.
    #
    DISTRO ?= "b2qt"
    # As an example of a subclass there is a "bleeding" edge policy configuration
    # where many versions are set to the absolute latest code from the upstream 
    # source control systems. This is just mentioned here as an example, its not
    # useful to most new users.
    # DISTRO ?= "poky-bleeding"
    #
    # Package Management configuration
    #
    # This variable lists which packaging formats to enable. Multiple package backends 
    # can be enabled at once and the first item listed in the variable will be used 
    # to generate the root filesystems.
    # Options are:
    #  - 'package_deb' for debian style deb files
    #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
    #  - 'package_rpm' for rpm style packages
    # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
    # We default to rpm:
    PACKAGE_CLASSES ?= "package_ipk"
    
    #
    # SDK/ADT target architecture
    #
    # This variable specifies the architecture to build SDK/ADT items for and means
    # you can build the SDK packages for architectures other than the machine you are 
    # running the build on (i.e. building i686 packages on an x86_64 host).
    # Supported values are i686 and x86_64
    #SDKMACHINE ?= "i686"
    #
    # Extra image configuration defaults
    #
    # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated 
    # images. Some of these options are added to certain image types automatically. The
    # variable can contain the following options:
    #  "dbg-pkgs"       - add -dbg packages for all installed packages
    #                     (adds symbol information for debugging/profiling)
    #  "dev-pkgs"       - add -dev packages for all installed packages
    #                     (useful if you want to develop against libs in the image)
    #  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
    #                     (useful if you want to run the package test suites)
    #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
    #  "tools-debug"    - add debugging tools (gdb, strace)
    #  "eclipse-debug"  - add Eclipse remote debugging support
    #  "tools-profile"  - add profiling tools (oprofile, exmap, lttng, valgrind)
    #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
    #  "debug-tweaks"   - make an image suitable for development
    #                     e.g. ssh root access has a blank password
    # There are other application targets that can be used here too, see
    # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
    # We default to enabling the debugging tweaks.
    EXTRA_IMAGE_FEATURES = "debug-tweaks"
    
    #
    # Additional image features
    #
    # The following is a list of additional classes to use when building images which
    # enable extra features. Some available options which can be included in this variable 
    # are:
    #   - 'buildstats' collect build statistics
    #   - 'image-mklibs' to reduce shared library files size for an image
    #   - 'image-prelink' in order to prelink the filesystem image
    #   - 'image-swab' to perform host system intrusion detection
    # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
    # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
    USER_CLASSES ?= "buildstats image-mklibs"
    
    #
    # Runtime testing of images
    #
    # The build system can test booting virtual machine images under qemu (an emulator)
    # after any root filesystems are created and run tests against those images. To
    # enable this uncomment this line. See classes/testimage(-auto).bbclass for
    # further details.
    #TEST_IMAGE = "1"
    #
    # Interactive shell configuration
    #
    # Under certain circumstances the system may need input from you and to do this it 
    # can launch an interactive shell. It needs to do this since the build is 
    # multithreaded and needs to be able to handle the case where more than one parallel
    # process may require the user's attention. The default is iterate over the available
    # terminal types to find one that works.
    #
    # Examples of the occasions this may happen are when resolving patches which cannot
    # be applied, to use the devshell or the kernel menuconfig
    #
    # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
    # Note: currently, Konsole support only works for KDE 3.x due to the way
    # newer Konsole versions behave
    #OE_TERMINAL = "auto"
    # By default disable interactive patch resolution (tasks will just fail instead):
    PATCHRESOLVE = "noop"
    
    #
    # Disk Space Monitoring during the build
    #
    # Monitor the disk space during the build. If there is less that 1GB of space or less
    # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
    # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
    # of the build. The reason for this is that running completely out of space can corrupt
    # files and damages the build in ways which may not be easily recoverable.
    BB_DISKMON_DIRS = "\
        STOPTASKS,${TMPDIR},1G,100K \
        STOPTASKS,${DL_DIR},1G,100K \
        STOPTASKS,${SSTATE_DIR},1G,100K \
        ABORT,${TMPDIR},100M,1K \
        ABORT,${DL_DIR},100M,1K \
        ABORT,${SSTATE_DIR},100M,1K" 
    
    #
    # Shared-state files from other locations
    #
    # As mentioned above, shared state files are prebuilt cache data objects which can 
    # used to accelerate build time. This variable can be used to configure the system
    # to search other mirror locations for these objects before it builds the data itself.
    #
    # This can be a filesystem directory, or a remote url such as http or ftp. These
    # would contain the sstate-cache results from previous builds (possibly from other 
    # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the 
    # cache locations to check for the shared objects.
    # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
    # at the end as shown in the examples below. This will be substituted with the
    # correct path within the directory structure.
    #SSTATE_MIRRORS ?= "\
    #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
    #file://.* file:///some/local/dir/sstate/PATH"
    
    #
    # Qemu configuration
    #
    # By default qemu will build with a builtin VNC server where graphical output can be
    # seen. The two lines below enable the SDL backend too. This assumes there is a
    # libsdl library available on your build system.
    #PACKAGECONFIG_pn-qemu-native = "sdl"
    #PACKAGECONFIG_pn-nativesdk-qemu = "sdl"
    #ASSUME_PROVIDED += "libsdl-native"
    
    
    # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
    # track the version of this file when it was generated. This can safely be ignored if
    # this doesn't mean anything to you.
    CONF_VERSION = "1"
    
    #INHERIT += "rm_work"
    INHERIT += "image-buildinfo"
    INHERIT += "internal-build"
    
    DISTRO_FEATURES_remove = "x11 wayland"
    
    
    BB_NUMBER_THREADS = '8'
    PARALLEL_MAKE = '-j 8'
    
    # Enables use of QtQuickCompiler if you have access to the gerrit project
    #ENABLE_QTQUICKCOMPILER = "1"
    ACCEPT_FSL_EULA = "1"
    LICENSE_FLAGS_WHITELIST = "commercial"
    
    QT_SDK_PATH = ""
    

    complete bblayers.conf (default):

    
    ############################################################################
    ##
    ## Copyright (C) 2016 The Qt Company Ltd.
    ## Contact: https://www.qt.io/licensing/
    ##
    ## This file is part of the Boot to Qt meta layer.
    ##
    ## $QT_BEGIN_LICENSE:GPL$
    ## Commercial License Usage
    ## Licensees holding valid commercial Qt licenses may use this file in
    ## accordance with the commercial license agreement provided with the
    ## Software or, alternatively, in accordance with the terms contained in
    ## a written agreement between you and The Qt Company. For licensing terms
    ## and conditions see https://www.qt.io/terms-conditions. For further
    ## information use the contact form at https://www.qt.io/contact-us.
    ##
    ## GNU General Public License Usage
    ## Alternatively, this file may be used under the terms of the GNU
    ## General Public License version 3 or (at your option) any later version
    ## approved by the KDE Free Qt Foundation. The licenses are as published by
    ## the Free Software Foundation and appearing in the file LICENSE.GPL3
    ## included in the packaging of this file. Please review the following
    ## information to ensure the GNU General Public License requirements will
    ## be met: https://www.gnu.org/licenses/gpl-3.0.html.
    ##
    ## $QT_END_LICENSE$
    ##
    ############################################################################
    # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
    # changes incompatibly
    POKY_BBLAYERS_CONF_VERSION = "2"
    
    BBPATH = "${TOPDIR}"
    BBFILES ?= ""
    BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) + '/../..')}"
    
    BBLAYERS ?= " \
      ${BSPDIR}/sources/poky/meta \
      ${BSPDIR}/sources/poky/meta-poky \
      ${BSPDIR}/sources/meta-fsl-arm \
      ${BSPDIR}/sources/meta-fsl-arm-extra \
      ${BSPDIR}/sources/meta-openembedded/meta-oe \
      ${BSPDIR}/sources/meta-openembedded/meta-python \
      ${BSPDIR}/sources/meta-openembedded/meta-networking \
      ${BSPDIR}/sources/meta-openembedded/meta-initramfs \
      ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
      ${BSPDIR}/sources/meta-boot2qt \
      ${BSPDIR}/sources/meta-boot2qt/meta-fsl-extras \
      ${BSPDIR}/sources/meta-mingw \
      ${BSPDIR}/sources/meta-qt5 \
      "                                            
    


  • When I said to share your layer I meant a layer u have created not bblayers.conf but nvm I see there isn't one.

    So u did

    DISTRO_FEATURES_append = " opengl"
    
    IMAGE_INSTALL_append = " \
            libgal-mx6 \
            libegl-mx6 \
            libvsc-mx6 \
            libglslc-mx6 \
            libgles2-mx6 \
    "
    

    And you still getting "Could not open egl display" error?

    Then I don't know what could be, maybe these are not the right packages for ur platform.

    Btw, you are using b2qt so I guess that u have a Qt commercial license. I'm sure u also have a hotline to contact Qt, you should ask them for help.
    I'm sorry I could not have helped you.



  • Yes,the error still exists,the config DISTRO_FEATURES_append and IMAGE_INSTALL_append dont work. I don't have a Qt commercial license.Maybe I need to analyse the Qt source.



  • @hflw said in Qt5.8 for arm:Could not open egl display:

    Yes,the error still exists,the config DISTRO_FEATURES_append and IMAGE_INSTALL_append dont work. I don't have a Qt commercial license.Maybe I need to analyse the Qt source.

    I would try first to prove that your GPU is "enabled", and by this I mean to run an OpenGL application and check that you effectively have the right packages. After proving that you gpu is working then you should look why the Qt application is failing.

    Btw, did you tried to install this package?

    qtbase-examples
    

    Do it if you haven't and try to run your qt application after that. It will install all the missing dependencies, this is how I discovered my missing packages.



  • @aV_V Studying code makes me headache.I almost lost my confidence.Do u have an OpenGL application?

    I find the key "qtbase" in the folder ipk:

    ./cortexa9hf-neon-mx6qdl/qtbase-plugins_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-tools_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-dbg_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-doc_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-mkspecs_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-dev_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-lic_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    ./cortexa9hf-neon-mx6qdl/qtbase-staticdev_5.8.0+git0+49dc9aa409-r0_cortexa9hf-neon-mx6qdl.ipk
    

    no "qtbase-examples",So i add "qtbase-examples" to IMAGE_INSTALL_append in local.conf,But when bitbake,the error:

    Couldn't find anything to satisfy 'qtbase-examples'
    

    May I know your Yocto Version?



  • @aV_V I strace the Qt app with cmd "strace",get detail infomation:

    ...
    open("/dev/galcore",O_RDWR) ....... ENOTTY(Inappropriate ioctl for device)
    ...
    
    So I think the kernel config maybe not right.
    


  • please do:

    root@YOURBOARD: apt-get update
    root@YOURBOARD: apt-get upgrade
    root@YOURBOARD: apt-cache search qt5 (here is list of cached modules)
    root@YOURBOARD: apt-get install qt5-default
    .....
    root@YOURBOARD: apt-get install all_needed_modules

    should working



  • hi,@Andrey-Shmelew

    the apt-get don't have source list. do you know the source address?



  • sorry , i don't know



  • I'm sorry for the absence, was busy.

    @hflw said in Qt5.8 for arm:Could not open egl display:

    no "qtbase-examples",So i add "qtbase-examples" to IMAGE_INSTALL_append in local.conf,But when bitbake,the error:

    Couldn't find anything to satisfy 'qtbase-examples'
    

    Do

    PACKAGECONFIG_append_pn-qtbase = " examples"
    IMAGE_INSTALL_append = " qtbase-examples"
    

    To debug Qt backends is better to use this:

    export QT_QPA_DEBUG=1
    export QT_LOGGING_RULES="qt.qpa.*=true"
    

    Regards.



  • @aV_V ,I add examples,but still don't work,below is debug info:

    root@b2qt-imx6dlsabresd:~# ./qqc2a 
    QML debugging is enabled. Only use this in a safe environment.
    qt.qpa.egldeviceintegration: EGL device integration plugin keys: ("eglfs_viv")
    qt.qpa.egldeviceintegration: EGL device integration plugin keys (sorted): ("eglfs_viv")
    qt.qpa.egldeviceintegration: Trying to load device EGL integration "eglfs_viv"
    qt.qpa.egldeviceintegration: Using EGL device integration "eglfs_viv"
    QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2 to enable double buffering and vsync.
     If this is not desired, you can override this via: export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
    Could not open egl display
    Aborted (core dumped)
    


  • @hflw Can you confirm that qtbase-examples has been installed? Do opkg info qtbase-examples and show the output



  • @aV_V I decide to update uboot and kernel kept the same version of Yocto.

    after I compile yocto,i compare the rootfs file,Something more about qt-examples,I think rootfs is OK



  • @aV_V Now it works after I updte the version to 4.1.29 of Linux and 2016-07 of uboot.

    Nice weekend!!!



  • @hflw :d nice


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.