I uncheck "Enable Kernel Debugger" (IMGNODEBUGGER=1) in Build Options,
and then run Sysgen. But after downloading the image, I still see "The
kernel Debugger is waiting to connect with target.".
Why is that? I use CEPC off the bat. By the way, KITL is enabled, and
it does not work either. From the serial output, it says,
"ERROR:OALKitlInit:KitlInit failed". I use RTL8139 for both
downloading and KITL by disabling VMINI. The whole project used to
works on CE .Net 4.2. Any help is appreciated.

AH

Re: kernel debugger and CE 5.0 by Karel

Karel
Wed Mar 02 00:13:52 CST 2005

There are two flags IMGNOKITL and IMGNODEBUGGER. Second only disable
debugger to be loaded on Windows CE start. KITL connection should still be
active (and depending on your sysgen settings it will bring you shell and
debugger output). I can't say why KITL initialization failed (put full
serial output in message, to give us context). If you build IMGNOKITL
image - message you see is normal (yes, it can be little confusing). If you
want to run standalone image you can set debug option in connections to none
to avoid this.

I think your primary problem is that you don't specify correctly KITL
device. Can you post full serial debug output?


--

Karel Danihelka
---
Windows CE CoreOS
This posting is provided "AS IS" with no warranties, and confers no rights.
---

<ah0@hotmail.com> wrote in message
news:1109704741.756357.126690@g14g2000cwa.googlegroups.com...
>I uncheck "Enable Kernel Debugger" (IMGNODEBUGGER=1) in Build Options,
> and then run Sysgen. But after downloading the image, I still see "The
> kernel Debugger is waiting to connect with target.".
> Why is that? I use CEPC off the bat. By the way, KITL is enabled, and
> it does not work either. From the serial output, it says,
> "ERROR:OALKitlInit:KitlInit failed". I use RTL8139 for both
> downloading and KITL by disabling VMINI. The whole project used to
> works on CE .Net 4.2. Any help is appreciated.
>
> AH
>



Re: kernel debugger and CE 5.0 by ah0

ah0
Wed Mar 02 12:41:48 CST 2005

Karel,

Thanks for your help. The below is from the serial port:

...
Download BIN file information:
-----------------------------------------------------
[0]: Base Address=0x220000 Length=0xF6AE50


****** OEMVerifyMemory Checking Range [ 0x220000 ==> 0x118AE4F ]
****** RAM Address ******


rom_offset=0x80000000.
Found pTOC signature.
ROMHDR at Address 00220044h
RomHdr.ulRAMStart=8118B000h RomHdr.physfirst=80220000h.
OEMLaunch ucLoaderFlags is 7
Download successful! Jumping to image at 00229348h...
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
NAND_FLASH with g_bDownloadImage=1 , pBootArgs->ucLoaderFlags=7
Lauch Windows CE from address 0x229348
Debug Serial Init


SysInit: GDTBase=8118b0e8 IDTBase=811dcec0 KData=811fd800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 81219000
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = B, dwI
oBase = D800, dwDfltType = 4) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0xD800).
RTL8139InitDMABuffer():: Start[0x811E0B40]-[0x811E0B40] - Size[0x10000]

Tx[0x811E0B40] - Rx[0x811E2340] - RxLength[0x8000] -
RxLengthBit[0x1000]
RTL8139:: built on [Feb 16 2005] [19:50:49]
RTL8139Init():: BaseIO[0xD800] : MemOffset[0xD800]
RTL8139Init():: TxBuff[0x811E0B40] - RxBuff[0x811E2340] -
LastRx[0x811EA33F]
RTL8139Init:: MAC = 00-40-F4-49-71-63
RTL8139 ethdbg library: perform auto negotiate.
RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
x86KitlCreateName: Using Device Name 'CEPC29027'
OALKitlCreateName: Using Device Name 'CEPC29027'
KITL: *** Device Name CEPC29027 ***
VBridge:: built on [Feb 16 2005] time [19:50:53]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA11F0CE0] to [0xA11F4CE0].
Rx buffer [0xA11F4D00] to [0xA11F8D00].
VBridge:: NK add MAC: [0-40-F4-49-71-63]
ERROR: OALKitlInit: KitlInit failed
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80229368.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!Enumerate Found deprecated load
instructions at (Drivers\BuiltIn\PPP). Driver cannot be unloaded.
...


The bringup was halted at "KITL: *** Device Name CEPC29027 ***" for
quite a while, and then finally WinCE was up.

AH


Re: kernel debugger and CE 5.0 by Karel

Karel
Thu Mar 03 00:10:26 CST 2005

Ok it looks familiar. There is problem with DHCP server on your network (I
expect you are running on network with DHCP server). Can you check network
trace - to see if there is DHCP renew request and there is correct replay
from server?

We find that some DHCP servers from security reasons require optional device
name in DHCP request.


--

Karel Danihelka
---
Windows CE CoreOS
This posting is provided "AS IS" with no warranties, and confers no rights.
---
<ah0@hotmail.com> wrote in message
news:1109788908.432631.140660@l41g2000cwc.googlegroups.com...
> Karel,
>
> Thanks for your help. The below is from the serial port:
>
> ...
> Download BIN file information:
> -----------------------------------------------------
> [0]: Base Address=0x220000 Length=0xF6AE50
>
>
> ****** OEMVerifyMemory Checking Range [ 0x220000 ==> 0x118AE4F ]
> ****** RAM Address ******
>
>
> rom_offset=0x80000000.
> Found pTOC signature.
> ROMHDR at Address 00220044h
> RomHdr.ulRAMStart=8118B000h RomHdr.physfirst=80220000h.
> OEMLaunch ucLoaderFlags is 7
> Download successful! Jumping to image at 00229348h...
> Got EDBG_CMD_JUMPIMG
> Got EDBG_CMD_CONFIG, flags:0x00000000
> NAND_FLASH with g_bDownloadImage=1 , pBootArgs->ucLoaderFlags=7
> Lauch Windows CE from address 0x229348
> Debug Serial Init
>
>
> SysInit: GDTBase=8118b0e8 IDTBase=811dcec0 KData=811fd800
> Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
> g_pPageDir = 81219000
> InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = B, dwI
> oBase = D800, dwDfltType = 4) ...
> InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0xD800).
> RTL8139InitDMABuffer():: Start[0x811E0B40]-[0x811E0B40] - Size[0x10000]
>
> Tx[0x811E0B40] - Rx[0x811E2340] - RxLength[0x8000] -
> RxLengthBit[0x1000]
> RTL8139:: built on [Feb 16 2005] [19:50:49]
> RTL8139Init():: BaseIO[0xD800] : MemOffset[0xD800]
> RTL8139Init():: TxBuff[0x811E0B40] - RxBuff[0x811E2340] -
> LastRx[0x811EA33F]
> RTL8139Init:: MAC = 00-40-F4-49-71-63
> RTL8139 ethdbg library: perform auto negotiate.
> RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
> x86KitlCreateName: Using Device Name 'CEPC29027'
> OALKitlCreateName: Using Device Name 'CEPC29027'
> KITL: *** Device Name CEPC29027 ***
> VBridge:: built on [Feb 16 2005] time [19:50:53]
> VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> Tx buffer [0xA11F0CE0] to [0xA11F4CE0].
> Rx buffer [0xA11F4D00] to [0xA11F8D00].
> VBridge:: NK add MAC: [0-40-F4-49-71-63]
> ERROR: OALKitlInit: KitlInit failed
> RTC - Status Reg B - 0x02
> X86Init done, OEMAddressTable = 80229368.
> OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> at (Driver
> s\BuiltIn\AFD). Driver cannot be unloaded.
> DeviceFolder::LoadDevice!Enumerate Found deprecated load
> instructions at (Drivers\BuiltIn\PPP). Driver cannot be unloaded.
> ...
>
>
> The bringup was halted at "KITL: *** Device Name CEPC29027 ***" for
> quite a while, and then finally WinCE was up.
>
> AH
>



Re: kernel debugger and CE 5.0 by ah0

ah0
Thu Mar 03 17:31:20 CST 2005

After I use a static ip, KITL works. But how come CE .Net 4.2 works
with our DHCP server?

AH


Re: kernel debugger and CE 5.0 by Steve

Steve
Thu Mar 03 17:48:03 CST 2005

What DHCP server are you using? We've found that some servers make hardcoded
assumptions about the order of the options in the DHCP requests and the CE
DHCP client doesn't always put them in the order that the server assumes.
While CE is a bit unusual in this respect it's not in violation of the
specs. The server is.