CE6.0 KITL Problem....

Tutorials Win: Microsoft Windows Forum

hi!
I building workspace for arm pxa270 wince6.0
Image was built successfully.
But when i try to load the image through the platform builder.
and enabled "Enable KITL on boot device" flag.
My image is not loading.
when i clear the flag my image is booting.
Why KITL is not working can any hace some idea.

This is th error i was getting:

!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002


Faulted in KCall, pCurThread->dwStartAddr = c0481120, PageFreeCount =
000008d0!!


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
Original Context when thread faulted:


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
Exception 'Prefetch Abort'(3) Thread-Id=014a0002(pth=83eab000)
PC=8013b23c BVA=c0b2d000, dwInfo = 00000400


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R0=c0b2c2e0 R1=00000000 R2=000012d0 R3=c0b2d000


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R4=c049829c R5=00000000 R6=00000000 R7=00000000


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R8=00000000 R9=00009999 R10=00001010 R11=d245e388


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R12=00000000 SP=d245d900 Lr=c0a9a46c Psr=2000001f


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
Context when faulted in KCall:


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
Exception 'Prefetch Abort'(3) Thread-Id=014a0002(pth=ffffc62c)
PC=00000000 BVA=c0b2d000, dwInfo = 00000400


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R0=0000000b R1=00000060 R2=821fd400 R3=00000000


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R4=821dde38 R5=00000000 R6=821b7870 R7=821b62f0


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R8=00000060 R9=821b7870 R10=821fcd20 R11=000000a0


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
R12=8011af00 SP=ffffc77c Lr=8011af84 Psr=20000013


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
Exception 'Prefetch Abort' (3): Thread-Id=014a0002(pth=83eab000), Proc-
Id=00400002(pprc=82200aa0) 'NK.EXE', VM-active=00400002(pprc=82200aa0)
'NK.EXE'


!KITLSend(DBGMSG): Reentrant call, Thread Id = 014A0002
PC=00000000(???+0x00000000) RA=8011af84(NK.EXE+0x0001af84)
SP=ffffc77c, BVA=00000000



Faulted in KCall, pCurThread->dwStartAddr = c0481120, PageFreeCount =
000008d0!!
Original Context when thread faulted:
Exception 'Prefetch Abort'(3) Thread-Id=014a0002(pth=83eab000)
PC=8013b23c BVA=c0b2d000, dwInfo = 00000400
R0=c0b2c2e0 R1=00000000 R2=000012d0 R3=c0b2d000
R4=c049829c R5=00000000 R6=00000000 R7=00000000
R8=00000000 R9=00009999 R10=00001010 R11=d245e388
R12=00000000 SP=d245d900 Lr=c0a9a46c Psr=2000001f
Context when faulted in KCall:
Exception 'Prefetch Abort'(3) Thread-Id=014a0002(pth=ffffbcc8)
PC=00000000 BVA=c0b2d000, dwInfo = 00000400
R0=0000000b R1=000002c6 R2=00000000 R3=00000000
R4=821dde38 R5=00000000 R6=821cf470 R7=821b62f0
R8=000002c6 R9=821cf470 R10=821fcd20 R11=00000000
R12=ffffbe28 SP=ffffbe18 Lr=8011af84 Psr=20000093
Exception 'Prefetch Abort' (3): Thread-Id=014a0002(pth=83eab000), Proc-
Id=00400002(pprc=82200aa0) 'NK.EXE', VM-active=00400002(pprc=82200aa0)
'NK.EXE'
PC=00000000(???+0x00000000) RA=8011af84(NK.EXE+0x0001af84)
SP=ffffbe18, BVA=00000000
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s).
This OK if KdStub stumbling on its own BP.
KdTrap: Exception in debugger, Addr=0x00000000 - attempting to
recover

RtlDispatchException: returning failure. Flags=0
NK Kernel: DEBUGCHK failed in file C:\ymzki\private\winceos\COREOS\nk
\kernel\nknormal\..\apicall.c at line 839
KPSLExceptionHandler: flags=1 ControlPc=fffffffc
RtlDispatchException: returning failure. Flags=1
NK Kernel: DEBUGCHK failed in file C:\ymzki\private\winceos\COREOS\nk
\kernel\nknormal\..\apicall.c at line 839
NK Kernel: DEBUGCHK failed in file C:\ymzki\private\winceos\COREOS\nk
\kernel\nknormal\..\exdsptch.c at line 333
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s).
This OK if KdStub stumbling on its own BP.
KdTrap: Exception in debugger, Addr=0xFFFFFFFC - unable to recover

Can any one suggest me something...

Thanks...
Top

Re: CE6.0 KITL Problem.... by Silver

Silver
Fri Apr 11 12:19:52 PDT 2008

Prefetch abort meansthat there was nothing mapped at the location the PC was
about to execute. There could be many reasons. It is likely that it has
something to do with KITL. So how did you setup KITL? What did you do to
select a transport?


Exception 'Prefetch Abort'(3) Thread-Id=014a0002(pth=83eab000)
PC=8013b23c BVA=c0b2d000, dwInfo = 00000400
Lr=c0a9a46c



Geoff
--

Top

Re: CE6.0 KITL Problem.... by Raghu

Raghu
Sun Apr 13 08:16:32 PDT 2008

Thansk for ur response.
I need to build a workpace for Pxa270 so i downloaded the
BSP from respective site and started building a platform (workspace)
for evaluation board.
During build i slected the build options for KITL.
IMAGENOKITL (KITL) along with platform debugger.

Build was succesfull.
While loading the image if i select the KITL support on target
device(Core OS settings on PB) using the flag provided by Platform
bulder(VS2005).
My image is not booting...i was geting above mentioned error.
If i disbale the KITL support on target device my image boots but
debugger won't be able to connect to target device.

I need to bring up the KITL but iam getting this error if i select
KITL.

Do i need to do anything else for KITL support.

Thanks,
Ragz

Top