Re: Image Binary Format by Dean
Dean
Mon Apr 09 08:25:07 CDT 2007
Several things...
One, I don't think you have a guarantee that the records are presented in
order. The might be, but I think it is no guarantee. You're better off
looking at the romimage output that shows you the unfilled holes.
Two, you have to understand the needs of the system. Code and read only
sections of XIP modules are uncompressed and stored at page boundaries.
That will create holes for every section that does not completely fill the
4K page. Any unfilled areas are holes in memory and are filled in where
possible with filler sections (data sections, data files etc). A hole will
still remain if there is no available data section small enough to fit into
it.
So the bigger your image, the more code and readonly sections you have, the
more holes that will exist in the image. How many of those get filled in
depends on how many data sections there are and whether they fit into the
available holes.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Jacky Ko" <JackyKo@discussions.microsoft.com> wrote in message
news:1CCC4E29-203D-44A1-A358-A54A489B4109@microsoft.com...
>I don't know how to explain the image holes in .bin or RAMIMAGE Please
>check
> out this record example
>
> Image Start = 0x00220000, length = 0x00B52D90
> Record [ 0] : Start = 0x00220000, Length = 0x00000010, Chksum =
> 0x00000829
> Record [ 1] : Start = 0x00220040, Length = 0x00000008, Chksum =
> 0x00000314
> Record [ 2] : Start = 0x00221000, Length = 0x0003EFFC, Chksum =
> 0x019B93D5
> Record [ 3] : Start = 0x00261000, Length = 0x000003A0, Chksum =
> 0x00014AD3
>
>
> There are many unused spaces in RAM.
> For example, 0x220020~ 0x220040
> 0x220048~0x221000
> Why do we leave these spaces?
>
> --
> Jacky Ko
> Microsoft MVP for Windows Embedded
> www.advantech.com
> Advantech Co., Ltd
>