Qt5 on Cubieboard - EGL Error : Could not create the egl surface: error = 0x300b

  • Hi,

    I'm trying to use Qt5 with Cubieboard:


    1G ARM cortex-A8 processor, NEON, VFPv3, 256KB L2 cache
    Mali400, OpenGL ES GPU
    512M/1GB DDR3 @480MHz
    HDMI 1080p Output
    10/100M Ethernet
    4Gb Nand Flash
    2 USB Host, 1 micro SD slot, 1 SATA, 1 ir
    96 extend pin including I2C, SPI, RGB/LVDS, CSI/TS, FM-IN, ADC, CVBS, VGA, SPDIF-OUT, R-TP..
    Running Android, Ubuntu and other Linux distributions

    Using Linaro Ubuntu 12.11, building the mali libs and building Qt5, I got to the point where config.summary reports the following:


    I thought I was OK with EGLFS support, but then, trying to run a typical helloworld app, I got:


    So while debating the issues at the cubieforums as well, I thought maybe someone here could help figuring out what is going on and how to fix it...

    I read many posts here about similar errors, all memory related - where users usually increased GPU memory to 64MB or above, usually Raspberry Pi.

    My Cubieboard has 1GB RAM and dmesg output follows:


    If anyone has any ideas, I can test them and post results as well - I bought this device recently and I believe Qt5 could be quite an advantage on it, at the moment I'm using it to manage an OpenVPN Server, Web Server, File Server... etc.

    Thanks in advance!

  • Hi,

    I've been reading upon the error message for the EGLFS platform:

    Could not create the egl surface: error = 0x300b

    Turns out that the message translates to EGL_BAD_NATIVE_WINDOW so now I'm trying to figure out what this means and how to fix it...

    Once again if anyone has any ideas - please let me know!

  • Hi wickwire

    I'm not quite sure if I can help you but I had similar errors with the eglfs on the beagleboard.

    What I did I set the folowing environment variables:

    export QT_QPA_EGLFS_DEPTH=16
    export DISPLAY=:0

    I also had to change my code which was devloped with Qt4.8.4 and QtQuick1.1
    I had to remove the obsolete qmlapplicationviewer class.

    After those changes it worked.

    Good luck.

Log in to reply

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