Kernal Debug enabled cannot boot up CEPC

I am using PB5.0. I am able to boot up CEPC when only KITL enabled with
ethernet, but failed when kernal debug enabled. My lan card is RIL8139. The
PB debug message and serial port message are attached below.
/////PB message////////////////////////////////////////////
0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 g_dwCPUFeatures = 0383f9ff
0 PID:0 TID:0 g_nMtrrCnt = 8
0 PID:0 TID:0 MTRR PhysMask0: 0000000fe0000800
0 PID:0 TID:0 MTRR PhysBase0: 0000000000000006
0 PID:0 TID:0 MTRR PhysMask1: 0000000ffe000800
0 PID:0 TID:0 MTRR PhysBase1: 000000001e000000
0 PID:0 TID:0 MTRR PhysMask2: 0000000000000000
0 PID:0 TID:0 MTRR PhysBase2: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask3: 0000000000000000
0 PID:0 TID:0 MTRR PhysBase3: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask4: 0000000000000000
0 PID:0 TID:0 MTRR PhysBase4: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask5: 0000000ffc000800
0 PID:0 TID:0 MTRR PhysBase5: 00000000e8000001
0 PID:0 TID:0 MTRR PhysMask6: 0000000000000000
0 PID:0 TID:0 MTRR PhysBase6: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask7: 0000000000000000
0 PID:0 TID:0 MTRR PhysBase7: 0000000000000000
0 PID:0 TID:0 PhysMask0: 0000000fe0000800
0 PID:0 TID:0 PhysMask1: 0000000ffe000800
0 PID:0 TID:0 PhysMask2: 0000000000000000
0 PID:0 TID:0 PhysMask3: 0000000000000000
0 PID:0 TID:0 PhysMask4: 0000000000000000
0 PID:0 TID:0 PhysMask5: 0000000000000000
0 PID:0 TID:0 PhysMask6: 0000000000000000
0 PID:0 TID:0 PhysMask7: 0000000000000000
0 PID:0 TID:0 g_nMtrrInuse = 2
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
0 PID:0 TID:0 &pTOC = 802279d8, pTOC = 81093be8, pTOC->ulRamFree =
81124000, MemForPT = 00004000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 11956, Secondary pages: 0,
Filesystem pages = 5978
0 PID:0 TID:0
Booting kernel with clean memory configuration:
0 PID:0 TID:0 Memory Sections:
0 PID:0 TID:0 [0] : start: 81129000, extension: 00003000, length:
02eb4000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023dc78.
0 PID:0 TID:0 Windows CE KernelInit
4294767297 PID:3fdf002 TID:3fdf1de Updated eptr->e32_vsize to = 00090000
4294767297 PID:3fdf002 TID:3fdf1de Scheduling the first thread.
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: KernelInit2:
pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit =
80260d90
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00005000
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00022000
4294767299 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00007000
4294767300 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00018000
4294767300 PID:3fdf002 TID:3fdf1de 0x83fdf030: Starting kernel debugger
software probe (KdStub) - KD API version 18
4294767300 PID:3fdf002 TID:3fdf1de 0x83fdf030: Calling KDEnableInt (FALSE,
NULL) without previously calling KDEnableInt (FALSE, p)
4294767309 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module NK.EXE at
address 0x80220000-0x802B0000 (RW data at 0x81096000-0x811041FF)

///////serial port message///////////////
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 5, dwIoBase = D000,
dwDfltType = 4) ...

InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=5, IOBase=0xD000).

RTL8139InitDMABuffer():: Start[0x810EC040]-[0x810EC040] - Size[0x10000]

Tx[0x810EC040] - Rx[0x810ED840] - RxLength[0x8000] - RxLengthBit[0x1000]

RTL8139:: built on [Jun 24 2004] [18:37:40]

RTL8139Init():: BaseIO[0xD000] : MemOffset[0xD000]

RTL8139Init():: TxBuff[0x810EC040] - RxBuff[0x810ED840] - LastRx[0x810F583F]

RTL8139Init:: MAC = 00-13-49-0C-6B-A9

RTL8139 ethdbg library: perform auto negotiate.

RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00

x86KitlCreateName: Using Device Name 'CEPC27561'
OALKitlCreateName: Using Device Name 'CEPC27561'
KITL: *** Device Name CEPC27561 ***
KITL: DHCP get/renew device IP: 10.19.10.127
VBridge:: built on [Jun 24 2004] time [18:37:41]

VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes

Tx buffer [0xA10FC1E0] to [0xA11001E0].

Rx buffer [0xA1100200] to [0xA1104200].

VBridge:: NK add MAC: [0-13-49-C-6B-A9]

KITL: Connected host IP: 10.19.10.174 Port: 3601
KeyIndex 0 = -1
KeyIndex 1 = -1
KeyIndex 2 = -1
KeyIndex 3 = -1
KeyIndex 4 = -1
KeyIndex 5 = -4194305
KeyIndex 6 = -4194305
KeyIndex 7 = -1
+KITLRegisterDfltClient, service:0
+KITLRegisterDfltClient, service:1
KITLGlobalState == 0x61
Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service PPSH
ProcessAdminMsg: Receive Config message for service DBGMSG
+KITLRegisterDfltClient, service:2
Waiting for service 'KDBG' to connect..., fUseSysCalls = 0

Steve
Thu Jul 28 10:01:26 CDT 2005

Well., that's not failing to boot. It's booting, starting the kernel
debugger and waiting for you to connect the debugger on the desktop side.
Once you start that in PB and it connects the boot will continue. In other
words, a Kernel debugger enabled build REQUIRES a connection to the desktop
portion of the debugging and it will wait forever until it gets it.

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

JayC
Thu Jul 28 20:37:44 CDT 2005

How do I establish that connection? I was thinking PB will take care of that
if I select debugger as KdStub in kernel service settings.
Is there any button or command I need to execute once it is waiting to
connect the debugger?

Thanks,
JayC

"Steve Maillet (eMVP)" wrote:

> Well., that's not failing to boot. It's booting, starting the kernel
> debugger and waiting for you to connect the debugger on the desktop side.
> Once you start that in PB and it connects the boot will continue. In other
> words, a Kernel debugger enabled build REQUIRES a connection to the desktop
> portion of the debugging and it will wait forever until it gets it.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
>

Steve
Thu Jul 28 21:25:24 CDT 2005

You need to start that from the IDE, typically done with the attach menu
item or toolbar button. It's possible the target communication settings are
disabling the debugger messages or more likely that a firewall or network
setting problem is getting in the way. (The IDE will look up the address it
is supposed to use based on the first network card in the network order. If
that's not the same network the device is connected to then it won't be able
to communicate)
--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com