Re: how to make sure that kernel is up
- From: "Chitra" <chitrar25@xxxxxxxxxxx>
- Date: 15 Feb 2007 20:38:54 -0800
Hi Dean,
Thanks for the reply. I don't think there is any problem related to
memory. First I faced the problem while downloading the kernel. I
could download only 13% of the image and the code used to crash, then
I spotted the problem where there was overlap. After that I don't
think there is any problem. I present my config.bib here, please let
me know where could be the problem
MEMORY
; OEM specific reserved ram areas
DRVGLOBAL 80000000 00001000 RESERVED
RESERVED1 80001000 0000F000 RESERVED
DMA 80080000 00080000 RESERVED
FRAMEBUFFER 80100000 00100000 RESERVED
; NK 80300000 02300000 RAMIMAGE ; 35 MB
NK 81600000 01E00000 RAMIMAGE ; 30 MB
; RAM 82600000 01A00000 RAM ; 26 MB
RAM 83400000 00C00000 RAM ; 12 MB
EDBG 80010000 00020000 RESERVED
; ** Configuration **
CONFIG
AUTOSIZE=ON
ROMSTART=80300000
ROMWIDTH=32
ROMSIZE=02300000
COMPRESSION=OFF
KERNELFIXUPS=ON
;
; ROMFLAGS is a bitmask of options for the kernel
; ROMFLAGS 0x0001 Disallow Paging
; ROMFLAGS 0x0002 Not all KMode
; ROMFLAGS 0x0010 Trust Module only
;
#if defined IMGNOTALLKMODE
ROMFLAGS=2
#else
ROMFLAGS=0
#endif
and the OEMADDRESSTABLE is as follows:
g_oalAddressTable
DCD 0x80000000, 0x08000000, 64 ; 64MB SDRAM on SDCS0
DCD 0x84000000, 0x12000000, 16 ; 1MB Ethernet Controller
on CS1
DCD 0x85000000, 0x00200000, 1 ;1MB Internal registers
DCD 0x86000000, 0x10000000, 32 ; 8MB Strata Flash on CS0
DCD 0x88000000, 0x16000000, 16 ; 3MB CF on CS5
DCD 0x00000000, 0x00000000, 0 ; end of table
; ENDIF
Please Reply.
Thanks & Regards,
Chitra
On Feb 15, 7:54 pm, "Dean Ramsier" <ramsiernos...@xxxxxxxxxx> wrote:
You have definitely crashed somewhere. Difficult to tell what is going on,
are you sure you don't have memory problems?
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Chitra" <chitra...@xxxxxxxxxxx> wrote in message
news:1171541850.657542.134130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All,
I want to know that how can we know that the kernel is completely
up. I went through the msdn document for BSP development which
explains all kernel startup function and tell that
SystemStartupFunc is where calls are made to start kernel monitoring
through CreateKernelThread, and execute IOCTL_HAL_POSTINIT through the
OEMIoControl function. But the OEMIOControl function does not call
with IOCTL_HAL_POSTINIT, this I found out by printing debug message in
OEMIOControl function.
One more question is do I need to include anything from catalog items
like filesystem into the os design?
Below is the debug message I get on my debug console, Can anybody help
me in finding out what the problem could be. I am not able to track
what is happening. I am not enabling KITL also. Please reply.
Thanks & Regards,
Chitra
OEMDebugInit END
MS Win CE Bootloader for the FS MC9328MXL Version 2.5 Built Feb 13
2007
CS8900: MAC Address: 0:23:31:36:1:75
Reset: Reset SUCCESS (SelfST).
Reset: Reset SUCCESS (SIBUSY).
INFO: Probe: CS8900 is detected.
INFO: *** Device Name MC9328MXL373 ***
+EbootSendBootmeAndWaitForTftp
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 0A39
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
IN...HUHUHUHU..1.
TCMP1(0x2a4450) TPRER1(0x0) TCTRL1(0x115)
Enable GPT1 interrupt
IN...HUHUHUHU..2.
+OEMInit: rtcInit
CS8900a INTERRUPT ENABLED!!!
+OEMInit: OALKitlStart (KITL init)
Firmware Init Done
Booting Windows CE version 5.00 for (ARM)
&pTOC = 81609fac, pTOC = 8310efc8, pTOC->ulRamFree = 83485000,
MemForPT = 00000000
Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 2937, Secondary pages: 0, Filesystem pages
= 1468
+OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
-OEMCacheRangeFlush
Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 83486000, extension: 00001000, length: 00b79000
Sp=ffffc7cc
ARMInit done.
Windows CE KernelInit
HeapInit: Entry 00, size 0576
HeapInit: Entry 01, size 0228
HeapInit: Entry 02, size 0036
HeapInit: Entry 03, size 0168
HeapInit: Entry 04, size 0064
HeapInit: Entry 05, size 0016
HeapInit: Entry 06, size 0524
HeapInit: Entry 07, size 1024
+OEMCacheRangeFlush(0x00000000, 0, 0x00000001)
-OEMCacheRangeFlush
InitMemoryPool: Init range: map=83486000 start=0b487000 end=0c000000
InitMemoryPool done, free=1469
AllocHandle: pci=81604338 pvObj=832d6520 pprc=832d6520
FSB: 00000000 (0)
FSB: waste=0
AllocHandle: phd=83fff000 hValue=03fff002
AllocHandle: pci=8160434c pvObj=83fff024 pprc=832d6520
AllocHandle: phd=83fff264 hValue=03fff266
MDAllocMemBlock: dwBase = c2000000, ixBlock = 00000000
MDAllocMemBlock: pPtbls = 832d65ec ixTbl = 00000000
MDAllocMemBlock: Allocated a new page for Page Table va = a3ffe000
MDAllocMemBlock: Allocating MemBlock
MDAllocMemBlock: returning 83fff288, aPages = a3ffe000
pmb = 83fff288, pmb->aPages = a3ffe000
cbNKCoProcRegSize = 0, pSave = 00000000, pRestore = 00000000
OpenExecutable: nk.exe
OpenExecutable: plain name = nk.exe
OpenExecutable: Filesys not loaded, Opening from ROM
OpenExe nk.exe: ROM: 8310f01c
(10) o32rp->o32_realaddr = 81601000
Updated eptr->e32_vsize to = 000a0000
VirtualAlloc(c2000000, 10000, 202000, 1)
MakePagePerms: 00000001 returns 0000000c
MDAllocMemBlock: dwBase = c2000000, ixBlock = 00000001
MDAllocMemBlock: Allocating MemBlock
MDAllocMemBlock: returning 83fff298, aPages = a3ffe040
VirtualAlloc: reserved lock=1
VirtualAlloc: created head block pmb=83fff298 (1)
Reserved 16 pages @c2010000
VirtualAlloc(c201f000, 1000, 1000, 4)
MakePagePerms: 00000004 returns 0000055e
Scanning 1 pages. ixFirB=1, dwVMBase = c2000000
Scanning block 83fff298 (1), ix=15 cPgScan=1
Allocating 1 pages.
GetHeldPage: Returning 0bffd000
Mapping 0bffd000 @001f000 perm=55e
Returning c201f000
MDCT: pTh=83fff024 Pc=81641838 Psr=001f GP=00000000 Sp=c201fee0
Scheduler: Created master thread 83fff024
Scheduling the first thread.
0x83fff024: KernelInit2: pCurThread=83fff024 hCurThread=03fff266
hCurProc=03fff002, KernelInit = 8162316c
0x83fff024: Detecting VFP...0x83fff024: ExceptionDispatch:
pexi=c201fd64 Pc=81615f50
0x83fff024: addr c201fefc, id 1, sp c201fdbc, fsr=00000005, BVA =
81615f50
0x83fff024: VFP Not Found!
0x83fff024: SC_LoadKernelLibrary entry: hd.dll
0x83fff024: LoadOneLibraryPart2: hd.dll, 1, 0x8000
0x83fff024: LoadOneLibrary hd.dll (hd.dll), LoadHigh = 0
0x83fff024: OpenExecutable: hd.dll
0x83fff024: OpenExecutable: plain name = hd.dll
0x83fff024: OpenExecutable: Filesys not loaded, Opening from ROM
0x83fff024: OpenExe hd.dll: ROM: 8310f05c
0x83fff024: (10) o32rp->o32_realaddr = 816c7000
0x83fff024: ChkDebug returns 1
0x83fff024: lpszFileName = 'hd.dll', pMod->bTrustLevel = 2
0x83fff024: Updated eptr->e32_vsize to = 00006000
0x83fff024: BasePtr is 816c6000
0x83fff024: LoadO32 : get section information 0
0x83fff024: (2) o32rp->o32_realaddr = 816c7000
0x83fff024: LoadO32 : get section information 1
0x83fff024: (2) o32rp->o32_realaddr = 832ec000
0x83fff024: LoadO32 : get section information 2
0x83fff024: (2) o32rp->o32_realaddr = 816cd000
0x83fff024: LoadO32 : reading section 0
0x83fff024: virtualcopying 816c7000 <- 816c7000 (4d3d)!
0x83fff024: LoadO32 : reading section 1
0x83fff024: (5) realaddr = 832ec000, psize = 0000044a
0x83fff024: LoadO32 : reading section 2
0x83fff024: virtualcopying 816cd000 <- 816cc000 (b0)!
0x83fff024: InitModule: rwHigh = 832ec974, rwLow = 832ec000
0x83fff024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: FindEntryPoint realaddr = 816c7000, entry = 00002d58, rva
= 00001000
0x83fff024: Done InitModule, StartIP = 816c8d58
0x83fff024: DoImports: eptr = 83fff33c, BaseAddr = 816c6000
0x83fff024: ObjectCall: obs = c201fc04, ra=816c8d94 h=83fff2cc
iMethod=ffffffea mode=1f extra=f000ffa8, prevSP = 00000000
0x83fff024: ObjectCall: 81603348 'Wn32' API call #22. disp=3.
0x83fff024: KPSLDispatch: pci 81603348, fnptr 816475c0
0x83fff024: SC_OpenEvent entry: 001f0003 00000000 8161330c c201fb10
0x83fff024: SC_OpenEvent exit: 00000000
0x83fff024: SCR: psrs = c201fc18
0x83fff024: SCRet: return to 816c8d94 Proc=832d6520 aky=1, mode =
0000001f
0x83fff024: SCRet: Before return psrs->mode = 1f, psrs->prevSP =
00000000
0x83fff024: SC_LoadKernelLibrary exit: 83fff2cc
0x83fff024: Hdstub loaded
0x83fff024: SC_CreateCrit entry: 832ec960
0x83fff024: SC_CreateCrit exit: 83fff47c
0x83fff024: SC_LoadKernelLibrary entry: osaxst0.dll
0x83fff024: LoadOneLibraryPart2: osaxst0.dll, 1, 0x8000
0x83fff024: LoadOneLibrary osaxst0.dll (osaxst0.dll), LoadHigh = 0
0x83fff024: OpenExecutable: osaxst0.dll
0x83fff024: OpenExecutable: plain name = osaxst0.dll
0x83fff024: OpenExecutable: Filesys not loaded, Opening from ROM
0x83fff024: OpenExe osaxst0.dll: ROM: 8310f07c
0x83fff024: (10) o32rp->o32_realaddr = 816ce000
0x83fff024: ChkDebug returns 1
0x83fff024: lpszFileName = 'osaxst0.dll', pMod->bTrustLevel = 2
0x83fff024: Updated eptr->e32_vsize to = 00029000
0x83fff024: BasePtr is 816cd000
0x83fff024: LoadO32 : get section information 0
0x83fff024: (2) o32rp->o32_realaddr = 816ce000
0x83fff024: LoadO32 : get section information 1
0x83fff024: (2) o32rp->o32_realaddr = 832ed000
0x83fff024: LoadO32 : get section information 2
0x83fff024: (2) o32rp->o32_realaddr = 816fa000
0x83fff024: LoadO32 : reading section 0
0x83fff024: virtualcopying 816ce000 <- 816ce000 (27084)!
0x83fff024: LoadO32 : reading section 1
0x83fff024: (5) realaddr = 832ed000, psize = 00000842
0x83fff024: LoadO32 : reading section 2
0x83fff024: virtualcopying 816fa000 <- 816f6000 (330)!
0x83fff024: InitModule: rwHigh = 832f0098, rwLow = 832ed000
0x83fff024: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x83fff024: -OEMCacheRangeFlush
0x83fff024: FindEntryPoint realaddr = 816ce000, entry = 00012b80, rva
= 00001000
0x83fff024: Done InitModule, StartIP = 816dfb80
0x83fff024: DoImports: eptr = 83fff594, BaseAddr = 816cd000
0x83fff024: ExceptionDispatch: pexi=c201fc24 Pc=8162202c
0x83fff024: addr c201fefc, id 1, sp c201fc50, fsr=00000005, BVA =
8162202c
0x83fff024: ObjectCall: obs = c201fc04, ra=816dfbbc h=83fff524
iMethod=ffffffea mode=1f extra=f000ffa8, prevSP = 00000000
0x83fff024: ObjectCall: 81603348 'Wn32' API call #22. disp=3.
0x83fff024: KPSLDispatch: pci 81603348, fnptr 816475c0
0x83fff024: SC_OpenEvent entry: 001f0003 00000000 8161330c c201fb10
0x83fff024: SC_OpenEvent exit: 00000000
0x83fff024: SCR: psrs = c201fc18
0x83fff024: SCRet: return to 816dfbbc Proc=832d6520 aky=1, mode =
0000001f
0x83fff024: SCRet: Before return psrs->mode = 1f, psrs->prevSP =
00000000
0x83fff024: SC_LoadKernelLibrary exit: 83fff524
...
read more »- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: how to make sure that kernel is up
- From: Dean Ramsier
- Re: how to make sure that kernel is up
- References:
- how to make sure that kernel is up
- From: Chitra
- Re: how to make sure that kernel is up
- From: Dean Ramsier
- how to make sure that kernel is up
- Prev by Date: Re: Does Evaluation version work fine..?
- Next by Date: Re: Does Evaluation version work fine..?
- 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):
Relevant Pages
|
