Re: removing the 4K jump in eboot start up code?
- From: "mobilevil" <kccheng@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jun 2005 23:29:17 +0800
well then I have no choice but to use non-ms tool for msys booting then...?
"Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:um2fkIzdFHA.2688@xxxxxxxxxxxxxxxxxxxxxxx
> Cannot be done directly at this time. I've been annoyed by this for a long
> time but until recently I was the only one. It has been submitted to MS so
> hopefully a future release will give us that capability. One possibility
> to get around the problem is to write an application that reads the
> generated image (.NB0 or with more work the BIN) and updates it to include
> the ARM exception vectors. If you put Startup as the beginning of your
> image and follow that with the exception vectors you can find the startup
> from the branch statement the tools put at the start of the image. From
> that you can then get the information for the exception vectors etc.. and
> build up the 4K image area based on that to include the vectors (which are
> usually just a branch instruction)
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
.
- Follow-Ups:
- Re: removing the 4K jump in eboot start up code?
- From: Wang Yeqing
- Re: removing the 4K jump in eboot start up code?
- References:
- removing the 4K jump in eboot start up code?
- From: mobilevil
- Re: removing the 4K jump in eboot start up code?
- From: Steve Maillet \(eMVP\)
- removing the 4K jump in eboot start up code?
- Prev by Date: Re: removing Unfilled ROM holes
- Next by Date: Re: MFC Application in O/S Image
- Previous by thread: Re: removing the 4K jump in eboot start up code?
- Next by thread: Re: removing the 4K jump in eboot start up code?
- Index(es):
Relevant Pages
|
|