Re: Bootloader Placement
- From: Hans-Bernhard Broeker <broeker@xxxxxxxxxxxxxxxxxxxxx>
- Date: 19 Apr 2006 11:53:29 GMT
Tom Lucas <news@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
What I'd like to do is seperate the bootloader code from the
application code and have the boot loader pass control to the
application once it has done its checks and, if necessary,
reprogramming. However, I don't think I could have the application
as stand-alone code as well because it would then be re-initialising
the hardware and memory of what was initialised previously in the
bootloader.
As has been said, re-initialization shouldn't usually be problematic
--- at worst, it'll just be a small waste of time on startup. If in
your case the hardware really can't be initialized more than once, I
think you should consider splitting up your mental image of the job
into *three* parts: a bootloader, a flash-updater, and the main
application. The bootloader would treat both of the others as
optional. I.e. if they're present, they're executed. This requires
some management (how to test whether the code is present, how to avoid
memory space collisions between flasher and main app...). This would
allow to keep all initializations that can't be re-done in the
bootloader.
--
Hans-Bernhard Broeker (broeker@xxxxxxxxxxxxxxxxxxxxx)
Even if all the snow were burnt, ashes would remain.
.
- Follow-Ups:
- Re: Bootloader Placement
- From: Tom Lucas
- Re: Bootloader Placement
- References:
- Bootloader Placement
- From: Tom Lucas
- Bootloader Placement
- Prev by Date: Re: FM0 (bi-phase space) decoding!
- Next by Date: Re: Bootloader Placement
- Previous by thread: Re: Bootloader Placement
- Next by thread: Re: Bootloader Placement
- Index(es):
Relevant Pages
|
