Re: WinCE 5.0 Problems at BootUp x86 HDD
- From: "Remi de Gravelaine" <gravelaine at aton dash sys dot fr>
- Date: Mon, 5 Mar 2007 10:25:22 +0100
Hi,
Your Bootloader obviously has support for Ethernet booloading ("Microsoft
Windows CE Ethernet Bootloader 3.5 for CE/PC (Jun 22 2004)".)
Despite the 'InitKitlNIC' reference, KITL is not used at this stage:
'InitKitlNIC' should be understood as 'Initialize the Network Interface
Controller that KITL will use, if present'. Also, don't confuse the
Bootloader code with your NK.BIN code: if you disable KITL in your image
(NK.BIN), it will not affect the Ethernet Bootloader code in any way.
Your problem is a hardware one:
EDBG:NE2000Init using I/O range at 0x0000E800
EDBG:NE2000:HWRamTest fail. srambase = 0x00010000, ramEnd = 0x00000000
EDBG:NE2000Init:HWInit HWRamTest failed
The code that manages your NE2000 controller (ne2kdbg.lib, look at
C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\ETHDBG\NE2000) is not able to access
the internal RAM of your NIC and you should fix that before going further.
HTH
Remi
.
- References:
- WinCE 5.0 Problems at BootUp x86 HDD
- From: Carnage
- WinCE 5.0 Problems at BootUp x86 HDD
- Prev by Date: Re: PmUpdatePowerStatus & battery driver
- Next by Date: Re: CreateDialog error 0x57
- Previous by thread: Re: WinCE 5.0 Problems at BootUp x86 HDD
- Next by thread: Re: Wince 5.0 Daylight Savings (DST) ISSUE
- Index(es):
Relevant Pages
|