Re: how to make sure that kernel is up

From: "Chitra" <chitrar25@xxxxxxxxxxx>
Date: 19 Feb 2007 02:29:08 -0800

Hi,

I have not enabled KITL so I cannot try this.

I have gone through many posts in this group and I have seen some
difference in my debug output before the following debug statement

!!!!!!!!!!!!!!!!!!!!!!!
FS: initializing ROM/RAM file system
!!!!!!!!!!!!!!!!!!!!!!!!

In the post the debug messages are as follows which I don't get in my
debug terminal

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
4294767347 PID:bfff002 TID:bfff266 0x8bfff024: >>> Loading module
coredll.dll at address 0x03F00000-0x03FF2000 (RW data at
0x01FFE000-0x01FFF7A5)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\CMPD\RELDIR\TAHITI_ARMV4I_DEBUG
\COREDLL.DLL'
4294767373 PID:2bfe5cc6 TID:2bfe5ca2 0x8bfe5a60: >>> Loading module
coredll.dll at address 0x03F00000-0x03FF2000 (RW data at
0x01FFE000-0x01FFF7A5)
4294767377 PID:2bfe5cc6 TID:2bfe5ca2 0x8bfe5a60: >>> Loading module
filesys.exe at address 0x04010000-0x0409F000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\CMPD\RELDIR\TAHITI_ARMV4I_DEBUG
\FILESYS.EXE'
4294767382 PID:2bfe5cc6 TID:2bfe5ca2 0x8bfe5a60: CertMod.dll not
found,
using old OEM Trust Model
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I don't get any message like "loaded module coredll.dll" or
"filesys.exe". As I am getting "FS: initializing ROM/RAM file system"
does it imply that all modules such as coredll.dll or filesys.exe are
loaded successfully. If I have to get these messages should I turn ON
some zone flags.
Please reply.

Thanks & Regards,
Chitra

On Feb 19, 10:46 am, vinoth <vin...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,
Are you getting target control shell.if you get then try "gi proc" command
there. if it will show the processes running currently then your kernel is
working fine.
--
vinoth.R
software Engineer

"Chitra" wrote:

Hi Vinoth,

I tried as you said, I included RAM/ROM based filesystem and this
is what I get in my debug console.

FS: initializing ROM/RAM file system
0x83fed024: SC_CreateAPIHandle: pvData == NULL
0x83fed024: FS: Registering file system ROM, index 2, flags 0x00000031
0x83fed024: FS: Mount complete (ROM, index 2, flags 0x00000031)

Is this debug message correct.

Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 172.16.5.35 Port 0400 Dest IP 172.16.5.142 Port 088A
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
EbootInitEtherTransport success
rom_offset=0x0.
ROMHDR at Address 81600044h
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
OEMLaunch::flag : 0x00000000h ...
INFO: OEMLaunch: Jumping to Physical Address 0x9601000h (Virtual
Address 0x81601000h)...

CALLING OEMLaunch::::
Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at
18:21:58
ProcessorType=0920 Revision=0
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable =
81601270
OAL hello message!
+
Building Date: "__DATE__", Time: "__TIME__"
+Power on Reset - Clear RAM
+OEMInit: InitClock
TCMP1(0x2a4450) TPRER1(0x0) TCTRL1(0x115)
Enable GPT1 interrupt
+OEMInit: rtcInit
CS8900a INTERRUPT ENABLED!!!
+OEMInit: OALKitlStart (KITL init)
Firmware Init Done
Booting Windows CE version 5.00 for (ARM)
&pTOC = 81609fac, pTOC = 8310c64c, pTOC->ulRamFree = 8346f000,
MemForPT = 00000000

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 2959, Secondary pages: 0, Filesystem pages
= 1479
+OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
-OEMCacheRangeFlush

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 83470000, extension: 00001000, length: 00b8f000
Sp=ffffc7cc
ARMInit done.
MMC INTERRUPT RCVD.......
MMC INTERRUPT END
Windows CE KernelInit
+OEMCacheRangeFlush(0x00000000, 0, 0x00000001)
-OEMCacheRangeFlush
Updated eptr->e32_vsize to = 000a0000
Scheduling the first thread.
0x83fff024: KernelInit2: pCurThread=83fff024 hCurThread=03fff266
hCurProc=03fff002, KernelInit = 816231f8
0x83fff024: Detecting VFP...0x83fff024: VFP Not Found!
0x83fff024: first = 01e30000, last = 02000000, SharedDllBase =
026c0000
0x83fff024: +OEMCacheRangeFlush(0x03f01000, 900584, 0x00000018)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: +OEMCacheRangeFlush(0xc3ffe000, 6053, 0x00000018)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: +OEMCacheRangeFlush(0x03fdf000, 23080, 0x00000018)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: +OEMCacheRangeFlush(0x03fe5000, 25252, 0x00000018)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: +IN IN OEMIoControl(0x10100b4, 0x0, 0, 0x0, 0, 0x0)
0x83fff024: +IN IN 2 OEMIoControl(0x10100b4,----- 0x101010c)
0x83fff024: +IN OEMIoControl::IOCTL_HAL_POSTINIT::::;;0x83fff024: +IN
IN 2 OEMIoControl(0x10100b4, 0x0, 0, 0x0, 0, 0x0)
0x83fff024: In OEMGetRealTime:::::::::
0x83fff024: END OEMGetRealTime:::::::::
0x83fff024: In OEMGetRealTime:::::::::
0x83fff024: END OEMGetRealTime:::::::::
0x83fff024: In OEMGetRealTime:::::::::
0x83fff024: END OEMGetRealTime:::::::::
0x83ff0400: In OEMGetRealTime:::::::::
0x83ff0400: END OEMGetRealTime:::::::::
0x83ff0400: In OEMGetRealTime:::::::::
0x83ff0400: END OEMGetRealTime:::::::::
0x83ff0a40: In OEMGetRealTime:::::::::
0x83ff0a40: END OEMGetRealTime:::::::::
0x83ff0ca4: +OEMCacheRangeFlush(0x00000000, 0, 0x00000003)
0x83ff0ca4: -OEMCacheRangeFlush
0x83ff0ca4: +OEMCacheRangeFlush(0xc2030000, 65536, 0x00000018)
0x83ff0ca4: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x040a0000, 4096, 0x00000003)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x040a0000, 4096, 0x00000018)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x04011000, 526616, 0x00000018)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x04092000, 39208, 0x00000018)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x0409c000, 7232, 0x00000018)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x0409e000, 164, 0x00000018)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: In OEMGetRealTime:::::::::
0x83fed024: END OEMGetRealTime:::::::::
+OEMCacheRangeFlush(0x00000000, 0, 0x00000018)
-OEMCacheRangeFlush
0x83ff0ca4: +OEMCacheRangeFlush(0x00000000, 0, 0x00000003)
0x83ff0ca4: -OEMCacheRangeFlush
0x83ff0ca4: +OEMCacheRangeFlush(0xc2050000, 65536, 0x00000018)
0x83ff0ca4: -OEMCacheRangeFlush
0x83fed024: CertMod.dll not found, using old OEM Trust Model
0x83fed024: FileSystem Starting - starting with clean file system
0x83fed024: +IN IN OEMIoControl(0x1010038, 0x40afb80, 16, 0x0, 0,
0x40afb90)
0x83fed024: +IN IN 2 OEMIoControl(0x10100b4,----- 0x101010c)
0x83fed024: In OEMGetRealTime:::::::::
0x83fed024: END OEMGetRealTime:::::::::
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: In OEMGetRealTime:::::::::
0x83fed024: END OEMGetRealTime:::::::::
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: In OEMGetRealTime:::::::::
0x83fed024: END OEMGetRealTime:::::::::
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: In OEMGetRealTime:::::::::
0x83fed024: END OEMGetRealTime:::::::::
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: FS: initializing ROM/RAM file system
0x83fed024: SC_CreateAPIHandle: pvData == NULL
0x83fed024: FS: Registering file system ROM, index 2, flags 0x00000031
0x83fed024: FS: Mount complete (ROM, index 2, flags 0x00000031)
0x83fed024: +IN IN OEMIoControl(0x101008c, 0x0, 0, 0x40af9f0, 4,
0x40af9f4)
0x83fed024: +IN IN 2 OEMIoControl(0x10100b4,----- 0x101010c)
0x83fed024: OEMIOCTL: ERROR: Unsupported IOCTL
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: Succeeded on CheckFile
0x83fed024: RestoreFile(0x03fdbcf2) called fDelete = TRUE
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fed024: -OEMCacheRangeFlush
0x83fed024: +OEMCacheRan

and the code hangs. Please reply.

Thanks & Regards,
Chitra

...

read more »- Hide quoted text -

- Show quoted text -

Follow-Ups:
- Re: how to make sure that kernel is up
  - From: Dean Ramsier

References:
- how to make sure that kernel is up
  - From: Chitra
- RE: how to make sure that kernel is up
  - From: vinoth
- Re: how to make sure that kernel is up
  - From: Chitra
- Re: how to make sure that kernel is up
  - From: vinoth

Prev by Date: Re: USB Mass Storage Device ( Not able to open the drive)
Next by Date: Re: Wince5.0 Hyper Terminal and Debug window Hangs up showing Enabling adapter ints...
Previous by thread: Re: how to make sure that kernel is up
Next by thread: Re: how to make sure that kernel is up
Index(es):
- Date
- Thread

Relevant Pages

[PATCH 1/3] CodingStyle updates
... +emit the message, you'll need to turn on DEBUG in your code, which can be ... +The kernel includes macros called likelyand unlikely, ... Suppose you're developing a file system ... +to have a file system with lots of block devices? ...
(Linux-Kernel)
PRB:wince.nls in CE5.0
... FileSystem Starting - starting with clean file system ... 0x83ce5024: FS: Registering file system StoreMgr, index 3, flags 0x00000001 ... 0x83ce5024: NK Kernel: DEBUGCHK failed in file ... The debug messages above will continue again and again, ...
(microsoft.public.windowsce.platbuilder)
Re: how to make sure that kernel is up
... Yes just confirm your behaviour of SDRAM. ... difference in my debug output before the following debug statement ... FS: initializing ROM/RAM file system ... MMC INTERRUPT END ...
(microsoft.public.windowsce.platbuilder)
Kitl cannot connect
... I am trying to get kitl working in order to debug my platform. ... Old or invalid version stamp in kernel structures - starting clean! ... FileSystem Starting - starting with clean file system ...
(microsoft.public.windowsce.platbuilder)
2.6.27-rc7 no init found on the root partition?
... but the kernel is unable to boot. ... XFS file system but no init found. ... it complains that root file system not found and I have ... # Input Device Drivers ...
(Linux-Kernel)