Re: Problem with KITL?

From: Bruce Eitman \(eMVP\) (beitmannospam_at_NOSPAM_applieddata.NOSPAM_net)
Date: 02/21/05 

Date: Mon, 21 Feb 2005 08:50:16 -0500

I wouldn't get my hopes up that this is a problem in Microsoft's code, not
to say that it isn't. Macallan was the code name for CE 5.0 at MS, if you
change that the WinCE420 you may find the file on your disk. What I don't
see in your output is any debug messages coming from your send/receive
functions. Does it work in polled mode? Do you have the address for the
Ethernet controller set correctly for your board? 

-- 
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
 www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"eijar" <eijar@discussions.microsoft.com> wrote in message
news:D45F57E9-7B25-4568-BE54-FFF164098179@microsoft.com...
> Hi!
>
> I haven't turned on more debug messages yet, but I tried to change my
> platform's build options. Following options are enabled
>
> Buffer tracked events in RAM
> Enable CE target control support
> Enable Eboot space in memory
> Enable event tracking during boot
> Enable full kernel mode
> Enable kernel debugger
> Enable KITL
>
> I can debug my code and I can see that code execution stops when running
> KCall((PKFN)SetThreadBasePrio, hCurThread, dwNKAlarmThrdPrio) function
from
> schedule.c. Only nk.exe process is running. Here are messages that I can
see
> from hyperterminal
>
> ARMInit done.
> +KITLRegisterDfltClient, service:2
> ProcessAdminMsg: Receive Config message for service KDBG
> ProcessAdminMsg: Receive Config message for service KDBG
> ProcessAdminMsg: Receive Config message for service KDBG
>   MarshalProcessesAsModules: Process ID 0x01FDF002 (NK.EXE) not using
> CoreDll.dll, may be in startup or shutdown.
>
>   MarshalProcessesAsModules: Process ID 0x01FDF002 (NK.EXE) not using
> CoreDll.dll, may be in startup or shutdown.
>
>   MarshalProcessesAsModules: Process ID 0x01FDF002 (NK.EXE) not using
> CoreDll.dll, may be in startup or shutdown.
>
>   GetProcessDebugInfo: Process ID 0x01FDF002 (NK.EXE) not using
CoreDll.dll,
> may be in startup or shutdown.
>
> KITL: Leaving polling mode...
> KITL Checking client registrations
> +RegisterClientPart2: Id 0x00000000
> KITL Timer thread started, (hTh: 0x01FDBF8E, pTh: 0x81FA75F8)
> -RegisterClientPart2
> +RegisterClientPart2: Id 0x00000001
> -RegisterClientPart2
> KITL Creating IST
> KITL Interrupt thread started (hTh: 0xA1FA4642, pTh: 0x81FA4400), using
> SYSINTR 16
> Enabling adapter ints...
> 0x81fdf024: [Stack fault]: Thread=81fdf024 Proc=81f0c720 'NK.EXE'
> 0x81fdf024: AKY=ffffffff PC=801ab864(NK.EXE+0x000ab864)
> RA=801adc50(NK.EXE+0x000adc50) BVA=c2011fe4 FSR=00000007
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801AB864 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
> 0x81fdf024: NKDispatchException: returning failure. Flags=1
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801AB864 -  unable to recover
>
> 0x81fdf024:
> Unhandled exception c00000fd:
> 0x81fdf024: Terminating thread 81fdf024
> 0x81fdf024: Secondary thread in proc 01fdf002 (NK.EXE) faulted!
> 0x81fdf024: Terminating process 01fdf002 (NK.EXE)!
> 0x81fdf024: Invalid handle: Set=1 Method=9
> 0x81fdf024: <<< Unloading module coredll.dll at address
> 0x03F10000-0x04000000 (RW data at 0x01FFE000-0x01FFF7A5)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: <<< Unloading module celog.dll at address
0x8021E000-0x80223000
> (RW data at 0x81F41000-0x81F4157C)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\loader.c at line 1982
> 0x81fdf024: <<< Unloading module kd.dll at address 0x801C0000-0x801E2000
(RW
> data at 0x81F28000-0x81F3A188)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\loader.c at line 1982
> 0x81fdf024: <<< Unloading module osaxst1.dll at address
> 0x80214000-0x8021D000 (RW data at 0x81F40000-0x81F40960)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\loader.c at line 1982
> 0x81fdf024: <<< Unloading module osaxst0.dll at address
> 0x801EA000-0x80213000 (RW data at 0x81F3C000-0x81F3F098)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\loader.c at line 1982
> 0x81fdf024: <<< Unloading module hd.dll at address 0x801E3000-0x801E9000
(RW
> data at 0x81F3B000-0x81F3B974)
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  attempting to recover
>
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x801279D0 -  unable to recover
>
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\loader.c at line 1982
> 0x81fdf024: Data Abort: Thread=81fdf024 Proc=81f0c720 'NK.EXE'
> 0x81fdf024: AKY=ffffffff PC=80191dd0(NK.EXE+0x00091dd0)
> RA=80191c6c(NK.EXE+0x00091c6c) BVA=c2000004 FSR=00000007
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x80191DD0 -  attempting to recover
>
> 0x81fdf024: NKDispatchException: no CALLSTACK object to continue...
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
>   KdTrap: Exception in debugger, Addr=0x80191DD0 -  unable to recover
>
> 0x81fdf024:
> Unhandled exception c0000005:
> 0x81fdf024: Exception 'Data Abort' Thread=81fdf024 AKY=ffffffff
PC=00000000
> BVA=c2000004
> 0x81fdf024:  R0=00000001  R1=0000006d  R2=00000008  R3=00000061
> 0x81fdf024:  R4=80174074  R5=c201f3dc  R6=276a6a1c  R7=00000322
> 0x81fdf024:  R8=002ed9e6  R9=00000000 R10=00000322 R11=00000001
> 0x81fdf024: R12=00000322  SP=c201f400  Lr=002ed9e6 Psr=8000001f
> 0x81fdf024: Can't terminate thread 81fdf024, sleeping forever
> 0x81fdf024: ERROR: c:\macallan\private\winceos\coreos\nk\kernel\schedule.c
> line 5288: 0x81fdf024: Abandoning CS 81f0c5a0 in PuntCritSec
> 0x81fdf024: NK Kernel: DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\arm\mdarm.c at line 1086
> 0x81fdf024: NKDispatchException: no CALLSTACK object to continue...
> 0x81fdf024: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1
> time(s). This OK if KdStub stumbling on its own BP.
> KdTrap: Exception in debugger, Addr=0x80191DD0 -  unable to recover
>
> As you can see there are messages
> "ERROR: c:\macallan\private\winceos\coreos\nk\kernel\schedule.c"
> and
> "DEBUGCHK failed in file
> c:\macallan\private\winceos\coreos\nk\kernel\arm\mdarm.c at line 1086 ".
> I don't have any "macellan" directory and I don't know where my code gets
> that. Is the problem schedule.c file that is not in "macellan" directory?
>
> Thanks!
>
>
> "Steve Maillet (eMVP)" wrote:
>
> > Typically I see devices stall at this point when the IDE is not set up
to
> > listen for the correct device name. (It's actually possible to set up
the
> > IDE to use a different name for the boot loader and KITL.) This results
> > either from incorrect settings in the IDE OR from bad code in either the
> > boot loader or OAL where it's determining the device name
inconsistently.
> >
> > -- 
> > Steve Maillet
> > EmbeddedFusion
> > www.EmbeddedFusion.com
> > smaillet at EmbeddedFusion dot com
> >
> >
> >

Relevant Pages

  • Re: Problem with KITL?
    ... Recursively calling KDEnableInt(FALSE, psvdThread!= NULL) 1 ... This OK if KdStub stumbling on its own BP. ... Exception in debugger, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: You wanted defensive writing...
    ... Couldn't you have set the debugger to break on all exceptions? ... > I've created an application that loads Caudill's TreeListView as its ... > I commented the line that called the insertion on start-up, ... > The exception caught me unaware, ...
    (microsoft.public.dotnet.general)
  • Re: You wanted defensive writing...
    ... Couldn't you have set the debugger to break on all exceptions? ... > I've created an application that loads Caudill's TreeListView as its ... > I commented the line that called the insertion on start-up, ... > The exception caught me unaware, ...
    (microsoft.public.dotnet.csharp.general)
  • Re: Yet again - closing a thread
    ... effort was involved in adding exception handlers to recover at each level where recovery ... I was able to recover and keep running. ... it is very likely a bug in the program. ... then the Wait will not fail. ...
    (microsoft.public.vc.mfc)
  • Re: Reconnect after Oracle maintenance
    ... maintenance), but once in a while it is still not able to recover, and ... driver level caching of the older corrupt connections that are retained ... When the DB recovers, our application throws the following exception, ...
    (microsoft.public.dotnet.framework.adonet)
Loading