Stuck at "Jumping to 0x00224D50" when booting up Win CE 6.0 image

[jrdchan]

Hi,

I am new to Win Ce, so please bear with me :)

I have downloaded the BSP for Atom processor from Bsquare and managed to
create an NK.bin image and setting up the harddisk with CEPCboot.144.

With NK.bin on the harddisk, i chose "Boot CE/PC (local nk.bin) at startup.
I see text rolling "Physical Sector ..." and percentages. All is good until
the screen blanks and text "Jumping to 0x00224D50" appears then system just
sits and waits.

Can anyone enlighted me what could be the issue and any document I can study?

regards Dawn

[Paul G. Tobey [ eMVP ]]

That's the point at which CE boots. It might indicate that you've built a
DEBUG image and the device is trying to connect to Platform Builder. It
might indicate that you built the OS wrong (config.bib, etc.), and there was
an exception early in boot. It might indicate that you included the wrong
display adapter, wrong display settings, wrong display type, etc. and the OS
is running fine, but the display simply isn't working.

We have no way to tell these apart based on what you've told us...

Paul T.

[handy1983]

Hello Paul,

thanks for you answer.
You're write, it's not stopping at "Jumping to XYZ".
So I will look at it and give you some news.

thanks

Nicolas

"Paul G. Tobey [eMVP]" wrote:

> You have a ton of information there. You can see that, in fact, it's not
> stopping at Jumping to XYZ, is it? It's starting Windows CE and that appears
> to me to be running just fine. The fact that your display is blank indicates
> one of the following, most of the time: you built the OS without display
> support, so nothing is drawn, you have display support but did not include an
> adapter driver for your display adapter, you included the adapter driver, but
> the adapter is not present or disabled, or the driver is not correctly
> configured. Since I see some font stuff happening, I'd say that your OS has
> display support. I don't see the display driver being loaded, although I
> might have missed it. You'll have to find and fix the problem...
>
> Paul T.

[handy1983]

Hello Paul,

I found why my display drivers wasn't load. It was because I was loading
"ddi_nop.ddl" (no display driver). Now I'm still stuck with "Jumping to XYZ"
message but as you can see in this debug nk.exe is trying to load
"ddi_flat.dll" :
Ceddk!CalibrateStallCounter: Stall counter loaded from registry(170)
System Default HKL value set to 00000409
Grow Gdi handle table from 0 to 64
LogFontFromRegistry(SYSTEM\GDI\SysFnt), lfHeight = -12OSAXST1: >>> Loading
Module 'ddi_flat.dll' (0x8A8AB09C) at address 0xC0AF0000-0xC0B35000 in
Process 'NK.EXE' (0x82651C80)
OEMSetMemoryAttributes: nRegNeeded = 6
Setting MTRR reg-pair:2 with 0x00000000800a0001, 0x0000000ffffe0800
Setting MTRR reg-pair:3 with 0x00000000800c0001, 0x0000000ffffc0800
Setting MTRR reg-pair:4 with 0x0000000080100001, 0x0000000ffff00800
Setting MTRR reg-pair:5 with 0x0000000080200001, 0x0000000fffe00800
Setting MTRR reg-pair:6 with 0x0000000080400001, 0x0000000ffff80800
Setting MTRR reg-pair:7 with 0x0000000080480001, 0x0000000ffffe0800
AllocSurface - Out of Memory 2
Couldn't allocate primary surface
Exception 'Access Violation' (14): Thread-Id=03910002(pth=8a89e75c),
Proc-Id=00400002(pprc=82651c80) 'NK.EXE', VM-active=00400002(pprc=82651c80)
'NK.EXE'
PC=c0afa65a(ddi_flat.dll+0x0000a65a) RA=c0afe393(ddi_flat.dll+0x0000e393)
SP=d140f304, BVA=0000001c
*** FAILED TO INITIALIZE DISPLAY DRIVER (ddi_flat.dll)! ***
*** MAKE SURE DISPLAY DRIVER CONFIGURATION SETTINGS ARE CORRECT! ***
Unknown: DEBUGCHK failed in file
D:\Dublin2-14\private\winceos\COREOS\gwe\mgdi\base\.\driver.cpp at line 118
KdTrap: JIT debugging requested, waiting for OEM selection

KdTrap: JIT debugging accepted

Even if I can clearly see the error, I'm still not able to correct it. I'm
wondering if you can give me more information about this error.
My chipset is :Mobile Intel® 945GSE Express Chipset.

Thanks for your time.

Regards

Nicolas