- October 26, 2011 at 3:07 pm #30666
we just upgraded from 2.7 to 2.9 because we wanted to test the IMG_multisampled_render_to_texture extension on our TI_OMAP3517 (SGX530).
Unfortunately neither our app nor the sdk sample apps are running. They fail at init time when creating the EGL context: the function eglGetDisplay() always return 0.
Do we miss something?
Btw, concerning the Linux emulation: the PVRFrame app don’t show up anymore. Is it normal?
jbmerli 2011-10-26 15:11:11October 26, 2011 at 5:20 pm #35187
This might get long so we moved it to avoid clogging up the news post. We can put any resolutions back there if there turns out to be a problem.
So to clarify, the eglGetDisplay function, is it in VFrame that this failure is occuring or is it on your OMAP device?
Concerning VFrame – yes, this has been removed as mentioned in the release notes. There is console output though for debugging purposes.
Tobias 2011-10-26 17:20:46October 26, 2011 at 5:35 pm #35188
Thanks for the answer.
For the eglGetDisplay func, it is returning 0 (fails) on the OMAP device…
JBOctober 27, 2011 at 10:42 am #35189
We just double checked our release on an ARMv7 platform and it ran without problem under NWS(Raw). Have you double checked that the windowing system you’ve built for is correct? Are you running the binaries in the SDK or building it yourself? Which windowing system are you using (NWS(Raw), X11 or EWS)?
TobiasOctober 27, 2011 at 10:58 am #35190
we tried both the binaries from the SDK and our own application.
We also recompiled the SimpleTriangle sample from the SDK, but it still don’t work.
We use Raw (Null Window System).
The platform is a TI OMAP 3517 (SGX 530).
What we do is recompiling our app (or the sample apps) with the new SDK (by linking in particular with the new libEGL.so and libOGLESv2.so), and then change LD_LIBRARY_PATH to run it with the same new runtime.
For the binaries from the ARMv7 SDK 2.9, we simply tried to run them with the new runtime.
None of the above works: we get no EGL context.
But if we switch back to the old runtime (by changing LD_LIBRARY_PATH) everything runs smoothly (even the apps compiled with the new sdk).
Hope this helps.
What can I do to help you diagnose?October 27, 2011 at 11:22 am #35191
ScottModeratorjbmerli wrote:What we do is recompiling our app (or the sample apps) with the new SDK (by linking in particular with the new libEGL.so and libOGLESv2.so), and then change LD_LIBRARY_PATH to run it with the same new runtime.Hi,The libEGL.so and libGLESv2.so that come with the 2.9 SDK from our site are just stub libraries which are just for linking against but contain no executable code so won’t function as drivers. I’m afraid to get updated drivers for your OMAP you’ll need to ask TI.Cheers,ScottOctober 27, 2011 at 11:40 am #35192
Thank you, I suspected something like that but I was not sure ; I’m new to the embedded world!
So I’ll ask TI.
To be sure I understood correctly: TI is providing its own libEGL and libOGLESv2, implementing OGLES for their hardware?
Thank you very much.October 27, 2011 at 12:36 pm #35193
Yep, TI are responsible for providing libEGL, libGLESv2 and other required files for their hardware.