# OMAP2530 EVM - OGLES Demos Crashing

**URL:** <https://forums.imgtec.com/t/omap2530-evm-ogles-demos-crashing/166>\
**Category:** PowerVR Insider\
**Created:** [October 14, 2008, 2:51pm UTC](https://forums.imgtec.com/t/omap2530-evm-ogles-demos-crashing/166 "2008-10-14T14:51:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jqweezy](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@jqweezy](https://forums.imgtec.com/u/jqweezy)\
**Post date:** [October 14, 2008, 2:51pm UTC](https://forums.imgtec.com/t/omap2530-evm-ogles-demos-crashing/166/1 "2008-10-14T14:51:18Z")

</div>

Hello,  
  
I have an OMAP2530 EVM and I am trying to run a couple of demos that come with the SDK:  
  
OGLESEvilSkull  
OGLESShowRoom  
  
When I first start the demos they seem to be fine, however, shortly after they crash with the following error:  
  
PVRShell: EGL 1.2 initialized  
Unhandled fault: external abort on non-linefetch (0x008) at 0x404b4e78  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
FreeDeviceMemCallback  
RecoverSystemSurfaceCallback  
omaplcd\_ddc\_swaptosystem : 166&nbsp;&nbsp; Shutting Down!!!  
Bus error  
  
Any ideas on why this happens? I appreciate any help you can give.  
  
Regards,  
JQ

---

<div class="post-metadata">

**Author:** ![CarlosSarria](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/carlossarria/32/263_2.png) [@CarlosSarria](https://forums.imgtec.com/u/CarlosSarria)\
**Post date:** [October 15, 2008, 8:51am UTC](https://forums.imgtec.com/t/omap2530-evm-ogles-demos-crashing/166/2 "2008-10-15T08:51:13Z")

</div>

Hello,

&nbsp;
  

We do not have a OMAP2530 EVM but we do have OMAP2430s, which I believe should be very similar.&nbsp;We have never seen a problem like the one you describe above.
  

This might be a bug in the drivers&nbsp;so you should get back to your supplier.
  

TI is responsible for the drivers on this platform.
  

&nbsp;
  

Regards.
  

&nbsp;
  

Carlos.