I am consistently getting a 0x300b error whenever attempting to execute a custom Qt 5.5.0 application on my Raspberry PI 2 Model B unit, no matter what I do, I have rebuilt this more then 5x and even did a full rebuild of the code of both my application and buildroot using "make clean all".
Could you please indicate: * The Buildroot version you're using * The Buildroot configuration (.config) you're using * An example application that exhibits the problem (can be an example application built in with Qt)
Also, please indicate the RPi FW config.txt that you're using (can be the default one provided by Buildroot). The one in Buildroot has small values for the GPU memory sizes, which are not enough for some video applications. Maybe these sizes should be increased in Buildroot.
Created attachment 6156 [details] Buildroot config
(In reply to comment #2) > Also, please indicate the RPi FW config.txt that you're using (can be the > default one provided by Buildroot). > > The one in Buildroot has small values for the GPU memory sizes, which are not > enough for some video applications. Maybe these sizes should be increased in > Buildroot. Ok, in a nutshell... Version: 2015.11-git-00108-g708818a Nature of custom application: A simple Qt 5 WebKit based browser intended to view limited numbers of sites, however intended to take full advantage of EGLFS HW Acceleration. As stated previously, whenever the said application was executed, it would refuse to run and output a 0x300b error code.
Just in case, test again after selecting BR2_PACKAGE_RPI_FIRMWARE_X and setting the following in package/rpi-firmware/config.txt (or using a post-build script, or directly on your SD card): gpu_mem_256=128 gpu_mem_512=256 gpu_mem_1024=512 Make sure that rpi-firmware has been rebuilt after these configuration changes before testing.
Yann, can you have a look ? Thanks!
Yann, could you please have a look? This issue is open since almost a year now :-/
I have absolutely no clue on how to investigate this, even less so how to eventually fix it. Besides, the issue is reported with running QtWebkit, which is not a simple application. As Thomas said on IRC "we cannot investigate and fix every random issue on every random platform". So, I'm marking this as "won't fix" for now. Sorry we could not have been of much help... :-/