• Locked Locked
  • Replies 6 replies
  • Subscribers 136 subscribers
  • Views 28264 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

EGL Error : Could not create the egl surface: error = 0x300b

Wick Wire
Note: This was originally posted on 18th March 2013 at http://forums.arm.com

Hi,

I have a Cubieboard embedded system:

http://cubieboard.org/

      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


The cubieboard is based on the AllWinner A10 SoC and this is what is available as documentation:

http://linux-sunxi.org/A10
http://linux-sunxi.org/Mali400

It uses Mali-400 MP for graphics - and I'm trying to use the Qt5 graphics framework with it.

Following the second link and installing the mali-libs from sunxi I'm able to display the coloured triangle and obtain the es_info2 output as stated.

When attempting to run a Qt5 App using the EGLFS platform, I'm getting:

EGL Error : Could not create the egl surface: error = 0x300b

So far I've managed to translate this error 0x300b to EGL_BAD_NATIVE_WINDOW but haven't got a clue about what it means and to solve it.


If anyone has any idea of why the error is showing, and how to fix it - please let me know.

Thanks in advance!
Parents
  • Note: This was originally posted on 24th May 2013 at http://forums.arm.com

    There is a difference between X11, and what we call 'framebuffer', or fbdev_window.
    If you have setup the device to use the X windowing system, then instead of setting up EGL to pass in a window that is of type fbdev_window, but you would want to create an X11 window and pass that into EGL instead. (Note it will allow you to use fbdev with an X11 environment, but there is no guarantee what the output may do)
    Similarly, the reverse is true if you are running in fbdev mode, without X support. You will need to setup EGL to take in an fbdev_window instead of an X11 window.

    I hope that clarifies a few things, please feel free to contact us further if you need further assistance.
Reply
  • Note: This was originally posted on 24th May 2013 at http://forums.arm.com

    There is a difference between X11, and what we call 'framebuffer', or fbdev_window.
    If you have setup the device to use the X windowing system, then instead of setting up EGL to pass in a window that is of type fbdev_window, but you would want to create an X11 window and pass that into EGL instead. (Note it will allow you to use fbdev with an X11 environment, but there is no guarantee what the output may do)
    Similarly, the reverse is true if you are running in fbdev mode, without X support. You will need to setup EGL to take in an fbdev_window instead of an X11 window.

    I hope that clarifies a few things, please feel free to contact us further if you need further assistance.
Children
No data