Hi,

I have a strange problem booting my WinCE 6.0 kernel. I suspect my RAM to 
fail but I'm not sure: I can verify all data in the CSD0 with my Lauterbach 
JTAG. 

The original BSP uses a different DDR2 from Samsung with a size of 64Mbyte - 
I'm using a 128Mbyte.

When I do a debug build I get these msg (I'm running the exact same nk.bin 
on the development platform as these are very close to eachother and 
therefore I know which msg to expect):

Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 16 2009 at 10:08:41
ProcessorType=0926  Revision=4
OEMAddressTable = 801010f4
INFO:OALLogSetZonesÐ"ÁÕÉM•ÑÑ¥¹Í¹ulZoneMask: 0xb
CPLD Init 1
Reset cause : Power On Reset
OEMInit:  silicon rev = 0x2
OALI2cInit: Trying to init I2C Interface
dry ice initial status 0x103
dry ice status 0x3
RTC not running. turning it on now
EMB: OALinitRTC done
EMB: 1
Setting up softlog at 0x83ffc000 for 0x800 entries
Booting Windows CE version 6.00 for (ARM)
&pTOC = 8121bc1c, pTOC = 8120bb84, pTOC->ulRamFree = 81220000, MemForPT = 
000010
00

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 11732, Secondary pages: 0, Filesystem pages = 1466

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 81222000, extension: 00006000, length: 02dd4000
NKStartup done, starting up kernel.
Windows CE KernelInit     <---- ****** this is the last dbg msg I get on our 
own target ****
Reserve VM for kernel XIP DLls, first = c0010000, last = c0ce0000
g_pprcNK == 0x81219aa0
Updated eptr->e32_vsize to = 0001d000
Initializing Memory Mapped File Support
Scheduling the first thread.
Detecting VFP... VFP Not Found!
LoaderInit: Initialing loader
Updated eptr->e32_vsize to = 0001d000
Updated eptr->e32_vsize to = 000a2000
PGPOOL: Reserved 768 pages for Loader pool
PGPOOL: Reserved 256 pages for File pool

The crash is always here and as my Eboot and Lauterbach DRAM test is running 
perfectly. I don't think it's signal integrity?

Anybody that has a good rutine that do a random check of the DRAM from Eboot?

Any idea?

Thanks in advanced!

Well, if you changed the amount of something (RAM or Flash? we don't know), 
from 64MB to 128MB, you probably should change the memory map in your BIB 
file.  You did that?

Paul T.

"Brian A." <BrianA@discussions.microsoft.com> wrote in message 
news:7392AED1-029F-45EB-9047-16C2B63479B2@microsoft.com...
> Hi,
>
> I have a strange problem booting my WinCE 6.0 kernel. I suspect my RAM to
> fail but I'm not sure: I can verify all data in the CSD0 with my 
> Lauterbach
> JTAG.
>
> The original BSP uses a different DDR2 from Samsung with a size of 
> 64Mbyte -
> I'm using a 128Mbyte.
>
> When I do a debug build I get these msg (I'm running the exact same nk.bin
> on the development platform as these are very close to eachother and
> therefore I know which msg to expect):
>
> Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 16 2009 at 10:08:41
> ProcessorType=0926  Revision=4
> OEMAddressTable = 801010f4
> INFO:OALLogSetZones�"���M.�ѥ��͹ulZoneMask: 0xb
> CPLD Init 1
> Reset cause : Power On Reset
> OEMInit:  silicon rev = 0x2
> OALI2cInit: Trying to init I2C Interface
> dry ice initial status 0x103
> dry ice status 0x3
> RTC not running. turning it on now
> EMB: OALinitRTC done
> EMB: 1
> Setting up softlog at 0x83ffc000 for 0x800 entries
> Booting Windows CE version 6.00 for (ARM)
> &pTOC = 8121bc1c, pTOC = 8120bb84, pTOC->ulRamFree = 81220000, MemForPT =
> 000010
> 00
>
> Old or invalid version stamp in kernel structures - starting clean!
> Configuring: Primary pages: 11732, Secondary pages: 0, Filesystem pages = 
> 1466
>
> Booting kernel with clean memory configuration:
> Memory Sections:
> [0] : start: 81222000, extension: 00006000, length: 02dd4000
> NKStartup done, starting up kernel.
> Windows CE KernelInit     <---- ****** this is the last dbg msg I get on 
> our
> own target ****
> Reserve VM for kernel XIP DLls, first = c0010000, last = c0ce0000
> g_pprcNK == 0x81219aa0
> Updated eptr->e32_vsize to = 0001d000
> Initializing Memory Mapped File Support
> Scheduling the first thread.
> Detecting VFP... VFP Not Found!
> LoaderInit: Initialing loader
> Updated eptr->e32_vsize to = 0001d000
> Updated eptr->e32_vsize to = 000a2000
> PGPOOL: Reserved 768 pages for Loader pool
> PGPOOL: Reserved 256 pages for File pool
>
> The crash is always here and as my Eboot and Lauterbach DRAM test is 
> running
> perfectly. I don't think it's signal integrity?
>
> Anybody that has a good rutine that do a random check of the DRAM from 
> Eboot?
>
> Any idea?
>
> Thanks in advanced!