I need to download a WinCE (3.0 as well as 5.0) x86 image over ethernet. The
download with eboot, started with loadcepc, works with normal speed. I can
see at the serial line output, that the device has been connected from
EShell. In the EShell window I see only one line of text:
RTC - Status Reg B - 0x02
but dont get the normal welcome message.
To verify, that there is no problem in my BSP, I built a MinKern as well as
a MinComm platform for the CEPC. I got the same result. I attached a network
sniffer for the dedicated network connection and was able to monitor the
traffic. The CEPC sends the BOOTME message, and the EShell downloads the
image with TFTP. Then it sends the ADMIN command JUMPING, that is ack'd by
the device. The device send SVCCONFIG requests, that are responsed with
correspondent replies. The device sends a DBGMSG line, that is ack'd by the
EShell. After that, both exchange PPSH messages with a rather low frequency
(compared with the download).
One surprise was, that the EShell sends in the JUMPING all three ports:
DBGMSG, PPSH as well as KDBG. Since the WinCE image is not kernel debugger
enabled and EShell has not the kernel debugger functionality, I dont see the
need for KDBG port.
The other surprise was, that the Platformbuilder works well aftern I have
downloaded an image with kernel debugger enabled. So I dont argue an problem
with the network or IRQ problems at the CEPC. But the PlatformBuilder has
the same problem, when I download an image w/o kernel debugger enabled.
I have googled the newsgroups, but found only that I was not the first with
problem in this stage, but no real hint how to continue. Is there a general
problem with eboot download of a not kernel debugger enabled platform?
Any advise is welcome.
Regards, Helge