Re: WinCE boot up

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Dear Lu,

Thanks for replying.
I figured out the problem. Actually I was using the wrong BSP.
But certainly I would like to know how to see the debug messages in case on
availability of the Serial and Ethernet port.

Warm Regards
Sanjeev
"Luc Cool" <luc__cool@xxxxxxxxxxx> wrote in message
news:me8gh.235977$Do3.5148812@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Debug messages are output without intervention from the CE drivers. In the
case of serial debug output, the messages are simply sent to the TXD
register of a uart, one byte at a time (X86 platform). The Uart sends out
the character in it's uart, after which the next is put in. Everything has
been kept as simple as possible to keep the debug message flow going, even
if the OS bootup stalls.
In wince 4.2, it was possible to sent the debug output to the screen as
well. In that case, you will have to leave the CE video driver out of it,
as
the characters are directly pushed into the video memory. This method only
works if the video adapter is set to a character mode. If it is switched
to
a graphical mode, either by the bootloader or by the CE video driver, you
won't see your debug output anymore.
I have also once done a project where I dumped the debug output to the Ide
device connected to the secundary ide controller. I had to disable the CE
driver for that device to avoid conflicts. It also was tricky since it
assumed that a file filled with spaces was already present on the device,
on
a fixed place, simply because I was a bit to lazy to decode the fat file
system structure on the disk. I could move my disk after a bootup to my
develop pc and analyse the debug output.

Maybe someone else on this group knows a better solution. I am interested
to
read one as well.

regards,

Luc


"Sanjeev Tiwari" <sanjeevtiwari@xxxxxxxxxxx> wrote in message
news:OyVQcMzHHHA.4216@xxxxxxxxxxxxxxxxxxxxxxx
Dear Bruce

Thanks for your reply, I went through the postings, and I found that we
need
the serial port debug messages to analyze the issue as there could be
many
points which cause the problem.
The hardware which I have does not have the serial port, or lets say it
does
not have the serial port exposed as it is a web-pad.
Is there any other way I can see the debug messages
The also does not have any Ethernet port.

The only port available is USB port.

Warm Regards
Sanjeev

"Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:O$9qyqrHHHA.1468@xxxxxxxxxxxxxxxxxxxxxxx
A search in this newsgroup for "Jumping to" will find many users who
have
experience the same problem and suggestions for fixing it.




http://groups.google.com/groups?as_q=Jumping+to&num=10&scoring=r&hl=en&as_ep


q=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uaut


hors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=13&as_m
axm=12&as_maxy=2006&safe=off

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Sanjeev Tiwari" <sanjeevtiwari@xxxxxxxxxxx> wrote in message
news:%23IbaB5qHHHA.4804@xxxxxxxxxxxxxxxxxxxxxxx
I have built a WinCE 5.0 image for AMD Geode Processor.

I am using LoadCEPC to load the image. The Loading of image
completes
100%
but after that I can see only

"Jumping to 0x00229368" message. the image does not boot beyond this
point.

What could be the problem?

Thanks in advance
Sanjeev










.

Relevant Pages