Re: PB 5.0: Image only boots 99%

Hi,

The error codes you get come from the biosloader; and not from the actual
windows ce image.

If you are a ce beginner, I would recommend to use the loadcepc.exe program
as bootloader for your image. It is based on dos and easier to go along
with. Once you got that running, you can switch to the biosloader, so you
don't need to pay for a dos license.

however, to answer your questions,

eboot.bix is the compressed version of eboot.bin. Since you load nk.bin in
your platform, it is normal you can delete it without any changes.

splash .bmx is the compressed version of splash.bmp, the file that makes the
CE background during booting.

the sources of the biosloader can be found in the
wince500\public\common\oak\csp\x86\biosloader\loader map. The debug.h file
contains the defines of the ERROR, WARNING and INFO codes. you can than
search the C files to see where they are generated.

regards,

Luc


"GT" <GT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:52E0A614-CFAB-46A7-B96A-F7C2034DFF8A@xxxxxxxxxxxxxxxx
Thank you for your answer Luc. Now please consider the "Industrial
Controller" template as an example.

I've built two debug versions and two release versions using the
"Industrial
Controller" template in PB 5.0. One debug and one release buid using the
x86
BSD and one debug and one release build using the AMD Geode x86 BSD.

I've then prepared the flash-card on the Advantech PCM-5823 using
mkdisk.exe, and copied the files from bootdisk.144 along with the binary
image (nk.bin) onto the flash-card (and of course altered the boot.ini to
boot from nk.bin). The flash-card contains the following files:
*BLDR
*Boot.ini
*eboot.bix
*nk.bin
*splash.bmx

When booting the debug version (on target) with the AMD Geode x86 image
the
following can be seen in Hyper Terminal using the serial port:
"Microsoft Windows CE BIOS Bootloader Version 2.2 (Built Mar 13 2004)
INFO: code=0x4.
INFO: code=0x4.
INFO: code=0x4.
WARNING: code=0x20.
Jumping to image (address=0x0)"
The the screen goes black and nothing happens.

When booting the debug version (on target) with the x86 image exactly the
same happens.

And when booting the release version (on target) with the AMD Geode x86
image exactly the same happens as well.

However When booting the release version (on target) with the x86 image
the
following can be seen in Hyper Terminal using the serial port:
"Microsoft Windows CE BIOS Bootloader Version 2.2 (Built Mar 13 2004)
INFO: code=0x4.
INFO: code=0x4.
INFO: code=0x4.
ERROR: code=0xB.
INFO: code=0x37.
WARNING: code=0x7.
ERROR: code=0x8."
This time the screen is not black. The Windows CE logo is shown with the
PROGRESS BAR below. The progress bar is only 2% filled up and then
everything
freezes.

One thing that I have also noted is that removing "eboot.bix" makes no
difference, and removing "splach.bmx" makes the Windows CE logo
dissappear,
but the progress bar still shows.


Now, why more debug information is displayed using the release build than
the debug build beats me, but what I'd really like to know is how to
procede
from here.

For instance, Where do I find out what "ERROR: code=0xB" means?

"Luc Cool" wrote:

Hi,

the way you describe it, you are using the bios bootloader to start your
image. I have no expierence yet with that one.

Considering your questions:

1. No, the Enable Eboot Space is not responsable for that.
2. The progress bar is probably a feature of the bios bootloader,
equivalent
to the progress bar of loadcepc I talked about before. loadcepc.exe is
not
included in the ce os image, as it is a 16 bit dos application used to
load
a image into memory and start it.
3. I have no answer to that, the information we have here is
insufficient.
4. In my opinion (but who am I), the simpliest method to see your debug
output is connecting a null modem cable between com1 of your target
platform
and a com port of your development platform. If tx, rx and gnd are
connected
to the rx, tx and gnd of the other site, the cable should work. No
handshake
wires are needed.
On your development pc, you should start hyperterminal, to see the debug
info that comes from your ce output.
Even release builds of CE generate debug output, but far less than debug
builds.
Try loadcepc.exe, but use nk.bin as argument instead of eboot.bin or
sboot.bin, eventually with the drive and folder info before it. like:
loadcepc.exe c:\nk.bin
You can add some parameters to choose the video resolution, and the com
port
used for debug output, but the info for that can be found in several
help
files. The flat vga driver uses 320x240 as default resolution and the os
uses com1 as debug port if none is specified.

This will directly transfer the wince os to the ram of your platform,
and
start it up. The serial debug port uses a baudrate of 38400 baud.

Also make sure you have a image with ram based registry and ram /rom
file
system. The hive based one has a more complex startup procedure, and, in
case of problems, has a bigger chance to abort it's normal boot
sequence. (I
didn't found this myself, I read it on this newsgroup. Sorry if i
violate
someones copyright by rewriting this, but I can only say I agree 100%
with
this.)

hope this helps.

regards,

luc


"GT" <GT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5968AB2B-29A1-49FA-BDEB-08EFF39057FC@xxxxxxxxxxxxxxxx
Yes there is a progress bar. Now let me give you some more details:

I'm trying to build a bootable Win CE 5.0 image for the Advantech
PCM-5823.
I've tried using a number of the predefined templates in Platform
Builder
5.0 (Industrial Controller, Internet Appliance etc), but without any
success.
In Platform-> Settings -> Build Options I have typically selected the
following
*Enable CE Target Control Support
*Enable Eboot Space in Memory
*Enable Full Kernel Mode
*Enable KITL

Further I have buit the template images (and some customized ones)
using
the
exact same settings for the x86 BSP and AMD GEODE x86 BSP (selected in
the
New Platform Wizard).
The result is as follows:
At bootup on target the screen is black and nothing happens using the
AMD
GEODE x86 images, whereas using the x86 images the Windows CE logo and
the
progress bar is displayed as previously explained.

Now I wonder
1) Is the reason for the displayed progress bar that "Enable Eboot
Space
in
Memory" is selected?
2)Is the progress bar showing because loadcepc.exe is somehow included
in
the nk.bin? (I'm booting from the flash card following the procedures
descred
on MSDN: "How to Boot a Run-Time Image on a CEPC from a Hard Disk
Drive").
3) Why is nothing happening when using the AMD GEODE x86 BSP which is
supposed to be custom made for the Advantech PCM-5823?

And last but not least:
4) How should I procede to do "a debug build to see what is going on"?
I'd really like to know, but I've not been able to find anything in
the
documentation about this.
I should also mention that (like so many others) I'm not able to make
the
CEPC boot with loadcepc.exe using the supplied CEPCBoot.144 floppy
disk.
I've
tried numerous of different options for the eboot (just about
everything
that is commented in the discussion groups, and in the online MSDN
documentation ), but with no luck. Neither is the serial boot working,
no
matter the selected baud rate etc. The CEPC never shows up under
Target ->
Connectivity Options. So yes, I'm very very interested in knowing how
to
do
"a debug build to see what is going on".

Looking forward for your answer.

"Luc Cool" wrote:

Hi,

you are probably talking about the progress bar loadcepc.exe puts on
the
screen when it loads a image. After loading, it should jump to the
entry
point of the image (either eboot.bin, sboot.bin or nk.bin) Maybe the
progress indicator doesn't reach the 100% due to some rounding
error's.
You
didn't mention which platform you are using, and what kind of image
you
are
trying to load..

regards,

Luc

"GT" <GT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6986E9A6-73FF-40C5-A99A-1325646A3790@xxxxxxxxxxxxxxxx
Sorry, I mean progress bar.

"Dean Ramsier" wrote:

Performance bar??? There is no such thing in the standard CE
release.
Have
you tried doing a debug build to see what is going on?
--
Dean Ramsier - eMVP
BSQUARE Corporation


"GT" <GT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5E911553-C102-4F70-9A3E-3B44A8504B5F@xxxxxxxxxxxxxxxx
Hello

I've made an image (or several to be perfectly honest) wiht PB
5.0
that
only
boots 99% and then stops completely. At bootup (on target) the
Windows
logo
and "Windows CE" is displayed with a performance bar below.
The
performace
bar fills up 99% and then everything freezes.

I have not been able to find from the documentation what is
actually
happening as the performance bar is filling up. Does anyone
know
where
to
find this information and a probable cause to my problem?

I've tried altering Platform->Settings-> Build Options a
number of
times.
And when I remove KITL, the image does not boot at all
(Windows
logo
and
performance bar are not displayed).












.

Relevant Pages

  • Re: PB 5.0: Image only boots 99%
    ... the Enable Eboot Space is not responsable for that. ... The progress bar is probably a feature of the bios bootloader, ... On your development pc, you should start hyperterminal, to see the debug ... *Enable CE Target Control Support ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PB 5.0: Image only boots 99%
    ... I've built two debug versions and two release versions using the "Industrial ... BSD and one debug and one release build using the AMD Geode x86 BSD. ... When booting the debug version (on target) with the AMD Geode x86 image the ... The progress bar is only 2% filled up and then everything ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Need Help in Debugging StandAlone WInCE 6.0 App using PB/VS 20
    ... Virtual Miniport Driver, VMINI, in the OS. ... Builder to also appear as a network adapter to the Windows CE OS. ... I've spent the past 3 days trying to get VS 2005 to allow me to debug ... I have solid connectivity with my target via KITL debugging, ...
    (microsoft.public.windowsce.app.development)
  • Re: usbmsfn on wince 5.0
    ... Can you attach your device running a Windows CE debug build to that ... If you can enable debug zones I think you may get some useful ... That does not mean that you can rule-out a problem inside its USB ... based devices to their Mac using a USB connection (there is a ...
    (microsoft.public.windowsce.platbuilder)
  • Re: C# app works perfectly on XP but not on 2003 server
    ... My program uses Windows Sockets ... >> when you say you put a debug code in, ... that whenever I put any debug code in the code ... >>>that generates the exception, the exception does not come again, but another ...
    (microsoft.public.dotnet.framework.windowsforms)