A
Fri May 28 10:55:01 CDT 2004
yes,yesy,yes, and don't know.
Another thing to watch out for, sometimes the size of the image is stored
persistantly in the
bootloader. This size is extracted when the .bin file is parsed via Ethernet
download.
If you are updating via Storage Card app this size location needs to be
updated also as it
is used by the bootloader to figure out how much memory to move from flash
to ram (assuming
we are executing from ram).
"Fabio - ElettronicaGF" <fmelandri@elettronicagf.it> wrote in message
news:3ad3b9c6.0405280022.2b62ccc8@posting.google.com...
> Hello A.User,
>
> Thank you for your quick reply.
> Excuse me but I'm rather newbie in WinCE so I have some more questions.
>
> Did you do theese steps?
> Map (with memorymap file function) the original .bin OS image file
> Parse it and extract data
> Program Flash record-by-record
>
> What library or functions did you use for program flash?
> Is bootpart library good for this work?
>
> During update I would like disable any other user operation and system
activity
> How can I reach it?
>
> Thanks a lot!
>
> FabioMelandri
> ElettronicaGF
>
>
> "A.User" <a_user@home.com> wrote in message
news:<OEeUr4CREHA.2468@tk2msftngp13.phx.gbl>...
> > I just finished writing exactly this application.
> > I used the CompactFramework altho its not necesssary (I just wanted a
cool
> > GUI)
> > Parsing the .bin file is not that bad ... look at the bootloader code.
> > Its nice if you have enough RAM to totally store a whole new image (may
be
> > upto 32M??)
> > I used the memorymap file function to overcome the application partition
> > size limit.
> > otherwise you have to "chunk it" not that cool if you lose power etc.
> >