I modified my Windos CE 4.2 BSP according the new directory layout and the
source file, update the environment setting, .cec file and etc,(not PQ OAL).
after I compiled my BSP, there is no GWES.exe generated in the
platform_dir\target\ARMV4I\retail\ directory, and when I boot this image, I
got the following message. BTW, when I remove the Display driver from the
NK.bin , the message almost the same:

====Without Display driver======
Windows CE Firmware Init
HalTimerInit()
InitClock()...
InitParallelPort()...
Clearing object store...
Clear pending gpio edge detects...
Calling KitlInit(FALSE)
KITL Initialized, passive mode
OEMInit Done.
Sp=ffffc7cc
OAL: GetUUID failed, no UUID available
OAL: OEMIoControl(IOCTL_HAL_GET_HWENTROPY): Returning FALSE
Data Abort: Thread=93f3a000 Proc=9150b660 'gwes.exe'
AKY=00000011 PC=00054c14(gwes.exe+0x00044c14)
RA=0004ce50(gwes.exe+0x0003ce50) B
VA=0a000008 FSR=00000007

=====With Display driver=====
Windows CE Firmware Init
HalTimerInit()
InitClock()...
InitParallelPort()...
Clearing object store...
Clear pending gpio edge detects...
Calling KitlInit(FALSE)
KITL Initialized, passive mode
OEMInit Done.
Sp=ffffc7cc
OAL: GetUUID failed, no UUID available
OAL: OEMIoControl(IOCTL_HAL_GET_HWENTROPY): Returning FALSE
Starting Load GPE ===Charles
Initializing Display
Display: DispDrvrInitialize: Attempting to map lcd controller registers...
Display: DispDrvrInitialize: Attempting to map control bit register address
rang
es...
Display: DispDrvrInitialize: Attempting to intialize frame buffer...
Display: VirtualAlloc...
Display: VirtualCopy...
Starting Load GPE ===Charles
Starting Load GPE ===Charles
Prefetch Abort: Thread=93f3a000 Proc=9150b660 'gwes.exe'
AKY=00000011 PC=00740053(gwes.exe+0x00730053)
RA=031779bc(ddi.dll+0x000079bc) BV
A=00740053 FSR=000004f0
Data Abort: Thread=93f3a000 Proc=9150b660 'gwes.exe'
AKY=00000011 PC=00052c30(gwes.exe+0x00042c30)
RA=000527c4(gwes.exe+0x000427c4) B
AKY=00000011 PC=00052c30(gwes.exe+0x00042c30)
RA=000527c4(gwes.exe+0x000427c4) B

Re: GWES in Windows CE 5.0 by Steve

Steve
Mon Dec 13 10:43:48 CST 2004

GWES.EXE is no longer built in the BSP as the NLED driver is pulled out of
GWES in V5.0. The errors you are getting are usually associated with bugs in
the display driver. Using the kernel debugger you can quickly identify the
source of the problem.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: GWES in Windows CE 5.0 by CharlesWang

CharlesWang
Mon Dec 13 11:29:03 CST 2004

Thanks Steve!

but the driver works fine in Windows CE 4.2, and in CE5.0, even I don't
include the display driver into image, still get the same errors.




"Steve Maillet (eMVP)" wrote:

> GWES.EXE is no longer built in the BSP as the NLED driver is pulled out of
> GWES in V5.0. The errors you are getting are usually associated with bugs in
> the display driver. Using the kernel debugger you can quickly identify the
> source of the problem.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
>

Re: GWES in Windows CE 5.0 by Steve

Steve
Mon Dec 13 11:44:18 CST 2004

what works in v4.x is not guaranteed to work in V5.x Use the kernel debugger
to see exactly where the error occurs. You might just have the registry set
up wrong or are not loading the correct driver etc...

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: GWES in Windows CE 5.0 by Umesh

Umesh
Tue Dec 14 02:23:03 CST 2004


hi,
i suppose 5.0 is backward compatible so whatever runs in 4.2 should run in
5.0 provided u have the right settings.We didnt face such problem but i think
u should be able to make gwes.exe as ur not using PQOAL.
could u send us ur gwes sources file..,may be ur missing path mapping ..did
u check the log file in ur gwes directory.
do u see gwes.lib in common or release directory?
hope it helps .
umesh jagga
"Steve Maillet (eMVP)" wrote:

> what works in v4.x is not guaranteed to work in V5.x Use the kernel debugger
> to see exactly where the error occurs. You might just have the registry set
> up wrong or are not loading the correct driver etc...
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
>

Re: GWES in Windows CE 5.0 by CharlesWang

CharlesWang
Thu Dec 16 11:15:05 CST 2004

Still got the similar message from Kernel Debugger.
not too much clue from the debuger message!

The sources file of my GWES like this:
=================================
!if "$(PLAT_NOGWES)"!="1"
RELEASETYPE=PLATFORM
EXEENTRY=WinMain
SYNCHRONIZE_DRAIN=1
TARGETNAME=gwes
TARGETTYPE=PROGRAM
TARGETLIBS=$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwes.lib \
!if exist($(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\$(LOCALE)\gwe_ui.res)
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\$(LOCALE)\gwe_ui.res \
!elseif exist($(_COMMONOAKROOT)\target\$(_CPUINDPATH)\$(LOCALE)\gwes.res)
$(_COMMONOAKROOT)\target\$(_CPUINDPATH)\$(LOCALE)\gwes.res \
!endif
!if "$(PLAT_NOBATTERY)" != "1" || "$(PLAT_NONLED)" != "1"
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_drv.lib \
!endif
!if exist($(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_ui.lib)
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_ui.lib \
!endif
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwestubs.lib \
$(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib

SOURCES=

TARGETFILES=dummy
=================================


Thanks



Re: GWES in Windows CE 5.0 by Umesh

Umesh
Mon Dec 20 19:43:02 CST 2004

dear charles.,
pls try this sources file settings:
!if "$(ODO_NOGWES)" == "1"
SKIPBUILD=1
!endif

RELEASETYPE=PLATFORM
EXEENTRY=WinMain
SYNCHRONIZE_DRAIN=1
TARGETNAME=gwes
TARGETTYPE=PROGRAM
TARGETLIBS=$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwes.lib \
!IF $(_WINCEOSVER) >= 400
!if exist($(_COMMONOAKROOT)\target\$(_CPUINDPATH)\0409\gwes.res)
$(_COMMONOAKROOT)\target\$(_CPUINDPATH)\0409\gwes.res \
!endif
!ELSE
!if exist($(_COMMONOAKROOT)\target\$(_CPUINDPATH)\usa\gwes.res)
$(_COMMONOAKROOT)\target\$(_CPUINDPATH)\usa\gwes.res \
!endif
!ENDIF
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\nleddrv.lib \
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwestubs.lib \
$(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib \
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\drvlib.lib

SOURCES=

TARGETFILES=dummy

regards
Umesh jagga


"Charles Wang" wrote:

> Still got the similar message from Kernel Debugger.
> not too much clue from the debuger message!
>
> The sources file of my GWES like this:
> =================================
> !if "$(PLAT_NOGWES)"!="1"
> RELEASETYPE=PLATFORM
> EXEENTRY=WinMain
> SYNCHRONIZE_DRAIN=1
> TARGETNAME=gwes
> TARGETTYPE=PROGRAM
> TARGETLIBS=$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwes.lib \
> !if exist($(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\$(LOCALE)\gwe_ui.res)
> $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\$(LOCALE)\gwe_ui.res \
> !elseif exist($(_COMMONOAKROOT)\target\$(_CPUINDPATH)\$(LOCALE)\gwes.res)
> $(_COMMONOAKROOT)\target\$(_CPUINDPATH)\$(LOCALE)\gwes.res \
> !endif
> !if "$(PLAT_NOBATTERY)" != "1" || "$(PLAT_NONLED)" != "1"
> $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_drv.lib \
> !endif
> !if exist($(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_ui.lib)
> $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\gwe_ui.lib \
> !endif
> $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\gwestubs.lib \
> $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib
>
> SOURCES=
>
> TARGETFILES=dummy
> =================================
>
>
> Thanks
>
>