Re: [ECOS] RedBoot porting

[Andrew Lunn <andrew dot lunn at ascom dot ch>]

> Andrew> What would be nice is being able to tell the app, don't jump
> Andrew> into ROM for a while, i need exclusive access to the FLASH.
> 
> Interesting - presumably you cannot disable interrupts for the
> duration of the flash update process?

Nope, it can take a number of seconds to write the image. 

> One way this could be accomplished is by providing a function (in RAM
> application) that saves the virtual vector table, fills it with
> pointers to NOP functions (in RAM) which count usage.  

Another simpler option is to make the ROM copy itself into RAM and run
from there. Some of the HALs already support this for apps, but has it
been tested for redboot? It also means you can then overwrite the
redboot image in FLASH while its running the copy in RAM. With the app
and the boot loader becoming closer tied together its becoming more
important to be able to upgrade the bootloader in the field as well as
the application.

        Andrew