Re: Does Evaluation version work fine..?

From: "Arun" <sirsiarunhegde@xxxxxxxxx>
Date: 16 Feb 2007 00:51:23 -0800

Hi,

I am working on MC9328MXL ARM920T architecture and using WINCE 5.0
evaluation version. I have set g_OalLogmask = 0xffffffff in OEMInit()
and below is the debug message I get on my debug console. I have not
enabled KITL.

Sent BOOTME to 255.255.255.255
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 06AE
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.
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 = 816231b8
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: +OEMCacheRangeFlush(0x00000000, 0, 0x00000004)
0x8

Thanks,
Arun

On Feb 16, 12:54 pm, "Henrik Viklund" <henrik.vikl...@xxxxxxxxx>
wrote:

For anyone to give a reasonably good answer to your question, it
wouldn't hurt to tell us exactly what platform and CPU architecture
you're trying to bring up, as well as providing as solid debug
information you can get.

Henrik Viklundhttp://www.addlogic.se

On Feb 16, 6:36 am, "Arun" <sirsiarunhe...@xxxxxxxxx> wrote:

Hi Thanks for your reply,

The problem is I am stuck in kernelInit2() function, I thought It
could be due to evaluation version. Any hint where could the problem
be, does only config.bib matter in bringing up the kernel because I am
sure that no memory overlap happening in my config.bib or any other
configuration files could be a problem like platform.bib or
platform.reg. please reply.

Thanks,
Arun

On Feb 16, 9:38 am, "<ctacke/>" <ctacke[@]opennetcf[dot]com> wrote:

The evaluation is no different that the release version except for the time
limit on use.

--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded Worldwww.opennetcf.com
--

"Arun" <sirsiarunhe...@xxxxxxxxx> wrote in message

news:1171599941.299153.309430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi all,
I m using evaluation version of WinCE 5.0. i got stuck in
bringing up the kernel. I want to know will the evaluation version be
helpful in bringing up the kernel. Has anybody used evaluation version
and got it working fine.

Thanks
Arun- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

References:
- Does Evaluation version work fine..?
  - From: Arun
- Re: Does Evaluation version work fine..?
  - From: <ctacke/>
- Re: Does Evaluation version work fine..?
  - From: Arun
- Re: Does Evaluation version work fine..?
  - From: Henrik Viklund

Prev by Date: Re: Platform Manager
Next by Date: Re: Platform Manager
Previous by thread: Re: Does Evaluation version work fine..?
Next by thread: [WinCE 5.0] Attaching Device over Ethernet get disconnected at the end?
Index(es):
- Date
- Thread

Relevant Pages

IXDP425: SwitchToDataCoherent
... I have a intel IXDP425 Step A0 board and I use a Windows CE.net 4.2 evaluation. ... but when i download kernel image i see in the debug console: ... OEMInit: Beginning Kernel level Initialization of IXDP425 ...
(microsoft.public.windowsce.embedded)
Re: [patch 0/2] Immediate Values - jump patching update
... assembly ("g" constraints for all the expressions), ... That unconditional evaluation can easily entail memory reads and ... trace things, which i believe any usable kernel tracer must offer), ... runtime overhead that current markers have. ...
(Linux-Kernel)
Re: Unresolved external _NkForceCleanBoot in function _OEMInit
... and the NKForceCleanBoot API was added to cover this condition. ... one recipe for forcing a clean boot was: ... void OEMInit() ... It seems strange that the kernel loaded coredll to call kernel-only ...
(microsoft.public.windowsce.platbuilder)
Re: Simple PB question...
... Anywhere in OEMInit() should be fine. ... that would be BSP specific. ... kernel portion of the BSP, it's probably easier to just rebuild the whole ... >>> power cycle, but now it seems this build does not. ...
(microsoft.public.windowsce.embedded)
Re: [patch 0/2] Immediate Values - jump patching update
... assembly ("g" constraints for all the expressions), ... That unconditional evaluation can easily entail memory reads and ... it would, with the current debug info format, enlargen the kernel RAM ...
(Linux-Kernel)