[En-Nut-Discussion] Fwd: RE: Reprogramming

Thiago A. Corrêa thiago.correa at gmail.com
Mon Jan 25 17:07:30 CET 2010


On Mon, Jan 25, 2010 at 1:32 PM, Allister G. Mannion
<Allister at amannion.com> wrote:
> Hi Ole,
> I have a similar requirement (might be the same as Peter's) where I want
> to keep the eboot code as part of my 'firmware'. At the moment I load
> (flash) it as a standalone, then flash my code (without the erase cycle)
> which always gets executed first. The reason I want the 'eboot' code
> there is so I can jump to it to tftp a new version of my firmware.

>From what I understand, you can already just jump to eboot, even if
they are not one single binary.

But if I'm missing the point, then the AVR32 DFU bootloader might be
of some inspiration to this I guess.

>From what I understand, they build it seperately, and then link with
the application where their assembly CRT does a .include
"boootloader.bin". This way, the entiere bootloader is placed in front
of the app. There is also a trampoline code (a jump) to the app area
when the bootloader is not supposed to run, so it starts the app and a
little link script trick defining an program_start symbol.

Might be worth taking a look.

Kind Regards,
    Thiago A Correa

More information about the En-Nut-Discussion mailing list