Re: Fast Start-up

Fast I/O or no I/O for loading the OS. If RAM access on your hardware is
very fast, copying the OS from flash or where ever you have it stored might
result in faster boot than executing directly in flash (you'll have to
test). If you're going to be copying the image from some storage device
(like a hard disk), to RAM, you want that device to be as fast as possible
and your code to configure and operate it (yes, it's in the bootloader; you
have to write it), needs to be as optimized as possible. If you're copying
from persistent storage to RAM, make the OS image as small as possible.

If you're executing directly out of flash, make sure that your processor
settings for the flash region are as optimized as you can make them without
sacrificing reliability.

Faster processors generally boot faster.

Again, though, without a specification that everyone in your team is willing
to commit to as far as how long the battery has to last, there's a
reasonable chance that you're wasting time. Suspend works very well on a
lot of the hardware that CE runs on and buying a bigger battery is a lot
cheaper than spending 6 months hacking 0.5 seconds off of your cold boot
time...

Paul T.

"Steady" <Steady@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FAD4E635-E550-4D70-8B88-215DD21D89DA@xxxxxxxxxxxxxxxx
Thanks,

I will check with the device vendor.

What do you recomend to improve the boot speed?

"Paul G. Tobey [eMVP]" wrote:

You need to be or know well the device vendor to know what is possible
with
respect to power management. Trying to do something good without knowing
is
likely to be a big waste of time. Pocket PC devices, even phones, which
are
essentially never off, have battery lives measured in days with
relatively
small batteries. You need to decide on a specification for how long the
device is going to live; that will guide you when you decide what happens
when you "hibernate".

You can improve boot speed, but it's still going to be seconds, not
milliseconds.

Paul T.

"Steady" <Steady@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9D069B17-4EB0-444C-B55F-DEED83E013A2@xxxxxxxxxxxxxxxx
I need to be very careful with the power consumption, and therfore need
to
power down the processor and peripherals. So I'm guessing I need to
either
use a power down and re-boot or some kind of hibernate? In addittion I
have
had some previous bad experiences with things such as bluetooth drivers
restarting, and thought a full boot might be safer option.

I have access to platform builder and have made small changes before. I
have
read somewhere that faster full boot times should be possible.

"Paul G. Tobey [eMVP]" wrote:

You haven't told us anything that would help us there. The "shutdown"
could
mean anything. It might be suspended, like what a Pocket PC does
after a
few minutes. When you press the power button, it's back on very
quickly,
as
the RAM was maintained, etc. and the processor simply has to be
started
up
where it stopped. It might literally be off, though, in which case,
you're
doing a full boot of Windows CE and 7 seconds is fantastic. If this
is
not
a device that you build, there's nothing you can do from an
application
program to change the power-down states provided by the device.

Paul T.

"Steady" <Steady@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5357105-DA57-4581-B423-F887F4BFDA93@xxxxxxxxxxxxxxxx
I'm a releative newbie on wince so sorry if this is obvious.

I have a low power mobile application which requires the O/S to
shutdown
and
then a later time restart quickly. Does anyone have any suggestions
on
how
I
can improve my start-up time (typically about 7 seconds at the
moment).

Thanks.








.