Hello,
Using TI's WinCE OMAP35X BSP, 6.15, there is a Data Abort Exception. This exception is generated at random, and it is difficult to predict when it will happen.
Using TI's WinCE OMAP35X BSP, 6.13, did not generate a similar error.
Apparently, the more activity in the system, the more chances it will expedite its generation.
All errors, so far, have in common the following info:
Exception 'Data Abort'(4) Thread-Id=0439000e(pth=84b090c0) PC=812466dc BVA=ffff1060, dwInfo = 00000807 R0=00000000 R1=0000fffc R2=6000011f R3=ffffc800 R4=d2fdfb70 R5=84b090c0 R6=00000000 R7=d2fdfb60 R8=00000002 R9=00000000 R10=00000000 R11=d2fdfd58 R12=812466dc SP=d2fdfb58 Lr=812466dc Psr=6000011f Exception 'Data Abort'(4) Thread-Id=0439000e(pth=ffff0e9c) PC=8122e6dc BVA=ffff1060, dwInfo = 00000807 R0=ffff1060 R1=00000004 R2=60000193 R3=ffffc800 R4=00000001 R5=00006590 R6=b1318000 R7=8385ed60 R8=8385ced4 R9=00000000 R10=00000000 R11=d2fdfd58 R12=8122f094 SP=ffff0fec Lr=81224938 Psr=60000193 Exception 'Data Abort' (4): Thread-Id=0439000e(pth=84b090c0), Proc-Id=00400002(pprc=83861308) 'NK.EXE', VM-active=05300006(pprc=84ad4000) 'explorer.exe' PC=8122e6dc(kernel.dll+0x000066dc) RA=81224938(NK.EXE+0x00024938) SP=ffff0fec, BVA=ffff1060
They point to a RA within NK.EXE, of 0x00024938. An excerpt of the NK.Map file is the following:
0001:000235a4 OALIoCtlHalILTiming 000345a4 f oal_ilt:ilt.obj
0001:00023730 __GSHandlerCheckCommon 00034730 f fulllibc:gshandler.obj
0001:0002376c __GSHandlerCheck 0003476c f fulllibc:gshandler.obj
0001:00023790 __security_check_cookie 00034790 f fulllibc:armsecgs.obj
0001:000237a4 __gsfailure 000347a4 f fulllibc:armsecgs.obj
0001:000237e8 __rt_udivrem64by64 000347e8 f fulllibc:mdsdiv64.obj
0001:000238e0 __rt_divrem64by64 000348e0 f fulllibc:mdsdiv64.obj
0001:00023930 __rt_udiv64by64 00034930 f fulllibc:mdsdiv64.obj
0001:00023940 __rt_urem64by64 00034940 f fulllibc:mdsdiv64.obj
0001:00023958 __rt_sdiv64by64 00034958 f fulllibc:mdsdiv64.obj
0001:00023968 __rt_srem64by64 00034968 f fulllibc:mdsdiv64.obj
Looking up the Module Offset (MO), it points toward the OALIoCtlHalILTiming function offset.
Insight into this problem would be appreciated.
Thanks,
Eugen