Re: removing Unfilled ROM holes
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Wed, 22 Jun 2005 12:00:26 -0400
Don't build the IPL with MS tools, is one option...
--
Dean Ramsier - eMVP
Vibren Technologies
http://www.vibren.com/Products/schema_bsp.htm
"mobilevil" <kccheng@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Ogbw57zdFHA.2420@xxxxxxxxxxxxxxxxxxxxxxx
> well but it is eboot... I have to devide eboot into 2, and the first half
of
> it fit in the xip region of nand flash. which is 2K in size.
> it's 27x, btw
> right now i am putting boot reason, memory, mmu init, copy code to sdram
and
> continue, into the first half.
> the second half is the C code, which contain ethernet stuff.
>
> anyway targeting code 2K in size, and my code around 10K now, still
trimming
> code. but the memory hole is 8K!?! no matter how hard I do, the 8K hole
and
> the 4K jump will kill the 2K xip region anyway!
>
> I am still contacting msys's fae, his sample code for another arm based
> platform is exactly 2K and don't have the 4K jump. I wonder why...
> "Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:u9DHJVzdFHA.2548@xxxxxxxxxxxxxxxxxxxxxxx
> > 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
> >
> >
>
>
.
- References:
- removing Unfilled ROM holes
- From: mobilevil
- Re: removing Unfilled ROM holes
- From: Dean Ramsier
- Re: removing Unfilled ROM holes
- From: Ten
- Re: removing Unfilled ROM holes
- From: Steve Maillet \(eMVP\)
- Re: removing Unfilled ROM holes
- From: mobilevil
- removing Unfilled ROM holes
- Prev by Date: Re: MFC Application in O/S Image
- Next by Date: Re: USB Mass Storage not recognized if already inserted at Startup
- Previous by thread: Re: removing Unfilled ROM holes
- Next by thread: Re: removing Unfilled ROM holes
- Index(es):
Relevant Pages
|
|