My target device is started with "loadcepc /E:300:9: /V eboot.bin". I
can connect and download an image to the device. About the time the
Windows CE Desktop appears on the target, Platform Builder can no longer
communicate with the device. If I try to view Processes or Threads I
just get "Waiting to receive data". The remote file viewer and remote
registry editor also fail to connect. Strangely enough if I select
"Reset Device" under Target in Platform Builder, the device gets the
signal to reset!

I am using Platform Builder for Microsoft Windows CE 5.0, Evaluation
Edition. I've tried both release and debug builds for several different
platforms. I have tried both enabling and disabling Debugging under
connectivity options.

My target is a Tri-M MZ104 Board @ 100 Mhz with 32 MB Ram and a generic
non-pnp NE2000 network card. This target works with no problems running
Windows CE .NET 4.1.

Here are the last view lines I get from the serial port:

Download successful! Jumping to image at 002293D8h...
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
NAND_FLASH with g_bDownloadImage=1 , pBootArgs->ucLoaderFlags=7
Lauch Windows CE from address 0x2293D8
Debug Serial Init

SysInit: GDTBase=80e670e8 IDTBase=80eb8ec0 KData=80ed9800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 80edc000
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq
= 9, dwIoBase = 300, dwDfltType = 1) ...
InitKitlNIC: Can't find PCI Ethernet NIC, use specified data (type = 1,
IRQ=9, IOBase=0x300), use .
+EDBG:NE2000Init
EDBG:NE2000Init using I/O range at 0x00000300
EDBG:NE2000:HWRamTest: srambase: 0x00004000, sramsize: 0x00004000,
pstart: 0x46
Ne2kDbg:: HWSetMCRegs():: Set all to 0x00
-EDBG:NE2000Init
x86KitlCreateName: Using Device Name 'CEPC49428'
OALKitlCreateName: Using Device Name 'CEPC49428'
KITL: *** Device Name CEPC49428 ***
KITL: DHCP get/renew device IP: 192.168.101.106
VBridge:: built on [Aug 20 2004] time [14:55:02]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA0ECCCE0] to [0xA0ED0CE0].
Rx buffer [0xA0ED0D00] to [0xA0ED4D00].
VBridge:: NK add MAC: [0-1-45-0-C1-14]
KITL: Connected host IP: 192.168.101.145 Port: 1320
KITLGlobalState == 0x61
KITL: Leaving polling mode...
VBridge:: VB_INITIALIZED returns [1]
VBridge:: RESET_BUFFER received.
VBridge:: built on [Aug 20 2004] time [14:55:02]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA0ECCCE0] to [0xA0ED0CE0].
Rx buffer [0xA0ED0D00] to [0xA0ED4D00].
Ne2kDbg:: MulticastRegs set to : 0-0-0-0-0-0-0-0
NE2KDBG:: Set Ndis filter [0xB] -> [0xC]
VBridge:: Current VMini packet filter = [0xB]
Ne2kDbg:: MulticastRegs set to : 0-0-0-80-0-0-0-0


Here is the output from Platform Builder:

Warning: Debugger service map is set to none. If your image has
debugging support it may not boot properly.
Cannot access selected Device from service host.
The Kernel Debugger is waiting to connect with target.
Debugger could not initialize connection.
The Kernel Debugger has been disconnected successfully.
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 X86Init done, OEMAddressTable = 802293f8.
69 PID:e1fcae6e TID:e1fcae3e OEMIoControl: Unsupported Code
0x101008c - device 0x0101 func 35
3296 PID:e1fcae6e TID:e1fcae3e OEMIoControl: Unsupported Code
0x10100d0 - device 0x0101 func 52
3299 PID:e1fcae6e TID:e1fcae3e OEMIoControl: Unsupported Code
0x10100f8 - device 0x0101 func 62
5803 PID:1f9fb16 TID:1fa8d56 DeviceFolder::LoadDevice!Enumerate
Found deprecated load instructions at (Drivers\BuiltIn\AFD). Driver
cannot be unloaded.
7036 PID:1f9fb16 TID:1fa8d56 DeviceFolder::LoadDevice!Enumerate
Found deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloaded.
7459 PID:1f9fb16 TID:1fa8d56 PCIbus!PCIEnum: WARNING: Resource
request for device 0:0:0 failed
13948 PID:c1e93c86 TID:c1fa8f92 ERROR:
C:\apps\ce\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\KEYBD\PS2_8042\.\ps2port.cpp
line 253:
13951 PID:c1e93c86 TID:c1fa8f92 Ps2Port::OutputBufPollRead: too long
waiting for output buffer full.
14015 PID:c1e93c86 TID:c1fa8f92 Lyg.p: Layout Manager successfully
initialized to 1


Regards,
George McCollister
NovaTech LLC

RE: PB Can't Communicate With Device After EBOOT in CE 5.0 by tleitao

tleitao
Mon Aug 30 16:31:32 CDT 2004

Hi George,

This looks like the case where KITL on the device and desktop has
successfully connected but target shell (shell.exe) is either not started
or hung on the device. Please double check that SYSGEN_SHELL=1 is set and
shell.exe is running. If debugger can connect, you can break into the
debugger and see which processes are running.

Thanks,

Toni

TLeitao (AT) microsoft.com