Re: removing Unfilled ROM holes
- From: "Steve Maillet \(eMVP\)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jun 2005 10:18:26 -0400
Executable code needs to be aligned on specific boundaries so the ROMIMAGE
tool aligns them properly, but that can often leave holes in the memory used
if the code doesn't match the exact size of the alignment. So, ROMIMAGE and
the ROM filesystem will fill in those holes with data from data files as
best it can. So the presence of holes is not something that you can change
and you can't do anything about how the tools fill them either. At best you
can combine Dlls together and link code statically instead of using a DLL to
change how it fits in memory reducing the sizes of the holes.
--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com
.
- Follow-Ups:
- Re: removing Unfilled ROM holes
- From: mobilevil
- Re: removing Unfilled ROM holes
- References:
- removing Unfilled ROM holes
- From: mobilevil
- Re: removing Unfilled ROM holes
- From: Dean Ramsier
- Re: removing Unfilled ROM holes
- From: Ten
- removing Unfilled ROM holes
- Prev by Date: Re: Can I directly put files into ResidentFlash in platform.bib ?
- Next by Date: RE: MFC Application in O/S Image
- Previous by thread: Re: removing Unfilled ROM holes
- Next by thread: Re: removing Unfilled ROM holes
- Index(es):
Relevant Pages
|
|